|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Wietse Venema (wietse
porcupine.org)
Date: Wed Oct 01 2008 - 10:23:28 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
rc:
> > Fixing the mail requires headers like:
> >
> > MIME-Version: 1.0
> > Content-type: text/plain
> > Content-transer-encoding: 8bit
> >
> > Wietse
>
> It is working now. I fixed the header externally with formail (can't
> Postfix do that without external help?)
It's the job of MUAs, mail applications, etc. to inject correctly
formatted mail into the email infrastructure. It's not the job of
an MTA to make arbitary content standards-compliant.
> I post my solution here for future references. Also any suggestions
> for improvements are welcome.
>
> #master.cf
> smtp inet n - n - - smtpd
> -o content_filter=filter:dummy
> sevenbit unix - - n - - smtp
> -o smtp_never_send_ehlo=yes
> filter unix - n n - 10 pipe
> flags=Rq user=nobody argv=/path/to/my.filter -f ${sender} -- ${recipient}
> ###############################
>
> #transport
> some1
user.com sevenbit:[my.relayhost]
> some2
user.com sevenbit:[my.relayhost]
> some3
user.com sevenbit:[my.relayhost]
> some4
user.com sevenbit:[my.relayhost]
I recommend that you run ALL mail FROM this application through
the filter so that it is always MIME compliant.
Once it is MIME compliant you can configure Postfix to always ignore
8BITMIME announcements so it converts all mail to 7bit encoding.
Or you can rely on automatic conversion when an 8BITMIME compliant
MTA (such as Postfix) sends mail to a non-8BITMIME mail server.
Wietse
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]