Executable Content / Executable Attachments best practice?

[kitchin]

Argh, I just realized I still have "bounce" on for these two CNC filters:

Executable Content
Executable Attachments

What's the best way to deal with these? Bounce is bad, and I don't want to blackhole legit mail just because the sender attaches an .exe when it should have been a .zip. So the only choice left is to block the mail and send myself a notification, since I shouldn't send anything back to the sender.

I'm thinking: redirect it to a new mailbox, then use a "processor filter" to strip out the body of the message. Or: redirect to a blackhole address, and use a "simple filter" there that logs it to a text file. The fact that I'm using the "executable" filters globally makes either solution more complicated.

Like I said, argh.

I searched the forums and neither filter has been discussed since 2004.

[kitchin]

Another afternoon spent/wasted on email filtering. Can anyone at FQ tell me if this perl algorithm always gets the header block in a Processor Filter?

$/= ''; ## delim on \n\n
$_= <STDIN>; ## get header (only)

In other words, is there ever any funny business with \r\r or \r\n\r\n between the headers and the body of the email message?

[Bruce]

In other words, is there ever any funny business with \r\r or \r\n\r\n between the headers and the body of the email message?The internet message format standard (http://www.ietf.org/rfc/rfc2822.txt) defines the separator line as "a line with nothing preceding the CRLF". Since qmail translates the CRLF sequence (\r\n) to a bare LF (\n), there should never be anything else on that line.

[kitchin]

Thanks Bruce, I though qmail was saving me from looking for oddball \r sequences and so it is!