> 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.
Heh... this is just one of the problems... then there are spambots which, instead of going to the first MX usually try the "last" one to attempt getting through the filters ... and then some other issues; see, the only real solution would be having ASSP on all the MX servers and setting up the various copies of ASSP to replicate data amongst them (using a database is the best approach) see, the problem in your case is that your secondary MS isn't under your control, so you can't setup its filtering as you like so you'll either have to "live with that" or you'll have to setup another ASSP box, possibly on a separate connection, to act as your secondary MX server ------------------------------------------------------------------------------ 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
