[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] mails of 2 domains -> to 1 domain
- Subject: Re: [cobalt-users] mails of 2 domains -> to 1 domain
- From: "Ben Feldmann" <RaQ@xxxxxxxxxxx>
- Date: Thu Feb 8 09:32:16 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Hi,
thx u....
...sorry, but your solution doesn't work.
Now I will create a new virtual site for the domain1.net with forwardings of each mail alias to alias@xxxxxxxxxxxxxx
Does anybody know whether a module for sendmail exists which can relay mails (alias@xxxxxxxxxxx) by analyzing their aliases and send them to alias@xxxxxxxxxxxxxxx
Ben
>>** But if I want to send a mail to info@xxxxxxxxxxxx (MX->www.icreatix.de, 62.40.13.24 where the alias is set up) the following error message comes back from my free e-mail **provider which I want to send the mail through.
>>
>>62.40.13.24 does not like recipient.
>>Remote host said: 550 <info@xxxxxxxxxxxx>... Relaying denied. Please check your mail first.
>>Giving up on 62.40.13.24.
>>
>>What could cause this message?
>
>Ben,
>
>Sorry if this response is a bit "muzzy", but I'm dealing still with
>these Cobalt upgrade issues that have effective shut down my systems (as
>explained in email to this list last night) with no end in sight.
>
>At any rate, the problem is not so much that "62.40.13.24 does not like
>recipient" but that they are not allowing you to relay through them.
>
>Since you can't add yourself to their relay table, here's what I'd do:
>
>Set up the MX for domain1 to go to domain2. Yes, you read that right.
>
>Then, log in on your box as root, and do the following:
>
>1) cd /etc
>2) vi virtusertable
>3) At the VERY bottom, add the following (with the right domain, of
> course):
>
>@domain2.com someaddress@xxxxxxxxxxx
>
>Where "someaddress" is the address you want it to go to.
>
>4) /usr/bin/makemap hash /etc/virtusertable.db < /etc/virtusertable
>
>What you have done is to make all email for domain1 go to domain2. You
>have then set *anything* going to domain2 to go to a single mailbox at
>62.40.13.24. If you don't want *all* mail being routed to a single
>mailbox, then set up separate entries in virtusertable:
>
>addr1@xxxxxxxxxxx addr1@xxxxxxxxxxx
>addr2@xxxxxxxxxxx addr2@xxxxxxxxxxx
>(and so on)
>
>Note that the space between the entry "@domain2.com" and the address is
>NOT a or even many spaces, but a TAB.
>
>If you're at all uncomfortable with hacking around in the virtual user
>table, as above, then do this as step 2a:
>
>mkdir /root/mybackups
>cp virtusertale* /root/mybackups
>
>Alternatively, you could, instead of setting "up the MX for domain1 to go
>to domain2" just put entries for *both* domain1 and domain2 in your
>virtusertable file.
>
>-Arf, JT
>------------------------------------------------------------------------------
> "If I knew what was going on, I'd *really* be indignant!"
> - Crow, "Mystery Science Theatre 3000"
>
> Join the UniServe Seti@Home Team: http://www.unisrv.net/computerguys/seti
>
>Unix, Networking and ISP Consulting lfm@xxxxxxxxxx
>http://www.unisrv.net MSN IM: S_A_Alis@xxxxxxxxxxx ICQ 9099687
>FurryMUCK (muck.furry.org 8888): S'A'Alis www.unisrv.net/lfm MSTie# 21756
>
>_______________________________________________
>cobalt-users mailing list
>cobalt-users@xxxxxxxxxxxxxxx
>To Subscribe or Unsubscribe, please go to:
>http://list.cobalt.com/mailman/listinfo/cobalt-users