|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Joey (Joey
Web56.net)
Date: Fri May 09 2008 - 09:27:02 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> -----Original Message-----
> From: Wietse Venema [mailto:wietse
porcupine.org]
> Sent: Friday, May 09, 2008 9:24 AM
> To: Joey
> Cc: postfix-users
postfix.org
> Subject: Re: mailq lockups
>
> Joey:
> > What legit business with exception of a big isp would have that many
> > mailservers.
> > Somehow there is something related to spam which is causing the lockup.
>
> Stop speculating, start doing real measurements.
>
> Send mail to the exchange box that pretends to come from such a domain.
>
> $ sendmail -f user
suspect-domain recipient... < inputfile
>
> where inputfile contains some text.
>
> And so on.
>
> Wietse
This was a good test, if I use the sender domain of the messages I am saying
are spam because they are the messages that lock up in the queue and remain
there:
sendmail -f colvdiyfq
naturalfoodchain.com testaccount
clientserver.net <
testfile
This times out sending to the exchange server.
If I take the same exact entry but put my domain as the sender like so:
sendmail -f colvdiyfq
mydomainname.com testaccount
clientserver.net <
testfile
It works perfectly with NO hung connections on either side.
I tried this with 2 different domains that were from messages that were
locked up in the queue on the postfix side with the same results.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]