d...@acbsco.com wrote:
Jim,
Not sure, but you could try to empty the contents of your
/var/qmail/control/blacklists file and then reload the qmail control
files. (make a backup of your blacklists file of course)
# /etc/init.d/qmail reload
In the past, I have read about delays, and one of the rbl's was having
to timeout before the email would be sent and/or received. Yes, it
seems odd that the rbl's would be checked on outgoing email, but by
default that is exactly what happens.
Anyway, it is an easy quick test.
Dave
Jim Bassett wrote:
That makes sense. I can't find anything though. Here's a couple more
points as a last try to see if anyone can think of anything:
I was wrong about the outgoing mail being delivered immediately even
though the client would hang. The mails are not delivered until the
client finally shows a completed send - usually around 3 minutes per
email (client show quick progress right up to completion, but then
hangs at the very end.)
If I telnet to port 25, do an auth login, and send mail from the
command line the same thing happens. The smtp server is completely
responsive up through where I say 'DATA' and type in the body of the
message. But then when I type /n/r./n/r to end the DATA absolutely
nothing happens for several minutes until it finally replies with
'250 ok'. (Is there any way to make the smtp server more verbose here?)
This same delay happens from multiple clients, multiple locations,
multiple email accounts. It happens whether the recipient is on the
same domain (same server) or on a remote server. But webmail can send
without delay in any situation.
Reverse DNS and resolving DNS are correct and trouble free.
That webmail can send but remote clients cannot seems like the key.
What is different in the sending process between these two? Are there
checks / scans that are done for remote clients that wouldn't be done
for someone logged into webmail?
I'd be curious to see why it does not happen in webmail myself, unless
you changed Squirrelmail from port 25 to 587.
You can turn on recordio (instructions in the wiki or in the archives)
and get a really verbose log that way. Does it happen if the user
switches to port 25 instead of 587?
You can also set the "-t n" option in your run file for the rblsmtpd
command. -t n (n being a number) will tell it to give up on a RBL lookup
after seconds (default is 60 seconds - and this is 60 seconds per
blacklist checked). For example:
RBLSMTPD="/usr/bin/rblsmtpd -t 10"
would tell rblsmtpd to check each blacklist, but to give up after 10
seconds if it does not answer.
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
