On 18 Dec 2009 at 8:54, Greybear wrote: > Hi all, > > I have a setup that contains an exchange 2003, an ASSP box in front of it > and a secondary mailserver at our ISP. > All the secondary MX does is forward all email to the ASSP box. we need this > to handle downtimes (maintenance mainly) > > ASSP has greylisting turned on (ASSP version: 1.5.1.5)
(Slightly aged version) > The problem is the following: > An unknown user sends and email - it gets greylisted. the normal behaviour > of the sneder smtp is to try with the secondary MX - out ISP. The email is > accepted by the ISP and gets relayed to the ASSP box - to early for > greylisting and it's filtered out by assp. Any connection that will fall back to a secondary mx after trying the primary isn't going to be stopped by greylisting. Just ensure you don't block the secondary and you should be OK - tackling the junk by other means. (You could set up a third mx pointing to your primary - that way you get the bots that go for the highest mx while still giving genuine mtas a backup.) paul ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
