Re: greylisting, exim-4.34 status
Marc MERLIN <[email protected]>
| Newsgroups | gmane.mail.exim.spamassassin |
|---|---|
| Message-ID | <[email protected]> |
On Tue, May 18, 2004 at 01:32:33AM +0100, Paul Makepeace wrote:
> Je 2004-05-15 19:22:57 +0100, Marc MERLIN skribis:
> > Yeah, things will work fine.
> > 1) most mail will go through just fine
> > 2) greylisted mail that is spam will go to your secondary MX, unless it was
> > already sent there to start with
> > 3) secondary MX will also greylist sender
> > 4) if sender resends a 2nd or 3rd time depending on above, the mail will
> > be accepted
> > 5) ...
> > 6) profit (*)
> >
> > Mmmh, actually not quite, I should build a greylist hack so that if
> > /var/spool/sa-exim/tuplets/12/174/92/all
> > or
> > /var/spool/sa-exim/tuplets/12/174/92/all/all
> > exit, then the mail is whitelisted automatically
>
> Does SAEximRunCond not enable you to bypass SA when taking connections
> from your MXen? (I have for example, {!eq
> {$sender_host_address}{217.207.14.60}}in the 'and' condition.)
Sorry, my fever was making me say stupid things. Yes, of course, you
shouldn't run SA when receiving mail from your secondary MXes, which solves
the greylisting problem too.
> So SAEximRunCond could solve exactly this, working as a whitelist for
> the greylisting?
Right
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger [email protected] for PGP key