-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/17/2007 09:35 AM, robgeo730 wrote: > Hello I'm a new user, I have used the search function but wasn't able to find > a situation like mine. > > I am fighting an uphill battle against a crappy hosting company that I can't > change from. We have our mail filtered via a Barracuda device (which is > working really well) that is on our MX, it then routes good email to the > SMTP server. The problem is that the SMTP server needs to be accessible for > our users to relay mail through it. Spammers are just doing port scans, > finding our SMTP server and sending spam directly to it bypassing the > Barracuda on the MX. The SMTP server has Spamassassin 2.63 on it (hosting > company wants to charge $200 to put 3.x on it and we can't upgrade it > ourselves) > > > 1. Would any legitimate email be sent directly to our IP or is it just > spammers who bypass the MX to send spam? I think it would just be spammers > as bypassing the MX is probably a violation of the SMTP RFC. > > 2. Since Spamassassin is on our SMTP server can a rule be created to only > allow email to be delivered to the users if it comes from the Barracuda MX? > This is with the assumption that email bypassing the MX has to be spam. > > Keep in mind that I don't have full access to the server. I can put a rule > in place and then I need to request the hosting company to restart the > spamd. > > I appreciate any input > > Thanks,
Wny not require SMTP authentication unless mail comes from your MX? You'd have to walk your users through enabled SMTP authentication, but that's just a one-time headache. - -- Steve -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFHPy7ReERILVgMyvARAkhUAJ9mEPGbC7c1zRRGhYzkpIfzVjkkJgCfdD/+ 6Z9GLh1RIYaXraEC8sbv9UU= =XBhH -----END PGP SIGNATURE-----
