Our e-mail content detector has just been triggered by a message you sent: To: [email protected] Subject: 2.UTF-8??????? Date: Sun Oct 10 16:46:37 2010 One or more of the attachments (msg-20952-4.txt) are on the list of unacceptable attachments for this site and will not have been delivered. Consider renaming the files to avoid this constraint. The virus detector said this about the message: Report: Report: MailScanner: No programs allowed (msg-20952-4.txt) -- MailScanner Email Virus Scanner Trysoft Corp. www.ichiayi.com For all your IT requirements visit: http://www.transtec.co.uk
: deny self-extract No self-extracting archives No self-extracting archives allowed #deny executable No executables No programs allowed #EXAMPLE: deny - x-dosexec No DOS executables No DOS programs allowed :
: #Also Find Numeric Phishing = yes Also Find Numeric Phishing = %rules-dir%/phishing.rules : Phishing Safe Sites File = %etc-dir%/phishing.safe.sites.conf :
# Trust SMTP subnets From: 192.168.11. no FromOrTo: default yes
: : 140.92.140.88
自動更新後仍然會保留自己加入的部份.
service MailScanner reload
: # When the TNEF (winmail.dat) attachments are expanded, should the # attachments contained in there be added to the list of attachments in # the message? # If you set this to "add" or "replace" then recipients of messages sent # in "Outlook Rich Text Format" (TNEF) will be able to read the attachments # if they are not using Microsoft Outlook. # # no => Leave winmail.dat TNEF attachments alone. # add => Add the contents of winmail.dat as extra attachments, but also # still include the winmail.dat file itself. This will result in # TNEF messages being doubled in size. # replace => Replace the winmail.dat TNEF attachment with the files it # contains, and delete the original winmail.dat file itself. # This means the message stays the same size, but is usable by # non-Outlook recipients. # # This can also be the filename of a ruleset. Use TNEF Contents = replace # Some versions of Microsoft Outlook generate unparsable Rich Text # format attachments. Do we want to deliver these bad attachments anyway? # Setting this to yes introduces the slight risk of a virus getting through, # but if you have a lot of troubled Outlook users you might need to do this. # We are working on a replacement for the TNEF decoder. # This can also be the filename of a ruleset. Deliver Unparsable TNEF = yes :
service MailScanner reload