SpamFilter is mainly designed to process incoming emails, which are then forwarded to your destination SMTP server(s) holding the actual mailboxes. To use SpamFilter as an "outgoing SMTP server", and relay emails out to the internet, there are a couple of options available.

1. You can add the IP addresses/networks of the users who wish to use SpamFilter as their "Outgoing SMTP Server" to the IP address whitelist in SpamFilter. Only IPs that have been whitelisted will be able to send emails out to the internet.

or...

2. SpamFilter supports SMTP Authentication. Users can be authenticated using either Active Directory, LDAP, or Unix-style password files. SSL support is also available. Any user that authenticates successfully is able to use SpamFilter to relay emails to the internet (and thus use it as their Outgoing SMTP server).

Please note that in all cases, SpamFilter will always forward emails to your destination SMTP server for delivery, even though these emails will be sent to external domains. For security reasons, to avoid becoming an open relay, SpamFilter will never emails directly to the internet.

If an IP is in the IP whitelist, it will *always* be able to relay and send emails thru SpamFilter. The only time an email will be blocked is if you've installed the optional anti-virus plugin, and the email contains a virus. In this case, virus-infected emails will always be stopped (but I doubt this is the case here).

Are you 100% sure that the "557" unable to relay error is generated by SpamFilter and not by your destination SMTP server...?

It is to note that, again, as we mentioned earlier, SpamFilter will forward all emails to your destination SMTP server for delivery. If the source of the emails is the server "mail.domainname.dk", and this server is the same one in SpamFilter's "Destination Server", you will need to be careful in avoiding mail loops, as every email SpamFilter receives will be forwarded back to mail.domainname.dk for the actual delivery.

How much you want for the license? Is it still available. Replay to omar@sama.jo

Hello oawwad,

It is complicated, you have to pass many hoops and must design the infrastructure accordingly.
Ours look like this and works more-or-less with a few helpers.

http://www.worldsoft-postmaster.info/

good luck

Hassan,

Can you answer this one. I have no clue how SA is setup?

thanks

Attif / Hassan
do you have much maintenance work on your SA?
I have a similar setup to yours (great network layout BTW), but we use message sniffer. although it costs a bit (only 50 bucks a month), we've found that the combination Spamfilter, then message sniffer, gives us near 0 rate spam.
I have no affiliation to message sniffer!
we have 0 effort on maintaining it. it updates automatically every 1 hour.

Amir

Amir,

hi,

We do not do a lot of maintenance on SA.
We handle most of our cases with blacklisted/whitelisted keywords  (which are the same for incoming/outgoing) served by a  NAS

One of them is what SA puts in the Subject "SA-Next-Action: Quarantine".

So basically we are not doing much on SA level and all network tests are disabled.


All of server (except the ones running Spamfilter) are running linux so adding another couple of beasts running mail sniffer is not really an option of us.








Edited by atifghaffar - 02 March 2009 at 7:32pm

Hi,

We use SA for outgoing mail (most for redirection mails). As Mr Ghaffar explain, we don't do a lot of maintenance. For time to time we update the rules "sa-update -D". Our SA is coupled with razor.

Regards,

Dear Atif,

I'm using the SF for incoming mail, and it works fine.
I also want to install  another SF to scan outgoing mail

Here is the setup i have in mind.
http://www.sama.jo/images/mail_setup.jpg

do you think this will work?
do i have to add my domains to local-list?
i think if i do that, it will allow all mail to go out, and will not block spam.

regards
OAWWAD