Benjamin Collar <[EMAIL PROTECTED]> wrote:
>Putting mail.aaa.com in rcpthosts and local would just tell qmail that
>it's okay to move the mail along, right? That, then, wouldn't solve the
>explosion problem.
No, that would try to deliver the mail locally.
>If it's impossible then the client won't use qmail.
Of course it's possible. :-)
>So please, what's the expensive, error prone way of handling it? Of
>course, I'll let them know that it may be better to fiddle with the
>Exchange servers so they'll accept mail.aaa.com, but they won't be happy
>with that.
I'm blissfully ignorant of the details of Exchange's operation. Does
it require only the envelope recipient or both the envelope recipient
and the header fields to contain aaa.com?
If it's just the envelope recipient that needs to change, put aaa.com
in control/rcpthosts and:
aaa.com:alias-aaa.com
in control/virtualdomains. If aaa.com is in control/locals, remove
it. Then in ~alias/.qmail-aaa:com-default, put:
|forward "$[EMAIL PROTECTED]"
If it requires the header to be rewritten, too, do the same as above,
but in the ~alias/.qmail-aaa:com-default, put:
|sed '1,/^$/s/mail\.aaa\.com/aaa.com/g' | forward "$[EMAIL PROTECTED]"
(That may need to be EXT2...can't tell without testing it.)
-Dave
