Banned attachments?

I doubt this error message comes from your server. This is either a bounce message from an external receiving server generated by some mail believed to be sent by you (which isn't even necessarily true). Ignore, unless this is a mail sent by you that you want to reach destination. In that case notify recipient.

In a Tiger default installation no attachment checking by extension is done. This wouldn't make any sense. Extension can be changed and do not reveal whether an attachment is potentially dangerous or not. The best protection against "bad" attachments is still a virus scanner like ClamAV.

Alex

Then you must have changed or implemented something.

Send me an e-mail to pterobyte -at- gmail.com So I can send you a mail from one of my servers an trace the logs.

No need to send me an attachment.

I sent you a test mail with a .zip and one with an .mdb attachment.

Zip went through no problem. .mdb came back. Doesn't look like it was bounced by amavisd though. Do you have any relaying smtp server in-between? Or a different content-filter? Anything that is not like in a standard install?

Alex

Don't you think this is something one would remember?
The way you asked sounded like you didn't play around with your configuration 😉

Check your configuration file:
/etc/amavisd.conf
for:
$banned filenamere

No it's not.
By default it is commented out (#), so you probably uncommented it at some point.

This what mine looks like:

$banned filenamere = new_RE(
qr'\.[a-zA-Z][a-zA-Z0-9]{0,3}\.(vbs|pif|scr|bat|com|exe|dll)$'i, # double extension
# qr'.\.(exe|vbs|pif|scr|bat|com)$'i, # banned extension - basic
# qr'.\.(ade|adp|bas|bat|chm|cmd|com|cpl|crt|exe|hlp|hta|inf|ins|isp|js|
# jse|lnk|mdb|mde|msc|msi|msp|mst|pcd|pif|reg|scr|sct|shs|shb|vb|
# vbe|vbs|wsc|wsf|wsh)$'ix, # banned extension - long
# qr'^\.(exe|zip|lha|tnef)$'i, # banned file(1) types
# qr'^application/x-msdownload$'i, # banned MIME types
# qr'^message/partial$'i, qr'^message/external-body$'i, # rfc2046
);