J Malcolm wrote:
> I may be missing something on FetchPop. But I believe instructions said
that I needed to add the
> domain name that the mail is being fetched from to the list of domains
hosted by James. Fine. I
> added austin.rr.com to my list of domains, and I can successfully fetch
mail from
> [EMAIL PROTECTED] But now, when I send mail to anybody else at
austin.rr.com (using my
> server as my outbound mail SMTP server), James now thinks he owns
austin.rr.com, and bounces the
> mail saying the user doesn't exist.
> What am I missing? Can I only reliably do FetchPop from a domain I never
expect to try to send
> other mail to?
The way I use is to change the mailet chain so that the matcher for local
delivery "RecipientIsLocal" is followed by one which delivers remotely for
selected domains, so we have...
<!-- If the recipient is for a local account, deliver it
locally -->
<mailet match="RecipientIsLocal" class="ToProcessor">
<processor> localTransport </processor>
</mailet>
<!-- Process 'local' servernames which are not entirely local. -->
<!-- eg: [EMAIL PROTECTED] IS local, [EMAIL PROTECTED] IS NOT
local. -->
<!-- If the host is matched, use remote delivery. -->
<mailet match="HostIs=austin.rr.com" class="ToProcessor">
<processor> remoteTransport </processor>
</mailet>
<!-- If the host is handled by this server and it did not get -->
<!-- locally delivered, this is an invalid recipient -->
<mailet match="HostIsLocal" class="ToProcessor">
<processor> local-address-error </processor>
<notice>550 - Requested action not taken: no such user
here</notice>
</mailet>
-- Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
