[Maia-users] two forward host .

[Ryan Delany (RG)]

> I don't think this will satisfy Davide's needs.  Currently (1.0.2) Maia
> injects mail back into Postfix on port 10025 (or whatever single entity
> you establish in the Maia configuration).  What Davide is asking (and
> has been asked several times before--check the archives) is to have Maia
> do the scanning for a domain, but have the flexibility of re-injecting
> this mail different servers, depending on the domain.
>
> The simple answer is this is currently not possible in 1.0.2.  I believe
> this is a feature that may be added in trunk.  I would love to have this
> feature.  It would simplify my life.  Currently I filter mail for
> several of my clients.  I then use getmail (or fetchmail) to retrieve
> the filtered messages from my server to their internal mail server.  If
> a per-domain destination were possible, I could just open say port 10025
> on their local server and inject this mail directly.

Darrick,

I guess I just have trouble understanding the difference between what oyu
want to do, and what you can do with postfix.  If you setup Postfix
correctly, the instance listening on port 10025 doesn't do anything except
accept the mail after amavis, and then the transport table will send it on
it's to it's final destination, which would seem to give an end result
identical to what you've described.  What am I missing?

For the tickets you referenced, I was the catalyst behind 392, which is
really just an alternate way to store the postfix transport table in a
mysql database instead of in a flat file.  I've set that up on my own
server in fact already and it works nicely.  I can just add a domain
direcly in the maia interface, including the transport info, and it stuffs
it into the db for me and postfix starts using it right away.

Ryan