* <[EMAIL PROTECTED]> [13/07/2005 1103EDT]: > On Wed, 13 Jul 2005, Keith Warno wrote: [...] > >Our primary MX currently points to our qmail box. I want to keep it > >this way. Some of the local users need the third-party Exchange service > >and the rest do not, so basically I need the qmail box to deliver mail > >locally for some users and relay mail to the Exchange box for those > >users who need the Exchange service. The Exchange service will also > >(probably) require SMTP auth, so the qmail box will have to be able to > >authenticate itself on behalf of those senders that are relaying thru it > >to the Exchange box. > I do this, but I don't want all my root mail forwarding to exchange, since > it has the possibility of killing it. I just put a .qmail file in the home > directories of the accounts that I want to forward, and setup exchange to > accept those message, I forward to <account>@exchange.domain.com, where > the MX record for domain.com is the qmail box (boxes actually). This works > great. You can also do this within LDAP by setting a > mailForwardingAddress, or using maildrop (via deliveryProgramPath) then > setting a .mailfilter file in the users home directory.
Good idea but it won't work for us because the only domain the exchange
server accepts mail for is 'valaran.com', the same domain that the qmail
box is the MX for and accepts mail & delivers locally for. In other
words, in a user's .qmail would have "&[EMAIL PROTECTED]", which will
loop. :)
Is there some program I can use via a .qmail program line that, when a
mail comes in for a user, it'll establish an SMTP connection to the
exchange box? Oh wait.... how about calling qmail-remote directly?
Does it make sense to do
|qmail-remote exchange.server.whatever "$SENDER" "$RECIPIENT"
?
--
SA Valaran Corp
GPG: 0xEC705AE9
I put the sh in IT.
pgpzNEM77hhxJ.pgp
Description: PGP signature
