Alessandro Vesely writes:

On 02/Aug/10 20:21, Sam Varshavchik wrote:
Alessandro Vesely writes:
My understanding is that the message was rewritten because it missed
an explicit "Content-Transfer-Encoding: 7bit". I see two ways of
fixing this with one liners:

Message rewriting is a fundamental operation. This concept has existed
since the very beginnings of email, where message rewriting was
common, as email transited between wildly different environments.

Let me recall that, in this case, what is obtained by the rewriting is a header field like

    Content-Transfer-Encoding: 7bit

which is the default.  Is it worth rewriting a message just for that?

This is a subjective viewpoint. In some cases its worth it, in others it's not. There are obvious benefits to standardizing the format of all outgoing messages. I think that's a worthwhile thing to do.

Still, header writing is still as valid today as it ever been. Any
scheme that breaks because of it, is exactly this: broken. If DKIM
gets broken when mail headers are writing and standardized, it's DKIM
that's broken, fundamentally, and that's what should be fixed.

Coping with broken environments, as you just recalled, has always been done.

Only to a certain degree. Another subjective notion is when enough becomes too much.

What I'm proposing is to adjust the advantage vs. annoyance balance by avoiding rewriting when it is /safe/ to do so. I completely agree that DKIM should be fixed, but we both know that that won't happen any time soon. Can Courier cope?

Courier can cope with DKIM-formatted messages just fine. It simply ignores that stuff. The problem is DKIM not coping with Courier, or, for that matter, any mail server that edits mail headers.

Attachment: pgpWg0pYrd18U.pgp
Description: PGP signature

------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to