Wietse Venema:
> Bryan Arenal:
> > I'm working on moving from PMTA over to Postfix and had a question on
> > relaying for virtual domains.  We send mail on customers' behalf and
> > one of the things I'm trying to figure out is how to implement PMTA's
> > "virtual-mta" in Postfix.  This defines the destination host and
> > credentials for the relaying.  For example each of these would be
> > their own respective config file:
> 
> Would the following help:
> 
>     sender_dependent_relayhost_maps
>         per-sender relayhost via the default SMTP client
> 
>     smtp_sender_dependent_authentication 
>         per-sender SASL login information
> 
> And for really special cases:
> 
>     sender_dependent_default_transport_maps
>         per-sender delivery agent and relay host,
>         allows custom SMTP client settings.
> 
> Each has some text at 
> https://www.postfix.org/postconf.5.html#name-of-parameter
> 
> That's all Postfix has to offer. 

Oh, and while this looks like you need multiple lookup tables, the
above can be implemented with a single *SQL database table. Just
set up the right queries on the Postfix side.

> Postfix does not virtualize delivery status notification messages.
> If mail can't be delivered then the user will receive a message that
> comes from the hostname in main.cf:mydestination, not from a virtual
> MTA.
> 
>       Wietse
> 
> > <virtual-mta smtp.office365.com-39-95002>
> > <domain *>
> >  route smtp.office365.com:587
> >  auth-username "USERNAME"
> >  auth-password "PASSWORD"
> >  use-starttls yes
> > </domain>
> > </virtual-mta>
> > 
> > <virtual-mta smtp.gmail.com-935-93737>
> > <domain *>
> >  route smtp.gmail.com:587
> >  auth-username "USERNAME"
> >  auth-password "PASSWORD"
> >  use-starttls yes
> > </domain>
> > </virtual-mta>
> > 
> > We have a lot of these; one per customer.  Is this possible to do in 
> > Postfix?
> > 
> > Thanks!
> > 
> 

Reply via email to