Wietse Venema:
> rc:
> > > > #transport
> > > > [EMAIL PROTECTED] sevenbit:[my.relayhost]
> > > > [EMAIL PROTECTED] sevenbit:[my.relayhost]
> > > > [EMAIL PROTECTED] sevenbit:[my.relayhost]
> > > > [EMAIL PROTECTED] sevenbit:[my.relayhost]
> >
> > > I recommend that you run ALL mail FROM this application through
> > > the filter so that it is always MIME compliant.
> >
> > Yes, that is exactly what I am doing on the first pass with formail.
> > This transport is only used on the second pass to convert to 7 bit
> > only email to certain destinations (the infamous Exchange 5 bug)
> > There is no way then to remove :[my.relayhost] from these entries and
> > let it use the one configured in main.cf?
>
> Yes. If sevenbit: ignores 8BITMIME announcements in EHLO replies,
> then you don't need to override the recipient domain with
> [my.relayhost].
Moreover, you can safely omit the user@ portions in your transport
map entries, because the "infamous Exchange 5 bug" (*) will happen
with all recipients that have the same domain.
Wietse
(*) Actually the behavior to bounce-instead-of-convert is legitimized
by the MIME RFCs, but we all know how politics tend to take
precedence over correctness.
