Hi,
> Instead of blindly trying random changes that may only have unwanted
> side-effects, collect the information needed to understand the problem.
I did not change anything that I am not able to revert back to it's original
settings.
I am not "blindly trying random changes" but implementing suggestions being
made in this thread and / or I found elsewhere online when I searched for
keywords like "postfix", "always_bcc", "content_filter" etc.
For the sake of keeping this mail readable, please refer to this link
(https://pastebin.com/nUz5BEdB) , there you will find an excerpt of the maillog
from two mails stuck in the queue.
I could try and generate a logfile, when postfix logs verbosely again (but as
the system is quite active I presume there will be many non-related information
in the excerpt). Would that be of any help?
I could also provide PCAP files and / or wireshark data, when there is a chance
to anonymise the information.
Thanks,
Niclas
-----Ursprüngliche Nachricht-----
Von: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
Im Auftrag von Viktor Dukhovni
Gesendet: Montag, 5. Februar 2018 20:01
An: Postfix users <postfix-users@postfix.org>
Betreff: [MASSMAIL]Re: Duplicate mails in mailq / always_bcc
> On Feb 5, 2018, at 12:04 PM, Niclas Rautenhaus
> <rautenh...@team-datentechnik.de> wrote:
>
> What I tried so far:
Instead of blindly trying random changes that may only have unwanted
side-effects, collect the information needed to understand the problem.
What you have not yet tried is posting the complete logging for some of the
queue-ids that got "stuck", and (more importantly) posting "tcpdump" output for
a captured session. If all else fails, then send a complete PCAP file off-list
to Wietse or me.
--
Viktor.
