Greetings, Matthias Andree!
> Am 27.12.18 um 02:05 schrieb Andrey Repin:
>> Greetings, Wietse Venema!
>>
>>> Andrey Repin:
>>>> Greetings, All!
>>>>
>>>>> I think I just broke my mail system. I'd like a quick help if possible.
>>>>> I have a remote server that accepts the mail for domain right now.
>>>>> The mail is retrieved from it by fetchmail and pushed to the local postfix
>>>>> instance to be delivered to the user mailboxes using
>>>>
>>>>> mda "/usr/sbin/sendmail -iG -N never -f %F -- %T"
>>>>
>>>>> The problem is, only virtual recipients are delivered correctly.
>>>>> An attempt to deliver mail for real users end in message being trashed
>>>>> with
>>>>> "delivery loop detected".
>>>>> The log says "bounced", but it is nowhere to be found. Not on postmaster,
>>>>> neither on the sender's address.
>>>>
>>>> Ok, I've managed to capture a bounce.
>>>> Here's headers of a message that was received (and bounced) by postfix.
>>>> Yes, the final destination is alexa...@ccenter.msk.ru, and the user
>>>> actually
>>>> exists.
>>
>>> Rule number one: email routing MUST NOT depend on the message
>>> header content and it MUST NOT depend on the message body content.
>>
>> It's neither. I have explicitly set final destination for each remote
>> account.
>> If there any way to work around it, until the migration is done and the
>> remote
>> server is decomissioned?
> Without fetchmail configuration details and logs, it's too hard to debug
> remotely.
> As Wietse stated, %T might be dangerous, if it's a single-user mailbox,
> you might as well just specify the user's name instead. Else you _must_
> make sure that fetchmail can properly derive envelope recipient headers
> (assuming that your mailbox stores them in some form), and that in turn
> assumes that your fetchmail configuration makes for a constant
> recipient...
fetchmail do not derive anything, the local recipient is set explicitly, and
yes, it was a single user, with no domain part.
Literal rejection text was
Dec 26 23:09:04 mxs postfix/local[1944]: 8540017BC8F0:
to=<alexa...@ccenter.msk.ru>, orig_to=<alexandr>, relay=local, delay=0.4,
delays=0.3/0/0/0.1, dsn=5.4.6, status=bounced (mail forwarding loop for
alexa...@ccenter.msk.ru)
I worked around it by specifying a local domain for recipient addresses.
poll pop3.ht-systems.ru
protocol POP3
uidl
auth password
user alexa...@ccenter.msk.ru
password "..."
to alexa...@ccenter.lan
> In which case you need to make sure that the messages you inject from
> fetchmail does not end up in the mailbox you are fetching from - which
> is what might be happening.
It's two different systems. I wasn't expecting such behavior.
> For the fetchmail end, see
> <http://www.fetchmail.info/fetchmail-FAQ.html#G3> (again, remove passwords).
--
With best regards,
Andrey Repin
Thursday, December 27, 2018 12:36:26
Sorry for my terrible english...
