On Sun 02 Mar 2014 at 10:06:17 +0100, Ralf Mardorf wrote:
> PS: I'll set up msmtp ASAP and then replace Evolutions SMTP thingy, to
> see if I get information about the issue.
Probably this will be a waste of time; you would be better off examining
the headers of your mails received from the list. For the one I'm
replying to:
Received: from [92.224.209.210] (g224209210.adsl.alicedsl.de [92.224.209.210])
(authenticated bits=0) by mail36c50.megamailservers.eu
(8.13.6/8.13.1) with ESMTP id
s2296FOR018536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA
bits=128 verify=NO) for <[email protected]>; Sun, 2
Mar 2014 09:06:17 +0000
alicedsl sends to mail36c50.megamailservers.eu at 09:06:17 +0000.
Received: from mail36c50.megamailservers.eu (mail226c50.megamailservers.eu
[91.136.10.236]) by bendel.debian.org (Postfix) with ESMTP id
0A883117 for
<[email protected]>; Sun, 2 Mar 2014 09:06:19 +0000 (UTC)
Two seconds later mail36c50.megamailservers.eu sends to bendel.debian.org.
No problem here.
Received: from bendel.debian.org ([127.0.0.1]) by localhost (lists.debian.org
[127.0.0.1]) (amavisd-new, port 2525) with ESMTP id iJSMII8IViEh
for
<[email protected]>; Sun, 2 Mar 2014 09:06:20 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by bendel.debian.org
(Postfix) with ESMTP id E2546ED for
<[email protected]>;
Sun, 2 Mar 2014 09:06:22 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by bendel.debian.org
(Postfix) with QMQP id 7F80C475; Sun, 2 Mar 2014 09:06:31 +0000
(UTC)
bendel is now ready to send the mail to the subscriber - 12 minutes after
first receiving it. (Other mails may show a 15/16 minute delay).
Altering the delay is not within your control.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: https://lists.debian.org/[email protected]
