`Content-Transfer-Encoding' SendMail
I have SendMail configured with the Smart_Host directive: define(~SMART_HOST'. `my.isp.com') since they are blocking out bound port 25. This works well. The problem I am experiencing is that all mail sent this way has the following in the email header: Content-Transfer-Encoding: quoted-printable I do not want to use that encoding specifically at all times. Even when set within my mail program for something else, such as 8-bit, it is still converted to the above format. What can I do to prevent this from happening? -- Gerard E. Seibert [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: `Content-Transfer-Encoding' SendMail
Gerard Seibert wrote: [ ...relaying email via your ISP... ] Content-Transfer-Encoding: quoted-printable I do not want to use that encoding specifically at all times. Even when set within my mail program for something else, such as 8-bit, it is still converted to the above format. What can I do to prevent this from happening? Nothing, really. Any MTA along the delivery path is allowed to change the encoding to quoted-printable, and many MTA's will do so even if the other side advertizes the 8BITMIME ESMTP extension. You can avoid seeing that header if you send mail that does not contain non-printable characters, or if the receiving MTA converts the mail back to an 8-bit format. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: `Content-Transfer-Encoding' SendMail
I have SendMail configured with the Smart_Host directive: define(~SMART_HOST'. `my.isp.com') since they are blocking out bound port 25. This works well. The problem I am experiencing is that all mail sent this way has the following in the email header: Content-Transfer-Encoding: quoted-printable I do not want to use that encoding specifically at all times. Even when set within my mail program for something else, such as 8-bit, it is still converted to the above format. What can I do to prevent this from happening? From my naive understanding of the smtp protocol I think that your sendmail and your provider's sendmail|qmail|postfix ask each other about supported encodings. When I telnet to my mail provider's port 25 and manually submit an EHLO I see a list of 250 responses. One shows me '250 8bitmime'. So I'd suggest you test this with your provider. Norbert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: `Content-Transfer-Encoding' SendMail
On Tuesday, July 19, 2005 10:16:00 AM Chuck Swiger [EMAIL PROTECTED] wrote: Gerard Seibert wrote: [ ...relaying email via your ISP... ] Content-Transfer-Encoding: quoted-printable I do not want to use that encoding specifically at all times. Even when set within my mail program for something else, such as 8-bit, it is still converted to the above format. What can I do to prevent this from happening? Nothing, really. Any MTA along the delivery path is allowed to change the encoding to quoted-printable, and many MTA's will do so even if the other side advertizes the 8BITMIME ESMTP extension. You can avoid seeing that header if you send mail that does not contain non-printable characters, or if the receiving MTA converts the mail back to an 8-bit format. -- -Chuck ** Reply Separator ** Tuesday, July 19, 2005 6:46:32 PM If I send a message through my ISP and do not use SendMail, the mail arrives as I sent it. If I throw SendMail into the mix, it always arrives as quoted-printable. I checked with my ISP. They claim that the mail is being changed on my end. They do not alter the Content-Transfer-Encoding method. -- Gerard E. Seibert [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
