Massive queue buildup

[Brent Addis]

you can't guarantee that non suspicious (however urgent) email won't be listed in an rbl or have an invalid HELO at all times.
 
Copied from another list as well:
 
One important thing to watch for is that for larger sites the server that
first tries to send your email might not be the one that tries to resend
it later. Greylisting sites will thus block the email for a while until
the sending site gets lucky and uses the same machine twice in a row.

Generating tempfail messages to sending sites is just asking for
trouble IMHO. You really can't determine exactly they will act and how
long they will take to retry to send the message. Any delay is 100%
your fault although most people using greylisting seem keen to push the
blame to the sending site.

It's the equivalent of ignoring someone when they first email/call you and
saying "If it's important they'll ring back" . Not very polite and
possibly not providing the best service to customers.

________________________________

From: mailscanner-bounces at lists.mailscanner.info on behalf of Ken A
Sent: Tue 11/14/2006 1:05 PM
To: MailScanner discussion
Subject: Re: Massive queue buildup





Brent Addis wrote:
> greylisting is bad and I will never ever run it. I know of one case where greylisting has very nearly killed someone.

Oh, come on.. tell us how!! lol


They probably shouldn't have been using email to do what they were, but
thats not the point.
> 
> greylisting adds an unnecessary delay to email, and can quite easilly be beaten if a spammer sets his mind to it.

There's no reason for it to delay legit mail. Just configure to delay
suspicious mail, based on rbl lookup or helo or whatever..

Ken A.
Pacific.Net


>
> ________________________________
>
> From: mailscanner-bounces at lists.mailscanner.info on behalf of Damian Mendoza
> Sent: Tue 11/14/2006 12:45 PM
> To: MailScanner discussion
> Subject: RE: Massive queue buildup
>
>
>
> Run a DNS server locally, add more memory/CPU, use Greylisting, process mail using sender address verification before SA at the postfix or sendmail level and use RBLs at the postfix or sendmail level.
>
> 
>
> That should get your server load down to 2.0 or lower to keep up with your traffic.
>
> 
>
> 
>
> Regards,
>
>
> Damian Mendoza
>
> Mission Viejo, CA
>
> 949 586-2200
>
> 
>
> 
>
> ________________________________
>
> From: mailscanner-bounces at lists.mailscanner.info [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Jay Chandler
> Sent: Monday, November 13, 2006 2:32 PM
> To: mailscanner at lists.mailscanner.info
> Subject: Massive queue buildup
>
> 
>
> Built my first Mailscanner / Postfix box on Friday due to a Sendmail meltdown last week-- was forced to throw this box into production early.
>
> 
>
> It ran fine over the weekend, but today there's a massive queue buildup when I run an mqueue-- 10K so far and building.
>
> 
>
> Any idea where to look to sort out where it's coming from?
>
> 
>
> It's possible the box itself is overloaded, 2 2.4 ghz procs, with a load average of around 13.
>
> 
>
> Any guidance would be greatly appreciated.
>
> 
>
>
--
MailScanner mailing list
mailscanner at lists.mailscanner.info
http://lists.mailscanner.info/mailman/listinfo/mailscanner

Before posting, read http://wiki.mailscanner.info/posting

Support MailScanner development - buy the book off the website!


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 6850 bytes
Desc: not available
Url : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20061114/f62ade16/attachment.bin