Attachment Notifications Blocked Yet Option Allowed?

[EFAUser1]

We have a file that users send us (*.dll) that is routinely blocked. Sometimes it goes through when the file is renamed to .txt others not. The real issue is that the user is not notified when the file is blocked. The system message that goes back to them is marked as red colored never sent despite the option to "Notify Senders Of Blocked Filenames Or Filetypes" being marked as yes. For the blocked file the Report reads "MailScanner: No programs allowed ("program name".txt). Do we have the right configuration setting or is it Notify Senders Of Viruses (currently set to No).

[shawniverson]

Notify Senders is not adviseable as this causes backscatter.

With that said, you also need the following setting enabled

Code: Select all

Notify Senders = yes

[EFAUser1]

Notify Senders is not adviseable as this causes backscatter.

With that said, you also need the following setting enabled

Code: Select all

Notify Senders = yes

Thanks for your quick reply! Unfortunately notify senders is already sent to yes though.

[shawniverson]

Can you share a "spam" report on the blocked attachment? I want to find out what component is blocking the file, as this may affect the settings you need...

[EFAUser1]

Can you share a "spam" report on the blocked attachment? I want to find out what component is blocking the file, as this may affect the settings you need...

Here is the initial email coming in as well as the spam report. Again, the spam report back to the sender (of a blocked file) gets marked as spam and never sent. Thanks for your help, I really appreciate it!

Edit: Assuming you're just going to say make the same changes as in this viewtopic.php?t=876? Is there any merit to some of the points he brings up after your initial suggestion or is changing that threshold to "2" the only option right now?

[shawniverson]

Edit: Assuming you're just going to say make the same changes as in this viewtopic.php?t=876? Is there any merit to some of the points he brings up after your initial suggestion or is changing that threshold to "2" the only option right now?

Unfortunately, no, since MailScanner controls this function. Watermark/Sender address checking supercedes whitelisting. I don't like it, and I brought this issue up on the MailScanner listserv long ago.

You can read the original thread here:

http://mailscanner.mailscanner.narkive. ... er-as-spam