Olivier Sannier wrote:
My courierd server is set as the MX for SomeDomain.com
When it's for SomeDomain.com, anything that gets delivered to it gets
forwarded transparently to the same address at SomeDomain.org
That's fairly simple. Do you have access to "somedomain.org"? I'm
assuming it's on another host. The easiest thing to do would be to add
somedomain.com to that host, but I'm also assuming you have some reason
to not to that...
If you're able to get a list of the valid addresses on somedomain.org,
then you can:
* add somedomain.org to esmtpacceptmailfor and hosteddomains
* create an alias file mapping all of the somedomain.org addresses to
somedomain.com
You'll also want to make arrangements on the MX for somedomain.org
server so that it never rejects messages from the MX from
somedomain.com. If it does, your queue and postmaster account are going
to fill up with spam, and the server will be difficult to manage properly.
It's possible to do a wildcard forward, but there are serious
disadvantages to doing so.
On top of that, I'd like to act as an open relay for a selected list of
accounts, provided they identify themselves during the STMP transfer.
That's not an open relay. An open relay is a machine that relays mail
without any checks on the origin or destination.
What you want is actually courier's default configuration. Set up
accounts for the users that you want to be able to relay mail, and then
configure their mail clients to authenticate themselves (and use SSL).
So in the end, none of the accounts actually receive any mail.
Do you think that's feasible with courier?
Yes.
8 messages in net.sourceforge.lists.courier-usersRe: [courier-users] SMTP relay from a...
