5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] courier and DKIM| From | Sent On | Attachments |
|---|---|---|
| Dino Ciuffetti | Apr 25, 2010 3:36 am | |
| Alessandro Vesely | Apr 25, 2010 4:19 am | |
| Dino Ciuffetti | Apr 25, 2010 11:56 am | |
| Harry Duncan | Apr 25, 2010 1:50 pm | |
| Sam Varshavchik | Apr 25, 2010 5:08 pm |
| Subject: | Re: [courier-users] courier and DKIM | |
|---|---|---|
| From: | Harry Duncan (usr....@gmail.com) | |
| Date: | Apr 25, 2010 1:50:54 pm | |
| List: | net.sourceforge.lists.courier-users | |
On Sun, Apr 25, 2010 at 7:56 PM, Dino Ciuffetti <di...@tuxweb.it> wrote:
Found the mail header modification that cause DKIM verification problem in my case from mails coming from gmail.com (and other) to my courier servers.
It's "Content-Type" header. Its value is not case protected by the DKIM
relaxed alghoritm specification at sign level, even if CT value should be
trated as case insensitive.
Sam, since changing/fixing the DKIM canonicalization standard is not a simple thing and will probably require a long time, is it possibile / may have sense / would you have time and desire to write a work around in courier to leave the CT value as it comes from the remote smtp client if it is not broken (avoid changing ISO-8859-1 to iso-8859-1)?
If memory serves me right this problem crops up with Courier MLM modifying a message when it is being redistributed. In that case, shouldn't the solution be that CourierMLM resigns the message as the origin of the distributed message? Other than that to my mind, you are going to end up chasing a never ending list of exceptions where something gets changed and DKIM breaks, and sticking plaster after sticking plaster to keep it working.
Harry.
------------------------------------------------------------------------------
_______________________________________________ courier-users mailing list cour...@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users