Rich Shepard put forth on 10/7/2009 1:38 PM:
> On Wed, 7 Oct 2009, LuKreme wrote:
>
>> Looking at my mail spool almost ALL mail is either 7bit, 8bit, or
>> quoted-printable.
>
> That's what I've seen here, too.
>
> Regardless, when I put those base64 messages on hold and looked at them
> thi
On Wed, 7 Oct 2009, LuKreme wrote:
Looking at my mail spool almost ALL mail is either 7bit, 8bit, or
quoted-printable.
That's what I've seen here, too.
Regardless, when I put those base64 messages on hold and looked at them
this morning, none was base64 Content-Transfer-Encoded. I'm witho
On 6-Oct-2009, at 15:02, Ralf Hildebrandt wrote:
In real life almost ALL mails are base64 encoded...
Wait, what?
$ grep -ir "^Content-Transfer-Encoding" . | wc -l
198485
$ grep -ir "^Content-Transfer-Encoding" . | grep -v base64 | wc -l
195574
Looking at my mail spool almost ALL mail is eit
Rich Shepard put forth on 10/6/2009 4:38 PM:
> On Tue, 6 Oct 2009, Ralf Hildebrandt wrote:
>
>>>I want to examine delivered messages that contain
>>> "Content-Transfer-Encoding: base64" in the header.
>>
>> Basically that would be all messages...
>
> Ralf,
>
> I asked locally about that be
On Tue, 6 Oct 2009, Wietse Venema wrote:
Perhaps "warn" is not the right concept for inspecting mail. Options more
directly related to mail inspection would be:
holdFreeze the mail in the queue until acted upon.
Frozen mail can be inspected with "postcat -q queueid", or
deleted/requeued
On Tue, 6 Oct 2009, Ralf Hildebrandt wrote:
I want to examine delivered messages that contain
"Content-Transfer-Encoding: base64" in the header.
Basically that would be all messages...
Ralf,
I asked locally about that because much of the spam I receive is coded
base64 while almost all
Rich Shepard:
> 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
* Rich Shepard :
>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 tha
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.
I want to
