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. Standards Track [Page 2]
RFC 2183 Content-Disposition 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'. A short parameter value containing only ASCII characters, but including `tspecials' characters, SHOULDbe represented as `quoted-string'. 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). `quoted-string' and `DIGIT' are defined in [RFC 822].
Troost, et. al. Standards Track [Page 3]
RFC 2183 Content-Disposition August 1997
2.1 The Inline Disposition Type
A bodypart should be marked `inline' if it is intended to be displayed automatically upon display of the message. Inline bodyparts should be presented in the order in which they occur,subject to the normal semantics of multipart messages.
2.2 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. 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.