From mark at msapiro.net Wed Feb 1 01:22:36 2017 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 31 Jan 2017 17:22:36 -0800 Subject: Ruleset syntax In-Reply-To: References: Message-ID: <4db15dbc-bd83-f14d-e242-d3ab09b9e3a6@msapiro.net> On 01/31/2017 02:37 AM, Marcelo Machado wrote: > It seems MailScanner is not reading the ruleset file from these parameters. > I did the test below and did not blocked the attachment > > Deny Filenames =%rules.dir%/deny.filenames.rules (MailScanenr.conf) > > From: *@netsol.com.br \.jpg$ (deny.filenames.rules) It's also not working for me in a test environment, even with a pattern like .*$ which should match anything. It works with patterns set as the Deny Filenames value, e.g. Deny Filenames = \.jpg$ but of course that's not what you want. I don't know why it isn't working with rule sets. I'm investigating. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Feb 1 05:12:06 2017 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 31 Jan 2017 21:12:06 -0800 Subject: Ruleset syntax In-Reply-To: <4db15dbc-bd83-f14d-e242-d3ab09b9e3a6@msapiro.net> References: <4db15dbc-bd83-f14d-e242-d3ab09b9e3a6@msapiro.net> Message-ID: On 01/31/2017 05:22 PM, Mark Sapiro wrote: > On 01/31/2017 02:37 AM, Marcelo Machado wrote: >> It seems MailScanner is not reading the ruleset file from these parameters. >> I did the test below and did not blocked the attachment >> >> Deny Filenames =%rules.dir%/deny.filenames.rules (MailScanenr.conf) >> >> From: *@netsol.com.br \.jpg$ (deny.filenames.rules) > > > It's also not working for me in a test environment, ... Actually, it's working fine. Try Deny Filenames = %rules-dir%/deny.filenames.rules i.e. $rules-dir%, not %rules.dir%. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ok at addix.net Wed Feb 1 15:34:16 2017 From: ok at addix.net (Oliver Kutscher) Date: Wed, 1 Feb 2017 16:34:16 +0100 Subject: "Allow Script Tags" affects attachments? Message-ID: Hi, I wonder if "Allow Script Tags" is also affecting attachments? So if a HTML containing "" is attached will the email be dropped if "Allow Script Tags" is set to "no"? -- MrLINK From jerry.benton at mailborder.com Wed Feb 1 20:16:51 2017 From: jerry.benton at mailborder.com (Jerry Benton) Date: Wed, 1 Feb 2017 15:16:51 -0500 Subject: "Allow Script Tags" affects attachments? In-Reply-To: References: Message-ID: There should NEVER be scripts tags in email. This is not how images are inserted. - Jerry Benton www.mailborder.com +1 - 844-436-6245 > On Feb 1, 2017, at 10:34 AM, Oliver Kutscher wrote: > > Hi, > > I wonder if "Allow Script Tags" is also affecting attachments? So if a HTML containing "" is attached will the email be dropped if "Allow Script Tags" is set to "no"? > > -- > MrLINK > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ok at addix.net Wed Feb 1 20:27:49 2017 From: ok at addix.net (Oliver Kutscher) Date: Wed, 1 Feb 2017 21:27:49 +0100 Subject: "Allow Script Tags" affects attachments? In-Reply-To: References: Message-ID: <5aa75b92-f6af-f4b7-c0af-49771b053832@addix.net> Thats right. Actually it is a cutomers mail server who wants be to ban script tags. I just ask myself if attachments are also affected. Right now I don't have a test server. -- MrLINK Am 01.02.2017 um 21:16 schrieb Jerry Benton: > There should NEVER be scripts tags in email. This is not how images are > inserted. > > - > Jerry Benton > www.mailborder.com > +1 - 844-436-6245 > > > >> On Feb 1, 2017, at 10:34 AM, Oliver Kutscher > > wrote: >> >> Hi, >> >> I wonder if "Allow Script Tags" is also affecting attachments? So if a >> HTML containing "" is attached will the email be >> dropped if "Allow Script Tags" is set to "no"? >> >> -- >> MrLINK >> >> >> -- >> MailScanner mailing list >> mailscanner at lists.mailscanner.info >> >> http://lists.mailscanner.info/mailman/listinfo/mailscanner >> > > > > > From Antony.Stone at mailscanner.open.source.it Wed Feb 1 20:29:41 2017 From: Antony.Stone at mailscanner.open.source.it (Antony Stone) Date: Wed, 1 Feb 2017 21:29:41 +0100 Subject: "Allow Script Tags" affects attachments? In-Reply-To: References: Message-ID: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> On Wednesday 01 February 2017 at 21:16:51, Jerry Benton wrote: > There should NEVER be scripts tags in email. This is not how images are > inserted. Surely the question was about script tags in HTML attachments to (plain text or HTML) emails, nothing to do with images...? Antony > > On Feb 1, 2017, at 10:34 AM, Oliver Kutscher wrote: > > > > Hi, > > > > I wonder if "Allow Script Tags" is also affecting attachments? So if a > > HTML containing "" is attached will the email be > > dropped if "Allow Script Tags" is set to "no"? > > > > -- > > MrLINK -- I don't know, maybe if we all waited then cosmic rays would write all our software for us. Of course it might take a while. - Ron Minnich, Los Alamos National Laboratory Please reply to the list; please *don't* CC me. From jerry.benton at mailborder.com Wed Feb 1 20:31:30 2017 From: jerry.benton at mailborder.com (Jerry Benton) Date: Wed, 1 Feb 2017 15:31:30 -0500 Subject: "Allow Script Tags" affects attachments? In-Reply-To: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> Message-ID: <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> Ok, attachments. The should NEVER be script tags in email. This is not how attachments are done. - Jerry Benton www.mailborder.com +1 - 844-436-6245 > On Feb 1, 2017, at 3:29 PM, Antony Stone wrote: > > On Wednesday 01 February 2017 at 21:16:51, Jerry Benton wrote: > >> There should NEVER be scripts tags in email. This is not how images are >> inserted. > > Surely the question was about script tags in HTML attachments to (plain text > or HTML) emails, nothing to do with images...? > > > Antony > >>> On Feb 1, 2017, at 10:34 AM, Oliver Kutscher wrote: >>> >>> Hi, >>> >>> I wonder if "Allow Script Tags" is also affecting attachments? So if a >>> HTML containing "" is attached will the email be >>> dropped if "Allow Script Tags" is set to "no"? >>> >>> -- >>> MrLINK > > -- > I don't know, maybe if we all waited then cosmic rays would write all our > software for us. Of course it might take a while. > > - Ron Minnich, Los Alamos National Laboratory > > Please reply to the list; > please *don't* CC me. > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Antony.Stone at mailscanner.open.source.it Wed Feb 1 20:35:56 2017 From: Antony.Stone at mailscanner.open.source.it (Antony Stone) Date: Wed, 1 Feb 2017 21:35:56 +0100 Subject: "Allow Script Tags" affects attachments? In-Reply-To: <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> Message-ID: <201702012135.56496.Antony.Stone@mailscanner.open.source.it> On Wednesday 01 February 2017 at 21:31:30, Jerry Benton wrote: > Ok, attachments. > > The should NEVER be script tags in email. This is not how attachments are > done. Sorry, am I misunderstanding? What's to stop me writing an HTML page, containing " is attached will the email be > >>> dropped if "Allow Script Tags" is set to "no"? > >>> > >>> -- > >>> MrLINK -- +++ Divide By Cucumber Error. Please Reinstall Universe And Reboot +++ Please reply to the list; please *don't* CC me. From ok at addix.net Wed Feb 1 20:40:57 2017 From: ok at addix.net (Oliver Kutscher) Date: Wed, 1 Feb 2017 21:40:57 +0100 Subject: "Allow Script Tags" affects attachments? In-Reply-To: <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> Message-ID: I'm not asking for what tags should or should not be in email. I'm asking if "Allow Script Tags" will affect attachments. So if I attach 3 html files to the emal where one of them contains one or more script tags, will MailScanner drop the email if "Allow Script Tags" is set to "no"? -- MrLINK Am 01.02.2017 um 21:31 schrieb Jerry Benton: > Ok, attachments. > > The should NEVER be script tags in email. This is not how attachments > are done. > > - > Jerry Benton > www.mailborder.com > +1 - 844-436-6245 > > > >> On Feb 1, 2017, at 3:29 PM, Antony Stone >> > > wrote: >> >> On Wednesday 01 February 2017 at 21:16:51, Jerry Benton wrote: >> >>> There should NEVER be scripts tags in email. This is not how images are >>> inserted. >> >> Surely the question was about script tags in HTML attachments to >> (plain text >> or HTML) emails, nothing to do with images...? >> >> >> Antony >> >>>> On Feb 1, 2017, at 10:34 AM, Oliver Kutscher >>> > wrote: >>>> >>>> Hi, >>>> >>>> I wonder if "Allow Script Tags" is also affecting attachments? So if a >>>> HTML containing "" is attached will the email be >>>> dropped if "Allow Script Tags" is set to "no"? >>>> >>>> -- >>>> MrLINK >> >> -- >> I don't know, maybe if we all waited then cosmic rays would write all our >> software for us. Of course it might take a while. >> >> - Ron Minnich, Los Alamos National Laboratory >> >> Please reply to the >> list; >> please *don't* >> CC me. >> >> >> -- >> MailScanner mailing list >> mailscanner at lists.mailscanner.info >> >> http://lists.mailscanner.info/mailman/listinfo/mailscanner >> > > > > > From mailscanner at replies.cyways.com Wed Feb 1 20:45:44 2017 From: mailscanner at replies.cyways.com (Peter H. Lemieux) Date: Wed, 1 Feb 2017 15:45:44 -0500 Subject: "Allow Script Tags" affects attachments? In-Reply-To: <201702012135.56496.Antony.Stone@mailscanner.open.source.it> References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <201702012135.56496.Antony.Stone@mailscanner.open.source.it> Message-ID: <578a443a-e689-f0e7-b402-589f1b693b4b@replies.cyways.com> To me, script tags are inherently dangerous and should always be blocked. Sure you can construct a "legitimate" HTML page with embedded scripts, but I doubt most messages with scripts are legitimate. What about ones that announce that you opened a message, despite your having blocked such notifications? Or ones that are designed for advertising and tracking purposes? Or worse, what about ones that download malware from remote servers and run it locally? I can think of lots of reasons why I don't want scripts in any email I receive. I have a hard time thinking of any examples where they would enhance my email experience. Peter On 02/01/2017 03:35 PM, Antony Stone wrote: > On Wednesday 01 February 2017 at 21:31:30, Jerry Benton wrote: > >> Ok, attachments. >> >> The should NEVER be script tags in email. This is not how attachments are >> done. > > Sorry, am I misunderstanding? > > What's to stop me writing an HTML page, containing " is attached will the email be >>>>> dropped if "Allow Script Tags" is set to "no"? >>>>> >>>>> -- >>>>> MrLINK > From mark at msapiro.net Thu Feb 2 01:29:50 2017 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 1 Feb 2017 17:29:50 -0800 Subject: "Allow Script Tags" affects attachments? In-Reply-To: References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> Message-ID: <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> On 02/01/2017 12:40 PM, Oliver Kutscher wrote: > I'm not asking for what tags should or should not be in email. I'm > asking if "Allow Script Tags" will affect attachments. Yes. > So if I attach 3 > html files to the emal where one of them contains one or more script > tags, will MailScanner drop the email if "Allow Script Tags" is set to > "no"? No. That's not what MailScanner does. What it will do is replace the one text/html part that contains the script tags with the appropriate Attachment-Warning.txt message. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ok at addix.net Thu Feb 2 08:15:23 2017 From: ok at addix.net (Oliver Kutscher) Date: Thu, 2 Feb 2017 09:15:23 +0100 Subject: "Allow Script Tags" affects attachments? In-Reply-To: <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> Message-ID: Hi, thanks for that answer. So MailScanner will detect script tags whether they are in the message itself or found within one or more attachment. -- MrLINK Am 02.02.2017 um 02:29 schrieb Mark Sapiro: > On 02/01/2017 12:40 PM, Oliver Kutscher wrote: >> I'm not asking for what tags should or should not be in email. I'm >> asking if "Allow Script Tags" will affect attachments. > > > Yes. > >> So if I attach 3 >> html files to the emal where one of them contains one or more script >> tags, will MailScanner drop the email if "Allow Script Tags" is set to >> "no"? > > > No. That's not what MailScanner does. What it will do is replace the one > text/html part that contains the script tags with the appropriate > Attachment-Warning.txt message. > From glenn.steen at gmail.com Thu Feb 2 16:12:59 2017 From: glenn.steen at gmail.com (Glenn Steen) Date: Thu, 2 Feb 2017 17:12:59 +0100 Subject: "Allow Script Tags" affects attachments? In-Reply-To: References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> Message-ID: Lets be clear about one thing... "HTML e-mail" is by definition a misnomer, referring to messages with at least one HTML representation of the message as a MIME attachment. IOW no different to the third HTML file attached similarily. There should also be a plain text attachment, but at least some MUAs will ignore that standard stipulation. But in essence, there is no difference if they are "in the message [body, presumably]" or "attached as separate files". Cheers! -- -- Glenn 2017-02-02 9:15 GMT+01:00 Oliver Kutscher : > Hi, > > thanks for that answer. So MailScanner will detect script tags whether > they are in the message itself or found within one or more attachment. > > -- > MrLINK > > Am 02.02.2017 um 02:29 schrieb Mark Sapiro: > >> On 02/01/2017 12:40 PM, Oliver Kutscher wrote: >> >>> I'm not asking for what tags should or should not be in email. I'm >>> asking if "Allow Script Tags" will affect attachments. >>> >> >> >> Yes. >> >> So if I attach 3 >>> html files to the emal where one of them contains one or more script >>> tags, will MailScanner drop the email if "Allow Script Tags" is set to >>> "no"? >>> >> >> >> No. That's not what MailScanner does. What it will do is replace the one >> text/html part that contains the script tags with the appropriate >> Attachment-Warning.txt message. >> >> > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > -- -- Glenn email: glenn < dot > steen < at > gmail < dot > com work: glenn < dot > steen < at > ap1 < dot > se -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at msapiro.net Thu Feb 2 16:32:39 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 2 Feb 2017 08:32:39 -0800 Subject: "Allow Script Tags" affects attachments? In-Reply-To: References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> Message-ID: <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> On 02/02/2017 12:15 AM, Oliver Kutscher wrote: > Hi, > > thanks for that answer. So MailScanner will detect script tags whether > they are in the message itself or found within one or more attachment. Yes, notwithstanding the fact that in a MIME multipart message, there is often no clear understanding of which MIME parts are the 'message itself' vs. an 'attachment'. MailScanner looks at each MIME part individually without regard to what some MUA or person thinks is the message or an attachment, and if it is a text/html part and contains script tags, deals with that part according to the applicable Allow Script Tags value. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ok at addix.net Fri Feb 3 08:57:41 2017 From: ok at addix.net (Oliver Kutscher) Date: Fri, 3 Feb 2017 09:57:41 +0100 Subject: "Allow Script Tags" affects attachments? In-Reply-To: <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> Message-ID: Thanks. -- MrLINK Am 02.02.2017 um 17:32 schrieb Mark Sapiro: > On 02/02/2017 12:15 AM, Oliver Kutscher wrote: >> Hi, >> >> thanks for that answer. So MailScanner will detect script tags whether >> they are in the message itself or found within one or more attachment. > > > Yes, notwithstanding the fact that in a MIME multipart message, there is > often no clear understanding of which MIME parts are the 'message > itself' vs. an 'attachment'. > > MailScanner looks at each MIME part individually without regard to what > some MUA or person thinks is the message or an attachment, and if it is > a text/html part and contains script tags, deals with that part > according to the applicable Allow Script Tags value. > From sales at edenusa.com Mon Feb 6 00:06:58 2017 From: sales at edenusa.com (Paul Scott) Date: Mon, 6 Feb 2017 00:06:58 +0000 Subject: "Allow Script Tags" affects attachments? In-Reply-To: References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> Message-ID: In the MAILSCANNER.CONF file, I find this statement: # In the "Filename Rules" and "Filetype Rules" rule files, you can # say that you want particular attachment names or types to be "disarmed" # by being renamed. See the sample files for examples of this. First, I do not know where these "sample files" are. I have searched for them, but cannot find them. I am having issues with allowing my users the ability to attach .PDF and .DOC and other types of files, and either send or receive them. This issue only started after the upgrade to the 5.0 version. Does someone have a clear explanation on how to go ahead and allow users to send/receive emails with .PDFs and .DOC (Word) files (just to start with)? I may also need to allow users to send/receive images and other file types. Your assistance is greatly appreciated! Thank you very much! Sincerely, Paul Scott Engineer, Eden USA Las Vegas, New York, Los Angeles Phone: 866.501.3336 Fax: 866.502.3336 FACEBOOK: http://www.facebook.com/edenusainc -----Original Message----- From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Oliver Kutscher Sent: Friday, February 03, 2017 12:58 AM To: mailscanner at lists.mailscanner.info Subject: Re: "Allow Script Tags" affects attachments? Thanks. -- MrLINK Am 02.02.2017 um 17:32 schrieb Mark Sapiro: > On 02/02/2017 12:15 AM, Oliver Kutscher wrote: >> Hi, >> >> thanks for that answer. So MailScanner will detect script tags >> whether they are in the message itself or found within one or more attachment. > > > Yes, notwithstanding the fact that in a MIME multipart message, there > is often no clear understanding of which MIME parts are the 'message > itself' vs. an 'attachment'. > > MailScanner looks at each MIME part individually without regard to > what some MUA or person thinks is the message or an attachment, and if > it is a text/html part and contains script tags, deals with that part > according to the applicable Allow Script Tags value. > -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner From mark at msapiro.net Mon Feb 6 00:34:40 2017 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 5 Feb 2017 16:34:40 -0800 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> Message-ID: <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> On 02/05/2017 04:06 PM, Paul Scott wrote: > In the MAILSCANNER.CONF file, I find this statement: > > # In the "Filename Rules" and "Filetype Rules" rule files, you can > # say that you want particular attachment names or types to be "disarmed" > # by being renamed. See the sample files for examples of this. > > First, I do not know where these "sample files" are. I have searched for them, but cannot find them. The "sample" files are in /etc/MailScanner/. Their names are archives.filename.rules.conf, archives.filetype.rules.conf, filename.rules.conf and filetype.rules.conf. They are both samples and the actual working files configured by default. > I am having issues with allowing my users the ability to attach .PDF and .DOC and other types of files, and either send or receive them. > > This issue only started after the upgrade to the 5.0 version. The default rules do not disallow .pdf or .doc files so there is something else going on. > Does someone have a clear explanation on how to go ahead and allow users to send/receive emails with .PDFs and .DOC (Word) files (just to start with)? Please tell us what happens when an email is sent with an attached .pdf or .doc file. What does MailScanner log in the system mail log and what does the received message contain. One possibility is the attachments are being denied if they seem to have double extensions, e.g. "Joes.file.pdf. I.e., with some exceptions if the actual extension is preceded by a period and 3 or 4 alphanumerics, it is a bad name. This is intended to stop things like "innocent_name.txt .exe" but stops a lot more than that. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From diederik at webrelated.nl Mon Feb 6 15:04:33 2017 From: diederik at webrelated.nl (Diederik van den Burger) Date: Mon, 6 Feb 2017 16:04:33 +0100 Subject: Inconsistent SpamAssassin report Message-ID: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> Hey, Recently I have installed MailScanner on our email server. All seems to be working fine except the integration with SpamAssassin. Several emails are not marked as spam which definitely are spam. At first I thought the problem could be solved by adding extra rules to my SpamAssassin config, but this is apparently not working. When I check the spam emails through MailWatch, I see the following tests were ran: BAYES_00, DCC_CHECK, FREEMAIL_FROM, RCVD_IN_DNSWL_BLOCKED, RDNS_NONE, SPF_SOFTFAIL, URIBL_BLOCKED, URIBL,RHS_DOB with a total score of 5.08. However, when I run: spamassassin -t -d < spamemail I get a report saying the following tests were ran: URIBL_RHS_DOB, URIBL_BLOCKED, RCVD_IN_RP_RNBL, FREEMAIL_FROM, SPF_SOFTFAIL, BAYES_50, PYZOR_CHECK, DCC_CHECK, RDNS_NONE, DIGEST_MULTIPLE with a total score of 11.9. So it seems like MailScanner runs a whole different version/instance of SpamAssassin. How do I go about solving this? Best regards, Diederik From jerry.benton at mailborder.com Mon Feb 6 19:21:48 2017 From: jerry.benton at mailborder.com (Jerry Benton) Date: Mon, 6 Feb 2017 14:21:48 -0500 Subject: Inconsistent SpamAssassin report In-Reply-To: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> Message-ID: <92A5BDFE-7EDF-41F8-813F-ACDD6F0F38F4@mailborder.com> Does the size of the email exceed your setting for Max spamassassin Size ? - Jerry Benton www.mailborder.com +1 - 844-436-6245 > On Feb 6, 2017, at 10:04 AM, Diederik van den Burger wrote: > > Hey, > > Recently I have installed MailScanner on our email server. All seems to be working fine except the integration with SpamAssassin. Several emails are not marked as spam which definitely are spam. At first I thought the problem could be solved by adding extra rules to my SpamAssassin config, but this is apparently not working. When I check the spam emails through MailWatch, I see the following tests were ran: > > BAYES_00, DCC_CHECK, FREEMAIL_FROM, RCVD_IN_DNSWL_BLOCKED, RDNS_NONE, SPF_SOFTFAIL, URIBL_BLOCKED, URIBL,RHS_DOB with a total score of 5.08. > > However, when I run: > > spamassassin -t -d < spamemail > > I get a report saying the following tests were ran: > > URIBL_RHS_DOB, URIBL_BLOCKED, RCVD_IN_RP_RNBL, FREEMAIL_FROM, SPF_SOFTFAIL, BAYES_50, PYZOR_CHECK, DCC_CHECK, RDNS_NONE, DIGEST_MULTIPLE with a total score of 11.9. > > So it seems like MailScanner runs a whole different version/instance of SpamAssassin. How do I go about solving this? > > > > Best regards, > Diederik > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > -------------- next part -------------- An HTML attachment was scrubbed... URL: From iversons at rushville.k12.in.us Mon Feb 6 19:28:06 2017 From: iversons at rushville.k12.in.us (Shawn Iverson) Date: Mon, 6 Feb 2017 14:28:06 -0500 Subject: Inconsistent SpamAssassin report In-Reply-To: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> Message-ID: Diederik, Does this also produce yet a different set of results? sudo su - postfix -c "spamassassin -t -d < path/to/spamemail" On Mon, Feb 6, 2017 at 10:04 AM, Diederik van den Burger < diederik at webrelated.nl> wrote: > Hey, > > Recently I have installed MailScanner on our email server. All seems to be > working fine except the integration with SpamAssassin. Several emails are > not marked as spam which definitely are spam. At first I thought the > problem could be solved by adding extra rules to my SpamAssassin config, > but this is apparently not working. When I check the spam emails through > MailWatch, I see the following tests were ran: > > BAYES_00, DCC_CHECK, FREEMAIL_FROM, RCVD_IN_DNSWL_BLOCKED, RDNS_NONE, > SPF_SOFTFAIL, URIBL_BLOCKED, URIBL,RHS_DOB with a total score of 5.08. > > However, when I run: > > spamassassin -t -d < spamemail > > I get a report saying the following tests were ran: > > URIBL_RHS_DOB, URIBL_BLOCKED, RCVD_IN_RP_RNBL, FREEMAIL_FROM, > SPF_SOFTFAIL, BAYES_50, PYZOR_CHECK, DCC_CHECK, RDNS_NONE, DIGEST_MULTIPLE > with a total score of 11.9. > > So it seems like MailScanner runs a whole different version/instance of > SpamAssassin. How do I go about solving this? > > > > Best regards, > Diederik > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > -- Shawn Iverson Director of Technology Rush County Schools 765-932-3901 x271 iversons at rushville.k12.in.us -------------- next part -------------- An HTML attachment was scrubbed... URL: From sales at edenusa.com Mon Feb 6 20:20:33 2017 From: sales at edenusa.com (Paul Scott) Date: Mon, 6 Feb 2017 20:20:33 +0000 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> Message-ID: Hello Mark, and thank you so much for your quick reply! Here is the full body of the email returned back to the user whom is sending out the email, with a Word .DOC file attached to it: ---------- Forwarded message ---------- From: Matt Brudin Date: Mon, Jan 9, 2017 at 2:51 PM Subject: Circle K -- City of Hemet (EA1611-001) To: "jon.austin at mp-eng.com" Warning: This message has had one or more attachments removed Warning: (the entire message). Warning: Please read the "EdenUSAInc-Attachment-Warning.txt" attachment(s) for more information. This is a message from the MailScanner E-Mail Virus Protection Service ---------------------------------------------------------------------- The original e-mail attachment "the entire message" was believed to be dangerous and/or infected by a virus and has been replaced by this warning message. Due to limitations placed on us by the Regulation of Investigatory Powers Act 2000, we were unable to keep a copy of the infected attachment. Please ask the sender of the message to disinfect their original version and send you a clean copy. At Mon Jan 9 14:51:21 2017 the scanner said: Too many attachments in message -- Postmaster Eden USA, Inc. www.edenitservices.com For all your IT requirements visit: http://www.transtec.co.uk As you'll see in the return message above, it is confusing, because there are two different issues being reported. One of the issues is as follows: The original e-mail attachment "the entire message" was believed to be dangerous and/or infected by a virus and has been replaced by this warning message. The OTHER issue is as follows: At Mon Jan 9 14:51:21 2017 the scanner said: Too many attachments in message So, which is the true issue, and how to get this fixed, is the question. Thank you very much! Sincerely, Paul Scott Sales Engineer, Eden USA Las Vegas, New York, Los Angeles Phone: 866.501.3336 Fax: 866.502.3336 FACEBOOK: http://www.facebook.com/edenusainc -----Original Message----- From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Mark Sapiro Sent: Sunday, February 05, 2017 4:35 PM To: MailScanner Discussion Subject: Re: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? On 02/05/2017 04:06 PM, Paul Scott wrote: > In the MAILSCANNER.CONF file, I find this statement: > > # In the "Filename Rules" and "Filetype Rules" rule files, you can # > say that you want particular attachment names or types to be "disarmed" > # by being renamed. See the sample files for examples of this. > > First, I do not know where these "sample files" are. I have searched for them, but cannot find them. The "sample" files are in /etc/MailScanner/. Their names are archives.filename.rules.conf, archives.filetype.rules.conf, filename.rules.conf and filetype.rules.conf. They are both samples and the actual working files configured by default. > I am having issues with allowing my users the ability to attach .PDF > and .DOC and other types of files, and either send or receive them. > > This issue only started after the upgrade to the 5.0 version. The default rules do not disallow .pdf or .doc files so there is something else going on. > Does someone have a clear explanation on how to go ahead and allow users to send/receive emails with .PDFs and .DOC (Word) files (just to start with)? Please tell us what happens when an email is sent with an attached .pdf or .doc file. What does MailScanner log in the system mail log and what does the received message contain. One possibility is the attachments are being denied if they seem to have double extensions, e.g. "Joes.file.pdf. I.e., with some exceptions if the actual extension is preceded by a period and 3 or 4 alphanumerics, it is a bad name. This is intended to stop things like "innocent_name.txt .exe" but stops a lot more than that. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner From mark at msapiro.net Mon Feb 6 21:05:58 2017 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 6 Feb 2017 13:05:58 -0800 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> Message-ID: <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> On 02/06/2017 12:20 PM, Paul Scott wrote: > Hello Mark, and thank you so much for your quick reply! > ... > As you'll see in the return message above, it is confusing, because there are two different issues being reported. > > One of the issues is as follows: > > The original e-mail attachment "the entire message" > was believed to be dangerous and/or infected by a virus and has been > replaced by this warning message. > > > The OTHER issue is as follows: > > At Mon Jan 9 14:51:21 2017 the scanner said: > Too many attachments in message > > > So, which is the true issue, and how to get this fixed, is the question. Thank you very much! Normally they would both be correct. MailScanner reporting that the configured virus scanner reported a problem and the virus scanner reporting the problem as "Too many attachments in message" There is a thread on this (involving you and me) in the archives starting at . Much of it is noise, but my reply at indicates that this situation is triggered by MailScanner's Maximum Attachments Per Message setting being exceeded. I haven't looked at this further since last November, but if that doesn't seem to be the issue, let me know and I'll check further. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From diederik at webrelated.nl Tue Feb 7 15:05:46 2017 From: diederik at webrelated.nl (diederik at webrelated.nl) Date: Tue, 7 Feb 2017 15:05:46 +0000 (UTC) Subject: Inconsistent SpamAssassin report In-Reply-To: 92A5BDFE-7EDF-41F8-813F-ACDD6F0F38F4@mailborder.com References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <92A5BDFE-7EDF-41F8-813F-ACDD6F0F38F4@mailborder.com> Message-ID: <20170207150546.608A2FA544@beta.mail.webrelated.nl> Dear Jerry, I have not changed the default setting for the max spamassassin size. It's at 200k. Best regards, Diederik > Does the size of the email exceed your setting for Max spamassassin Size ? > > - > Jerry Benton > www.mailborder.com > +1 - 844-436-6245 -- Diederik van den Burger From diederik at webrelated.nl Tue Feb 7 15:46:57 2017 From: diederik at webrelated.nl (diederik at webrelated.nl) Date: Tue, 7 Feb 2017 15:46:57 +0000 (UTC) Subject: Inconsistent SpamAssassin report In-Reply-To: References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> Message-ID: <20170207154657.EABB2FA54F@beta.mail.webrelated.nl> Dear Shawn, Indeed, running that command produces another set of results, so now I have three different SA reports on the same email. Interesting to note is the following things: 1. This command throws me the following warning: Feb 7 15:39:27.217 [3250] warn: config: path "/root/.spamassassin" is inaccessible: Permission denied Feb 7 15:39:27.218 [3250] warn: config: path "/root/.spamassassin/user_prefs" is inaccessible: Permission denied Feb 7 15:39:27.218 [3250] warn: config: default user preference file /root/.spamassassin/user_prefs not accessible: Permission denied 2. In found out that whenever I run MailScanner --lint in the /root directory, I get an error saying that SpamAssassin is not installed. 3. Similar to the previous point, whenever I run the command you proposed in the /root folder, I get the following errors: Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from @INC): Can't locate Mail/SpamAssassin/Plugin/SpamCop.pm: lib/Mail/SpamAssassin/Plugin/SpamCop.pm: Permission denied at (eval 35) line 1. Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from @INC): Can't locate Mail/SpamAssassin/Plugin/AutoLearnThreshold.pm: lib/Mail/SpamAssassin/Plugin/AutoLearnThreshold.pm: Permission denied at (eval 36) line 1. Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from @INC): Can't locate Mail/SpamAssassin/Plugin/WhiteListSubject.pm: lib/Mail/SpamAssassin/Plugin/WhiteListSubject.pm: Permission denied at (eval 37) line 1. Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from @INC): Can't locate Mail/SpamAssassin/Plugin/MIMEHeader.pm: lib/Mail/SpamAssassin/Plugin/MIMEHeader.pm: Permission denied at (eval 38) line 1. This continues for another 20 lines or so. I do not know whether point two and three are related to my initial problem, but I thought it was worth mentioning. Thanks in advance, Diederik > Diederik, > > Does this also produce yet a different set of results? > > sudo su - postfix -c "spamassassin -t -d < path/to/spamemail" From jerry.benton at mailborder.com Tue Feb 7 17:38:43 2017 From: jerry.benton at mailborder.com (Jerry Benton) Date: Tue, 7 Feb 2017 12:38:43 -0500 Subject: Inconsistent SpamAssassin report In-Reply-To: <20170207150546.608A2FA544@beta.mail.webrelated.nl> References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <92A5BDFE-7EDF-41F8-813F-ACDD6F0F38F4@mailborder.com> <20170207150546.608A2FA544@beta.mail.webrelated.nl> Message-ID: <5EC15346-DC7F-4DC0-BC3F-2F931FDC08E8@mailborder.com> Was the message that was clean bigger than 200k? If so, it was not scanned. - Jerry Benton www.mailborder.com +1 - 844-436-6245 > On Feb 7, 2017, at 10:05 AM, diederik at webrelated.nl wrote: > > Dear Jerry, > > I have not changed the default setting for the max spamassassin size. It's at 200k. > > Best regards, > Diederik > > >> Does the size of the email exceed your setting for Max spamassassin Size ? >> >> - >> Jerry Benton >> www.mailborder.com >> +1 - 844-436-6245 > > -- > Diederik van den Burger > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > -------------- next part -------------- An HTML attachment was scrubbed... URL: From diederik at webrelated.nl Tue Feb 7 17:45:32 2017 From: diederik at webrelated.nl (Diederik van den Burger) Date: Tue, 7 Feb 2017 18:45:32 +0100 Subject: Inconsistent SpamAssassin report In-Reply-To: <5EC15346-DC7F-4DC0-BC3F-2F931FDC08E8@mailborder.com> References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <92A5BDFE-7EDF-41F8-813F-ACDD6F0F38F4@mailborder.com> <20170207150546.608A2FA544@beta.mail.webrelated.nl> <5EC15346-DC7F-4DC0-BC3F-2F931FDC08E8@mailborder.com> Message-ID: The message was just 2.19kB, so I don't believe that's the problem. Regardless, MailWatch does say it was scanned, it's just that the score is different (and lower than I would expect) compared to when I run Spamassassin on the email manually. Best regards, Diederik > On 07 Feb 2017, at 18:38, Jerry Benton wrote: > > Was the message that was clean bigger than 200k? If so, it was not scanned. > > - > Jerry Benton > www.mailborder.com > +1 - 844-436-6245 > > > >> On Feb 7, 2017, at 10:05 AM, diederik at webrelated.nl wrote: >> >> Dear Jerry, >> >> I have not changed the default setting for the max spamassassin size. It's at 200k. >> >> Best regards, >> Diederik >> >> >>> Does the size of the email exceed your setting for Max spamassassin Size ? >>> >>> - >>> Jerry Benton >>> www.mailborder.com >>> +1 - 844-436-6245 >> >> -- >> Diederik van den Burger >> >> >> -- >> MailScanner mailing list >> mailscanner at lists.mailscanner.info >> http://lists.mailscanner.info/mailman/listinfo/mailscanner >> > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jerry.benton at mailborder.com Tue Feb 7 17:48:55 2017 From: jerry.benton at mailborder.com (Jerry Benton) Date: Tue, 7 Feb 2017 12:48:55 -0500 Subject: Inconsistent SpamAssassin report In-Reply-To: References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <92A5BDFE-7EDF-41F8-813F-ACDD6F0F38F4@mailborder.com> <20170207150546.608A2FA544@beta.mail.webrelated.nl> <5EC15346-DC7F-4DC0-BC3F-2F931FDC08E8@mailborder.com> Message-ID: You have to run spamassassin pointing to the /etc/MailScanner/spamassassin.conf file. - Jerry Benton www.mailborder.com +1 - 844-436-6245 > On Feb 7, 2017, at 12:45 PM, Diederik van den Burger wrote: > > The message was just 2.19kB, so I don't believe that's the problem. Regardless, MailWatch does say it was scanned, it's just that the score is different (and lower than I would expect) compared to when I run Spamassassin on the email manually. > > Best regards, > Diederik > > >> On 07 Feb 2017, at 18:38, Jerry Benton > wrote: >> >> Was the message that was clean bigger than 200k? If so, it was not scanned. >> >> - >> Jerry Benton >> www.mailborder.com >> +1 - 844-436-6245 >> >> >> >>> On Feb 7, 2017, at 10:05 AM, diederik at webrelated.nl wrote: >>> >>> Dear Jerry, >>> >>> I have not changed the default setting for the max spamassassin size. It's at 200k. >>> >>> Best regards, >>> Diederik >>> >>> >>>> Does the size of the email exceed your setting for Max spamassassin Size ? >>>> >>>> - >>>> Jerry Benton >>>> www.mailborder.com >>>> +1 - 844-436-6245 >>> >>> -- >>> Diederik van den Burger >>> >>> >>> -- >>> MailScanner mailing list >>> mailscanner at lists.mailscanner.info >>> http://lists.mailscanner.info/mailman/listinfo/mailscanner >>> >> >> >> >> -- >> MailScanner mailing list >> mailscanner at lists.mailscanner.info >> http://lists.mailscanner.info/mailman/listinfo/mailscanner >> > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > -------------- next part -------------- An HTML attachment was scrubbed... URL: From iversons at rushville.k12.in.us Tue Feb 7 17:52:32 2017 From: iversons at rushville.k12.in.us (Shawn Iverson) Date: Tue, 7 Feb 2017 12:52:32 -0500 Subject: Inconsistent SpamAssassin report In-Reply-To: <20170207154657.EABB2FA54F@beta.mail.webrelated.nl> References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <20170207154657.EABB2FA54F@beta.mail.webrelated.nl> Message-ID: Ahh yes, see Jerry's later reply. You need to point to the /etc/MailScanner/spamassassin.conf. Hence the error messages also in this case. Although, assuming MailScanner is running as the postfix user, you may need to continue looking into this deeper. On Tue, Feb 7, 2017 at 10:46 AM, Diederik van den Burger < diederik at webrelated.nl> wrote: > Dear Shawn, > > Indeed, running that command produces another set of results, so now I > have three different SA reports on the same email. Interesting to note is > the following things: > > 1. This command throws me the following warning: > Feb 7 15:39:27.217 [3250] warn: config: path "/root/.spamassassin" is > inaccessible: Permission denied > Feb 7 15:39:27.218 [3250] warn: config: path "/root/.spamassassin/user_prefs" > is inaccessible: Permission denied > Feb 7 15:39:27.218 [3250] warn: config: default user preference file > /root/.spamassassin/user_prefs not accessible: Permission denied > > 2. In found out that whenever I run MailScanner --lint in the /root > directory, I get an error saying that SpamAssassin is not installed. > > 3. Similar to the previous point, whenever I run the command you proposed > in the /root folder, I get the following errors: > Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from > @INC): Can't locate Mail/SpamAssassin/Plugin/SpamCop.pm: > lib/Mail/SpamAssassin/Plugin/SpamCop.pm: Permission denied at (eval 35) > line 1. > Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from > @INC): Can't locate Mail/SpamAssassin/Plugin/AutoLearnThreshold.pm: > lib/Mail/SpamAssassin/Plugin/AutoLearnThreshold.pm: Permission denied at > (eval 36) line 1. > Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from > @INC): Can't locate Mail/SpamAssassin/Plugin/WhiteListSubject.pm: > lib/Mail/SpamAssassin/Plugin/WhiteListSubject.pm: Permission denied at > (eval 37) line 1. > Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from > @INC): Can't locate Mail/SpamAssassin/Plugin/MIMEHeader.pm: > lib/Mail/SpamAssassin/Plugin/MIMEHeader.pm: Permission denied at (eval > 38) line 1. > > This continues for another 20 lines or so. I do not know whether point two > and three are related to my initial problem, but I thought it was worth > mentioning. > > > Thanks in advance, > Diederik > > > > > Diederik, > > > > Does this also produce yet a different set of results? > > > > sudo su - postfix -c "spamassassin -t -d < path/to/spamemail" > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > -- Shawn Iverson Director of Technology Rush County Schools 765-932-3901 x271 iversons at rushville.k12.in.us -------------- next part -------------- An HTML attachment was scrubbed... URL: From diederik at webrelated.nl Tue Feb 7 17:54:54 2017 From: diederik at webrelated.nl (Diederik van den Burger) Date: Tue, 7 Feb 2017 18:54:54 +0100 Subject: Inconsistent SpamAssassin report In-Reply-To: References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <92A5BDFE-7EDF-41F8-813F-ACDD6F0F38F4@mailborder.com> <20170207150546.608A2FA544@beta.mail.webrelated.nl> <5EC15346-DC7F-4DC0-BC3F-2F931FDC08E8@mailborder.com> Message-ID: <2576BAD9-4028-4D0D-9283-B55654D731C1@webrelated.nl> Thanks for your help by the way. When I run the following command: spamassassin -t -d -C /etc/MailScanner/spamassassin.conf < spamemail or even sudo su postfix -p -c "spamassassin -t -d -C /etc/MailScanner/spamassassin.conf < spamemail" I still get the following warnings: Feb 7 17:52:36.156 [4359] warn: config: path "/root/.spamassassin" is inaccessible: Permission denied Feb 7 17:52:36.157 [4359] warn: config: path "/root/.spamassassin/user_prefs" is inaccessible: Permission denied Feb 7 17:52:36.157 [4359] warn: config: default user preference file /root/.spamassassin/user_prefs not accessible: Permission denied And furthermore, I also don't get a spam report anymore. It says: "(no report template found)" Is this expected behaviour? Best regards, Diederik > On 07 Feb 2017, at 18:48, Jerry Benton wrote: > > You have to run spamassassin pointing to the /etc/MailScanner/spamassassin.conf file. > > - > Jerry Benton > www.mailborder.com > +1 - 844-436-6245 > > > >> On Feb 7, 2017, at 12:45 PM, Diederik van den Burger > wrote: >> >> The message was just 2.19kB, so I don't believe that's the problem. Regardless, MailWatch does say it was scanned, it's just that the score is different (and lower than I would expect) compared to when I run Spamassassin on the email manually. >> >> Best regards, >> Diederik >> >> >>> On 07 Feb 2017, at 18:38, Jerry Benton > wrote: >>> >>> Was the message that was clean bigger than 200k? If so, it was not scanned. >>> >>> - >>> Jerry Benton >>> www.mailborder.com >>> +1 - 844-436-6245 >>> >>> >>> >>>> On Feb 7, 2017, at 10:05 AM, diederik at webrelated.nl wrote: >>>> >>>> Dear Jerry, >>>> >>>> I have not changed the default setting for the max spamassassin size. It's at 200k. >>>> >>>> Best regards, >>>> Diederik >>>> >>>> >>>>> Does the size of the email exceed your setting for Max spamassassin Size ? >>>>> >>>>> - >>>>> Jerry Benton >>>>> www.mailborder.com >>>>> +1 - 844-436-6245 >>>> >>>> -- >>>> Diederik van den Burger >>>> >>>> >>>> -- >>>> MailScanner mailing list >>>> mailscanner at lists.mailscanner.info >>>> http://lists.mailscanner.info/mailman/listinfo/mailscanner >>>> >>> >>> >>> >>> -- >>> MailScanner mailing list >>> mailscanner at lists.mailscanner.info >>> http://lists.mailscanner.info/mailman/listinfo/mailscanner >>> >> >> >> >> -- >> MailScanner mailing list >> mailscanner at lists.mailscanner.info >> http://lists.mailscanner.info/mailman/listinfo/mailscanner >> > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sales at edenusa.com Tue Feb 7 17:55:04 2017 From: sales at edenusa.com (Paul Scott) Date: Tue, 7 Feb 2017 17:55:04 +0000 Subject: Inconsistent SpamAssassin report In-Reply-To: References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <20170207154657.EABB2FA54F@beta.mail.webrelated.nl> Message-ID: <482DA9E2372B7C61.4200b191-21a1-44b4-8ff5-373b29e67a49@mail.outlook.com> Where is this pointing to done? Paul Scott Eden USA, Inc. 866.501.3336 On Tue, Feb 7, 2017 at 9:53 AM -0800, "Shawn Iverson" > wrote: Ahh yes, see Jerry's later reply. You need to point to the /etc/MailScanner/spamassassin.conf. Hence the error messages also in this case. Although, assuming MailScanner is running as the postfix user, you may need to continue looking into this deeper. On Tue, Feb 7, 2017 at 10:46 AM, Diederik van den Burger > wrote: Dear Shawn, Indeed, running that command produces another set of results, so now I have three different SA reports on the same email. Interesting to note is the following things: 1. This command throws me the following warning: Feb 7 15:39:27.217 [3250] warn: config: path "/root/.spamassassin" is inaccessible: Permission denied Feb 7 15:39:27.218 [3250] warn: config: path "/root/.spamassassin/user_prefs" is inaccessible: Permission denied Feb 7 15:39:27.218 [3250] warn: config: default user preference file /root/.spamassassin/user_prefs not accessible: Permission denied 2. In found out that whenever I run MailScanner --lint in the /root directory, I get an error saying that SpamAssassin is not installed. 3. Similar to the previous point, whenever I run the command you proposed in the /root folder, I get the following errors: Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from @INC): Can't locate Mail/SpamAssassin/Plugin/SpamCop.pm: lib/Mail/SpamAssassin/Plugin/SpamCop.pm: Permission denied at (eval 35) line 1. Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from @INC): Can't locate Mail/SpamAssassin/Plugin/AutoLearnThreshold.pm: lib/Mail/SpamAssassin/Plugin/AutoLearnThreshold.pm: Permission denied at (eval 36) line 1. Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from @INC): Can't locate Mail/SpamAssassin/Plugin/WhiteListSubject.pm: lib/Mail/SpamAssassin/Plugin/WhiteListSubject.pm: Permission denied at (eval 37) line 1. Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from @INC): Can't locate Mail/SpamAssassin/Plugin/MIMEHeader.pm: lib/Mail/SpamAssassin/Plugin/MIMEHeader.pm: Permission denied at (eval 38) line 1. This continues for another 20 lines or so. I do not know whether point two and three are related to my initial problem, but I thought it was worth mentioning. Thanks in advance, Diederik > Diederik, > > Does this also produce yet a different set of results? > > sudo su - postfix -c "spamassassin -t -d < path/to/spamemail" -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner -- Shawn Iverson Director of Technology Rush County Schools 765-932-3901 x271 iversons at rushville.k12.in.us [https://docs.google.com/uc?export=download&id=0Bw5iD0ToYvs_cy1OZFNIZ0drYVU&revid=0Bw5iD0ToYvs_UitIcHVIWkJVVTl2VGpxVUE0d0FQcHBIRXk4PQ] -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From iversons at rushville.k12.in.us Tue Feb 7 18:08:47 2017 From: iversons at rushville.k12.in.us (Shawn Iverson) Date: Tue, 7 Feb 2017 13:08:47 -0500 Subject: Inconsistent SpamAssassin report In-Reply-To: <482DA9E2372B7C61.4200b191-21a1-44b4-8ff5-373b29e67a49@mail.outlook.com> References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <20170207154657.EABB2FA54F@beta.mail.webrelated.nl> <482DA9E2372B7C61.4200b191-21a1-44b4-8ff5-373b29e67a49@mail.outlook.com> Message-ID: Using the -c option. On Tue, Feb 7, 2017 at 12:55 PM, Paul Scott wrote: > Where is this pointing to done? > > Paul Scott > Eden USA, Inc. > 866.501.3336 <(866)%20501-3336> > > > > > On Tue, Feb 7, 2017 at 9:53 AM -0800, "Shawn Iverson" < > iversons at rushville.k12.in.us> wrote: > > Ahh yes, see Jerry's later reply. You need to point to the >> /etc/MailScanner/spamassassin.conf. Hence the error messages also in >> this case. Although, assuming MailScanner is running as the postfix user, >> you may need to continue looking into this deeper. >> >> On Tue, Feb 7, 2017 at 10:46 AM, Diederik van den Burger < >> diederik at webrelated.nl> wrote: >> >>> Dear Shawn, >>> >>> Indeed, running that command produces another set of results, so now I >>> have three different SA reports on the same email. Interesting to note is >>> the following things: >>> >>> 1. This command throws me the following warning: >>> Feb 7 15:39:27.217 [3250] warn: config: path "/root/.spamassassin" is >>> inaccessible: Permission denied >>> Feb 7 15:39:27.218 [3250] warn: config: path >>> "/root/.spamassassin/user_prefs" is inaccessible: Permission denied >>> Feb 7 15:39:27.218 [3250] warn: config: default user preference file >>> /root/.spamassassin/user_prefs not accessible: Permission denied >>> >>> 2. In found out that whenever I run MailScanner --lint in the /root >>> directory, I get an error saying that SpamAssassin is not installed. >>> >>> 3. Similar to the previous point, whenever I run the command you >>> proposed in the /root folder, I get the following errors: >>> Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from >>> @INC): Can't locate Mail/SpamAssassin/Plugin/SpamCop.pm: >>> lib/Mail/SpamAssassin/Plugin/SpamCop.pm: Permission denied at (eval 35) >>> line 1. >>> Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from >>> @INC): Can't locate Mail/SpamAssassin/Plugin/AutoLearnThreshold.pm: >>> lib/Mail/SpamAssassin/Plugin/AutoLearnThreshold.pm: Permission denied >>> at (eval 36) line 1. >>> Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from >>> @INC): Can't locate Mail/SpamAssassin/Plugin/WhiteListSubject.pm: >>> lib/Mail/SpamAssassin/Plugin/WhiteListSubject.pm: Permission denied at >>> (eval 37) line 1. >>> Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from >>> @INC): Can't locate Mail/SpamAssassin/Plugin/MIMEHeader.pm: >>> lib/Mail/SpamAssassin/Plugin/MIMEHeader.pm: Permission denied at (eval >>> 38) line 1. >>> >>> This continues for another 20 lines or so. I do not know whether point >>> two and three are related to my initial problem, but I thought it was worth >>> mentioning. >>> >>> >>> Thanks in advance, >>> Diederik >>> >>> >>> >>> > Diederik, >>> > >>> > Does this also produce yet a different set of results? >>> > >>> > sudo su - postfix -c "spamassassin -t -d < path/to/spamemail" >>> >>> >>> -- >>> MailScanner mailing list >>> mailscanner at lists.mailscanner.info >>> http://lists.mailscanner.info/mailman/listinfo/mailscanner >>> >>> >> >> >> -- >> Shawn Iverson >> Director of Technology >> Rush County Schools >> 765-932-3901 x271 <(765)%20932-3901> >> iversons at rushville.k12.in.us >> >> >> > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > -- Shawn Iverson Director of Technology Rush County Schools 765-932-3901 x271 iversons at rushville.k12.in.us -------------- next part -------------- An HTML attachment was scrubbed... URL: From iversons at rushville.k12.in.us Tue Feb 7 18:09:42 2017 From: iversons at rushville.k12.in.us (Shawn Iverson) Date: Tue, 7 Feb 2017 13:09:42 -0500 Subject: Inconsistent SpamAssassin report In-Reply-To: References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <20170207154657.EABB2FA54F@beta.mail.webrelated.nl> <482DA9E2372B7C61.4200b191-21a1-44b4-8ff5-373b29e67a49@mail.outlook.com> Message-ID: Correction -C (caps) On Tue, Feb 7, 2017 at 1:08 PM, Shawn Iverson wrote: > Using the -c option. > > On Tue, Feb 7, 2017 at 12:55 PM, Paul Scott wrote: > >> Where is this pointing to done? >> >> Paul Scott >> Eden USA, Inc. >> 866.501.3336 <(866)%20501-3336> >> >> >> >> >> On Tue, Feb 7, 2017 at 9:53 AM -0800, "Shawn Iverson" < >> iversons at rushville.k12.in.us> wrote: >> >> Ahh yes, see Jerry's later reply. You need to point to the >>> /etc/MailScanner/spamassassin.conf. Hence the error messages also in >>> this case. Although, assuming MailScanner is running as the postfix user, >>> you may need to continue looking into this deeper. >>> >>> On Tue, Feb 7, 2017 at 10:46 AM, Diederik van den Burger < >>> diederik at webrelated.nl> wrote: >>> >>>> Dear Shawn, >>>> >>>> Indeed, running that command produces another set of results, so now I >>>> have three different SA reports on the same email. Interesting to note is >>>> the following things: >>>> >>>> 1. This command throws me the following warning: >>>> Feb 7 15:39:27.217 [3250] warn: config: path "/root/.spamassassin" is >>>> inaccessible: Permission denied >>>> Feb 7 15:39:27.218 [3250] warn: config: path >>>> "/root/.spamassassin/user_prefs" is inaccessible: Permission denied >>>> Feb 7 15:39:27.218 [3250] warn: config: default user preference file >>>> /root/.spamassassin/user_prefs not accessible: Permission denied >>>> >>>> 2. In found out that whenever I run MailScanner --lint in the /root >>>> directory, I get an error saying that SpamAssassin is not installed. >>>> >>>> 3. Similar to the previous point, whenever I run the command you >>>> proposed in the /root folder, I get the following errors: >>>> Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from >>>> @INC): Can't locate Mail/SpamAssassin/Plugin/SpamCop.pm: >>>> lib/Mail/SpamAssassin/Plugin/SpamCop.pm: Permission denied at (eval >>>> 35) line 1. >>>> Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from >>>> @INC): Can't locate Mail/SpamAssassin/Plugin/AutoLearnThreshold.pm: >>>> lib/Mail/SpamAssassin/Plugin/AutoLearnThreshold.pm: Permission denied >>>> at (eval 36) line 1. >>>> Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from >>>> @INC): Can't locate Mail/SpamAssassin/Plugin/WhiteListSubject.pm: >>>> lib/Mail/SpamAssassin/Plugin/WhiteListSubject.pm: Permission denied at >>>> (eval 37) line 1. >>>> Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from >>>> @INC): Can't locate Mail/SpamAssassin/Plugin/MIMEHeader.pm: >>>> lib/Mail/SpamAssassin/Plugin/MIMEHeader.pm: Permission denied at (eval >>>> 38) line 1. >>>> >>>> This continues for another 20 lines or so. I do not know whether point >>>> two and three are related to my initial problem, but I thought it was worth >>>> mentioning. >>>> >>>> >>>> Thanks in advance, >>>> Diederik >>>> >>>> >>>> >>>> > Diederik, >>>> > >>>> > Does this also produce yet a different set of results? >>>> > >>>> > sudo su - postfix -c "spamassassin -t -d < path/to/spamemail" >>>> >>>> >>>> -- >>>> MailScanner mailing list >>>> mailscanner at lists.mailscanner.info >>>> http://lists.mailscanner.info/mailman/listinfo/mailscanner >>>> >>>> >>> >>> >>> -- >>> Shawn Iverson >>> Director of Technology >>> Rush County Schools >>> 765-932-3901 x271 <(765)%20932-3901> >>> iversons at rushville.k12.in.us >>> >>> >>> >> >> >> -- >> MailScanner mailing list >> mailscanner at lists.mailscanner.info >> http://lists.mailscanner.info/mailman/listinfo/mailscanner >> >> >> > > > -- > Shawn Iverson > Director of Technology > Rush County Schools > 765-932-3901 x271 <(765)%20932-3901> > iversons at rushville.k12.in.us > > > -- Shawn Iverson Director of Technology Rush County Schools 765-932-3901 x271 iversons at rushville.k12.in.us -------------- next part -------------- An HTML attachment was scrubbed... URL: From diederik at webrelated.nl Tue Feb 7 18:11:37 2017 From: diederik at webrelated.nl (Diederik van den Burger) Date: Tue, 7 Feb 2017 19:11:37 +0100 Subject: Inconsistent SpamAssassin report In-Reply-To: References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <20170207154657.EABB2FA54F@beta.mail.webrelated.nl> <482DA9E2372B7C61.4200b191-21a1-44b4-8ff5-373b29e67a49@mail.outlook.com> Message-ID: I've done this, see the thread with Jerry. Still seeing warnings and suddenly the SA report vanishes. > On 07 Feb 2017, at 19:09, Shawn Iverson wrote: > > Correction -C (caps) > > On Tue, Feb 7, 2017 at 1:08 PM, Shawn Iverson > wrote: > Using the -c option. > > On Tue, Feb 7, 2017 at 12:55 PM, Paul Scott > wrote: > Where is this pointing to done? > > > Paul Scott > Eden USA, Inc. > 866.501.3336 > > > > > On Tue, Feb 7, 2017 at 9:53 AM -0800, "Shawn Iverson" > wrote: > > Ahh yes, see Jerry's later reply. You need to point to the /etc/MailScanner/spamassassin.conf. Hence the error messages also in this case. Although, assuming MailScanner is running as the postfix user, you may need to continue looking into this deeper. > > On Tue, Feb 7, 2017 at 10:46 AM, Diederik van den Burger > wrote: > Dear Shawn, > > Indeed, running that command produces another set of results, so now I have three different SA reports on the same email. Interesting to note is the following things: > > 1. This command throws me the following warning: > Feb 7 15:39:27.217 [3250] warn: config: path "/root/.spamassassin" is inaccessible: Permission denied > Feb 7 15:39:27.218 [3250] warn: config: path "/root/.spamassassin/user_prefs" is inaccessible: Permission denied > Feb 7 15:39:27.218 [3250] warn: config: default user preference file /root/.spamassassin/user_prefs not accessible: Permission denied > > 2. In found out that whenever I run MailScanner --lint in the /root directory, I get an error saying that SpamAssassin is not installed. > > 3. Similar to the previous point, whenever I run the command you proposed in the /root folder, I get the following errors: > Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from @INC): Can't locate Mail/SpamAssassin/Plugin/SpamCop.pm : lib/Mail/SpamAssassin/Plugin/SpamCop.pm: Permission denied at (eval 35) line 1. > Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from @INC): Can't locate Mail/SpamAssassin/Plugin/AutoLearnThreshold.pm: lib/Mail/SpamAssassin/Plugin/AutoLearnThreshold.pm: Permission denied at (eval 36) line 1. > Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from @INC): Can't locate Mail/SpamAssassin/Plugin/WhiteListSubject.pm: lib/Mail/SpamAssassin/Plugin/WhiteListSubject.pm: Permission denied at (eval 37) line 1. > Feb 7 15:41:20.572 [3263] warn: plugin: failed to parse plugin (from @INC): Can't locate Mail/SpamAssassin/Plugin/MIMEHeader.pm : lib/Mail/SpamAssassin/Plugin/MIMEHeader.pm: Permission denied at (eval 38) line 1. > > This continues for another 20 lines or so. I do not know whether point two and three are related to my initial problem, but I thought it was worth mentioning. > > > Thanks in advance, > Diederik > > > > > Diederik, > > > > Does this also produce yet a different set of results? > > > > sudo su - postfix -c "spamassassin -t -d < path/to/spamemail" > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > > > -- > Shawn Iverson > Director of Technology > Rush County Schools > 765-932-3901 x271 > iversons at rushville.k12.in.us > > > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > > > > -- > Shawn Iverson > Director of Technology > Rush County Schools > 765-932-3901 x271 > iversons at rushville.k12.in.us > > > > > > -- > Shawn Iverson > Director of Technology > Rush County Schools > 765-932-3901 x271 > iversons at rushville.k12.in.us > > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailscanner at replies.cyways.com Tue Feb 7 18:11:54 2017 From: mailscanner at replies.cyways.com (Peter Lemieux) Date: Tue, 7 Feb 2017 13:11:54 -0500 Subject: Inconsistent SpamAssassin report In-Reply-To: <2576BAD9-4028-4D0D-9283-B55654D731C1@webrelated.nl> References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <92A5BDFE-7EDF-41F8-813F-ACDD6F0F38F4@mailborder.com> <20170207150546.608A2FA544@beta.mail.webrelated.nl> <5EC15346-DC7F-4DC0-BC3F-2F931FDC08E8@mailborder.com> <2576BAD9-4028-4D0D-9283-B55654D731C1@webrelated.nl> Message-ID: On most implementations only root will have access to /root/.spamassassin since /root usually has 700 permissions or more limited ones. Is MailScanner running as the postfix user or as root? If the latter, those permission errors shouldn't arise during scans run from MailScanner. What happens if you run your tests as root? Did I miss it, or did you not identify which platform you're running MailScanner on? I stick with CentOS for servers. In my experience MailScanner has installed and run flawlessly on that distribution for years. Peter On 02/07/2017 12:54 PM, Diederik van den Burger wrote: > Thanks for your help by the way. When I run the following command: > > spamassassin -t -d -C /etc/MailScanner/spamassassin.conf < spamemail > or even > sudo su postfix -p -c "spamassassin -t -d -C > /etc/MailScanner/spamassassin.conf < spamemail" > > I still get the following warnings: > > Feb 7 17:52:36.156 [4359] warn: config: path "/root/.spamassassin" is > inaccessible: Permission denied > Feb 7 17:52:36.157 [4359] warn: config: path > "/root/.spamassassin/user_prefs" is inaccessible: Permission denied > Feb 7 17:52:36.157 [4359] warn: config: default user preference file > /root/.spamassassin/user_prefs not accessible: Permission denied > > And furthermore, I also don't get a spam report anymore. It says: > "(no report template found)" > Is this expected behaviour? > > > Best regards, > Diederik From diederik at webrelated.nl Tue Feb 7 18:17:56 2017 From: diederik at webrelated.nl (Diederik van den Burger) Date: Tue, 7 Feb 2017 19:17:56 +0100 Subject: Inconsistent SpamAssassin report In-Reply-To: References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <92A5BDFE-7EDF-41F8-813F-ACDD6F0F38F4@mailborder.com> <20170207150546.608A2FA544@beta.mail.webrelated.nl> <5EC15346-DC7F-4DC0-BC3F-2F931FDC08E8@mailborder.com> <2576BAD9-4028-4D0D-9283-B55654D731C1@webrelated.nl> Message-ID: <488F45F3-1B66-48AE-8545-E36FAC9A433E@webrelated.nl> MailScanner is running as the postfix user. If I run the spamassassin command as root I do not see any errors. Is there any way to see logs on the spamassassin command as MailScanner runs it? And indeed I have not mentioned my OS yet. I am running Ubuntu 16.04.1. While I respect your advise on using CentOS, I am willing to try and debug this first. As MailScanner lists Ubuntu as supported, I believe it should work. If I really cannot figure it out I will think of switching to CentOS. Thanks though ;). > On 07 Feb 2017, at 19:11, Peter Lemieux wrote: > > On most implementations only root will have access to /root/.spamassassin since /root usually has 700 permissions or more limited ones. > > Is MailScanner running as the postfix user or as root? If the latter, those permission errors shouldn't arise during scans run from MailScanner. > > What happens if you run your tests as root? > > Did I miss it, or did you not identify which platform you're running MailScanner on? I stick with CentOS for servers. In my experience MailScanner has installed and run flawlessly on that distribution for years. > > Peter > > > On 02/07/2017 12:54 PM, Diederik van den Burger wrote: >> Thanks for your help by the way. When I run the following command: >> >> spamassassin -t -d -C /etc/MailScanner/spamassassin.conf < spamemail >> or even >> sudo su postfix -p -c "spamassassin -t -d -C >> /etc/MailScanner/spamassassin.conf < spamemail" >> >> I still get the following warnings: >> >> Feb 7 17:52:36.156 [4359] warn: config: path "/root/.spamassassin" is >> inaccessible: Permission denied >> Feb 7 17:52:36.157 [4359] warn: config: path >> "/root/.spamassassin/user_prefs" is inaccessible: Permission denied >> Feb 7 17:52:36.157 [4359] warn: config: default user preference file >> /root/.spamassassin/user_prefs not accessible: Permission denied >> >> And furthermore, I also don't get a spam report anymore. It says: >> "(no report template found)" >> Is this expected behaviour? >> >> >> Best regards, >> Diederik > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > From mark at msapiro.net Tue Feb 7 18:20:32 2017 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 7 Feb 2017 10:20:32 -0800 Subject: Inconsistent SpamAssassin report In-Reply-To: <488F45F3-1B66-48AE-8545-E36FAC9A433E@webrelated.nl> References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <92A5BDFE-7EDF-41F8-813F-ACDD6F0F38F4@mailborder.com> <20170207150546.608A2FA544@beta.mail.webrelated.nl> <5EC15346-DC7F-4DC0-BC3F-2F931FDC08E8@mailborder.com> <2576BAD9-4028-4D0D-9283-B55654D731C1@webrelated.nl> <488F45F3-1B66-48AE-8545-E36FAC9A433E@webrelated.nl> Message-ID: <58ee5957-b194-7be7-2f2a-f31efe1b4ed7@msapiro.net> On 02/07/2017 10:17 AM, Diederik van den Burger wrote: > > And indeed I have not mentioned my OS yet. I am running Ubuntu 16.04.1. While I respect your advise on using CentOS, I am willing to try and debug this first. As MailScanner lists Ubuntu as supported, I believe it should work. If I really cannot figure it out I will think of switching to CentOS. You shouldn't need to switch. MailScanner runs fine for me on Ubuntu 16.04. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mailscanner at replies.cyways.com Tue Feb 7 18:39:32 2017 From: mailscanner at replies.cyways.com (Peter Lemieux) Date: Tue, 7 Feb 2017 13:39:32 -0500 Subject: Inconsistent SpamAssassin report In-Reply-To: <488F45F3-1B66-48AE-8545-E36FAC9A433E@webrelated.nl> References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <92A5BDFE-7EDF-41F8-813F-ACDD6F0F38F4@mailborder.com> <20170207150546.608A2FA544@beta.mail.webrelated.nl> <5EC15346-DC7F-4DC0-BC3F-2F931FDC08E8@mailborder.com> <2576BAD9-4028-4D0D-9283-B55654D731C1@webrelated.nl> <488F45F3-1B66-48AE-8545-E36FAC9A433E@webrelated.nl> Message-ID: I can see running the incoming daemon as the postfix user, but I don't see any reason to run MailScanner itself that way. PL On 02/07/2017 01:17 PM, Diederik van den Burger wrote: > MailScanner is running as the postfix user. If I run the spamassassin > command as root I do not see any errors. Is there any way to see logs on > the spamassassin command as MailScanner runs it? From mark at msapiro.net Tue Feb 7 19:10:11 2017 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 7 Feb 2017 11:10:11 -0800 Subject: Inconsistent SpamAssassin report In-Reply-To: References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <92A5BDFE-7EDF-41F8-813F-ACDD6F0F38F4@mailborder.com> <20170207150546.608A2FA544@beta.mail.webrelated.nl> <5EC15346-DC7F-4DC0-BC3F-2F931FDC08E8@mailborder.com> <2576BAD9-4028-4D0D-9283-B55654D731C1@webrelated.nl> <488F45F3-1B66-48AE-8545-E36FAC9A433E@webrelated.nl> Message-ID: On 02/07/2017 10:39 AM, Peter Lemieux wrote: > I can see running the incoming daemon as the postfix user, but I don't see > any reason to run MailScanner itself that way. MailScanner runs as the postfix user so it can dequeue messages from Postfix's hold queue and after scanning queue them in Postfix's incoming queue. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From sales at edenusa.com Tue Feb 7 21:16:53 2017 From: sales at edenusa.com (Paul Scott) Date: Tue, 7 Feb 2017 21:16:53 +0000 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> Message-ID: Hello Mark, Just so that you (and others) know, I have fixed this issue, but not in a way that you may suspect. To make things very clear, here is what I found: 1. I already had the number of attachments allowed set to allow as many as a client wishes (the -1 setting). 2. I already had virus scanning turned OFF, as in the following. # If you want to be able to switch scanning on/off for different users or # different domains, set this to the filename of a ruleset. # This can also be the filename of a ruleset. Virus Scanning = no These settings are the two obvious areas as reported by the returned message, which I have shared with everybody. So, I setup the file attachments area to the following, and it worked (i.e., now clients can send and receive attachments again): Allow any attachment filenames matching any of the patterns listed here. # If this setting is empty, it is ignored and no matches are made. # This can also be the filename of a ruleset. Allow Filenames = \.txt$ \.pdf$ \.doc$ # Deny any attachment filenames matching any of the patterns listed here. # If this setting is empty, it is ignored and no matches are made. # This can also be the filename of a ruleset. Deny Filenames = # # Set where to find the attachment filename ruleset. # The structure of this file is explained elsewhere, but it is used to # accept or reject file attachments based on their name, regardless of # whether they are infected or not. # # This can also point to a ruleset, but the ruleset filename must end in # ".rules" so that MailScanner can determine if the filename given is # a ruleset or not! #Filename Rules = %etc-dir%/filename.rules Filename Rules = # To simplify web-based configuration systems, there are now two extra # settings here. They are both intended for use with normal rulesets # that you would expect to find in %rules-dir%. The first gives a list # of patterns to match against the attachment filetypes, and a filetype # is allowed if it matches any of these patterns. The second gives the # the equivalent list for patterns that are used to deny filetypes. # If either of these match at all, then filetype.rules.conf is ignored # for that filetype. # So you can easily have a set like this: # Allow Filetypes = script postscript # Deny Filetypes = executable MPEG # Allow MIME Filetypes = text/plain text/html # Deny MIME Filetypes = dosexec # which is a lot simpler than having to handle filetype.rules.conf! # It is far simpler when you want to change the allowed+denied list for # different domains/addresses, as you can use the filetype of a simple # ruleset here instead. # Allow any attachment filetypes matching any of the patterns listed here. # If this setting is empty, it is ignored and no matches are made. # This can also be the filename of a ruleset. Allow Filetypes = # Allow any attachment MIME types matching any of the patterns listed here. # If this setting is empty, it is ignored and no matches are made. # This can also be the filename of a ruleset. Allow File MIME Types = # Deny any attachment filetypes matching any of the patterns listed here. # If this setting is empty, it is ignored and no matches are made. # This can also be the filename of a ruleset. Deny Filetypes = # Deny any attachment MIME types matching any of the patterns listed here. # If this setting is empty, it is ignored and no matches are made. # This can also be the filename of a ruleset. Deny File MIME Types = # Set where to find the attachment filetype ruleset. # The structure of this file is explained elsewhere, but it is used to # accept or reject file attachments based on their content as determined # by the "file" command, regardless of whether they are infected or not. # # This can also point to a ruleset, but the ruleset filename must end in # ".rules" so that MailScanner can determine if the filename given is # a ruleset or not! # # To disable this feature, set this to just "Filetype Rules =" or set # the location of the file command to a blank string. #Filetype Rules = %etc-dir%/filetype.rules Filetype Rules = Basically, turning everything off. However, I did find another issue, and that is that the standard way we use to restart MailScanner has changed. I tried this: [root at mail MailScanner]#service mailscanner restart Which appeared to restart the MailScanner correctly, but processing no longer worked. I had to reboot the machine, which caused a major issue, and had to drive 100+ miles to the server room to manually start it up again. What is the recommended way of getting MailScanner properly restarted, after making configuration file changes? Thank you again very much for your help! Sincerely, Paul Scott, Engineer Eden USA, Incorporated Event Production Services Since 1995 Los Angeles-Las Vegas-New York sales at edenusa.com?OR?edenusasales at gmail.com Telephone(s): 866.501.3336 OR 951.505.6967 Fax: 866.502.3336? WEBSITE: https://www.edenusa.com FACEBOOK: http://www.facebook.com/edenusainc -----Original Message----- From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Mark Sapiro Sent: Monday, February 06, 2017 1:06 PM To: mailscanner at lists.mailscanner.info Subject: Re: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? On 02/06/2017 12:20 PM, Paul Scott wrote: > Hello Mark, and thank you so much for your quick reply! > ... > As you'll see in the return message above, it is confusing, because there are two different issues being reported. > > One of the issues is as follows: > > The original e-mail attachment "the entire message" > was believed to be dangerous and/or infected by a virus and has been > replaced by this warning message. > > > The OTHER issue is as follows: > > At Mon Jan 9 14:51:21 2017 the scanner said: > Too many attachments in message > > > So, which is the true issue, and how to get this fixed, is the question. Thank you very much! Normally they would both be correct. MailScanner reporting that the configured virus scanner reported a problem and the virus scanner reporting the problem as "Too many attachments in message" There is a thread on this (involving you and me) in the archives starting at . Much of it is noise, but my reply at indicates that this situation is triggered by MailScanner's Maximum Attachments Per Message setting being exceeded. I haven't looked at this further since last November, but if that doesn't seem to be the issue, let me know and I'll check further. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner From mark at msapiro.net Tue Feb 7 21:28:55 2017 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 7 Feb 2017 13:28:55 -0800 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> Message-ID: <1813f6fc-8854-071c-105e-dee269789772@msapiro.net> On 02/07/2017 01:16 PM, Paul Scott wrote: > > Basically, turning everything off. However, I did find another issue, and that is that the standard way we use to restart MailScanner has changed. I tried this: > > [root at mail MailScanner]#service mailscanner restart > > Which appeared to restart the MailScanner correctly, but processing no longer worked. I had to reboot the machine, which caused a major issue, and had to drive 100+ miles to the server room to manually start it up again. > > What is the recommended way of getting MailScanner properly restarted, after making configuration file changes? It is what you did. Namely, service mailscanner restart Why it didn't work, I can't say. There have been changes from MailScanner V4 to V5 in that restarting, starting and stopping the MTA is decoupled from restarting, starting and stopping MailScanner. In order to say more, I'd need to know what your MTA is and the contents of /etc/init.d/mailscanner. Also, the contents of the system mail log from around the time you did the service mailscanner restart might have clues. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From sales at edenusa.com Wed Feb 8 23:39:42 2017 From: sales at edenusa.com (Paul Scott) Date: Wed, 8 Feb 2017 23:39:42 +0000 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: <1813f6fc-8854-071c-105e-dee269789772@msapiro.net> References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> <1813f6fc-8854-071c-105e-dee269789772@msapiro.net> Message-ID: Hello Mark, Our MTA is Sendmail. The contents of the /etc/init.d/mailscanner file are massive and difficult to cut and paste here. So I don't know how I am going to fix that issue. However, that is secondary to the attachment issue. Unfortunately, in the meantime, I also had another incident where a sender sending an attachment resulted in this bounce-back email again (I added those "--START OF MESSAGE-- and --END..." banners): --START OF MESSAGE-- Warning: This message has had one or more attachments removed Warning: (the entire message). Warning: Please read the "EdenUSAInc-Attachment-Warning.txt" attachment(s) for more information. This is a message from the MailScanner E-Mail Virus Protection Service ---------------------------------------------------------------------- The original e-mail attachment "the entire message" was believed to be dangerous and/or infected by a virus and has been replaced by this warning message. Due to limitations placed on us by the Regulation of Investigatory Powers Act 2000, we were unable to keep a copy of the infected attachment. Please ask the sender of the message to disinfect their original version and send you a clean copy. At Wed Feb 8 07:28:11 2017 the scanner said: Too many attachments in message -- Postmaster Eden USA, Inc. www.edenitservices.com For all your IT requirements visit: http://www.transtec.co.uk --END OF MESSAGE-- Also, where is that very last line coming from? "For all your IT requirements visit: http://www.transteck.co.uk" In fact, please also note that the "EdenUSAInc-Attacvhment-Warning.txt" attachment is not actually attached to the message. I really need to get this fixed. Do you have any more ideas? I simply need to SHUT OFF all file attachment scanning, and tell MailScanner somehow to stop doing anything at all with attachments. I just want to allow everything through, in terms of attachments. Thank you very much for your help. -----Original Message----- From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Mark Sapiro Sent: Tuesday, February 07, 2017 1:29 PM To: mailscanner at lists.mailscanner.info Subject: Re: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? On 02/07/2017 01:16 PM, Paul Scott wrote: > > Basically, turning everything off. However, I did find another issue, and that is that the standard way we use to restart MailScanner has changed. I tried this: > > [root at mail MailScanner]#service mailscanner restart > > Which appeared to restart the MailScanner correctly, but processing no longer worked. I had to reboot the machine, which caused a major issue, and had to drive 100+ miles to the server room to manually start it up again. > > What is the recommended way of getting MailScanner properly restarted, after making configuration file changes? It is what you did. Namely, service mailscanner restart Why it didn't work, I can't say. There have been changes from MailScanner V4 to V5 in that restarting, starting and stopping the MTA is decoupled from restarting, starting and stopping MailScanner. In order to say more, I'd need to know what your MTA is and the contents of /etc/init.d/mailscanner. Also, the contents of the system mail log from around the time you did the service mailscanner restart might have clues. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner From mark at msapiro.net Thu Feb 9 16:30:41 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 9 Feb 2017 08:30:41 -0800 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> <1813f6fc-8854-071c-105e-dee269789772@msapiro.net> Message-ID: <378148dd-1f8e-5eb2-8267-900903ac4080@msapiro.net> On 02/08/2017 03:39 PM, Paul Scott wrote: > > Unfortunately, in the meantime, I also had another incident where a sender sending an attachment resulted in this bounce-back email again (I added those "--START OF MESSAGE-- and --END..." banners): > > > --START OF MESSAGE-- > Warning: This message has had one or more attachments removed > Warning: (the entire message). > Warning: Please read the "EdenUSAInc-Attachment-Warning.txt" attachment(s) for more information. > > This is a message from the MailScanner E-Mail Virus Protection Service > ---------------------------------------------------------------------- > The original e-mail attachment "the entire message" > was believed to be dangerous and/or infected by a virus and has been replaced by this warning message. > > Due to limitations placed on us by the Regulation of Investigatory Powers Act 2000, we were unable to keep a copy of the infected attachment. Please ask the sender of the message to disinfect their original version and send you a clean copy. > > At Wed Feb 8 07:28:11 2017 the scanner said: > Too many attachments in message > > -- > Postmaster > Eden USA, Inc. > www.edenitservices.com > > For all your IT requirements visit: http://www.transtec.co.uk > --END OF MESSAGE-- I am unable to duplicate this exactly, so I can't help much, but in another post you said > 1. I already had the number of attachments allowed set to allow as many as a client wishes (the -1 setting). If you are thinking of "Maximum Attachment Size", thois is OK, but if you really mean "Maximum Attachments Per Message", there is no "unlimited" value, but '-1' might be interpreted as a very large, unsigned number, so it might be OK. > Also, where is that very last line coming from? "For all your IT requirements visit: http://www.transteck.co.uk" >From some ISP's MTA, either the sender or the recipient of the message. > I really need to get this fixed. Do you have any more ideas? I simply need to SHUT OFF all file attachment scanning, and tell MailScanner somehow to stop doing anything at all with attachments. I just want to allow everything through, in terms of attachments. What does MailScanner log in the mail log for this message? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Thu Feb 9 19:49:41 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 9 Feb 2017 11:49:41 -0800 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: References: Message-ID: On 02/08/2017 03:39 PM, Paul Scott wrote: > > Our MTA is Sendmail. See and . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From sales at edenusa.com Fri Feb 10 05:28:44 2017 From: sales at edenusa.com (Paul Scott) Date: Fri, 10 Feb 2017 05:28:44 +0000 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: <378148dd-1f8e-5eb2-8267-900903ac4080@msapiro.net> References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> <1813f6fc-8854-071c-105e-dee269789772@msapiro.net> <378148dd-1f8e-5eb2-8267-900903ac4080@msapiro.net> Message-ID: Hello Mark, I pretty much managed to get mailscanner to restart a bit better. Still working on that, but I think I can nail it eventually. With regards to the attachments issue, I think I might finally be starting to get to the bottom of this. Here is the entry from the log which corresponds to the generation of the odd message that my clients get when a sender sends an email with attachments: Feb 8 15:41:46 mail MailScanner[14031]: Message v18NfGNg014804 from 216.205.24.106 (betty.tran at ioausa.com) to mp-eng.com is too big for spam checks (1572191 > 150000 bytes) So, of course when an email has attachments, it is quite large. This message is generated incorrectly, for two reasons: 1. It is not the NUMBER of attachments which is generating this message, but that is what the message says. 2. When the size of an email is too large for spam checks, it is supposed to be processed through without modification or error, as is indicated by this section of the MAILSCANNER.CONF file: # Spammers do not have the power to send out huge messages to everyone as # it costs them too much (more smaller messages makes more profit than less # very large messages). So if a message is bigger than a certain size, it # is highly unlikely to be spam. Limiting this saves a lot of time checking # huge messages. # Disable this option by setting it to a huge value. # This is measured in bytes. # This can also be the filename of a ruleset. Max Spam Check Size = 150k So there you have it. This is exactly where the breakdown is. Just because the message is too big for spam checks, the Mailscanner system is removing all of the attachments, and generating the bounce-back message to my clients. I suppose I could "Disable this option by setting it to a huge value", but eventually, the same thing will happen (e.g, when 10 large attachments are sent, which excess the new setting). I honestly think there is a bug here somewhere, or something not right in the programming or configuration logic, or at the very least, the wrong message is being generated and the client is being penalized by their valid email being rejected. In addition, the file that the message claims to be attached (EdenUSAInc-Attachment-Warning.txt), does NOT exist anywhere on the server's HD. At any rate, something is just not right here. Please let me know. Thank you! Paul Scott -----Original Message----- From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Mark Sapiro Sent: Thursday, February 09, 2017 8:31 AM To: mailscanner at lists.mailscanner.info Subject: Re: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? On 02/08/2017 03:39 PM, Paul Scott wrote: > > Unfortunately, in the meantime, I also had another incident where a sender sending an attachment resulted in this bounce-back email again (I added those "--START OF MESSAGE-- and --END..." banners): > > > --START OF MESSAGE-- > Warning: This message has had one or more attachments removed > Warning: (the entire message). > Warning: Please read the "EdenUSAInc-Attachment-Warning.txt" attachment(s) for more information. > > This is a message from the MailScanner E-Mail Virus Protection Service > ---------------------------------------------------------------------- > The original e-mail attachment "the entire message" > was believed to be dangerous and/or infected by a virus and has been replaced by this warning message. > > Due to limitations placed on us by the Regulation of Investigatory Powers Act 2000, we were unable to keep a copy of the infected attachment. Please ask the sender of the message to disinfect their original version and send you a clean copy. > > At Wed Feb 8 07:28:11 2017 the scanner said: > Too many attachments in message > > -- > Postmaster > Eden USA, Inc. > www.edenitservices.com > > For all your IT requirements visit: http://www.transtec.co.uk --END OF > MESSAGE-- I am unable to duplicate this exactly, so I can't help much, but in another post you said > 1. I already had the number of attachments allowed set to allow as many as a client wishes (the -1 setting). If you are thinking of "Maximum Attachment Size", thois is OK, but if you really mean "Maximum Attachments Per Message", there is no "unlimited" value, but '-1' might be interpreted as a very large, unsigned number, so it might be OK. > Also, where is that very last line coming from? "For all your IT requirements visit: http://www.transteck.co.uk" >From some ISP's MTA, either the sender or the recipient of the message. > I really need to get this fixed. Do you have any more ideas? I simply need to SHUT OFF all file attachment scanning, and tell MailScanner somehow to stop doing anything at all with attachments. I just want to allow everything through, in terms of attachments. What does MailScanner log in the mail log for this message? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner From iversons at rushville.k12.in.us Fri Feb 10 10:59:02 2017 From: iversons at rushville.k12.in.us (Shawn Iverson) Date: Fri, 10 Feb 2017 05:59:02 -0500 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> <1813f6fc-8854-071c-105e-dee269789772@msapiro.net> <378148dd-1f8e-5eb2-8267-900903ac4080@msapiro.net> Message-ID: I typically bump this value up a bit. On Fri, Feb 10, 2017 at 12:28 AM, Paul Scott wrote: > Hello Mark, > > I pretty much managed to get mailscanner to restart a bit better. Still > working on that, but I think I can nail it eventually. > > With regards to the attachments issue, I think I might finally be starting > to get to the bottom of this. Here is the entry from the log which > corresponds to the generation of the odd message that my clients get when a > sender sends an email with attachments: > > Feb 8 15:41:46 mail MailScanner[14031]: Message v18NfGNg014804 from > 216.205.24.106 (betty.tran at ioausa.com) to mp-eng.com is too big for spam > checks (1572191 > 150000 bytes) > > So, of course when an email has attachments, it is quite large. This > message is generated incorrectly, for two reasons: > > 1. It is not the NUMBER of attachments which is generating this message, > but that is what the message says. > > 2. When the size of an email is too large for spam checks, it is supposed > to be processed through without modification or error, as is indicated by > this section of the MAILSCANNER.CONF file: > > # Spammers do not have the power to send out huge messages to everyone as > # it costs them too much (more smaller messages makes more profit than less > # very large messages). So if a message is bigger than a certain size, it > # is highly unlikely to be spam. Limiting this saves a lot of time checking > # huge messages. > # Disable this option by setting it to a huge value. > # This is measured in bytes. > # This can also be the filename of a ruleset. > Max Spam Check Size = 150k > > > So there you have it. This is exactly where the breakdown is. Just > because the message is too big for spam checks, the Mailscanner system is > removing all of the attachments, and generating the bounce-back message to > my clients. > > I suppose I could "Disable this option by setting it to a huge value", but > eventually, the same thing will happen (e.g, when 10 large attachments are > sent, which excess the new setting). I honestly think there is a bug here > somewhere, or something not right in the programming or configuration > logic, or at the very least, the wrong message is being generated and the > client is being penalized by their valid email being rejected. > > In addition, the file that the message claims to be attached > (EdenUSAInc-Attachment-Warning.txt), does NOT exist anywhere on the > server's HD. > > At any rate, something is just not right here. > > Please let me know. > > Thank you! > Paul Scott > > > -----Original Message----- > From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists. > mailscanner.info] On Behalf Of Mark Sapiro > Sent: Thursday, February 09, 2017 8:31 AM > To: mailscanner at lists.mailscanner.info > Subject: Re: File(name|type) rules - was hijacked: "Allow Script Tags" > affects attachments? > > On 02/08/2017 03:39 PM, Paul Scott wrote: > > > > Unfortunately, in the meantime, I also had another incident where a > sender sending an attachment resulted in this bounce-back email again (I > added those "--START OF MESSAGE-- and --END..." banners): > > > > > > --START OF MESSAGE-- > > Warning: This message has had one or more attachments removed > > Warning: (the entire message). > > Warning: Please read the "EdenUSAInc-Attachment-Warning.txt" > attachment(s) for more information. > > > > This is a message from the MailScanner E-Mail Virus Protection Service > > ---------------------------------------------------------------------- > > The original e-mail attachment "the entire message" > > was believed to be dangerous and/or infected by a virus and has been > replaced by this warning message. > > > > Due to limitations placed on us by the Regulation of Investigatory > Powers Act 2000, we were unable to keep a copy of the infected attachment. > Please ask the sender of the message to disinfect their original version > and send you a clean copy. > > > > At Wed Feb 8 07:28:11 2017 the scanner said: > > Too many attachments in message > > > > -- > > Postmaster > > Eden USA, Inc. > > www.edenitservices.com > > > > For all your IT requirements visit: http://www.transtec.co.uk --END OF > > MESSAGE-- > > > I am unable to duplicate this exactly, so I can't help much, but in > another post you said > > > 1. I already had the number of attachments allowed set to allow as many > as a client wishes (the -1 setting). > > > If you are thinking of "Maximum Attachment Size", thois is OK, but if you > really mean "Maximum Attachments Per Message", there is no "unlimited" > value, but '-1' might be interpreted as a very large, unsigned number, so > it might be OK. > > > > Also, where is that very last line coming from? "For all your IT > requirements visit: http://www.transteck.co.uk" > > > From some ISP's MTA, either the sender or the recipient of the message. > > > > I really need to get this fixed. Do you have any more ideas? I simply > need to SHUT OFF all file attachment scanning, and tell MailScanner somehow > to stop doing anything at all with attachments. I just want to allow > everything through, in terms of attachments. > > > What does MailScanner log in the mail log for this message? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > -- Shawn Iverson Director of Technology Rush County Schools 765-932-3901 x271 iversons at rushville.k12.in.us -------------- next part -------------- An HTML attachment was scrubbed... URL: From glenn.steen at gmail.com Fri Feb 10 12:31:22 2017 From: glenn.steen at gmail.com (Glenn Steen) Date: Fri, 10 Feb 2017 13:31:22 +0100 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> <1813f6fc-8854-071c-105e-dee269789772@msapiro.net> <378148dd-1f8e-5eb2-8267-900903ac4080@msapiro.net> Message-ID: Scott, Could you please report the values for all your maximum settings? Do something like: egrep "^Max" /etc/MailScanner/MailScanner.conf There used to be a logical trap/bug in the setting of Maximum Spam Check Size and Maximum Spamassassin Size (both theese need be relatively "huge". or you'll mess up SpamAssassin results badly). With the latter a bit smaller than the former... I've got: Max Spam Check Size = 6500000 Max SpamAssassin Size = 3600000 Also, pay attention to the Spamassassin timout value. Further, a comment on your "I've turned everyting off" statement... This is sometimes easier said than done. There are a number of settings you need change, apart from the ones you mention. I suspect you would find more ... interresting... facts (and not alternative ones, at that) if you ensure that the failures actually do get quarantined. That way you can inspect the actual raw message/queue file for discrepacies. Cheers! -- -- Glenn 2017-02-10 6:28 GMT+01:00 Paul Scott : > Hello Mark, > > I pretty much managed to get mailscanner to restart a bit better. Still > working on that, but I think I can nail it eventually. > > With regards to the attachments issue, I think I might finally be starting > to get to the bottom of this. Here is the entry from the log which > corresponds to the generation of the odd message that my clients get when a > sender sends an email with attachments: > > Feb 8 15:41:46 mail MailScanner[14031]: Message v18NfGNg014804 from > 216.205.24.106 (betty.tran at ioausa.com) to mp-eng.com is too big for spam > checks (1572191 > 150000 bytes) > > So, of course when an email has attachments, it is quite large. This > message is generated incorrectly, for two reasons: > > 1. It is not the NUMBER of attachments which is generating this message, > but that is what the message says. > > 2. When the size of an email is too large for spam checks, it is supposed > to be processed through without modification or error, as is indicated by > this section of the MAILSCANNER.CONF file: > > # Spammers do not have the power to send out huge messages to everyone as > # it costs them too much (more smaller messages makes more profit than less > # very large messages). So if a message is bigger than a certain size, it > # is highly unlikely to be spam. Limiting this saves a lot of time checking > # huge messages. > # Disable this option by setting it to a huge value. > # This is measured in bytes. > # This can also be the filename of a ruleset. > Max Spam Check Size = 150k > > > So there you have it. This is exactly where the breakdown is. Just > because the message is too big for spam checks, the Mailscanner system is > removing all of the attachments, and generating the bounce-back message to > my clients. > > I suppose I could "Disable this option by setting it to a huge value", but > eventually, the same thing will happen (e.g, when 10 large attachments are > sent, which excess the new setting). I honestly think there is a bug here > somewhere, or something not right in the programming or configuration > logic, or at the very least, the wrong message is being generated and the > client is being penalized by their valid email being rejected. > > In addition, the file that the message claims to be attached > (EdenUSAInc-Attachment-Warning.txt), does NOT exist anywhere on the > server's HD. > > At any rate, something is just not right here. > > Please let me know. > > Thank you! > Paul Scott > > > -----Original Message----- > From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists. > mailscanner.info] On Behalf Of Mark Sapiro > Sent: Thursday, February 09, 2017 8:31 AM > To: mailscanner at lists.mailscanner.info > Subject: Re: File(name|type) rules - was hijacked: "Allow Script Tags" > affects attachments? > > On 02/08/2017 03:39 PM, Paul Scott wrote: > > > > Unfortunately, in the meantime, I also had another incident where a > sender sending an attachment resulted in this bounce-back email again (I > added those "--START OF MESSAGE-- and --END..." banners): > > > > > > --START OF MESSAGE-- > > Warning: This message has had one or more attachments removed > > Warning: (the entire message). > > Warning: Please read the "EdenUSAInc-Attachment-Warning.txt" > attachment(s) for more information. > > > > This is a message from the MailScanner E-Mail Virus Protection Service > > ---------------------------------------------------------------------- > > The original e-mail attachment "the entire message" > > was believed to be dangerous and/or infected by a virus and has been > replaced by this warning message. > > > > Due to limitations placed on us by the Regulation of Investigatory > Powers Act 2000, we were unable to keep a copy of the infected attachment. > Please ask the sender of the message to disinfect their original version > and send you a clean copy. > > > > At Wed Feb 8 07:28:11 2017 the scanner said: > > Too many attachments in message > > > > -- > > Postmaster > > Eden USA, Inc. > > www.edenitservices.com > > > > For all your IT requirements visit: http://www.transtec.co.uk --END OF > > MESSAGE-- > > > I am unable to duplicate this exactly, so I can't help much, but in > another post you said > > > 1. I already had the number of attachments allowed set to allow as many > as a client wishes (the -1 setting). > > > If you are thinking of "Maximum Attachment Size", thois is OK, but if you > really mean "Maximum Attachments Per Message", there is no "unlimited" > value, but '-1' might be interpreted as a very large, unsigned number, so > it might be OK. > > > > Also, where is that very last line coming from? "For all your IT > requirements visit: http://www.transteck.co.uk" > > > From some ISP's MTA, either the sender or the recipient of the message. > > > > I really need to get this fixed. Do you have any more ideas? I simply > need to SHUT OFF all file attachment scanning, and tell MailScanner somehow > to stop doing anything at all with attachments. I just want to allow > everything through, in terms of attachments. > > > What does MailScanner log in the mail log for this message? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > -- -- Glenn email: glenn < dot > steen < at > gmail < dot > com work: glenn < dot > steen < at > ap1 < dot > se -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at msapiro.net Fri Feb 10 16:04:05 2017 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 10 Feb 2017 08:04:05 -0800 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: References: <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> <1813f6fc-8854-071c-105e-dee269789772@msapiro.net> <378148dd-1f8e-5eb2-8267-900903ac4080@msapiro.net> Message-ID: On 02/09/2017 09:28 PM, Paul Scott wrote: > > With regards to the attachments issue, I think I might finally be starting to get to the bottom of this. Here is the entry from the log which corresponds to the generation of the odd message that my clients get when a sender sends an email with attachments: > > Feb 8 15:41:46 mail MailScanner[14031]: Message v18NfGNg014804 from 216.205.24.106 (betty.tran at ioausa.com) to mp-eng.com is too big for spam checks (1572191 > 150000 bytes) > > So, of course when an email has attachments, it is quite large. This message is generated incorrectly, for two reasons: The above message is not why you get the "too many attachments message". All that should do is skip SpamAssassin entirely for that message. What messages do you see if you grep the log for 'Feb 8 15:41:4.*MailScanner.14031' (dropping the last digit of the seconds and replacing [ with . are intentional). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From sales at edenusa.com Fri Feb 10 18:20:36 2017 From: sales at edenusa.com (Paul Scott) Date: Fri, 10 Feb 2017 18:20:36 +0000 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: References: <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> <1813f6fc-8854-071c-105e-dee269789772@msapiro.net> <378148dd-1f8e-5eb2-8267-900903ac4080@msapiro.net> Message-ID: Hello Mark, This is what I get: [root at mail log]# grep 'Feb 8 15:41:4.*MailScanner.14031' maillog Feb 8 15:41:46 mail MailScanner[14031]: Message v18NfGNg014804 from 216.205.24.106 (betty.tran at ioausa.com) to mp-eng.com is too big for spam checks (1572191 > 150000 bytes) Feb 8 15:41:46 mail MailScanner[14031]: Spam Checks: Found 1 spam messages Feb 8 15:41:48 mail MailScanner[14031]: Cleaned: Delivered 1 cleaned messages Feb 8 15:41:48 mail MailScanner[14031]: Deleted 2 messages from processing-database Feb 8 15:41:48 mail MailScanner[14031]: Logging message v18NfJdu014805 to SQL Feb 8 15:41:48 mail MailScanner[14031]: Logging message v18NfGNg014804 to SQL So, yes...the message was still delivered, along with the odd warning message, but the 7 attachments that she was sending were stripped and gone, and the message "Too many attachments" was in the warning message. And can you please let me know where this " EdenUSAInc-Attachment-Warning.txt" file is supposed to be, if it is supposed to be a part of the system, or? I know where the "EdenUSAInc" is coming from. It is as defined in the mailscanner.conf file here: Enter a short identifying name for your organisation below, this is # used to make the X-MailScanner headers unique for your organisation. # Multiple servers within one site should use an identical value here # to avoid adding multiple redundant headers where mail has passed # through several servers within your organisation. # # Note: Some Symantec scanners complain (incorrectly) about "." # ***** characters appearing in the names of headers. # Some other mail servers complain about "_" characters # appearing in the names of headers as well. # So don't put "." or "_" in this setting. # # **** RULE: It must not contain any spaces! **** %org-name% = EdenUSAInc The rest of the file name is being generated within MailScanner. Thank you again, Paul Scott Eden USA, Inc. -----Original Message----- From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Mark Sapiro Sent: Friday, February 10, 2017 8:04 AM To: mailscanner at lists.mailscanner.info Subject: Re: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? On 02/09/2017 09:28 PM, Paul Scott wrote: > > With regards to the attachments issue, I think I might finally be starting to get to the bottom of this. Here is the entry from the log which corresponds to the generation of the odd message that my clients get when a sender sends an email with attachments: > > Feb 8 15:41:46 mail MailScanner[14031]: Message v18NfGNg014804 from > 216.205.24.106 (betty.tran at ioausa.com) to mp-eng.com is too big for > spam checks (1572191 > 150000 bytes) > > So, of course when an email has attachments, it is quite large. This message is generated incorrectly, for two reasons: The above message is not why you get the "too many attachments message". All that should do is skip SpamAssassin entirely for that message. What messages do you see if you grep the log for 'Feb 8 15:41:4.*MailScanner.14031' (dropping the last digit of the seconds and replacing [ with . are intentional). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner From sales at edenusa.com Fri Feb 10 18:26:58 2017 From: sales at edenusa.com (Paul Scott) Date: Fri, 10 Feb 2017 18:26:58 +0000 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> <1813f6fc-8854-071c-105e-dee269789772@msapiro.net> <378148dd-1f8e-5eb2-8267-900903ac4080@msapiro.net> Message-ID: Hello Glenn, Thank you very much for your reply. Here is the result: [root at mail MailScanner]# egrep "^Max" /etc/MailScanner/MailScanner.conf Max Children = 5 Max Unscanned Bytes Per Scan = 100m Max Unsafe Bytes Per Scan = 50m Max Unscanned Messages Per Scan = 30 Max Unsafe Messages Per Scan = 30 Max Normal Queue Size = 30 Maximum Processing Attempts = 10 Maximum Attachments Per Message = 20 Maximum Message Size = %rules-dir%/max.message.size.rules Maximum Attachment Size = -1 Maximum Archive Depth = 0 Max Spam List Timeouts = 10 Max Spam Check Size = 15000k Max SpamAssassin Size = 40k Max SpamAssassin Timeouts = 90 Max Custom Spam Scanner Size = 20000 Max Custom Spam Scanner Timeouts = 10 [root at mail MailScanner]# NOTE: Does using the ?k? screw anything up? That?s what was in there before, but it was ?150k?, which was obviously too small. I see that your values are huge, but there is no ?k? indicated: Max Spam Check Size = 6500000 Max SpamAssassin Size = 3600000 And this is the content of the max.message.size.rules file, which is setting a max for this particular client to 1GB, and 20MB for everyone else: # # The following line specifies the default result used when none of the # other rules match. In this example, # Maximum Message Size = 0 # means that there is no limit to the size of the message. # To: *@mp-eng.com 1000M From: *@mp-eng.com 1000M FromOrTo: default 20M Thank you again! Paul Scott From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Glenn Steen Sent: Friday, February 10, 2017 4:31 AM To: MailScanner Discussion Subject: Re: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? Scott, Could you please report the values for all your maximum settings? Do something like: egrep "^Max" /etc/MailScanner/MailScanner.conf There used to be a logical trap/bug in the setting of Maximum Spam Check Size and Maximum Spamassassin Size (both theese need be relatively "huge". or you'll mess up SpamAssassin results badly). With the latter a bit smaller than the former... I've got: Max Spam Check Size = 6500000 Max SpamAssassin Size = 3600000 Also, pay attention to the Spamassassin timout value. Further, a comment on your "I've turned everyting off" statement... This is sometimes easier said than done. There are a number of settings you need change, apart from the ones you mention. I suspect you would find more ... interresting... facts (and not alternative ones, at that) if you ensure that the failures actually do get quarantined. That way you can inspect the actual raw message/queue file for discrepacies. Cheers! -- -- Glenn 2017-02-10 6:28 GMT+01:00 Paul Scott >: Hello Mark, I pretty much managed to get mailscanner to restart a bit better. Still working on that, but I think I can nail it eventually. With regards to the attachments issue, I think I might finally be starting to get to the bottom of this. Here is the entry from the log which corresponds to the generation of the odd message that my clients get when a sender sends an email with attachments: Feb 8 15:41:46 mail MailScanner[14031]: Message v18NfGNg014804 from 216.205.24.106 (betty.tran at ioausa.com) to mp-eng.com is too big for spam checks (1572191 > 150000 bytes) So, of course when an email has attachments, it is quite large. This message is generated incorrectly, for two reasons: 1. It is not the NUMBER of attachments which is generating this message, but that is what the message says. 2. When the size of an email is too large for spam checks, it is supposed to be processed through without modification or error, as is indicated by this section of the MAILSCANNER.CONF file: # Spammers do not have the power to send out huge messages to everyone as # it costs them too much (more smaller messages makes more profit than less # very large messages). So if a message is bigger than a certain size, it # is highly unlikely to be spam. Limiting this saves a lot of time checking # huge messages. # Disable this option by setting it to a huge value. # This is measured in bytes. # This can also be the filename of a ruleset. Max Spam Check Size = 150k So there you have it. This is exactly where the breakdown is. Just because the message is too big for spam checks, the Mailscanner system is removing all of the attachments, and generating the bounce-back message to my clients. I suppose I could "Disable this option by setting it to a huge value", but eventually, the same thing will happen (e.g, when 10 large attachments are sent, which excess the new setting). I honestly think there is a bug here somewhere, or something not right in the programming or configuration logic, or at the very least, the wrong message is being generated and the client is being penalized by their valid email being rejected. In addition, the file that the message claims to be attached (EdenUSAInc-Attachment-Warning.txt), does NOT exist anywhere on the server's HD. At any rate, something is just not right here. Please let me know. Thank you! Paul Scott -----Original Message----- From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Mark Sapiro Sent: Thursday, February 09, 2017 8:31 AM To: mailscanner at lists.mailscanner.info Subject: Re: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? On 02/08/2017 03:39 PM, Paul Scott wrote: > > Unfortunately, in the meantime, I also had another incident where a sender sending an attachment resulted in this bounce-back email again (I added those "--START OF MESSAGE-- and --END..." banners): > > > --START OF MESSAGE-- > Warning: This message has had one or more attachments removed > Warning: (the entire message). > Warning: Please read the "EdenUSAInc-Attachment-Warning.txt" attachment(s) for more information. > > This is a message from the MailScanner E-Mail Virus Protection Service > ---------------------------------------------------------------------- > The original e-mail attachment "the entire message" > was believed to be dangerous and/or infected by a virus and has been replaced by this warning message. > > Due to limitations placed on us by the Regulation of Investigatory Powers Act 2000, we were unable to keep a copy of the infected attachment. Please ask the sender of the message to disinfect their original version and send you a clean copy. > > At Wed Feb 8 07:28:11 2017 the scanner said: > Too many attachments in message > > -- > Postmaster > Eden USA, Inc. > www.edenitservices.com > > For all your IT requirements visit: http://www.transtec.co.uk --END OF > MESSAGE-- I am unable to duplicate this exactly, so I can't help much, but in another post you said > 1. I already had the number of attachments allowed set to allow as many as a client wishes (the -1 setting). If you are thinking of "Maximum Attachment Size", thois is OK, but if you really mean "Maximum Attachments Per Message", there is no "unlimited" value, but '-1' might be interpreted as a very large, unsigned number, so it might be OK. > Also, where is that very last line coming from? "For all your IT requirements visit: http://www.transteck.co.uk" From some ISP's MTA, either the sender or the recipient of the message. > I really need to get this fixed. Do you have any more ideas? I simply need to SHUT OFF all file attachment scanning, and tell MailScanner somehow to stop doing anything at all with attachments. I just want to allow everything through, in terms of attachments. What does MailScanner log in the mail log for this message? -- Mark Sapiro > The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner -- -- Glenn email: glenn < dot > steen < at > gmail < dot > com work: glenn < dot > steen < at > ap1 < dot > se -------------- next part -------------- An HTML attachment was scrubbed... URL: From sales at edenusa.com Fri Feb 10 19:12:14 2017 From: sales at edenusa.com (Paul Scott) Date: Fri, 10 Feb 2017 19:12:14 +0000 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> <1813f6fc-8854-071c-105e-dee269789772@msapiro.net> <378148dd-1f8e-5eb2-8267-900903ac4080@msapiro.net> Message-ID: Hello Glen, What do you set your Spamassissin timeout value to? Mine is set to 90 seconds. Thank you very much! Paul Scott From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Glenn Steen Sent: Friday, February 10, 2017 4:31 AM To: MailScanner Discussion Subject: Re: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? Scott, Could you please report the values for all your maximum settings? Do something like: egrep "^Max" /etc/MailScanner/MailScanner.conf There used to be a logical trap/bug in the setting of Maximum Spam Check Size and Maximum Spamassassin Size (both theese need be relatively "huge". or you'll mess up SpamAssassin results badly). With the latter a bit smaller than the former... I've got: Max Spam Check Size = 6500000 Max SpamAssassin Size = 3600000 Also, pay attention to the Spamassassin timout value. Further, a comment on your "I've turned everyting off" statement... This is sometimes easier said than done. There are a number of settings you need change, apart from the ones you mention. I suspect you would find more ... interresting... facts (and not alternative ones, at that) if you ensure that the failures actually do get quarantined. That way you can inspect the actual raw message/queue file for discrepacies. Cheers! -- -- Glenn 2017-02-10 6:28 GMT+01:00 Paul Scott >: Hello Mark, I pretty much managed to get mailscanner to restart a bit better. Still working on that, but I think I can nail it eventually. With regards to the attachments issue, I think I might finally be starting to get to the bottom of this. Here is the entry from the log which corresponds to the generation of the odd message that my clients get when a sender sends an email with attachments: Feb 8 15:41:46 mail MailScanner[14031]: Message v18NfGNg014804 from 216.205.24.106 (betty.tran at ioausa.com) to mp-eng.com is too big for spam checks (1572191 > 150000 bytes) So, of course when an email has attachments, it is quite large. This message is generated incorrectly, for two reasons: 1. It is not the NUMBER of attachments which is generating this message, but that is what the message says. 2. When the size of an email is too large for spam checks, it is supposed to be processed through without modification or error, as is indicated by this section of the MAILSCANNER.CONF file: # Spammers do not have the power to send out huge messages to everyone as # it costs them too much (more smaller messages makes more profit than less # very large messages). So if a message is bigger than a certain size, it # is highly unlikely to be spam. Limiting this saves a lot of time checking # huge messages. # Disable this option by setting it to a huge value. # This is measured in bytes. # This can also be the filename of a ruleset. Max Spam Check Size = 150k So there you have it. This is exactly where the breakdown is. Just because the message is too big for spam checks, the Mailscanner system is removing all of the attachments, and generating the bounce-back message to my clients. I suppose I could "Disable this option by setting it to a huge value", but eventually, the same thing will happen (e.g, when 10 large attachments are sent, which excess the new setting). I honestly think there is a bug here somewhere, or something not right in the programming or configuration logic, or at the very least, the wrong message is being generated and the client is being penalized by their valid email being rejected. In addition, the file that the message claims to be attached (EdenUSAInc-Attachment-Warning.txt), does NOT exist anywhere on the server's HD. At any rate, something is just not right here. Please let me know. Thank you! Paul Scott -----Original Message----- From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Mark Sapiro Sent: Thursday, February 09, 2017 8:31 AM To: mailscanner at lists.mailscanner.info Subject: Re: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? On 02/08/2017 03:39 PM, Paul Scott wrote: > > Unfortunately, in the meantime, I also had another incident where a sender sending an attachment resulted in this bounce-back email again (I added those "--START OF MESSAGE-- and --END..." banners): > > > --START OF MESSAGE-- > Warning: This message has had one or more attachments removed > Warning: (the entire message). > Warning: Please read the "EdenUSAInc-Attachment-Warning.txt" attachment(s) for more information. > > This is a message from the MailScanner E-Mail Virus Protection Service > ---------------------------------------------------------------------- > The original e-mail attachment "the entire message" > was believed to be dangerous and/or infected by a virus and has been replaced by this warning message. > > Due to limitations placed on us by the Regulation of Investigatory Powers Act 2000, we were unable to keep a copy of the infected attachment. Please ask the sender of the message to disinfect their original version and send you a clean copy. > > At Wed Feb 8 07:28:11 2017 the scanner said: > Too many attachments in message > > -- > Postmaster > Eden USA, Inc. > www.edenitservices.com > > For all your IT requirements visit: http://www.transtec.co.uk --END OF > MESSAGE-- I am unable to duplicate this exactly, so I can't help much, but in another post you said > 1. I already had the number of attachments allowed set to allow as many as a client wishes (the -1 setting). If you are thinking of "Maximum Attachment Size", thois is OK, but if you really mean "Maximum Attachments Per Message", there is no "unlimited" value, but '-1' might be interpreted as a very large, unsigned number, so it might be OK. > Also, where is that very last line coming from? "For all your IT requirements visit: http://www.transteck.co.uk" From some ISP's MTA, either the sender or the recipient of the message. > I really need to get this fixed. Do you have any more ideas? I simply need to SHUT OFF all file attachment scanning, and tell MailScanner somehow to stop doing anything at all with attachments. I just want to allow everything through, in terms of attachments. What does MailScanner log in the mail log for this message? -- Mark Sapiro > The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner -- -- Glenn email: glenn < dot > steen < at > gmail < dot > com work: glenn < dot > steen < at > ap1 < dot > se -------------- next part -------------- An HTML attachment was scrubbed... URL: From sales at edenusa.com Fri Feb 10 19:27:57 2017 From: sales at edenusa.com (Paul Scott) Date: Fri, 10 Feb 2017 19:27:57 +0000 Subject: Spamassassin Upgrade Message-ID: My CentOS 5 system is currently running Spam Assassin v3.2.5-1.el5, which is the latest as picked up by yum updates. My question is, if I were to upgrade manually to the very latest version of Spam Assassin (3.4.1), what would need to be done to insure that MailScanner uses it? Has anybody already gone through this exercise? Sincerely, Paul Scott, Engineer Eden USA, Incorporated Event Production Services Since 1995 Los Angeles-Las Vegas-New York sales at edenusa.com OR edenusasales at gmail.com Telephone(s): 866.501.3336 OR 951.505.6967 Fax: 866.502.3336 WEBSITE: https://www.edenusa.com FACEBOOK: http://www.facebook.com/edenusainc -------------- next part -------------- An HTML attachment was scrubbed... URL: From iversons at rushville.k12.in.us Fri Feb 10 19:34:49 2017 From: iversons at rushville.k12.in.us (Shawn Iverson) Date: Fri, 10 Feb 2017 14:34:49 -0500 Subject: Spamassassin Upgrade In-Reply-To: References: Message-ID: CentOS 5? On Fri, Feb 10, 2017 at 2:27 PM, Paul Scott wrote: > My CentOS 5 system is currently running Spam Assassin v3.2.5-1.el5, which > is the latest as picked up by yum updates. > > > > My question is, if I were to upgrade manually to the very latest version > of Spam Assassin (3.4.1), what would need to be done to insure that > MailScanner uses it? > > > > Has anybody already gone through this exercise? > > > > Sincerely, > > > > Paul Scott, Engineer > > Eden USA, Incorporated > Event Production Services Since 1995 > Los Angeles-Las Vegas-New York > sales at edenusa.com OR edenusasales at gmail.com > Telephone(s): 866.501.3336 <(866)%20501-3336> OR 951.505.6967 > <(951)%20505-6967> > Fax: 866.502.3336 <(866)%20502-3336> > > > > WEBSITE: https://www.edenusa.com > > FACEBOOK: http://www.facebook.com/edenusainc > > > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > -- Shawn Iverson Director of Technology Rush County Schools 765-932-3901 x271 iversons at rushville.k12.in.us -------------- next part -------------- An HTML attachment was scrubbed... URL: From sales at edenusa.com Fri Feb 10 21:40:29 2017 From: sales at edenusa.com (Paul Scott) Date: Fri, 10 Feb 2017 21:40:29 +0000 Subject: Spamassassin Upgrade In-Reply-To: References: Message-ID: Forget the 5, it is CentOS. [root at mail ~]# uname -a Linux mail.edenhosting.net 2.6.18-417.el5 #1 SMP Tue Dec 20 15:36:28 UTC 2016 i686 i686 i386 GNU/Linux [root at mail ~]# Thank you! Paul Scott From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Shawn Iverson Sent: Friday, February 10, 2017 11:35 AM To: MailScanner Discussion Subject: Re: Spamassassin Upgrade CentOS 5? On Fri, Feb 10, 2017 at 2:27 PM, Paul Scott > wrote: My CentOS 5 system is currently running Spam Assassin v3.2.5-1.el5, which is the latest as picked up by yum updates. My question is, if I were to upgrade manually to the very latest version of Spam Assassin (3.4.1), what would need to be done to insure that MailScanner uses it? Has anybody already gone through this exercise? Sincerely, Paul Scott, Engineer Eden USA, Incorporated Event Production Services Since 1995 Los Angeles-Las Vegas-New York sales at edenusa.com OR edenusasales at gmail.com Telephone(s): 866.501.3336 OR 951.505.6967 Fax: 866.502.3336 WEBSITE: https://www.edenusa.com FACEBOOK: http://www.facebook.com/edenusainc -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner -- Shawn Iverson Director of Technology Rush County Schools 765-932-3901 x271 iversons at rushville.k12.in.us [https://docs.google.com/uc?export=download&id=0Bw5iD0ToYvs_cy1OZFNIZ0drYVU&revid=0Bw5iD0ToYvs_UitIcHVIWkJVVTl2VGpxVUE0d0FQcHBIRXk4PQ] -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at msapiro.net Fri Feb 10 22:43:38 2017 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 10 Feb 2017 14:43:38 -0800 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: References: <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> <1813f6fc-8854-071c-105e-dee269789772@msapiro.net> <378148dd-1f8e-5eb2-8267-900903ac4080@msapiro.net> Message-ID: On 02/10/2017 10:20 AM, Paul Scott wrote: > Hello Mark, > > This is what I get: > > [root at mail log]# grep 'Feb 8 15:41:4.*MailScanner.14031' maillog > Feb 8 15:41:46 mail MailScanner[14031]: Message v18NfGNg014804 from 216.205.24.106 (betty.tran at ioausa.com) to mp-eng.com is too big for spam checks (1572191 > 150000 bytes) > Feb 8 15:41:46 mail MailScanner[14031]: Spam Checks: Found 1 spam messages > Feb 8 15:41:48 mail MailScanner[14031]: Cleaned: Delivered 1 cleaned messages > Feb 8 15:41:48 mail MailScanner[14031]: Deleted 2 messages from processing-database > Feb 8 15:41:48 mail MailScanner[14031]: Logging message v18NfJdu014805 to SQL > Feb 8 15:41:48 mail MailScanner[14031]: Logging message v18NfGNg014804 to SQL This is somewhat odd. I think the only log messages relating specifically to this message are: > Feb 8 15:41:46 mail MailScanner[14031]: Message v18NfGNg014804 from 216.205.24.106 (betty.tran at ioausa.com) to mp-eng.com is too big for spam checks (1572191 > 150000 bytes) > Feb 8 15:41:48 mail MailScanner[14031]: Cleaned: Delivered 1 cleaned messages > Feb 8 15:41:48 mail MailScanner[14031]: Logging message v18NfGNg014804 to SQL The messages: > Feb 8 15:41:46 mail MailScanner[14031]: Spam Checks: Found 1 spam messages > Feb 8 15:41:48 mail MailScanner[14031]: Logging message v18NfJdu014805 to SQL Appear to refer to a different message and the > Feb 8 15:41:48 mail MailScanner[14031]: Deleted 2 messages from processing-database message refers to both of them. I would expect to see additional log messages referring to the "cleaning" of v18NfGNg014804. > So, yes...the message was still delivered, along with the odd warning message, but the 7 attachments that she was sending were stripped and gone, and the message "Too many attachments" was in the warning message. > > And can you please let me know where this " EdenUSAInc-Attachment-Warning.txt" file is supposed to be, if it is supposed to be a part of the system, or? I know where the "EdenUSAInc" is coming from. It is as defined in the mailscanner.conf file here: I think you are seeing the EdenUSAInc-Attachment-Warning.txt file. It is what you refer to as the "odd warning message". Your MUA displays it inline, but it is probably an attached MIME part with name EdenUSAInc-Attachment-Warning.txt. It comes from the 'Deleted Virus Message Report' setting in your MailScanner configuration. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Feb 10 23:10:51 2017 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 10 Feb 2017 15:10:51 -0800 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: References: Message-ID: <47edf0a9-cedf-a2a8-977b-1c0e13072130@msapiro.net> Mark Sapiro wrote: > I think you are seeing the EdenUSAInc-Attachment-Warning.txt file. It is > what you refer to as the "odd warning message". Your MUA displays it > inline, but it is probably an attached MIME part with name > EdenUSAInc-Attachment-Warning.txt. Actually, since it is the "entire message" that's being replaced, it may not be a separate MIME part, but the rest of my reply still holds. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From sales at edenusa.com Sat Feb 11 00:49:20 2017 From: sales at edenusa.com (Paul Scott) Date: Sat, 11 Feb 2017 00:49:20 +0000 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: <47edf0a9-cedf-a2a8-977b-1c0e13072130@msapiro.net> References: <47edf0a9-cedf-a2a8-977b-1c0e13072130@msapiro.net> Message-ID: Well, unfortunately, this is just getting more and more confusing. Yes, it is a message that is odd because it obviously doesn't sense, as it has nothing to do with too many attachments. For now, I've been able to resolve the most nagging problem, and that is that my clients can now finally send up to 10 attachments, and up to a certain size, and this was fixed by increasing a value that doesn't appear to have anything to do with "number of attachments." All that I am saying here is that the message isn't clear and leads folks to look in the wrong places. I know that I am not at the top of this game, as my primary focus in life is staying alive (I have congestive heart disease and am on a ton of awful medications, some of which mess with my thinking and memory processes), and I struggle daily to run a profitable business. I know that I am sometimes ridiculed on this list for my stupidity, but I have nowhere else to go for help, so am very, very appreciative, and will continue to donate to the cause, regardless of the flak that I sometimes experience. So that said, please don't ever think that my comments here are in any way demeaning of this wonderful software! Sincerely, Paul Scott -----Original Message----- From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Mark Sapiro Sent: Friday, February 10, 2017 3:11 PM To: mailscanner at lists.mailscanner.info Subject: Re: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? Mark Sapiro wrote: > I think you are seeing the EdenUSAInc-Attachment-Warning.txt file. It > is what you refer to as the "odd warning message". Your MUA displays > it inline, but it is probably an attached MIME part with name > EdenUSAInc-Attachment-Warning.txt. Actually, since it is the "entire message" that's being replaced, it may not be a separate MIME part, but the rest of my reply still holds. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner From m.a.young at durham.ac.uk Sat Feb 11 12:29:42 2017 From: m.a.young at durham.ac.uk (M A Young) Date: Sat, 11 Feb 2017 12:29:42 +0000 (GMT) Subject: Spamassassin Upgrade In-Reply-To: References: Message-ID: On Fri, 10 Feb 2017, Paul Scott wrote: > My CentOS 5 system is currently running Spam Assassin v3.2.5-1.el5, which is > the latest as picked up by yum updates. > > My question is, if I were to upgrade manually to the very latest version of > Spam Assassin (3.4.1), what would need to be done to insure that MailScanner > uses it? > > Has anybody already gone through this exercise? I built myself a 3.4.1 rpm on CentOS 6 and that seems to work without any difficulty, however as support for CentOS 5 ends in March you should be seriously considering updating the whole system, and not just spamassassin. Michael Young From sales at edenusa.com Sat Feb 11 18:00:17 2017 From: sales at edenusa.com (Paul Scott) Date: Sat, 11 Feb 2017 18:00:17 +0000 Subject: Spamassassin Upgrade In-Reply-To: References: Message-ID: Hello Michael, There are just a few areas in MailScanner that "point" to Spamassassin, and a few things that have to be done in the Spamassassin installation. I just do not remember that they are. An entire OS upgrade is pretty drastic just to get to an update Spamassassin, very time consuming, and could potentially bring down the system for quite some time, even when very carefully instructing the installer to NOT upgrade the many packages that MailScanner uses. I have very custom Sendmail builds that I modified and built myself, as well as DRAC, popper, BIND and other manually compiled programs. As hardware is fairly inexpensive, of course, I could also purchase a new server and start fresh, install a fresh MailScanner and all of its add-ons, and slowly migrate from the older server to the new one, but wow, this is a massive exercise. So, when you did your 3.4.1 upgrade, do you remember having to do anything additional within MailScanner to ensure that it is using that install? Thank you very much! Paul Scott -----Original Message----- From: M A Young [mailto:m.a.young at durham.ac.uk] Sent: Saturday, February 11, 2017 4:30 AM To: Paul Scott Cc: MailScanner Discussion Subject: Re: Spamassassin Upgrade On Fri, 10 Feb 2017, Paul Scott wrote: > My CentOS 5 system is currently running Spam Assassin v3.2.5-1.el5, > which is the latest as picked up by yum updates. > > My question is, if I were to upgrade manually to the very latest > version of Spam Assassin (3.4.1), what would need to be done to insure > that MailScanner uses it? > > Has anybody already gone through this exercise? I built myself a 3.4.1 rpm on CentOS 6 and that seems to work without any difficulty, however as support for CentOS 5 ends in March you should be seriously considering updating the whole system, and not just spamassassin. Michael Young From sales at edenusa.com Sat Feb 11 19:13:44 2017 From: sales at edenusa.com (Paul Scott) Date: Sat, 11 Feb 2017 19:13:44 +0000 Subject: Spamassassin Upgrade In-Reply-To: References: Message-ID: Hello Shawn, Check this out: https://servertail.com/upgrading-centos-5-6-and-7/ Of course, I will begin planning on a course of action, but this is a very tedious operation. I did manage to just get ClamAV upgraded manually to the very latest version, and will do SpamAssasin next. Thank you very much! Paul Scott From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Shawn Iverson Sent: Friday, February 10, 2017 11:35 AM To: MailScanner Discussion Subject: Re: Spamassassin Upgrade CentOS 5? On Fri, Feb 10, 2017 at 2:27 PM, Paul Scott > wrote: My CentOS 5 system is currently running Spam Assassin v3.2.5-1.el5, which is the latest as picked up by yum updates. My question is, if I were to upgrade manually to the very latest version of Spam Assassin (3.4.1), what would need to be done to insure that MailScanner uses it? Has anybody already gone through this exercise? Sincerely, Paul Scott, Engineer Eden USA, Incorporated Event Production Services Since 1995 Los Angeles-Las Vegas-New York sales at edenusa.com OR edenusasales at gmail.com Telephone(s): 866.501.3336 OR 951.505.6967 Fax: 866.502.3336 WEBSITE: https://www.edenusa.com FACEBOOK: http://www.facebook.com/edenusainc -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner -- Shawn Iverson Director of Technology Rush County Schools 765-932-3901 x271 iversons at rushville.k12.in.us [https://docs.google.com/uc?export=download&id=0Bw5iD0ToYvs_cy1OZFNIZ0drYVU&revid=0Bw5iD0ToYvs_UitIcHVIWkJVVTl2VGpxVUE0d0FQcHBIRXk4PQ] -------------- next part -------------- An HTML attachment was scrubbed... URL: From glenn.steen at gmail.com Mon Feb 13 09:56:43 2017 From: glenn.steen at gmail.com (Glenn Steen) Date: Mon, 13 Feb 2017 10:56:43 +0100 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> <1813f6fc-8854-071c-105e-dee269789772@msapiro.net> <378148dd-1f8e-5eb2-8267-900903ac4080@msapiro.net> Message-ID: Hello Scott, The values I have are in bytes, hence the huge values (they're just 6.5MB and 3.6MB respectively... Which is quite enough for most spam, since spammers tend to keep things "short and sweet"). This is due to some old version of MailScanner not correctly understanding the SI multiple indicators ("k", "M" etc)... And since that is sure to work, why change it:-). Obvioulsy (from the log snippet you shared (adressed to Mark)), the 15000k specification doesnt work for you. Try putting the byte values in, restart MS and see what gives! Oh, and allowing GB e-mail... I imagine anything like that would be bounced pretty much from every other MTA on the planet;-) The Maximum Attachments Per Message would likely the interresting setting, provided that actually is the problem... And since the warning message indicates that it replaces "The whole message", that's likely not it (this can happen in a range of situations, where different functions in MailScanner detect something amiss with the body in it's entirety... MS will the replace the body with the warning as stated, but since there is no other text/body, that will be displayed as the actual body... Can be a bit confusing at first, but is actually a good indicator:)). Things that historically has had this effect on "the whole message" are filetype rules, UU-decoding/disabling etc. This is why it would be very valuable for you to actually quarantine the message, so that you can inspect the message file in the quarantine. The UUdecode stuff is very likely your culprit, since that tries to deduce if "the whole message" is actually a UUencoded message and should be passed through uudecode.... If this misfires, you might end up with a uudecode that returns some astronomical amount of "attachments" and renders "the whole message" suspect. Another possibility would be if the e-mail has a problem with MIME boundaries... Again, this would be easiest to see in the quarantined message/queue file. Cheers! -- -- Glenn 2017-02-10 19:26 GMT+01:00 Paul Scott : > Hello Glenn, > > > > Thank you very much for your reply. Here is the result: > > > > [root at mail MailScanner]# egrep "^Max" /etc/MailScanner/MailScanner.conf > > Max Children = 5 > > Max Unscanned Bytes Per Scan = 100m > > Max Unsafe Bytes Per Scan = 50m > > Max Unscanned Messages Per Scan = 30 > > Max Unsafe Messages Per Scan = 30 > > Max Normal Queue Size = 30 > > Maximum Processing Attempts = 10 > > Maximum Attachments Per Message = 20 > > Maximum Message Size = %rules-dir%/max.message.size.rules > > Maximum Attachment Size = -1 > > Maximum Archive Depth = 0 > > Max Spam List Timeouts = 10 > > Max Spam Check Size = 15000k > > Max SpamAssassin Size = 40k > > Max SpamAssassin Timeouts = 90 > > Max Custom Spam Scanner Size = 20000 > > Max Custom Spam Scanner Timeouts = 10 > > [root at mail MailScanner]# > > > > NOTE: Does using the ?k? screw anything up? That?s what was in there > before, but it was ?150k?, which was obviously too small. > > > > I see that your values are huge, but there is no ?k? indicated: > > > > Max Spam Check Size = 6500000 > Max SpamAssassin Size = 3600000 > > > > > > > > And this is the content of the max.message.size.rules file, which is > setting a max for this particular client to 1GB, and 20MB for everyone else: > > > > # > > # The following line specifies the default result used when none of the > > # other rules match. In this example, > > # Maximum Message Size = 0 > > # means that there is no limit to the size of the message. > > # > > > > To: *@mp-eng.com 1000M > > From: *@mp-eng.com 1000M > > > > FromOrTo: default 20M > > > > > > Thank you again! > > Paul Scott > > > > > > *From:* MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists. > mailscanner.info] *On Behalf Of *Glenn Steen > *Sent:* Friday, February 10, 2017 4:31 AM > *To:* MailScanner Discussion > > *Subject:* Re: File(name|type) rules - was hijacked: "Allow Script Tags" > affects attachments? > > > > Scott, > > Could you please report the values for all your maximum settings? Do > something like: > egrep "^Max" /etc/MailScanner/MailScanner.conf > > There used to be a logical trap/bug in the setting of Maximum Spam Check > Size and Maximum Spamassassin Size (both theese need be relatively "huge". > or you'll mess up SpamAssassin results badly). With the latter a bit > smaller than the former... I've got: > Max Spam Check Size = 6500000 > Max SpamAssassin Size = 3600000 > > Also, pay attention to the Spamassassin timout value. > > Further, a comment on your "I've turned everyting off" statement... This > is sometimes easier said than done. There are a number of settings you need > change, apart from the ones you mention. I suspect you would find more ... > interresting... facts (and not alternative ones, at that) if you ensure > that the failures actually do get quarantined. That way you can inspect the > actual raw message/queue file for discrepacies. > > Cheers! > -- > > -- Glenn > > > > 2017-02-10 6:28 GMT+01:00 Paul Scott : > > Hello Mark, > > I pretty much managed to get mailscanner to restart a bit better. Still > working on that, but I think I can nail it eventually. > > With regards to the attachments issue, I think I might finally be starting > to get to the bottom of this. Here is the entry from the log which > corresponds to the generation of the odd message that my clients get when a > sender sends an email with attachments: > > Feb 8 15:41:46 mail MailScanner[14031]: Message v18NfGNg014804 from > 216.205.24.106 (betty.tran at ioausa.com) to mp-eng.com is too big for spam > checks (1572191 > 150000 bytes) > > So, of course when an email has attachments, it is quite large. This > message is generated incorrectly, for two reasons: > > 1. It is not the NUMBER of attachments which is generating this message, > but that is what the message says. > > 2. When the size of an email is too large for spam checks, it is supposed > to be processed through without modification or error, as is indicated by > this section of the MAILSCANNER.CONF file: > > # Spammers do not have the power to send out huge messages to everyone as > # it costs them too much (more smaller messages makes more profit than less > # very large messages). So if a message is bigger than a certain size, it > # is highly unlikely to be spam. Limiting this saves a lot of time checking > # huge messages. > # Disable this option by setting it to a huge value. > # This is measured in bytes. > # This can also be the filename of a ruleset. > Max Spam Check Size = 150k > > > So there you have it. This is exactly where the breakdown is. Just > because the message is too big for spam checks, the Mailscanner system is > removing all of the attachments, and generating the bounce-back message to > my clients. > > I suppose I could "Disable this option by setting it to a huge value", but > eventually, the same thing will happen (e.g, when 10 large attachments are > sent, which excess the new setting). I honestly think there is a bug here > somewhere, or something not right in the programming or configuration > logic, or at the very least, the wrong message is being generated and the > client is being penalized by their valid email being rejected. > > In addition, the file that the message claims to be attached > (EdenUSAInc-Attachment-Warning.txt), does NOT exist anywhere on the > server's HD. > > At any rate, something is just not right here. > > Please let me know. > > Thank you! > Paul Scott > > > -----Original Message----- > From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists. > mailscanner.info] On Behalf Of Mark Sapiro > Sent: Thursday, February 09, 2017 8:31 AM > To: mailscanner at lists.mailscanner.info > Subject: Re: File(name|type) rules - was hijacked: "Allow Script Tags" > affects attachments? > > On 02/08/2017 03:39 PM, Paul Scott wrote: > > > > Unfortunately, in the meantime, I also had another incident where a > sender sending an attachment resulted in this bounce-back email again (I > added those "--START OF MESSAGE-- and --END..." banners): > > > > > > --START OF MESSAGE-- > > Warning: This message has had one or more attachments removed > > Warning: (the entire message). > > Warning: Please read the "EdenUSAInc-Attachment-Warning.txt" > attachment(s) for more information. > > > > This is a message from the MailScanner E-Mail Virus Protection Service > > ---------------------------------------------------------------------- > > The original e-mail attachment "the entire message" > > was believed to be dangerous and/or infected by a virus and has been > replaced by this warning message. > > > > Due to limitations placed on us by the Regulation of Investigatory > Powers Act 2000, we were unable to keep a copy of the infected attachment. > Please ask the sender of the message to disinfect their original version > and send you a clean copy. > > > > At Wed Feb 8 07:28:11 2017 the scanner said: > > Too many attachments in message > > > > -- > > Postmaster > > Eden USA, Inc. > > www.edenitservices.com > > > > For all your IT requirements visit: http://www.transtec.co.uk --END OF > > MESSAGE-- > > > I am unable to duplicate this exactly, so I can't help much, but in > another post you said > > > 1. I already had the number of attachments allowed set to allow as many > as a client wishes (the -1 setting). > > > If you are thinking of "Maximum Attachment Size", thois is OK, but if you > really mean "Maximum Attachments Per Message", there is no "unlimited" > value, but '-1' might be interpreted as a very large, unsigned number, so > it might be OK. > > > > Also, where is that very last line coming from? "For all your IT > requirements visit: http://www.transteck.co.uk" > > > From some ISP's MTA, either the sender or the recipient of the message. > > > > I really need to get this fixed. Do you have any more ideas? I simply > need to SHUT OFF all file attachment scanning, and tell MailScanner somehow > to stop doing anything at all with attachments. I just want to allow > everything through, in terms of attachments. > > > What does MailScanner log in the mail log for this message? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > > > -- > > -- Glenn > email: glenn < dot > steen < at > gmail < dot > com > work: glenn < dot > steen < at > ap1 < dot > se > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > -- -- Glenn email: glenn < dot > steen < at > gmail < dot > com work: glenn < dot > steen < at > ap1 < dot > se -------------- next part -------------- An HTML attachment was scrubbed... URL: From glenn.steen at gmail.com Mon Feb 13 10:00:43 2017 From: glenn.steen at gmail.com (Glenn Steen) Date: Mon, 13 Feb 2017 11:00:43 +0100 Subject: File(name|type) rules - was hijacked: "Allow Script Tags" affects attachments? In-Reply-To: References: <201702012129.41416.Antony.Stone@mailscanner.open.source.it> <5FBC86D5-8B63-42FE-82A6-514B1A96B0A6@mailborder.com> <7413fc7a-57e0-ebb8-9aea-af4fb696c2c4@msapiro.net> <21b9884c-b665-dc71-9891-ed23ef31f4c8@msapiro.net> <3e0710e8-c05e-8fef-8c83-ed76866dda7e@msapiro.net> <1d7f148c-4d1b-4438-9cb3-226c4dc5740e@msapiro.net> <1813f6fc-8854-071c-105e-dee269789772@msapiro.net> <378148dd-1f8e-5eb2-8267-900903ac4080@msapiro.net> Message-ID: It needs be so huge it most likely will never trigger (at least if you employ expiry on lagre volumes of data... If you have slow (filebased) expiry of your bayes data, a low value will never let you complete and expiry... amongst other things:-)). I have it set to: SpamAssassin Timeout = 600 Cheers! -- -- Glenn 2017-02-10 20:12 GMT+01:00 Paul Scott : > Hello Glen, > > > > What do you set your Spamassissin timeout value to? > > > > Mine is set to 90 seconds. > > > > Thank you very much! > > > > Paul Scott > > > > > > *From:* MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists. > mailscanner.info] *On Behalf Of *Glenn Steen > *Sent:* Friday, February 10, 2017 4:31 AM > *To:* MailScanner Discussion > > *Subject:* Re: File(name|type) rules - was hijacked: "Allow Script Tags" > affects attachments? > > > > Scott, > > Could you please report the values for all your maximum settings? Do > something like: > egrep "^Max" /etc/MailScanner/MailScanner.conf > > There used to be a logical trap/bug in the setting of Maximum Spam Check > Size and Maximum Spamassassin Size (both theese need be relatively "huge". > or you'll mess up SpamAssassin results badly). With the latter a bit > smaller than the former... I've got: > Max Spam Check Size = 6500000 > Max SpamAssassin Size = 3600000 > > Also, pay attention to the Spamassassin timout value. > > Further, a comment on your "I've turned everyting off" statement... This > is sometimes easier said than done. There are a number of settings you need > change, apart from the ones you mention. I suspect you would find more ... > interresting... facts (and not alternative ones, at that) if you ensure > that the failures actually do get quarantined. That way you can inspect the > actual raw message/queue file for discrepacies. > > Cheers! > -- > > -- Glenn > > > > 2017-02-10 6:28 GMT+01:00 Paul Scott : > > Hello Mark, > > I pretty much managed to get mailscanner to restart a bit better. Still > working on that, but I think I can nail it eventually. > > With regards to the attachments issue, I think I might finally be starting > to get to the bottom of this. Here is the entry from the log which > corresponds to the generation of the odd message that my clients get when a > sender sends an email with attachments: > > Feb 8 15:41:46 mail MailScanner[14031]: Message v18NfGNg014804 from > 216.205.24.106 (betty.tran at ioausa.com) to mp-eng.com is too big for spam > checks (1572191 > 150000 bytes) > > So, of course when an email has attachments, it is quite large. This > message is generated incorrectly, for two reasons: > > 1. It is not the NUMBER of attachments which is generating this message, > but that is what the message says. > > 2. When the size of an email is too large for spam checks, it is supposed > to be processed through without modification or error, as is indicated by > this section of the MAILSCANNER.CONF file: > > # Spammers do not have the power to send out huge messages to everyone as > # it costs them too much (more smaller messages makes more profit than less > # very large messages). So if a message is bigger than a certain size, it > # is highly unlikely to be spam. Limiting this saves a lot of time checking > # huge messages. > # Disable this option by setting it to a huge value. > # This is measured in bytes. > # This can also be the filename of a ruleset. > Max Spam Check Size = 150k > > > So there you have it. This is exactly where the breakdown is. Just > because the message is too big for spam checks, the Mailscanner system is > removing all of the attachments, and generating the bounce-back message to > my clients. > > I suppose I could "Disable this option by setting it to a huge value", but > eventually, the same thing will happen (e.g, when 10 large attachments are > sent, which excess the new setting). I honestly think there is a bug here > somewhere, or something not right in the programming or configuration > logic, or at the very least, the wrong message is being generated and the > client is being penalized by their valid email being rejected. > > In addition, the file that the message claims to be attached > (EdenUSAInc-Attachment-Warning.txt), does NOT exist anywhere on the > server's HD. > > At any rate, something is just not right here. > > Please let me know. > > Thank you! > Paul Scott > > > -----Original Message----- > From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists. > mailscanner.info] On Behalf Of Mark Sapiro > Sent: Thursday, February 09, 2017 8:31 AM > To: mailscanner at lists.mailscanner.info > Subject: Re: File(name|type) rules - was hijacked: "Allow Script Tags" > affects attachments? > > On 02/08/2017 03:39 PM, Paul Scott wrote: > > > > Unfortunately, in the meantime, I also had another incident where a > sender sending an attachment resulted in this bounce-back email again (I > added those "--START OF MESSAGE-- and --END..." banners): > > > > > > --START OF MESSAGE-- > > Warning: This message has had one or more attachments removed > > Warning: (the entire message). > > Warning: Please read the "EdenUSAInc-Attachment-Warning.txt" > attachment(s) for more information. > > > > This is a message from the MailScanner E-Mail Virus Protection Service > > ---------------------------------------------------------------------- > > The original e-mail attachment "the entire message" > > was believed to be dangerous and/or infected by a virus and has been > replaced by this warning message. > > > > Due to limitations placed on us by the Regulation of Investigatory > Powers Act 2000, we were unable to keep a copy of the infected attachment. > Please ask the sender of the message to disinfect their original version > and send you a clean copy. > > > > At Wed Feb 8 07:28:11 2017 the scanner said: > > Too many attachments in message > > > > -- > > Postmaster > > Eden USA, Inc. > > www.edenitservices.com > > > > For all your IT requirements visit: http://www.transtec.co.uk --END OF > > MESSAGE-- > > > I am unable to duplicate this exactly, so I can't help much, but in > another post you said > > > 1. I already had the number of attachments allowed set to allow as many > as a client wishes (the -1 setting). > > > If you are thinking of "Maximum Attachment Size", thois is OK, but if you > really mean "Maximum Attachments Per Message", there is no "unlimited" > value, but '-1' might be interpreted as a very large, unsigned number, so > it might be OK. > > > > Also, where is that very last line coming from? "For all your IT > requirements visit: http://www.transteck.co.uk" > > > From some ISP's MTA, either the sender or the recipient of the message. > > > > I really need to get this fixed. Do you have any more ideas? I simply > need to SHUT OFF all file attachment scanning, and tell MailScanner somehow > to stop doing anything at all with attachments. I just want to allow > everything through, in terms of attachments. > > > What does MailScanner log in the mail log for this message? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > > > -- > > -- Glenn > email: glenn < dot > steen < at > gmail < dot > com > work: glenn < dot > steen < at > ap1 < dot > se > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > -- -- Glenn email: glenn < dot > steen < at > gmail < dot > com work: glenn < dot > steen < at > ap1 < dot > se -------------- next part -------------- An HTML attachment was scrubbed... URL: From glenn.steen at gmail.com Mon Feb 13 10:23:17 2017 From: glenn.steen at gmail.com (Glenn Steen) Date: Mon, 13 Feb 2017 11:23:17 +0100 Subject: Spamassassin Upgrade In-Reply-To: References: Message-ID: Hello Scott, I do understand that the process of upgrading to CentOS 7 is ... daunting, and seem wasteful when all you need is a better SpamAssassin, but ... CentOS 5 has served you long and true, and should be put to rest;-) I did a new install on CentOS 7 when it was first released... It was a pain, especially the systemd stuff, and trying to cope with SElinux (maaany "local" rules:-)). But after that, it actually works very well. Sure, the whole toolchain need be updated and adjusted (and some things is simply done ... differently...:-)), but it is a good move, that will buy you peace of mind for a relatively long time. Trying to maintain a distro that is no longer supported... is a loosing battle/not worth your time, IMO. Cheers! -- -- Glenn 2017-02-11 20:13 GMT+01:00 Paul Scott : > Hello Shawn, > > > > Check this out: > > > > https://servertail.com/upgrading-centos-5-6-and-7/ > > > > Of course, I will begin planning on a course of action, but this is a very > tedious operation. > > > > I did manage to just get ClamAV upgraded manually to the very latest > version, and will do SpamAssasin next. > > > > Thank you very much! > > Paul Scott > > > > *From:* MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists. > mailscanner.info] *On Behalf Of *Shawn Iverson > *Sent:* Friday, February 10, 2017 11:35 AM > *To:* MailScanner Discussion > *Subject:* Re: Spamassassin Upgrade > > > > CentOS 5? > > > > On Fri, Feb 10, 2017 at 2:27 PM, Paul Scott wrote: > > My CentOS 5 system is currently running Spam Assassin v3.2.5-1.el5, which > is the latest as picked up by yum updates. > > > > My question is, if I were to upgrade manually to the very latest version > of Spam Assassin (3.4.1), what would need to be done to insure that > MailScanner uses it? > > > > Has anybody already gone through this exercise? > > > > Sincerely, > > > > Paul Scott, Engineer > > Eden USA, Incorporated > Event Production Services Since 1995 > Los Angeles-Las Vegas-New York > sales at edenusa.com OR edenusasales at gmail.com > Telephone(s): 866.501.3336 <(866)%20501-3336> OR 951.505.6967 > <(951)%20505-6967> > Fax: 866.502.3336 <(866)%20502-3336> > > > > WEBSITE: https://www.edenusa.com > > FACEBOOK: http://www.facebook.com/edenusainc > > > > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > > > > -- > > Shawn Iverson > > Director of Technology > > Rush County Schools > > 765-932-3901 x271 <(765)%20932-3901> > > iversons at rushville.k12.in.us > > > > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > -- -- Glenn email: glenn < dot > steen < at > gmail < dot > com work: glenn < dot > steen < at > ap1 < dot > se -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at jonesol.com Mon Feb 13 20:15:32 2017 From: dave at jonesol.com (Dave Jones) Date: Mon, 13 Feb 2017 14:15:32 -0600 Subject: Spamassassin Upgrade In-Reply-To: References: Message-ID: http://efa-project.org On Feb 13, 2017 4:23 AM, "Glenn Steen" wrote: Hello Scott, I do understand that the process of upgrading to CentOS 7 is ... daunting, and seem wasteful when all you need is a better SpamAssassin, but ... CentOS 5 has served you long and true, and should be put to rest;-) I did a new install on CentOS 7 when it was first released... It was a pain, especially the systemd stuff, and trying to cope with SElinux (maaany "local" rules:-)). But after that, it actually works very well. Sure, the whole toolchain need be updated and adjusted (and some things is simply done ... differently...:-)), but it is a good move, that will buy you peace of mind for a relatively long time. Trying to maintain a distro that is no longer supported... is a loosing battle/not worth your time, IMO. Cheers! -- -- Glenn 2017-02-11 20:13 GMT+01:00 Paul Scott : > Hello Shawn, > > > > Check this out: > > > > https://servertail.com/upgrading-centos-5-6-and-7/ > > > > Of course, I will begin planning on a course of action, but this is a very > tedious operation. > > > > I did manage to just get ClamAV upgraded manually to the very latest > version, and will do SpamAssasin next. > > > > Thank you very much! > > Paul Scott > > > > *From:* MailScanner [mailto:mailscanner-bounces+sales= > edenusa.com at lists.mailscanner.info] *On Behalf Of *Shawn Iverson > *Sent:* Friday, February 10, 2017 11:35 AM > *To:* MailScanner Discussion > *Subject:* Re: Spamassassin Upgrade > > > > CentOS 5? > > > > On Fri, Feb 10, 2017 at 2:27 PM, Paul Scott wrote: > > My CentOS 5 system is currently running Spam Assassin v3.2.5-1.el5, which > is the latest as picked up by yum updates. > > > > My question is, if I were to upgrade manually to the very latest version > of Spam Assassin (3.4.1), what would need to be done to insure that > MailScanner uses it? > > > > Has anybody already gone through this exercise? > > > > Sincerely, > > > > Paul Scott, Engineer > > Eden USA, Incorporated > Event Production Services Since 1995 > Los Angeles-Las Vegas-New York > sales at edenusa.com OR edenusasales at gmail.com > Telephone(s): 866.501.3336 <(866)%20501-3336> OR 951.505.6967 > <(951)%20505-6967> > Fax: 866.502.3336 <(866)%20502-3336> > > > > WEBSITE: https://www.edenusa.com > > FACEBOOK: http://www.facebook.com/edenusainc > > > > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > > > > -- > > Shawn Iverson > > Director of Technology > > Rush County Schools > > 765-932-3901 x271 <(765)%20932-3901> > > iversons at rushville.k12.in.us > > > > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > -- -- Glenn email: glenn < dot > steen < at > gmail < dot > com work: glenn < dot > steen < at > ap1 < dot > se -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner -------------- next part -------------- An HTML attachment was scrubbed... URL: From sales at edenusa.com Mon Feb 13 20:33:01 2017 From: sales at edenusa.com (Paul Scott) Date: Mon, 13 Feb 2017 20:33:01 +0000 Subject: Spamassassin Upgrade In-Reply-To: References: Message-ID: I successfully managed to upgrade SpamAssassin to 3.4.1, by manually downloading the tarball and compiling and installing it. After the install, I ran ?sa-update? and that took a long time, and took the system to a crawl, as it consumed to much memory. Now everything is working fine with the new SpamAssassin. Now just trying to get the ClamAV daemon working correctly. Have a permissions issue, which is all over the Internet in Google searches, but there are no solutions thus far. Thank you for your help! From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Glenn Steen Sent: Monday, February 13, 2017 2:23 AM To: MailScanner Discussion Subject: Re: Spamassassin Upgrade Hello Scott, I do understand that the process of upgrading to CentOS 7 is ... daunting, and seem wasteful when all you need is a better SpamAssassin, but ... CentOS 5 has served you long and true, and should be put to rest;-) I did a new install on CentOS 7 when it was first released... It was a pain, especially the systemd stuff, and trying to cope with SElinux (maaany "local" rules:-)). But after that, it actually works very well. Sure, the whole toolchain need be updated and adjusted (and some things is simply done ... differently...:-)), but it is a good move, that will buy you peace of mind for a relatively long time. Trying to maintain a distro that is no longer supported... is a loosing battle/not worth your time, IMO. Cheers! -- -- Glenn 2017-02-11 20:13 GMT+01:00 Paul Scott >: Hello Shawn, Check this out: https://servertail.com/upgrading-centos-5-6-and-7/ Of course, I will begin planning on a course of action, but this is a very tedious operation. I did manage to just get ClamAV upgraded manually to the very latest version, and will do SpamAssasin next. Thank you very much! Paul Scott From: MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists.mailscanner.info] On Behalf Of Shawn Iverson Sent: Friday, February 10, 2017 11:35 AM To: MailScanner Discussion > Subject: Re: Spamassassin Upgrade CentOS 5? On Fri, Feb 10, 2017 at 2:27 PM, Paul Scott > wrote: My CentOS 5 system is currently running Spam Assassin v3.2.5-1.el5, which is the latest as picked up by yum updates. My question is, if I were to upgrade manually to the very latest version of Spam Assassin (3.4.1), what would need to be done to insure that MailScanner uses it? Has anybody already gone through this exercise? Sincerely, Paul Scott, Engineer Eden USA, Incorporated Event Production Services Since 1995 Los Angeles-Las Vegas-New York sales at edenusa.com OR edenusasales at gmail.com Telephone(s): 866.501.3336 OR 951.505.6967 Fax: 866.502.3336 WEBSITE: https://www.edenusa.com FACEBOOK: http://www.facebook.com/edenusainc -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner -- Shawn Iverson Director of Technology Rush County Schools 765-932-3901 x271 iversons at rushville.k12.in.us [https://docs.google.com/uc?export=download&id=0Bw5iD0ToYvs_cy1OZFNIZ0drYVU&revid=0Bw5iD0ToYvs_UitIcHVIWkJVVTl2VGpxVUE0d0FQcHBIRXk4PQ] -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner -- -- Glenn email: glenn < dot > steen < at > gmail < dot > com work: glenn < dot > steen < at > ap1 < dot > se -------------- next part -------------- An HTML attachment was scrubbed... URL: From glenn.steen at gmail.com Tue Feb 14 08:32:41 2017 From: glenn.steen at gmail.com (Glenn Steen) Date: Tue, 14 Feb 2017 09:32:41 +0100 Subject: Spamassassin Upgrade In-Reply-To: References: Message-ID: Scott, Be more specific. What permission error? In which situation? The "normal" thing to miss is correct group permissions and ownership on the MailScanner Incoming directories (files and directories created by MailScanner that the clamd daemon needs be able to read). Simplest solution: Determine what user clamd runs as (with ps) become that user by way of "su - -s /bin/bash" try navigate to/read files in the work directory/-ies of MailScanner. Use ls/chown/chmod to rectify any "permanent" errors, and amend the MailScanner.conf file to match your system... usually is all needed to be done:-) Cheers! -- -- Glenn 2017-02-13 21:33 GMT+01:00 Paul Scott : > I successfully managed to upgrade SpamAssassin to 3.4.1, by manually > downloading the tarball and compiling and installing it. > > > > After the install, I ran ?sa-update? and that took a long time, and took > the system to a crawl, as it consumed to much memory. > > > > Now everything is working fine with the new SpamAssassin. > > > > Now just trying to get the ClamAV daemon working correctly. Have a > permissions issue, which is all over the Internet in Google searches, but > there are no solutions thus far. > > > > Thank you for your help! > > > > > > > > *From:* MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists. > mailscanner.info] *On Behalf Of *Glenn Steen > *Sent:* Monday, February 13, 2017 2:23 AM > > *To:* MailScanner Discussion > *Subject:* Re: Spamassassin Upgrade > > > > Hello Scott, > > I do understand that the process of upgrading to CentOS 7 is ... daunting, > and seem wasteful when all you need is a better SpamAssassin, but ... > CentOS 5 has served you long and true, and should be put to rest;-) > > I did a new install on CentOS 7 when it was first released... It was a > pain, especially the systemd stuff, and trying to cope with SElinux (maaany > "local" rules:-)). But after that, it actually works very well. > > Sure, the whole toolchain need be updated and adjusted (and some things is > simply done ... differently...:-)), but it is a good move, that will buy > you peace of mind for a relatively long time. > > Trying to maintain a distro that is no longer supported... is a loosing > battle/not worth your time, IMO. > > Cheers! > -- > > -- Glenn > > > > 2017-02-11 20:13 GMT+01:00 Paul Scott : > > Hello Shawn, > > > > Check this out: > > > > https://servertail.com/upgrading-centos-5-6-and-7/ > > > > Of course, I will begin planning on a course of action, but this is a very > tedious operation. > > > > I did manage to just get ClamAV upgraded manually to the very latest > version, and will do SpamAssasin next. > > > > Thank you very much! > > Paul Scott > > > > *From:* MailScanner [mailto:mailscanner-bounces+sales=edenusa.com at lists. > mailscanner.info] *On Behalf Of *Shawn Iverson > *Sent:* Friday, February 10, 2017 11:35 AM > *To:* MailScanner Discussion > *Subject:* Re: Spamassassin Upgrade > > > > CentOS 5? > > > > On Fri, Feb 10, 2017 at 2:27 PM, Paul Scott wrote: > > My CentOS 5 system is currently running Spam Assassin v3.2.5-1.el5, which > is the latest as picked up by yum updates. > > > > My question is, if I were to upgrade manually to the very latest version > of Spam Assassin (3.4.1), what would need to be done to insure that > MailScanner uses it? > > > > Has anybody already gone through this exercise? > > > > Sincerely, > > > > Paul Scott, Engineer > > Eden USA, Incorporated > Event Production Services Since 1995 > Los Angeles-Las Vegas-New York > sales at edenusa.com OR edenusasales at gmail.com > Telephone(s): 866.501.3336 <(866)%20501-3336> OR 951.505.6967 > <(951)%20505-6967> > Fax: 866.502.3336 <(866)%20502-3336> > > > > WEBSITE: https://www.edenusa.com > > FACEBOOK: http://www.facebook.com/edenusainc > > > > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > > > > -- > > Shawn Iverson > > Director of Technology > > Rush County Schools > > 765-932-3901 x271 <(765)%20932-3901> > > iversons at rushville.k12.in.us > > > > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > > > -- > > -- Glenn > email: glenn < dot > steen < at > gmail < dot > com > work: glenn < dot > steen < at > ap1 < dot > se > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > > -- -- Glenn email: glenn < dot > steen < at > gmail < dot > com work: glenn < dot > steen < at > ap1 < dot > se -------------- next part -------------- An HTML attachment was scrubbed... URL: From danita at caledonia.net Wed Feb 15 20:44:49 2017 From: danita at caledonia.net (Danita Zanre) Date: Wed, 15 Feb 2017 14:44:49 -0600 Subject: Allow filenames Message-ID: I have a sender who makes PDFs from Excel spreadsheets, and creates the names as "GD021517-5.xls.pdf?. ?These are being blocked as "MailScanner: Attempt to hide real filename extension?. ?I?d like to allow these for a particular receiving domain only (we have multiple domain names that our system scans for. ?I thought I had seen a setting that would allow this, but I can no longer find it. Help please? Thanks. Danita Zanr?, Move Out of the Office I love my job, and you can too! Tel: (720) 319-7530 - Caledonia Network Consulting Tel: (720) 319-8240 - Move Out of the Office -------------- next part -------------- An HTML attachment was scrubbed... URL: From danita at caledonia.net Wed Feb 15 21:07:35 2017 From: danita at caledonia.net (Danita Zanre) Date: Wed, 15 Feb 2017 15:07:35 -0600 Subject: Allowing URL shorteners Message-ID: wp.me?is wordpress? own url shortener, and I noticed today that mailscanner says this: MailScanner has detected definite fraud in the website at "wp.me". Do not trust this website: http://wp.me/p8jXWt-9A?- this is definitely ?not fraud?. ?I like the idea of pointing out that some links can be dangerous, but wordpress.com?issues these shortened urls by default. ?How can I tweak the ideas of what mailscanner thinks of as fraud, etc. ?While one could argue that places like bit.ly,?goo.gl etc can hide malicious sites since individuals can craft these shortened URLs, t.co, wp.me?and ow.ly?are generally controlled by the owning sites. ?Should these warrant such a vehement warning? Danita Zanr?, Move Out of the Office I love my job, and you can too! Tel: (720) 319-7530 - Caledonia Network Consulting Tel: (720) 319-8240 - Move Out of the Office -------------- next part -------------- An HTML attachment was scrubbed... URL: From jerry.benton at mailborder.com Wed Feb 15 22:54:58 2017 From: jerry.benton at mailborder.com (Jerry Benton) Date: Wed, 15 Feb 2017 17:54:58 -0500 Subject: Allowing URL shorteners In-Reply-To: References: Message-ID: Add it to your phishing whitelists file. - Jerry Benton www.mailborder.com +1 - 844-436-6245 > On Feb 15, 2017, at 4:07 PM, Danita Zanre wrote: > > wp.me is wordpress? own url shortener, and I noticed today that mailscanner says this: > > MailScanner has detected definite fraud in the website at "wp.me ". Do not trust this website: http://wp.me/p8jXWt-9A - this is definitely ?not fraud?. I like the idea of pointing out that some links can be dangerous, but wordpress.com issues these shortened urls by default. How can I tweak the ideas of what mailscanner thinks of as fraud, etc. While one could argue that places like bit.ly , goo.gl etc can hide malicious sites since individuals can craft these shortened URLs, t.co , wp.me and ow.ly are generally controlled by the owning sites. Should these warrant such a vehement warning? > > Danita Zanr?, Move Out of the Office > I love my job, and you can too! > Tel: (720) 319-7530 - Caledonia Network Consulting > Tel: (720) 319-8240 - Move Out of the Office > > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at msapiro.net Wed Feb 15 23:14:44 2017 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 15 Feb 2017 15:14:44 -0800 Subject: Allow filenames In-Reply-To: References: Message-ID: <08dfbb2b-a8ae-698a-0879-7b62b54613af@msapiro.net> On 02/15/2017 12:44 PM, Danita Zanre wrote: > I have a sender who makes PDFs from Excel spreadsheets, and creates the > names as "GD021517-5.xls.pdf?. These are being blocked as "MailScanner: > Attempt to hide real filename extension?. I?d like to allow these for a > particular receiving domain only (we have multiple domain names that our > system scans for. I thought I had seen a setting that would allow this, > but I can no longer find it. At the end of /etc/MailScanner/filename.rules.conf you will see > # Allow repeated file extension, e.g. blah.zip.zip > allow (\.[a-z0-9]{3})\1$ - - > > # Allow days of the week and months in doc names, e.g. blah.wed.doc > allow \.(mon|tue|wed|thu|fri|sat|sun)\.[a-z0-9]{3}$ - - > allow \.(jan|feb|mar|apr|may|jun|june|jul|july|aug|sep|sept|oct|nov|dec)\.[a-z0-9]{3}$ - - > > # Deny all other double file extensions. This catches any hidden filenames. > deny \.[a-z][a-z0-9]{2,3}\s*\.[a-z0-9]{3}$ Found possible filename hiding Attempt to hide real filename extension If all you want is to allow names that end with .xls.pdf, add the line allow \.xls\.pdf$ - - ahead of the # Deny comment, or if you want to allow all double extensions, just remove the # Deny comment and the following deny line. Also read the info at the beginning of the file, especially the part about using tabs, not spaces as field delimiters. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From danita at caledonia.net Thu Feb 16 00:28:27 2017 From: danita at caledonia.net (Danita Zanre) Date: Wed, 15 Feb 2017 18:28:27 -0600 Subject: Allow filenames In-Reply-To: <08dfbb2b-a8ae-698a-0879-7b62b54613af@msapiro.net> References: <08dfbb2b-a8ae-698a-0879-7b62b54613af@msapiro.net> Message-ID: Perfect - thanks! Danita Zanr?, Move Out of the Office I love my job, and you can too! Tel: (720) 319-7530 - Caledonia Network Consulting Tel: (720) 319-8240 - Move Out of the Office On February 15, 2017 at 5:25:26 PM, Mark Sapiro (mark at msapiro.net) wrote: On 02/15/2017 12:44 PM, Danita Zanre wrote: > I have a sender who makes PDFs from Excel spreadsheets, and creates the > names as "GD021517-5.xls.pdf?. These are being blocked as "MailScanner: > Attempt to hide real filename extension?. I?d like to allow these for a > particular receiving domain only (we have multiple domain names that our > system scans for. I thought I had seen a setting that would allow this, > but I can no longer find it. At the end of /etc/MailScanner/filename.rules.conf you will see > # Allow repeated file extension, e.g. blah.zip.zip > allow (\.[a-z0-9]{3})\1$ - - > > # Allow days of the week and months in doc names, e.g. blah.wed.doc > allow \.(mon|tue|wed|thu|fri|sat|sun)\.[a-z0-9]{3}$ - - > allow \.(jan|feb|mar|apr|may|jun|june|jul|july|aug|sep|sept|oct|nov|dec)\.[a-z0-9]{3}$ - - > > # Deny all other double file extensions. This catches any hidden filenames. > deny \.[a-z][a-z0-9]{2,3}\s*\.[a-z0-9]{3}$ Found possible filename hiding Attempt to hide real filename extension If all you want is to allow names that end with .xls.pdf, add the line allow \.xls\.pdf$ - - ahead of the # Deny comment, or if you want to allow all double extensions, just remove the # Deny comment and the following deny line. Also read the info at the beginning of the file, especially the part about using tabs, not spaces as field delimiters. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner -- This message has been scanned for viruses and dangerous content by Iris MailScanner, and is believed to be clean. -------------- next part -------------- An HTML attachment was scrubbed... URL: From danita at caledonia.net Thu Feb 16 00:28:36 2017 From: danita at caledonia.net (Danita Zanre) Date: Wed, 15 Feb 2017 18:28:36 -0600 Subject: Allowing URL shorteners In-Reply-To: References: Message-ID: Ah - I forgot that one. ?Thanks. Danita Zanr?, Move Out of the Office I love my job, and you can too! Tel: (720) 319-7530 - Caledonia Network Consulting Tel: (720) 319-8240 - Move Out of the Office On February 15, 2017 at 5:04:36 PM, Jerry Benton (jerry.benton at mailborder.com) wrote: Add it to your phishing whitelists file.? - Jerry Benton www.mailborder.com +1 -?844-436-6245 On Feb 15, 2017, at 4:07 PM, Danita Zanre wrote: wp.me?is wordpress? own url shortener, and I noticed today that mailscanner says this: MailScanner has detected definite fraud in the website at "wp.me". Do not trust this website:?MailScanner has detected definite fraud in the website at "wp.me". Do not trust this website: http://wp.me/p8jXWt-9A?- this is definitely ?not fraud?. ?I like the idea of pointing out that some links can be dangerous, but?wordpress.com?issues these shortened urls by default. ?How can I tweak the ideas of what mailscanner thinks of as fraud, etc. ?While one could argue that places like?bit.ly,?goo.gl?etc can hide malicious sites since individuals can craft these shortened URLs,?t.co,?wp.me?and?ow.ly?are generally controlled by the owning sites. ?Should these warrant such a vehement warning? Danita Zanr?,?Move Out of the Office I love my job, and you can too! Tel: (720) 319-7530 - Caledonia Network Consulting Tel: (720) 319-8240 - Move Out of the Office --? MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner -- This message has been scanned for viruses and dangerous content by Iris MailScanner, and is believed to be clean. -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner -------------- next part -------------- An HTML attachment was scrubbed... URL: From markussen at media24.no Mon Feb 20 14:13:47 2017 From: markussen at media24.no (Trond M. Markussen) Date: Mon, 20 Feb 2017 15:13:47 +0100 Subject: Stopping .js in .zip Message-ID: <090301d28b83$8ec75350$ac55f9f0$@media24.no> Hi, Could someone please let me know the best way to stop javascript (.js) files within .zip files? Currently we have: in filename.rules.conf (among others): allow \.zip$ deny \.jse?$ deny \.js$ deny \.exe$ And the entire filetype.rules.conf: allow text - - allow \bscript - - allow archive - - allow postscript - - #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 #deny ELF No executables No programs allowed #deny Registry No Windows Registry entries No Windows Registry files allowed #deny MPEG No MPEG movies No MPEG movies allowed #deny AVI No AVI movies No AVI movies allowed #deny MNG No MNG/PNG movies No MNG movies allowed #deny QuickTime No QuickTime movies No QuickTime movies allowed #deny ASF No Windows media No Windows media files allowed #deny metafont No Windows Metafont drawings No WMF drawings allowed Please let me know your suggestions using filename/filetype rules, and/or deny.filetypes.rules. Regards, Trond M. Markussen Media24 AS -------------- next part -------------- An HTML attachment was scrubbed... URL: From funk.gabor at hunetkft.hu Mon Feb 20 14:27:06 2017 From: funk.gabor at hunetkft.hu (=?UTF-8?Q?FUNK_G=c3=a1bor?=) Date: Mon, 20 Feb 2017 15:27:06 +0100 Subject: Stopping .js in .zip In-Reply-To: <090301d28b83$8ec75350$ac55f9f0$@media24.no> References: <090301d28b83$8ec75350$ac55f9f0$@media24.no> Message-ID: <8989359a-438f-7718-c8ba-2541b590e4b2@hunetkft.hu> >> Could someone please let me know the best way to stop javascript (.js) files within .zip files? something like this: file: MailScanner.conf Archives Are = zip rar ace lzh gz dat 1 2 7z gzip bzip bz bz2 cab xz Archives: Filename Rules = %etc-dir%/rules/file/_filename-zip.rules file: _filename-zip.rules FromOrTo: default /etc/MailScanner/filename-zip.rules.conf file: filename-zip.rules.conf | grep js deny \.js$ javascript file .js pontentally containing malicious trojan G. From donnerk at gmail.com Tue Feb 21 11:48:18 2017 From: donnerk at gmail.com (Nerk Nerk) Date: Tue, 21 Feb 2017 12:48:18 +0100 Subject: Mailscanner, forwarding and SPF Message-ID: Dear MailScanner-fanatics, Currently I am facing some issues using MailScanner. Mostly, when the following situation is current: - Some domain using SPF, for example Paypal, sends a mail to a domain that I filter for - The domain is filtered through Mailscanner - The e-mail is forwarded to the destination - The destination server is not under my control. They do SPF checking and reject the mail because the sending domain does not list my mailscanner IP as a valid sender Ofcourse I have thought of some solutions: 1- They need to whitelist the IP of my mailscanner 2- They need to turn off the SPF checks at the destination Both solutions however, require actions from a hosting party that I don't know and that is probably not willing. A third option: 3- I need to rewrite the sending domain somehow Has anyone else come across this problem? How did you solve it? I am really wondering what solution commercial spam filtering services, such as SpamExperts for example, are using. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Antony.Stone at mailscanner.open.source.it Tue Feb 21 11:56:40 2017 From: Antony.Stone at mailscanner.open.source.it (Antony Stone) Date: Tue, 21 Feb 2017 12:56:40 +0100 Subject: Mailscanner, forwarding and SPF In-Reply-To: References: Message-ID: <201702211256.40488.Antony.Stone@mailscanner.open.source.it> On Tuesday 21 February 2017 at 12:48:18, Nerk Nerk wrote: > Dear MailScanner-fanatics, > > Currently I am facing some issues using MailScanner. Mostly, when the > following situation is current: > > - Some domain using SPF, for example Paypal, sends a mail to a domain that > I filter for So, you are the destination of the MX records... > - The domain is filtered through Mailscanner > - The e-mail is forwarded to the destination How does that happen? > - The destination server is not under my control. They do SPF checking and > reject the mail because the sending domain does not list my mailscanner IP > as a valid sender > > Ofcourse I have thought of some solutions: > 1- They need to whitelist the IP of my mailscanner That would be good, considering that they've bought (?) a filtering service from you, and expect mail to pass through your servers on the way to theirs. > 2- They need to turn off the SPF checks at the destination Do they receive any direct (ie: not filtered through your servers) email? > Both solutions however, require actions from a hosting party that I don't > know and that is probably not willing. So, why have they pointed their MX records at your server, if they're not wiling to adjust their server to match this? > A third option: > 3- I need to rewrite the sending domain somehow Yes, like manay mailing lists do. > Has anyone else come across this problem? How did you solve it? > > I am really wondering what solution commercial spam filtering services, > such as SpamExperts for example, are using. I can't speak for them. Antony. -- Never automate fully anything that does not have a manual override capability. Never design anything that cannot work under degraded conditions in emergency. Please reply to the list; please *don't* CC me. From donnerk at gmail.com Tue Feb 21 12:15:51 2017 From: donnerk at gmail.com (Nerk Nerk) Date: Tue, 21 Feb 2017 13:15:51 +0100 Subject: Mailscanner, forwarding and SPF In-Reply-To: <201702211256.40488.Antony.Stone@mailscanner.open.source.it> References: <201702211256.40488.Antony.Stone@mailscanner.open.source.it> Message-ID: Thank you for your answers. The problem is, that the people that use my filters, don't own the server that their email is hosted on. So they can't always decide to turn something off. 2017-02-21 12:56 GMT+01:00 Antony Stone < Antony.Stone at mailscanner.open.source.it>: > On Tuesday 21 February 2017 at 12:48:18, Nerk Nerk wrote: > > > Dear MailScanner-fanatics, > > > > Currently I am facing some issues using MailScanner. Mostly, when the > > following situation is current: > > > > - Some domain using SPF, for example Paypal, sends a mail to a domain > that > > I filter for > > So, you are the destination of the MX records... > > > - The domain is filtered through Mailscanner > > - The e-mail is forwarded to the destination > > How does that happen? > > > - The destination server is not under my control. They do SPF checking > and > > reject the mail because the sending domain does not list my mailscanner > IP > > as a valid sender > > > > Ofcourse I have thought of some solutions: > > 1- They need to whitelist the IP of my mailscanner > > That would be good, considering that they've bought (?) a filtering service > from you, and expect mail to pass through your servers on the way to > theirs. > > > 2- They need to turn off the SPF checks at the destination > > Do they receive any direct (ie: not filtered through your servers) email? > > > Both solutions however, require actions from a hosting party that I don't > > know and that is probably not willing. > > So, why have they pointed their MX records at your server, if they're not > wiling to adjust their server to match this? > > > A third option: > > 3- I need to rewrite the sending domain somehow > > Yes, like manay mailing lists do. > > > Has anyone else come across this problem? How did you solve it? > > > > I am really wondering what solution commercial spam filtering services, > > such as SpamExperts for example, are using. > > I can't speak for them. > > > Antony. > > -- > Never automate fully anything that does not have a manual override > capability. > Never design anything that cannot work under degraded conditions in > emergency. > > Please reply to the > list; > please *don't* CC > me. > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From donnerk at gmail.com Tue Feb 21 12:57:49 2017 From: donnerk at gmail.com (Nerk Nerk) Date: Tue, 21 Feb 2017 13:57:49 +0100 Subject: Mailscanner, forwarding and SPF In-Reply-To: References: <201702211256.40488.Antony.Stone@mailscanner.open.source.it> Message-ID: Same thing happens with DKIM/DMARC by the way, not just SPF. 2017-02-21 13:15 GMT+01:00 Nerk Nerk : > Thank you for your answers. > > The problem is, that the people that use my filters, don't own the server > that their email is hosted on. So they can't always decide to turn > something off. > > 2017-02-21 12:56 GMT+01:00 Antony Stone open.source.it>: > >> On Tuesday 21 February 2017 at 12:48:18, Nerk Nerk wrote: >> >> > Dear MailScanner-fanatics, >> > >> > Currently I am facing some issues using MailScanner. Mostly, when the >> > following situation is current: >> > >> > - Some domain using SPF, for example Paypal, sends a mail to a domain >> that >> > I filter for >> >> So, you are the destination of the MX records... >> >> > - The domain is filtered through Mailscanner >> > - The e-mail is forwarded to the destination >> >> How does that happen? >> >> > - The destination server is not under my control. They do SPF checking >> and >> > reject the mail because the sending domain does not list my mailscanner >> IP >> > as a valid sender >> > >> > Ofcourse I have thought of some solutions: >> > 1- They need to whitelist the IP of my mailscanner >> >> That would be good, considering that they've bought (?) a filtering >> service >> from you, and expect mail to pass through your servers on the way to >> theirs. >> >> > 2- They need to turn off the SPF checks at the destination >> >> Do they receive any direct (ie: not filtered through your servers) email? >> >> > Both solutions however, require actions from a hosting party that I >> don't >> > know and that is probably not willing. >> >> So, why have they pointed their MX records at your server, if they're not >> wiling to adjust their server to match this? >> >> > A third option: >> > 3- I need to rewrite the sending domain somehow >> >> Yes, like manay mailing lists do. >> >> > Has anyone else come across this problem? How did you solve it? >> > >> > I am really wondering what solution commercial spam filtering services, >> > such as SpamExperts for example, are using. >> >> I can't speak for them. >> >> >> Antony. >> >> -- >> Never automate fully anything that does not have a manual override >> capability. >> Never design anything that cannot work under degraded conditions in >> emergency. >> >> Please reply to the >> list; >> please *don't* >> CC me. >> >> >> -- >> MailScanner mailing list >> mailscanner at lists.mailscanner.info >> http://lists.mailscanner.info/mailman/listinfo/mailscanner >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From diederik at webrelated.nl Tue Feb 21 13:14:07 2017 From: diederik at webrelated.nl (Diederik van den Burger) Date: Tue, 21 Feb 2017 14:14:07 +0100 Subject: Inconsistent SpamAssassin report In-Reply-To: References: <6BC08B22-C0E3-4A67-B947-58EDDEC6CAFE@webrelated.nl> <92A5BDFE-7EDF-41F8-813F-ACDD6F0F38F4@mailborder.com> <20170207150546.608A2FA544@beta.mail.webrelated.nl> <5EC15346-DC7F-4DC0-BC3F-2F931FDC08E8@mailborder.com> <2576BAD9-4028-4D0D-9283-B55654D731C1@webrelated.nl> <488F45F3-1B66-48AE-8545-E36FAC9A433E@webrelated.nl> Message-ID: <6CAD4AE8-CE5F-41A1-BBCE-AF7711F19BA2@webrelated.nl> I just wanted to give an update on this. The problem actually was two-fold. For some reason, postfix did not have the correct permissions to run the Pyzor and Razor tests, hence the first difference. For future reference, I debugged this using the following command: sudo su postfix -p -c 'spamassassin -D -t -d -p /etc/MailScanner/spamassassin.conf < /spam/file.txt' -D is obviously debugging, -d removes any existing spam reports, -t enables test mode and I did not use -c but -p to pipe in the preferences. Scrolling through the output it became evident that there was a permission error. The second issue was completely my own fault and I almost feel stupid for admitting it. I sometimes saw differences in bayes scores. This was because I had a cronjob automatically learning files that were marked as spam. So when they first came in through MailWatch, they hadn't been learned yet but afterwards they had been, obviously raising the score. I felt like it was necessary to post this update, specifically the first part, since this might help people in the future. > On 7 Feb 2017, at 20:10, Mark Sapiro wrote: > > On 02/07/2017 10:39 AM, Peter Lemieux wrote: >> I can see running the incoming daemon as the postfix user, but I don't see >> any reason to run MailScanner itself that way. > > > MailScanner runs as the postfix user so it can dequeue messages from > Postfix's hold queue and after scanning queue them in Postfix's incoming > queue. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > From Antony.Stone at mailscanner.open.source.it Tue Feb 21 13:29:32 2017 From: Antony.Stone at mailscanner.open.source.it (Antony Stone) Date: Tue, 21 Feb 2017 14:29:32 +0100 Subject: Mailscanner, forwarding and SPF In-Reply-To: References: <201702211256.40488.Antony.Stone@mailscanner.open.source.it> Message-ID: <201702211429.32990.Antony.Stone@mailscanner.open.source.it> On Tuesday 21 February 2017 at 13:15:51, Nerk Nerk wrote: > Thank you for your answers. > > The problem is, that the people that use my filters, don't own the server > that their email is hosted on. So they can't always decide to turn > something off. So, maybe they should consider owning their own server, or having a fully- hosted email service (not just filtering) from you? Further information on how the mail flow works (see my questions below) would be helpful to us if you want some suggestions on how to set up a workaround, if the customer isn't prepared or able to make the ideal changes. > 2017-02-21 12:56 GMT+01:00 Antony Stone: > > On Tuesday 21 February 2017 at 12:48:18, Nerk Nerk wrote: > > > Dear MailScanner-fanatics, > > > > > > Currently I am facing some issues using MailScanner. Mostly, when the > > > following situation is current: > > > > > > - Some domain using SPF, for example Paypal, sends a mail to a domain > > > that I filter for > > > > So, you are the destination of the MX records... > > > > > - The domain is filtered through Mailscanner > > > - The e-mail is forwarded to the destination > > > > How does that happen? > > > > > - The destination server is not under my control. They do SPF checking > > > and reject the mail because the sending domain does not list my > > > mailscanner IP as a valid sender > > > > > > Ofcourse I have thought of some solutions: > > > 1- They need to whitelist the IP of my mailscanner > > > > That would be good, considering that they've bought (?) a filtering > > service from you, and expect mail to pass through your servers on the > > way to theirs. > > > > > 2- They need to turn off the SPF checks at the destination > > > > Do they receive any direct (ie: not filtered through your servers) email? > > > > > Both solutions however, require actions from a hosting party that I > > > don't know and that is probably not willing. > > > > So, why have they pointed their MX records at your server, if they're not > > wiling to adjust their server to match this? > > > > > A third option: > > > 3- I need to rewrite the sending domain somehow > > > > Yes, like many mailing lists do. > > > > > Has anyone else come across this problem? How did you solve it? > > > > > > I am really wondering what solution commercial spam filtering services, > > > such as SpamExperts for example, are using. > > > > I can't speak for them. > > > > > > Antony. -- These clients are often infected by viruses or other malware and need to be fixed. If not, the user at that client needs to be fixed... - Henrik Nordstrom, on Squid users' mailing list Please reply to the list; please *don't* CC me. From markussen at media24.no Tue Feb 21 13:53:02 2017 From: markussen at media24.no (Trond M. Markussen) Date: Tue, 21 Feb 2017 14:53:02 +0100 Subject: SV: Stopping .js in .zip In-Reply-To: <8989359a-438f-7718-c8ba-2541b590e4b2@hunetkft.hu> References: <090301d28b83$8ec75350$ac55f9f0$@media24.no> <8989359a-438f-7718-c8ba-2541b590e4b2@hunetkft.hu> Message-ID: <0a0401d28c49$d2924bf0$77b6e3d0$@media24.no> Thanks for the feedback. I noticed that there was no " Archives Are" setting in MailScanner.conf, presumably this was added in a later version (we are running 4.74.16). - Is there another way to make sure .js witnin .zip files are stopped (using the current version)? - Would you recommend upgrading to the latest version (if so, is this a complicated and/or risky process)? Regards, Trond M. -----Opprinnelig melding----- Fra: MailScanner [mailto:mailscanner-bounces+markussen=media24.no at lists.mailscanner.info] P? vegne av FUNK G?bor Sendt: 20. februar 2017 15:27 Til: MailScanner Discussion Emne: Re: Stopping .js in .zip >> Could someone please let me know the best way to stop javascript (.js) files within .zip files? something like this: file: MailScanner.conf Archives Are = zip rar ace lzh gz dat 1 2 7z gzip bzip bz bz2 cab xz Archives: Filename Rules = %etc-dir%/rules/file/_filename-zip.rules file: _filename-zip.rules FromOrTo: default /etc/MailScanner/filename-zip.rules.conf file: filename-zip.rules.conf | grep js deny \.js$ javascript file .js pontentally containing malicious trojan G. -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner From mark at msapiro.net Tue Feb 21 16:40:56 2017 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 21 Feb 2017 08:40:56 -0800 Subject: Mailscanner, forwarding and SPF In-Reply-To: References: <201702211256.40488.Antony.Stone@mailscanner.open.source.it> Message-ID: On 02/21/2017 04:57 AM, Nerk Nerk wrote: > Same thing happens with DKIM/DMARC by the way, not just SPF. These are separate issues. For SPF, the issue is PayPal doesn't list your server as authorized to send mail with envelope from PayPal, so you can't just relay the mail, you also have to rewrite the envelope sender which means "resending" the message rather than relaying it so that the next hop sees the envelope as from say mailscanner at your.domain rather than sender at paypal.com. This is a problem with the design of SPF and occurs with any situation where there is a .forward or other type of relaying. The problem with rewriting the envelope sender is it will cause downstream bounces to be returned to you rather than the original sender. Also see , but note that this doesn't rewrite the envelope sender. It just records the original envelope sender in an Envelope-From: header in the message. DKIM signatures are a different issue. If you make no transformation to the message which affects the body or DKIM signed headers, DKIM will still validate downstream. If the issue breaking DKIM is added MailScanner headers, see DMARC is yet another issue, but if the message is DKIM signed by the From: domain and you don't break the DKIM sig, the message should pass DMARC. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Feb 21 17:16:26 2017 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 21 Feb 2017 09:16:26 -0800 Subject: SV: Stopping .js in .zip In-Reply-To: <0a0401d28c49$d2924bf0$77b6e3d0$@media24.no> References: <090301d28b83$8ec75350$ac55f9f0$@media24.no> <8989359a-438f-7718-c8ba-2541b590e4b2@hunetkft.hu> <0a0401d28c49$d2924bf0$77b6e3d0$@media24.no> Message-ID: <7057d6d8-9714-1ff5-7765-40af82dbd6ec@msapiro.net> On 02/21/2017 05:53 AM, Trond M. Markussen wrote: > Thanks for the feedback. I noticed that there was no " Archives Are" setting > in MailScanner.conf, presumably this was added in a later version (we are > running 4.74.16). It was added in 4.76.1. > - Is there another way to make sure .js witnin .zip files are stopped (using > the current version)? I don't recall for sure, but I think in versions prior to 4.76, the same filename rules were applied to files inside archives just as to unarchived files. > - Would you recommend upgrading to the latest version (if so, is this a > complicated and/or risky process)? Upgrading would be good, but the latest (v5) versions have significant changes so the process isn't completely turnkey. There are still v4 packages at https://s3.amazonaws.com/msv4/rpm/MailScanner-4.85.3-1.rpm.tar.gz https://s3.amazonaws.com/msv4/suse/MailScanner-4.85.3-1.suse-rpm.tar.gz https://s3.amazonaws.com/msv4/tar/MailScanner-4.85.3-1.tar.gz https://s3.amazonaws.com/msv4/deb/MailScanner-4.85.3-1.deb.tar.gz and a later deb at https://s3.amazonaws.com/msv4/deb/MailScanner-4.86.1-1.deb.tar.gz although the other 4.86.1-1 versions don't seem to be there. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From markussen at media24.no Wed Feb 22 12:29:49 2017 From: markussen at media24.no (Trond M. Markussen) Date: Wed, 22 Feb 2017 13:29:49 +0100 Subject: SV: SV: Stopping .js in .zip In-Reply-To: <7057d6d8-9714-1ff5-7765-40af82dbd6ec@msapiro.net> References: <090301d28b83$8ec75350$ac55f9f0$@media24.no> <8989359a-438f-7718-c8ba-2541b590e4b2@hunetkft.hu> <0a0401d28c49$d2924bf0$77b6e3d0$@media24.no> <7057d6d8-9714-1ff5-7765-40af82dbd6ec@msapiro.net> Message-ID: <0ac601d28d07$5d407ac0$17c17040$@media24.no> Thanks for the info. In that case, stopping these attacks should not be a problem with the current MS version as I understand it. Could it be a conflict between allowing ZIPs and denying JS files in filename.rules.conf? allow \.zip$ deny \.jse?$ By the way, we have Maximum Archive Depth = 5. Is there perhaps a way to block js files in filetype.rules.conf? Regards, Trond M. -----Opprinnelig melding----- Fra: MailScanner [mailto:mailscanner-bounces+markussen=media24.no at lists.mailscanner.info] P? vegne av Mark Sapiro Sendt: 21. februar 2017 18:16 Til: mailscanner at lists.mailscanner.info Emne: Re: SV: Stopping .js in .zip On 02/21/2017 05:53 AM, Trond M. Markussen wrote: > Thanks for the feedback. I noticed that there was no " Archives Are" > setting in MailScanner.conf, presumably this was added in a later > version (we are running 4.74.16). It was added in 4.76.1. > - Is there another way to make sure .js witnin .zip files are stopped > (using the current version)? I don't recall for sure, but I think in versions prior to 4.76, the same filename rules were applied to files inside archives just as to unarchived files. > - Would you recommend upgrading to the latest version (if so, is this > a complicated and/or risky process)? Upgrading would be good, but the latest (v5) versions have significant changes so the process isn't completely turnkey. There are still v4 packages at https://s3.amazonaws.com/msv4/rpm/MailScanner-4.85.3-1.rpm.tar.gz https://s3.amazonaws.com/msv4/suse/MailScanner-4.85.3-1.suse-rpm.tar.gz https://s3.amazonaws.com/msv4/tar/MailScanner-4.85.3-1.tar.gz https://s3.amazonaws.com/msv4/deb/MailScanner-4.85.3-1.deb.tar.gz and a later deb at https://s3.amazonaws.com/msv4/deb/MailScanner-4.86.1-1.deb.tar.gz although the other 4.86.1-1 versions don't seem to be there. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -- MailScanner mailing list mailscanner at lists.mailscanner.info http://lists.mailscanner.info/mailman/listinfo/mailscanner From mark at msapiro.net Thu Feb 23 03:27:46 2017 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 22 Feb 2017 19:27:46 -0800 Subject: Stopping .js in .zip In-Reply-To: <0ac601d28d07$5d407ac0$17c17040$@media24.no> References: <090301d28b83$8ec75350$ac55f9f0$@media24.no> <8989359a-438f-7718-c8ba-2541b590e4b2@hunetkft.hu> <0a0401d28c49$d2924bf0$77b6e3d0$@media24.no> <7057d6d8-9714-1ff5-7765-40af82dbd6ec@msapiro.net> <0ac601d28d07$5d407ac0$17c17040$@media24.no> Message-ID: On 02/22/2017 04:29 AM, Trond M. Markussen wrote: > Thanks for the info. In that case, stopping these attacks should not be a > problem with the current MS version as I understand it. I would think so, but I don't have a pre 4.76 version to test/experiment with so I don't know for sure. > Could it be a conflict between allowing ZIPs and denying JS files in > filename.rules.conf? > allow \.zip$ > deny \.jse?$ You might try changing the order of 'deny \.jse?$' and 'allow \.zip$' in that file. I wouldn't think it would matter, but it might. > Is there perhaps a way to block js files in filetype.rules.conf? I don't think so. filetype.rules.conf relies on the type reported by the 'file' command, and in testing a few .js files, the report is either 'HTML document, ASCII text' or 'ASCII text' and you certainly don't want to block those. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From daniel at brunt.ca Fri Feb 24 18:47:42 2017 From: daniel at brunt.ca (Daniel Brunt) Date: Fri, 24 Feb 2017 18:47:42 +0000 Subject: Mailscanner, forwarding and SPF Message-ID: Hi Don, Bottom line...the people that use your EFA for filtering cannot, as long as they are using a hosted email service that does SPF checking. Period. My g/f had similar issue using GoDaddy for her e-mail. I was filtering her e-mail via Barracuda (formerly MailFoundry). I was asked to troubleshoot NDRs. Turns out, GoDaddy had implemented SPF checking and was rejecting emails forwarded from Barracuda where the domain had a SPF record. No way around this since GoDaddy was unwilling to whitelist Barracuda mail servers from the SPF check; and their whitelisting mechanism is post-SPF check. I had to turn off the Barracuda email filtering for her. She was not happy. She started receiving a *lot* more SPAM as a result. The only solution for you and your clients is for you to host their email behind your EFA appliance. -Daniel ------------------------------------------------------------------------------ Message: 1 Date: Tue, 21 Feb 2017 13:15:51 +0100 From: Nerk Nerk To: MailScanner Discussion Subject: Re: Mailscanner, forwarding and SPF Message-ID: Content-Type: text/plain; charset="utf-8" Thank you for your answers. The problem is, that the people that use my filters, don't own the server that their email is hosted on. So they can't always decide to turn something off. 2017-02-21 12:56 GMT+01:00 Antony Stone < Antony.Stone at mailscanner.open.source.it>: > On Tuesday 21 February 2017 at 12:48:18, Nerk Nerk wrote: > > > Dear MailScanner-fanatics, > > > > Currently I am facing some issues using MailScanner. Mostly, when > > the following situation is current: > > > > - Some domain using SPF, for example Paypal, sends a mail to a > > domain > that > > I filter for > > So, you are the destination of the MX records... > > > - The domain is filtered through Mailscanner > > - The e-mail is forwarded to the destination > > How does that happen? > > > - The destination server is not under my control. They do SPF > > checking > and > > reject the mail because the sending domain does not list my > > mailscanner > IP > > as a valid sender > > > > Ofcourse I have thought of some solutions: > > 1- They need to whitelist the IP of my mailscanner > > That would be good, considering that they've bought (?) a filtering > service from you, and expect mail to pass through your servers on the > way to theirs. > > > 2- They need to turn off the SPF checks at the destination > > Do they receive any direct (ie: not filtered through your servers) email? > > > Both solutions however, require actions from a hosting party that I > > don't know and that is probably not willing. > > So, why have they pointed their MX records at your server, if they're > not wiling to adjust their server to match this? > > > A third option: > > 3- I need to rewrite the sending domain somehow > > Yes, like manay mailing lists do. > > > Has anyone else come across this problem? How did you solve it? > > > > I am really wondering what solution commercial spam filtering > > services, such as SpamExperts for example, are using. > > I can't speak for them. > > > Antony. > > -- > Never automate fully anything that does not have a manual override > capability. > Never design anything that cannot work under degraded conditions in > emergency. > > Please reply to the > list; > please > *don't* CC me. > > > -- > MailScanner mailing list > mailscanner at lists.mailscanner.info > http://lists.mailscanner.info/mailman/listinfo/mailscanner > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From f9612692 at gmail.com Sat Feb 25 05:37:06 2017 From: f9612692 at gmail.com (=?UTF-8?B?5p2O5pS/55KL?=) Date: Sat, 25 Feb 2017 13:37:06 +0800 Subject: About compress file. Message-ID: I compress a execution file. like abc.exe > abc.zip or any compress (rar gz 7z gzip bzip) I want abc.zip can be passed but deny abc.exe . How do I do? -------------- next part -------------- An HTML attachment was scrubbed... URL: From mark at msapiro.net Sat Feb 25 05:54:45 2017 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 24 Feb 2017 21:54:45 -0800 Subject: About compress file. In-Reply-To: References: Message-ID: <715ea7af-4949-8407-3167-84403be76124@msapiro.net> On 02/24/2017 09:37 PM, ??? wrote: > I compress a execution file. like abc.exe > abc.zip or any compress (rar > gz 7z gzip bzip) > > I want abc.zip can be passed but deny abc.exe . With any MailScanner since 4.76.1 this should be the default behavior. .zip, .gz, .tgz, .Z and .bz2 are all allowed by default. .rar is neither explicitly allowed or denied, but you can always add it to filename.rules.conf. For files inside archives, archives.filename.rules.conf controls and denies .exe by default. For MailScanner prior to 4.76.1 there is no separate archives.filename.rules.conf, but archives should be allowed unless they contain disallowed files. If this is not what you see, please be specific about your MailScanner version and the type of archive and the contents that behave differently. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan