# MIME compliance

**URL:** <https://www.finalbuilder.com/forums/t/mime-compliance/4519>\
**Category:** Discussion\
**Created:** [July 10, 2012, 12:01pm UTC](https://www.finalbuilder.com/forums/t/mime-compliance/4519 "2012-07-10T12:01:06Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cgockel](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/c/ea5d25/32.png) [@cgockel](https://www.finalbuilder.com/forums/u/cgockel)\
**Post date:** [July 10, 2012, 12:01pm UTC](https://www.finalbuilder.com/forums/t/mime-compliance/4519/1 "2012-07-10T12:01:06Z")

</div>

Hello,

I use 'sendmail' to inform users if there occured an error. The mail is plain text with three attachments. The attachments are log-files (text) from automise. Now I have information from our IT that the mail isn't mime compliant and so gets stuck in our spamfilter (and may get stuck in our customer's spamfilters).

The error says: wrong content-disposition. Could you check this? Is there a chance to fix this? Or have I just to change the settings?

Thanks

HHK

Following is the explanation from the mime check (sorry for the formatting):

Content-Disposition: text/plain;

filename="20120710\_0005\_Nachtlauf\_FehlerMeldung.txt"

Definition:

Troost, et. al.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Standards Track&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 2]

RFC 2183&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Content-Disposition&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; August 1997

In the extended BNF notation of [RFC 822], the Content-Disposition header field is defined as follows:

disposition := "Content-Disposition" ":"

disposition-type \*(";" disposition-parm)

disposition-type := "inline" / "attachment" / extension-token ; values are not case-sensitive

disposition-parm := filename-parm / creation-date-parm / modification-date-parm / read-date-parm / size-parm / parameter

filename-parm := "filename" "=" value

creation-date-parm := "creation-date" "=" quoted-date-time

modification-date-parm := "modification-date" "=" quoted-date-time

read-date-parm := "read-date" "=" quoted-date-time

size-parm := "size" "=" 1\*DIGIT

quoted-date-time := quoted-string

; contents MUST be an RFC 822 `date-time'

; numeric timezones (+HHMM or -HHMM) MUST be used

NOTE ON PARAMETER VALUE LENGHTS: A short (length \<= 78 characters) parameter value containing only non-`tspecials' characters SHOULD be represented as a single `token'.&nbsp; A short parameter value containing only ASCII characters, but including `tspecials' characters, SHOULDbe represented as `quoted-string'.&nbsp; Parameter values longer than 78 characters, or which contain non-ASCII characters, MUST be encoded as specified in [RFC 2184]

`Extension-token', `parameter', `tspecials' and `value' are defined according to [RFC 2045] (which references [RFC 822] in the definition of some of these tokens).&nbsp; `quoted-string' and `DIGIT' are defined in [RFC 822].

Troost, et. al.&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Standards Track&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [Page 3]

RFC 2183&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Content-Disposition&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; August 1997

2.1&nbsp; The Inline Disposition Type

A bodypart should be marked `inline' if it is intended to be displayed automatically upon display of the message.&nbsp; Inline bodyparts should be presented in the order in which they occur,subject to the normal semantics of multipart messages.

2.2&nbsp; The Attachment Disposition Type

Bodyparts can be designated `attachment' to indicate that they areseparate from the main body of the mail message, and that their display should not be automatic, but contingent upon some furtheraction of the user.&nbsp; The MUA might instead present the user of a bitmap terminal with an iconic representation of the attachments, or, on character terminals, with a list of attachments from which the user could select for viewing or storage.

---

<div class="post-metadata">

**Author:** ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)\
**Post date:** [July 11, 2012, 9:41am UTC](https://www.finalbuilder.com/forums/t/mime-compliance/4519/2 "2012-07-11T09:41:42Z")

</div>

I made a minor change to the email action which may or may not fix this :   
  
 [http://downloads.automise.com/downloads/automise/400/AT400\_205.exe](http://downloads.automise.com/downloads/automise/400/AT400_205.exe)

---

<div class="post-metadata">

**Author:** ![cgockel](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/c/ea5d25/32.png) [@cgockel](https://www.finalbuilder.com/forums/u/cgockel)\
**Post date:** [July 12, 2012, 2:34am UTC](https://www.finalbuilder.com/forums/t/mime-compliance/4519/3 "2012-07-12T02:34:09Z")

</div>

Hi Vincent,

that was fast! Thanks a lot! That seems to fix it.

Regards

HHK