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.

Dear Support...I'm testing the SF now, and installed it on a separate servers.I redirected the MX0 to the SF server, and the SF will forward to my mail server.Its working fine for incoming emails. scanning and blocking SPAM.Now... i need to use it for outgoing messages. I added the server IP to the white-list, and SF start receiving the messages.The problem is that the SF is forwarding messages back to my mail server :)Emails are doing loops between SF server and my mail server.Any suggestions to solve this problem?ThanksOAWWAD

Do you guyz use Bayes? I use spamassassin and have often struggled with how to train bayes engine since there is no per user spamassassin settings and if you have a lot of diverse users it can vary greatly.

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.

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

Hmmm. I like that last line. I use spamassassin w/bayes and have struggeled with different schemes to automatically feed the bayes spam/ham folders each day for update that occurs at midnight each night. I also not happy with he performance of SA on a windows system. Might have to look into message sniffer since I don't really have time to mess with the Bayes part of SA anymore. I first heard of message sniffer 6 years ago when I was using Imail. I guess if they've been around this long they will be around a little longer ;-)

It will not be able to run any IP checks as all IPs are trusted internal IPs.You will be able to do keyword checks, etc.It the outgoing scanner is used internally then you can add a * in allowed domains.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot delete your posts in this forumYou cannot edit your posts in this forumYou cannot create polls in this forumYou cannot vote in polls in this forum