+1
> On 15 May 2017, at 06:32, Viktor Dukhovni wrote:
>
>
>> On May 15, 2017, at 12:26 AM, Bill Cole
>> wrote:
>>
>> If you want versatile, nuanced, precise, and accurate attachment handling,
>> there is no
>> better tool than MIMEDefang.
>
> The MIME normalizer I wrote in my early days as
> On May 15, 2017, at 12:26 AM, Bill Cole
> wrote:
>
> If you want versatile, nuanced, precise, and accurate attachment handling,
> there is no
> better tool than MIMEDefang.
The MIME normalizer I wrote in my early days as Morgan Stanley postmaster, just
before
Y2K New Years, was tasked with
On 14 May 2017, at 7:43, Kevin A. McGrail wrote:
On 5/14/2017 7:22 AM, john wrote:
This may not be a Postfix problem, but bearing in mind the recent
events this forum may have some good ideas.
After the recent rasomeware attacks we are considering the idea of
blocking all attachments. I a
On Sun, May 14, 2017 at 07:22:14AM -0400, john wrote:
> This may not be a Postfix problem, but bearing in mind the recent
> events this forum may have some good ideas.
No, it isn't.
> After the recent rasomeware attacks we are considering the idea of
> blocking all attachments. I am not sure of
On 5/14/2017 7:22 AM, john wrote:
This may not be a Postfix problem, but bearing in mind the recent
events this forum may have some good ideas.
After the recent rasomeware attacks we are considering the idea of
blocking all attachments. I am not sure of the best way of doing
this, but seve
john wrote:
> 1. block all email with attachments - a little too drastic for some as there
> are legit
> reasons for attachments.
> block all email that is in any format that can hide executable code.
IMO this won't work.
> 2. rename attachments so that they will not/cannot be executed/
This may not be a Postfix problem, but bearing in mind the recent events
this forum may have some good ideas.
After the recent rasomeware attacks we are considering the idea of
blocking all attachments. I am not sure of the best way of doing this,
but several ideas have been put forward:
1.
