On Thu, Aug 22, 2024 at 12:32:31PM +0200, Tomas Habarta via Postfix-users wrote:
> As the stray CR/LF replacement is implemented in cleanup server, I
> assume that the corresponding queue file is already modified
Correct, the replacement takes place as part of writing the queue file.
Of course you have not posted evidence of your configuration, so hard to
know whether it matches your intent. Post the output of at least:
$ postconf -d cleanup_replace_stray_cr_lf
$ postconf cleanup_replace_stray_cr_lf
The former to make sure the parameter is actually supported in your
build.
> I can actually see a couple of CRs in body (raw hexdump of the queue
> file and search for x0d)
That's not the right way. Instead, use "poscat -hb", and look for a bare CR.
# postcat -qbh $qid |
perl -ne '
next unless m{\r[^\n]};
s/([\x00-\x1f\xff\\])/sprintf qq(\\x{%02x}), ord($1)/eg;
print qq($_\n)
'
> but not quite sure whether this is a valid approach...
Sadly, not.
> Need to wait a month to try to catch and hold a sample with the
> replace option set to "no" to get an idea how the source looks like
> originally, but in the meantime, anyone noticed any similar behaviour
> or better, any idea if (and if yes why) this might be possible to
> happen within Postfix?
Waiting is not necessary, just try to send a dedicated recipient whose
messages are always kept in the hold queue (HOLD access(5) action) a
message with a stray CR and see what happens.
--
Viktor.
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
