On Samstag, 24. September 2005 19:26 Herb Martin wrote: > SA threshold exceeded will cause a non-greylisted message > to be sent through the greylist process. This can happen > at most once per message (even when resent) but normally > happens on only a small percentages since everything that > was otherwise suspicious got greylisted initially.
That sounds interesting. > Also, for us SpamAssass in is TOO LATE in the chain > 95% of the time. We've already greylisted most things > by the time SA runs (and thus avoid the expense of SA > processing if the mail is not from a reasonably > functional SMTP server.) I'm not sure I understood you. You do - reject on some hard criteria - check RBLs, SA assign scores - if some SA hit, greylist Is SA before or after greylist? mfg zmi -- // Michael Monnerie, Ing.BSc --- it-management Michael Monnerie // http://zmi.at Tel: 0660/4156531 Linux 2.6.11 // PGP Key: "lynx -source http://zmi.at/zmi2.asc | gpg --import" // Fingerprint: EB93 ED8A 1DCD BB6C F952 F7F4 3911 B933 7054 5879 // Keyserver: www.keyserver.net Key-ID: 0x70545879
pgpwLgNYrEmgY.pgp
Description: PGP signature
