 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
1 message in net.sourceforge.lists.courier-users[courier-users] mime boundary modific...| From | Sent On | Attachments |
|---|---|---|
| Oliver Jusinger | Dec 24, 2004 4:42 pm |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | [courier-users] mime boundary modification | Actions... |
|---|---|---|
| From: | Oliver Jusinger (joli...@gmx.at) | |
| Date: | Dec 24, 2004 4:42:39 pm | |
| List: | net.sourceforge.lists.courier-users | |
Courier is modifying the mime boundaries of our outgoing mails. The problem:
Some few recepients are using a greylisting which hashes the complete mail. Ours mails are not accepted on the second attempt, because Courier creates new boundaries on every resend (see details below).
Most important for me: It seems like a bug for me, that courier creates new boundaries on every resend attempt (I am not too happy with greylisting, but that's not the question here). The result is, all mime formated mails are not accepted.
Besides I am interested why the boundaries are reformatted anyway. I could not google any explanations, maybe somebody has a link or some info? (I admit I am not too familar with courier. Sorry if this question is too "newbie" in this list).
Now the details:
1) Original body of our outgoing mail:
This is a MIME encoded message.
--=_ad9d6b78cc5df1835dd63162590fa2db Content-Type: multipart/alternative; boundary="=_8037e88464f7de3605ba3026253e5cbb"
--=_8037e88464f7de3605ba3026253e5cbb Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit
2) traffic logged by sniffit:
1st attempt: This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages.
--=_www-2966-1103933092-0001-2 Content-Type: multipart/alternative; boundary="=_www-2966-1103933092-0001-3"
This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages.
--=_www-2966-1103933092-0001-3 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit
2nd attempt: This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages.
--=_www-3196-1103933392-0001-2 Content-Type: multipart/alternative; boundary="=_www-3196-1103933392-0001-3"
This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages.
--=_www-3196-1103933392-0001-3 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit
Versions: ii courier-base 0.47-3 Courier Mail Server - Base system ii courier-maildr 0.47-3 Courier Mail Server - Mail delivery agent ii courier-mlm 0.47-3 Courier Mail Server - Mailing list manager ii courier-mta 0.47-3 Courier Mail Server - ESMTP daemon ii courier-mta-ss 0.47-3 Courier Mail Server - ESMTP over SSL ii courier-ssl 0.47-3 Courier Mail Server - SSL/TLS Support
greetings Oliver