Gordon Messmer wrote:
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...
I don't have full control over somedomain.org, but I do have the list of
all valid email addresses. And yes, it's on another host where I cannot
access any configuration files. I have a web interface to configure the
valid accounts, but I'm not even aware of what's behind the scenes in
terms of mail server.
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
Sounds good. I assume the "alias" file is described in the
documentation, I'll look it up.
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.
How do I setup this?
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).
Fair enough, I'll do that.
Thanks for the help
Olivier