<p>thks yr reply</p><p>ok, the local user for the postmaster role is there. your idea reg. local users and forward files sounds to be a solution. i will try it.</p><p>thks</p><p>dhf</p><p> </p>

hello forum, testing mercury/32 as gateway ( module S and C ) for all inbound mails to check some good features which our old exchange2k doesn't have. mercury has no local users, module c send all mails to our internal exchange server. works fine so far. problem: i want to accept (on transaction level) mails for those users only, who hv a exchange account. i can provide a whitelist for valid rcpt to's, but i can't see how to setup in the module S. is it possible at all? are there other solutions to overcome this problem? thks in adv dhf

<blockquote>mercury has no local users, module c send all mails to our internal exchange server. works fine so far.</blockquote><p>Mercury must always have at least one local user to act as postmaster.</p><blockquote>problem: i want to accept (on transaction level) mails for those users only, who hv a exchange account. i can provide a whitelist for valid rcpt to's, but i can't see how to setup in the module S. is it possible at all? are there other solutions to overcome this problem?</blockquote>I assume that you want to only accept mail at MercuryS for users if they have a valid local account and this cannot be done at MercuryS unless they have a local account. and so the easiest way to do this is to give all the Exchange users a local account and then use a forward file in the local account to forward the mail to the Exchange account. Might be a pain to do for the initial setup but can be better way to move the mail.  Might even be able to use one of the various tools available for the Exchange server to pull the mail from the user accounts via POP3 as well.  Might even be a cleaner way to get all the mail to the Exchange host.