I've been getting over the last months several of these notices. Sometimes
a few per day. What's the problem? Can't this be avoided?
This is the mail system at host mail.centos.org.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to <postmaster>
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<centos at centos.org>: mail forwarding loop for centos at centos.org
Final-Recipient: rfc822; centos at centos.org
Original-Recipient: rfc822;centos at centos.org
Action: failed
Status: 5.4.6
Diagnostic-Code: X-Postfix; mail forwarding loop for centos at centos.org
Kai
--
Kai Sch?tzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
On Wed, 2009-06-17 at 11:31 +0200, Kai Schaetzl wrote:> > <centos at centos.org>: mail forwarding loop for centos at centos.org > > Final-Recipient: rfc822; centos at centos.org > Original-Recipient: rfc822;centos at centos.org > Action: failed > Status: 5.4.6 > Diagnostic-Code: X-Postfix; mail forwarding loop for centos at centos.org--- So you you only just got them when sending a message to the list? I get them also at random it seems but the message will still make into the list though you get the error. I did bring it to Ralphs attention a few months back, but I thought it was just me getting them. John
Kai Schaetzl wrote:> I've been getting over the last months several of these notices. Sometimes > a few per day. What's the problem? Can't this be avoided?> The mail system > > <centos at centos.org>: mail forwarding loop for centos at centos.orgI haven't the faintest idea *why* those happen. Especially as the mails in question do make it through to the list (and I never got one of those, so I cannot really look at all the headers). There is a user "centos" on that machine, but as aliases >> local users in postfix context, I'm really out of ideas. Ralph -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20090617/3d7c621a/attachment-0001.sig>
> Kai Schaetzl wrote: >> I've been getting over the last months several of these notices. Sometimes >> a few per day. What's the problem? Can't this be avoided? > >> The mail system >> >> <centos at centos.org>: mail forwarding loop for centos at centos.org > > I haven't the faintest idea *why* those happen. Especially as the mails > in question do make it through to the list (and I never got one of > those, so I cannot really look at all the headers). > > There is a user "centos" on that machine, but as aliases >> local users > in postfix context, I'm really out of ideas.i got one as well and when i looked in the headers it appears to be getting generated via a ohio state trying to reinject the message back to the list. Received: from meriadoc.asc.ohio-state.edu (meriadoc.asc.ohio-state.edu [128.146.117.124]) by mail.centos.org (Postfix) with ESMTP id 8326B67B45 for <centos at centos.org>; Tue, 16 Jun 2009 10:33:39 -0400 (EDT) Received: from gollum.asc.ohio-state.edu ([128.146.117.98]) by meriadoc.asc.ohio-state.edu with Microsoft SMTPSVC(6.0.3790.3959); Tue, 16 Jun 2009 10:33:36 -0400 Received: from mail pickup service by gollum.asc.ohio-state.edu with Microsoft SMTPSVC; Tue, 16 Jun 2009 10:33:34 -0400 Received: from exchange.asc.ohio-state.edu ([128.146.117.123]) by meriadoc.asc.ohio-state.edu with Microsoft SMTPSVC(6.0.3790.3959); Fri, 12 Jun 2009 13:18:04 -0400 Received: from tnc-mta-2.it.ohio-state.edu ([140.254.54.48]) by exchange.asc.ohio-state.edu with Microsoft SMTPSVC(6.0.3790.3959); Fri, 12 Jun 2009 12:41:16 -0400
Ralph Angenendt wrote on Wed, 17 Jun 2009 13:15:20 +0200:> There is a user "centos" on that machine, but as aliases >> local users > in postfix context, I'm really out of ideas.I think there must be some forwards that temporarily do not work or create a loop condition. Btw, it's happening only since a year or so. Or it's a misconfigured Exchange system that passes the mail thru again to centos at centos.org which then gets detected. Kai -- Kai Sch?tzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com