I belive that's simply a pine configuration. The other thing is to
make sure is that you're not masquerading. Often times on mail hubs we
do that deliberately so all the mail has a consistent return address.
But in your case, you probably want to make sure sendmail is not
masquerading. That's all controlled by macros, so look at the *mc file
your using to build sendmail.cf.
-- Rob
--On 09/23/00 11:14:59 PM -0500 Jonathan Wilson <[EMAIL PROTECTED]>
wrote:
> hmm...I put the new domain first, in the sendmail.cf file, but when I
> sent a test mail from pine it's still using the old box.domain.tld.
> Is that because that's what' in /etc/hosts, if so does this simply
> mean that I have to change the box's hostname to the new domain
> alltogether?
>
> JW
>
>
> At 11:12 AM 9/22/2000 -0700, you wrote:
>> I'm presuming you're not interested in keeping domains separate
>> within sendmail (that is, set up virtual domains within sendmail).
>> If that assumption is correct, simply add all hostnames, hostname
>> and hostname+domain (ie., fully qualified) to the sendmail.cw file.
>> Sendmail will then happily act as the final delivery agent for the
>> those hosts. Sendmail can also, I believe, be configured to include
>> that information directly in the sendmail.cf file, but my book with
>> the m4 macros for building sendmail.cf is at my other office so I
>> can't give you syntax if you prefer to not include the sendmail.cw
>> file.
>>
>> -- Rob
>>
>>
>> --On 09/22/00 11:58:32 AM -0500 Jonathan Wilson <[EMAIL PROTECTED]>
>> wrote:
>>
>>> Howdy,
>>>
>>> We now have several domain names pointing to our main Red Hat
>>> server. Most of them are for various web sites and are only used
>>> by Apache. However we do have this situation: our original
>>> intention was to name this box newhostname.our_domain.our_tld and
>>> we did, and that's what's in /etc/hosts however we can't send mail
>>> to that box because all mail going to our domain is snarfed up by
>>> our NT mail server :-/ which my boss doesn't want to change.
>>>
>>> So he bought a new domain name today, just for the Linux server, the
>>> primary reason being that we should now be able to send and receive
>>> mail there.
>>>
>>> So my question is, do I need to put the new domain name in
>>> /etc/hosts, or anywhere else? If not will it affect sendmail? Will
>>> sendmail pick up mail sent to that domain simply because the DNS and
>>> MX record point there? And how will it know to put "from:
>>> *@newdomain.com" on outgoing mail?
>>>
>>> Basically I've never dealt with multiple host/domain names and I'm
>>> not sure what to do :-)
>>>
>>>
>>> JW
>>>
>>>
>>>
>>> _______________________________________________
>>> Redhat-list mailing list
>>> [EMAIL PROTECTED]
>>> https://listman.redhat.com/mailman/listinfo/redhat-list
>>
>>
>>
>>
>> _ _ _ _ _ _ _ _ _ _
>> /\_\_\_\_\ /\_\ /\_\_\_\_\_\
>> /\/_/_/_/_/ /\/_/ \/_/_/_/_/_/ QUIDQUID LATINE DICTUM SIT,
>> /\/_/__\/_/ __ /\/_/ /\/_/ PROFUNDUM VIDITUR
>> /\/_/_/_/_/ /\_\ /\/_/ /\/_/
>> /\/_/ \/_/ /\/_/_/\/_/ /\/_/ (Whatever is said in Latin
>> \/_/ \/_/ \/_/_/_/_/ \/_/ appears profound)
>>
>> Rob Tanner
>> McMinnville, Oregon
>> [EMAIL PROTECTED]
>>
>>
>>
>> _______________________________________________
>> Redhat-list mailing list
>> [EMAIL PROTECTED]
>> https://listman.redhat.com/mailman/listinfo/redhat-list
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
_ _ _ _ _ _ _ _ _ _
/\_\_\_\_\ /\_\ /\_\_\_\_\_\
/\/_/_/_/_/ /\/_/ \/_/_/_/_/_/ QUIDQUID LATINE DICTUM SIT,
/\/_/__\/_/ __ /\/_/ /\/_/ PROFUNDUM VIDITUR
/\/_/_/_/_/ /\_\ /\/_/ /\/_/
/\/_/ \/_/ /\/_/_/\/_/ /\/_/ (Whatever is said in Latin
\/_/ \/_/ \/_/_/_/_/ \/_/ appears profound)
Rob Tanner
McMinnville, Oregon
[EMAIL PROTECTED]
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
