I use Imail 9.02 with Declude as a primary mail machine, and a front end for a Lyris listserv machine.

With Declude / Sniffer/ etc I have had very good luck with Spam & Virus interception.

However, we are now getting tons of bogus spam to our secondary Lyris listserv machine which Imail acts as a front end.

Since most of the spam is sent / to a bogus address, the mail gets accepted by Imail as the primary MX and then of course fails in the SMTP transfer to the secondary machine. Mail to the iMail machine directly fails at a 550 SMTP session.

This was generating tons of bounced mails from [EMAIL PROTECTED] attempting to be delivered to either the bogus address, or legtimate address that did NOT originate the spam. Started noticing Spam warnings from AOL, and other services.

The only thing I have figured I can do is blocking the postmaster failed delivery attempts back to null, but this doesn't help the legtimate email that might be misaddressed.

Since there are thousands of addresses on the Lyris machine that could be valid, I can't set up an alias on the Imail machine, so it would be rejected at the 550 SMTP level there.

Any other thoughts on how to handle this?

And has anyone thought on why we have to spend hours and hours and $$ $ to do nothing but protect our machines / users from spammers but the internet community and regulators have really done nothing but be reactive to this problem? I've run servers on the net for 15+ years, and lately 90+% of our traffic is spam related ... just a waste of resources and bandwidth. For a small operation like myself, I'm frustrated that nothing is being done to solve this problem on a global scale, and the internet is collapsing under its own weight because of it <sigh>

David
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/

Reply via email to