-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 07.11.2013 10:32, schrieb Steffen Kaiser:
On Thu, 7 Nov 2013, Jan Phillip Greimann wrote:
That's even the only one with lmtp-debug-messages, now all log entries look like that:
is this some sort of LMTP ahead to probe the recipient? Greylisting perhaps with local recipients? Does " decided action=PREPEND X-policyd-weight: using cached result;" mean that no action has been performed, but the negative result cached already will be returned. Do you have a corresponding lmtp log entry?
I've enabled dovecots debug-log after the problems happened, so there are no corresponding lmtp logs.
To test LMTP try this:
telnet to your LMTP port, or for an Unix socket:
socat - UNIX:/var/run/dovecot/lmtp
Then speak LMTP:
LHLO loc mail from:bounce-mc.us5_9954939.11045-jg+introversion=larptreff.de@mail33.wdc03.rsgsv.net
rcpt to:jg+introversion@larptreff.de quit
and without the +detail in rcpt to. If you get to enter the QUIT without losing you connection, your postfix log entry does not makes sense to me. 2xx responses are successful, 4xx temporary error, 5xx errors. You should not see no other resonse codes.
Okay, the log entries make no sense at all it seems. With socat it works like charm.
See the Dovecot log and probably monitor the system for an abort or segfault of a Dovecot LMTP process.
As far as I see there are no segfaults. Postfix and dovecot are logging to syslog --> mail.log, and there is only the given output.
Regards Jan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJSe2LAAAoJENEKhqzzuxPllZUH/jm3eCAPMhnmGShj1V0qwZnA YbmrEfLBjqm8Yh3KMhmyzZLDF6wkv4JEFJJGpeHlfQ1yRuHb7QZ0/z0hVceQCkOp JSv7+o9QWurRMbQmcu/CzL5JFz2p9SLN4vRReAgXWmavCazwzgnzeoDzf705rajy 2rMlwwLn0VGVAykFP0IHTLL+ldWaCCur0A98mHe3lKeK9OOGbBrrdDoW+VSMQVUi x60vBHmcoN0L3EKXYyVC1G2BMPXNC/RiT4ElAjJCNA7M0kKyPtU5ZVsiiEUFYWm1 btrizND9+8bMI/T1axjw5Jv94HqKC6KIJMXprwipuXWUeA68snUIDy17wFqEa1U= =E8P3 -----END PGP SIGNATURE-----