* Rich Shepard <rshep...@appl-ecosys.com>: > The Postfix book tells me that using the WARN option on a restriction > (such as in the /etc/postfix/header_checks file) logs the warning while > delivering the message. However, there is apparently no marking of the > message so it's clearly identified as one that tripped that warning.
Usually you can identify the message using sender, recipient and/or message-id: Oct 6 22:59:28 mail postfix/cleanup[2703]: 75B5C1C360A: warning: header Subject: AARON LORDSON ON A TALENT SHOW !! from server009.hostspectrum.com[64.92.105.16]; from=<cont...@aaronlordson.com> to=<spamvic...@charite.de> proto=ESMTP helo=<server009.hostspectrum.com> using the QueueID I can retrieve the message-id: Oct 6 22:59:28 mail postfix/cleanup[2703]: 75B5C1C360A: message-id=<201f6b9c8267c0517c1cd88b1fb52...@lordsons-macbook-pro.local> > I want to examine delivered messages that contain > "Content-Transfer-Encoding: base64" in the header. Basically that would be all messages... > Adding that string to the header_checks file with a WARN option does > not explicitly identify those messages. > > Use of the warn action is not giving me the results I want. How should I > be doing this? Alternatively, if I use the HOLD option instead, where are > those messages held until I can examine them? What exactly is it that you want to do. In real life almost ALL mails are base64 encoded... -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
signature.asc
Description: Digital signature
