273685Re: SMTP proxy????
- Feb 1, 2011On Tue, Feb 01, 2011 at 07:11:52PM +0100, Ignacio Garcia wrote:
> > This splits into two use-cases:In addition to recipient lists, you need mailstore locations, and
> > * Relay
> > - Each server accepts mail for the other's domains, and relays
> > them to the right server. All you need is access to a table
> > of valid recipients for the relay domains, and table of
> > said domain names.
> > * Full-service:
> > - Each server accepts mail for all the domains, and delivers
> > to the correct mail store. Need fully unified data model.
> > Which use-case are you aiming for?
> definitely full-service. I do not understand whan you say that I need a
> fully unified data model.
transport settings, ... to actually deliver the mail.
> >> - both servers need to check against both databases for validThis is for the "relay" use-case.
> >> destinations
> > Correct (s/destinations/user-addresses/).
> ypu're right.
> >> - each server must know if delivery is to be local or it has to be
> >> relayed to the other server.
> > Postfix does that automatically. Just add the domain to "relay_domains"
> > and not to virtual_mailbox_domains, or similar.
> >> - one server virtual_transport=maildrop (to courier-imap), the otherSorry, for the full-service use case, both sets of SMTP servers
> >> =dovecot (we are going with dovecot for the future, the one with courier
> >> is older, but plenty of users)
> > The difference in final delivery mechanisms is immaterial.
need to support both delivery mechanisms and choose the correct
one for each user.
Ideally it would be LMTP for both, and the IMAP servers would handle
the delivery logistics.
> So, can you point me to the right direction in learning how to get theLearn about virtual_alias rewriting or per-user transports in
> full-service configuration done?
ADDRESS_REWRITING_README.html. Strongly consider using LMTP for
all MTA -> Mail store deliveries, so that the MTA does not need
to understand the internal architecture of the IMAP store.
- << Previous post in topic Next post in topic >>