| Attachment Filter: Message violates MIME standards: MIME syntax violation [message #1517] |
Wed, 25 October 2006 18:53 |
J.Moser
Messages: 2
Registered: October 2006 |
Junior Member |
|
|
hello,
we are using No Spam Today! Service (V2.3.5.3) on a windows server 2000 (sp4). lately we have a lot of mails coming from different mac (apple) computers with some problemes around the attachment filter. No Spam Today is claiming that some of these mails will have a "broken" mime syntax. i was playing some time with these mails and tracked it down to this mime header
--Apple-Mail-11-929081845
Content-Type: multipart/mixed;
boundary=Apple-Mail-12-929081845
to my question: is this header really "broken" or is it a false-detection?
and is there another solution as to disable the MIME Error policy in No Spam Today?
j.moser
|
|
|
| Re: Attachment Filter: Message violates MIME standards: MIME syntax violation [message #1518 is a reply to message #1517 ] |
Thu, 26 October 2006 17:32  |
support
Messages: 889
Registered: April 2004 |
Senior Member |
|
|
This snippet looks as if the mail in question was a nested multipart message, where the inner message used the same boundary marker as the outer message. This might work with some mail clients, or even most mail clients, but it is incorrect.
Customer Support
Byteplant GmbH
|
|
|
| Re: Attachment Filter: Message violates MIME standards: MIME syntax violation [message #1519 is a reply to message #1518 ] |
Thu, 26 October 2006 18:19 |
J.Moser
Messages: 2
Registered: October 2006 |
Junior Member |
|
|
hello,
thanks for your answer. in this case, it is not _my_ problem 
btw. is it possible, that this kind of mail with broken MIME will get another fault-reply than the standard reject message (as defined in nospamtoday.cf with the varible RejectMessage)?
j.moser
|
|
|
| Re: Attachment Filter: Message violates MIME standards: MIME syntax violation [message #1520 is a reply to message #1519 ] |
Fri, 27 October 2006 09:57 |
support
Messages: 889
Registered: April 2004 |
Senior Member |
|
|
> btw. is it possible, that this kind of mail with broken MIME
> will get another fault-reply than the standard reject message
> (as defined in nospamtoday.cf with the varible RejectMessage)?
This suggestion has been on our "Todo" list for quite some time.
Customer Support
Byteplant GmbH
|
|
|
| Re: Attachment Filter: Message violates MIME standards: MIME syntax violation [message #1521 is a reply to message #1517 ] |
Tue, 21 November 2006 08:46 |
Dave Camenisch
Messages: 30
Registered: December 2004 |
Member |
|
|
I have the same problem... It forced me to disable the mime filter 
-- Dave
|
|
|
| Re: Attachment Filter: Message violates MIME standards: MIME syntax violation [message #1522 is a reply to message #1517 ] |
Thu, 14 December 2006 21:54 |
Mark Haller
Messages: 27
Registered: August 2004 |
Junior Member |
|
|
Hi there,
I have the exact same problem and need to get a fix for this urgently.
Even worse - the person sending mails has been using the same address for a very long time (a couple of years) so he is a "regular" of GOOD MAIL through NST.
What is the solution to this?
Regards
Mark in England
|
|
|
| Re: Attachment Filter: Message violates MIME standards: MIME syntax violation [message #1523 is a reply to message #1522 ] |
Mon, 18 December 2006 11:33 |
support
Messages: 889
Registered: April 2004 |
Senior Member |
|
|
Well, as stated earlier in this thread, the only thing you can do is to set the MIME error policy something other than reject/delete.
This should not give you sleepless nights, because so far no worms or viruses are known that exploit bad MIME syntax to get past virus filters or attachment filters.
Customer Support
Byteplant GmbH
|
|
|
| Re: Attachment Filter: Message violates MIME standards: MIME syntax violation [message #1524 is a reply to message #1517 ] |
Fri, 22 December 2006 21:51 |
Heidner
Messages: 121
Registered: February 2005 |
Senior Member |
|
|
One of the most common violations of the MIME RFC's that I see -- is the improper use of CRLF's. The RFC requires them in many places and a lot of e-mail programs miss using both CRLF or putting them in the correct locations (like before and after the MIME boundary records...)
In a future version of the MIME filter it would be nice if we could select which portions of MIME violations are scored... and possibly include a warning line (similar to spamassassins) that the e-mail might be mime non-compliant. The latter would allow the users to get back to the senders and put pressure on the non-compliant e-mail programs.
|
|
|
| Re: Attachment Filter: Message violates MIME standards: MIME syntax violation [message #1525 is a reply to message #1517 ] |
Thu, 22 March 2007 23:04 |
dpw27
Messages: 1
Registered: March 2007 |
Junior Member |
|
|
Hi,
We are using No Spam Today! Service (V2.3.5.5) and the MIME filter is picking up more and more "incorrect" MIME headers. Most are apple mail - these are only picked up if they contain an attachment.
Also we have noticed this new detection:
--=======AVGMAIL-4601F8F665D7=======
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0066_01C76C97.6577CCC0"
------=_NextPart_000_0066_01C76C97.6577CCC0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
------=_NextPart_000_0066_01C76C97.6577CCC0
Content-Type: text/html; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
------=_NextPart_000_0066_01C76C97.6577CCC0--
--=======AVGMAIL-4601F8F665D7=======
Content-Type: text/plain; x-avg=cert; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Content-Description: "AVG certification"
--=======AVGMAIL-4601F8F665D7=======--
Does this filter add any value to maintaining the integrity of our inbound email? or should we switch this off?
Can an exception be written for apple mail and AVG headers?
Thanks,
David
|
|
|
| Re: Attachment Filter: Message violates MIME standards: MIME syntax violation [message #1526 is a reply to message #1525 ] |
Fri, 13 April 2007 12:25 |
Dave Camenisch
Messages: 30
Registered: December 2004 |
Member |
|
|
>> Can an exception be written for apple mail and AVG headers?
Would be a nice feature!
-- Dave
|
|
|
Members
Search
Help
Register
Login
Home
