> Ok. I've attached the message here. It has a Content-Type charset > specified. It also specifies a Content-Transfer-Encoding header. Both were > inserted by mutt. What courier did was not to change the headers, but to > re-order them, and that caused the signature to become invalid. So, the > question is, why did courier change the order of the headers when they were > perfectly valid? Simple: it mustn't. sendmail had the same bug, and they fixed it in 8.9.3.
- Re: problem using quoted printable encoding wi... Anand Buddhdev
- Re: problem using quoted printable encodin... Suresh Ramasubramanian
- Re: problem using quoted printable encoding with gp... Thomas Roessler
- Re: problem using quoted printable encoding wi... Thomas Roessler
- Re: problem using quoted printable encodin... Thomas Roessler
- Summary: courier-mta BROKEN. Thomas Roessler
- Re: Summary: courier-mta BROKEN. Nils Vogels
- Re: Summary: courier-mta BROKEN. Anand Buddhdev
- Re: Summary: courier-mta BROKEN. Sam Varshavchik
- Re: Summary: courier-mta BROKEN. Anand Buddhdev
- Re: Summary: courier-mta BROKEN. Lars Hecking
- Re: Summary: courier-mta BROKEN. Sam Varshavchik
- Re: Summary: courier-mta BROKEN. Thomas Roessler
- Re: Summary: courier-mta BROKEN. Thomas Roessler