On 12/23/2010 2:08 PM, Ray wrote:
On December 23, 2010 10:48:07 am Noel Jones wrote:
On 12/23/2010 11:33 AM, Ray wrote:
I believe that the message is being accepted by Postfix due to lines like
the following in the logs
Dec 23 10:12:20 wserver amavis[15273]: (15273-12) Passed CLEAN,
[70.65.***.***] [70.65.***.***]<r...@stilltech.net> ->
<******...@shaw.ca>, Message-ID:<201012231011.54704....@stilltech.net>,
mail_id: MS2XU3vqlzc0, Hits: 0.013, size: 557, queued_as: 6CF0C1B173C,
14673 ms
(redacted IP address is the machine I'm sending email from. Redacted
email is on the local cabelco mail server.)
Wow, nearly 15 seconds to scan a 557 byte message. If all
your amavis scans are that slow or slower you might want some
help from the amavis-users list.
Anyway, on the postfix-users list we prefer to see postfix
logging.
I'm not 100% sure the problem is on the remote server, that's why I would
like to trace the communication between my server and the remote server.
Thanks again,
Ray
Start with showing us the one-line entry postfix/smtp makes
when sending to the remote server, and we'll go on from there.
-- Noel Jones
Hello all,
thank you for your quick response. All the gory details that you asked for
follow. I have provided the output of postconf -n, and all the log details for
my last message to this list as an example.
The only thing I asked for is the one-line postfix/smtp log
entry when postfix attempts delivery to the remote server
you're having trouble with. I don't see that anywhere.
After we see that, we'll tell you if we need anything else.
My question is " is there a way to
see in detail, through logging or simulation, what is happening when my mail
server relays or attempts to relay, a message from me to an outside server
that is not under my control, and for which I will never get logs.
Postfix verbose logs will show in painful detail what postfix
does. This is rarely necessary and often masks the real
problem in a flood of unrelated information.
http://www.postfix.org/DEBUG_README.html#debug_peer
A TCP sniffer such as wireshark or tcpdump will show details
of the conversation. This is rarely necessary and often
distracts from the real problem.
http://www.postfix.org/DEBUG_README.html#sniffer
-- Noel Jones
