>Are we bored yet... It looks like the software that's sending it into
Postfix over and over again is likely the "pykolab"
>thing on port 10026.
I was able to locate the files that pykolab was using to create this mayhem.
Thank you so much Viktor!
>There are no "Received:" headers here, are you sure you've posted *all* the
headers? All messages received by Postfix get a "Received" header
prepended. Where are they? However, we do see that the message went
through >Amavis, so ypu should have logs for that... and ideally for how it
got into
> The message was created by something other than local submission, since it
arrived via SMTP to 127.0.0.1.
You are perhaps right. The message id appears to be same for this
problematic email (i.e. for every attempt to deliver this email to
x...@icloud.com the message id is 2f18001d6e499$48eeff40$
>The logs are rather a jumble, please collate the logs by queue-id, avoiding
mixing different messages together, and show all logs for any queue-id
that's relevant.
Here is the collated output from the script:
Jan 12 17:56:26 mail postfix/smtpd[17788]: connect from xxx[127.0.0.1]
Jan 12 17:56:26
>Once your master.cf file is correct, it is no longer of much interest.
What matters now is logs and main.cf.
Here is what I see now with the same email going out again and again:
Jan 12 17:56:26 mail postfix/smtpd[17788]: connect from xxx[127.0.0.1]
Jan 12 17:56:26 mail postfix/smtpd[17788]: AE
I changed the last column in bounce line to bounce (it used to be discard)
in master.cf.
Now I get NDRs every minute or so because of those retrying emails. What
next?
Here is my master.cf:
# Postfix master process configuration file. For details on the format
# of the file, see the master(5) m
