On Friday, Sep 12, 2003, at 01:42 Europe/Berlin, Mike Oliver wrote:
> syn uw <syn_uw@hotmail.com> wrote:
>> One of our subscribed users (to our mailing list) cannot receive any
>> mails
>> posted to our mailing list. When sending out a mail we receive a
>> "Delivery
>> Status Notification (Failure)" from their mail server. This is the
>> error
>> message:
>>
>> ---
>> This is an automatically generated Delivery Status Notification.
>>
>> Unable to deliver message to the following recipients, because the
>> message
>> was forwarded more than the maximum allowed times. This could
>> indicate a
>> mail loop.
>>
>> Final-Recipient: rfc822;emailaddress@here.com
>> Action: failed
>> Status: 4.4.6
>> ---
>>
>> Is that because their mail server may not like majordomo ? Or what
>> could be
>> the problem here ?
>
> The problem is that by the time the message reaches the subscriber's
> mail server, the message has accumulated a lot of 'Received' headers.
> (It gets one more each time a mail server forwards the message, both on
> its way to your list server and again on its way from your server to
> the subscriber.) Based on the number of headers, this mail server
> thinks that the message might just be going around in circles so it
> bounces the message back to you.
>
>> Is out a problem on our side (the mailing list side) or
>> is it a problem on their mail server ?
>
> It's just a consequence of a long mail path.
It is also possible, that two MTAs on the remote site are indeed
playing ping-pong with the mail.
In that case just unsubsribe the recepient and let him resubscribe when
his postmaster figures out what is wrong.
Sometimes it is just a single user, who will find out, that forwarding
from account A to B, and then setting a .forward from B to A is not
such a great idea. :-)
Regards
Susan Barnes
References:
|
|
