But again, since almost no legitimate email is ever
greylisted only almost nothing DESIRABLE EVER gets
delayed.
So you ONLY greylist what the RBLs tell you is on their list? Maybe I need
to go back and re-read your original email, which I skimmed perhaps too
lightly... because even back in
--- email builder [EMAIL PROTECTED] wrote:
But again, since almost no legitimate email is ever
greylisted only almost nothing DESIRABLE EVER gets
delayed.
So you ONLY greylist what the RBLs tell you is on their list? Maybe I need
to go back and re-read your original email, which I
-Original Message-
From: email builder [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 27, 2005 1:54 AM
To: users@spamassassin.apache.org
Subject: RE: best of RBLs without the FPs
--- email builder [EMAIL PROTECTED] wrote:
But again, since almost no legitimate email is ever
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
From: Rob McEwen [mailto:[EMAIL PROTECTED]
In fact, a good example of positive solutions would be Herb
Martin's recent post about using Greylisting and RBLs
together where the message is not blocked outright based on
RBLs... but, rather, the RBL triggers the greylisting... that
was a
On Samstag, 24. September 2005 17:48 Herb Martin wrote:
But again, since almost no legitimate email is ever
greylisted only almost nothing DESIRABLE EVER gets
delayed.
That depends on your setup. Here, we basically use:
- checks on HELO, SPF, RBL, etc - 550 reject
- checks on SA - accept but
From: Michael Monnerie [mailto:[EMAIL PROTECTED]
On Samstag, 24. September 2005 17:48 Herb Martin wrote:
But again, since almost no legitimate email is ever greylisted only
almost nothing DESIRABLE EVER gets delayed.
That depends on your setup. Here, we basically use:
- checks on HELO,
Herb asked:
What makes you uncomfortable? There really are only
two issues:
1) Delay of legitimage email
2) Broken legitimate servers that won't resend
Herb,
Many web page event-driven e-mails may not have a re-try mechanism. And I
think that some legit opt-in lists and newsletters also might
Michael Monnerie said:
But as for Rob's way of doing things: Again this involves manual
whitelists. It would be nice if there were automated things, as manual
stuff tends to be error prone, outdated and not updated :-(
Interestingly, just this evening, a legit message sent to my server was
Herb asked:
What makes you uncomfortable? There really are only two issues:
1) Delay of legitimate email
2) Broken legitimate servers that won't resend
Herb,
Many web page event-driven e-mails may not have a re-try
mechanism. And I think that some legit opt-in lists and
newsletters
But I have solved this problem forevermore by placing the
following override in my DNS server:
// American Express ;
zone 34.32.193.list.dsbl.org in { type master; notify no;
file master/null.zone; }; zone
34.32.193.sbl-xbl.spamhaus.org in { type master; notify no;
file
On Sep 24, 2005, at 2:41 PM, Rob McEwen wrote:
Herb asked:
What makes you uncomfortable? There really are only
two issues:
1) Delay of legitimage email
2) Broken legitimate servers that won't resend
Herb,
Many web page event-driven e-mails may not have a re-try mechanism.
Those web
12 matches
Mail list logo
