[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Smail not delivering mail to local domain



Pat,

I had the same problem and made the same change.  Sorry I didn't recognize
that when you posted your query; I made the change to the hostnames line
in /etc/smail/config more on a hunch than based on actually understanding
what I was doing ;-), and I promptly forgot about it.  I had already
set up the corporate M$-Exchange server as the smarthost (that term
is a little ironic in this case?) but could not get the mail routed
through it for in-company mail without removing the ":mycompany.com"
domain specification, as you did.

I had no local support on this because I'm running the "wrong" softare
(i.e. Linux) as my desktop OS, so I just hacked away until it worked.
I have wondered if there was a better way to solve this and would agree
that a FAQ that spelled out how to deal with this situation would be
most helpful.  This is not an esoteric configuration problem.

Bottom line: I have had no problems with mail since setting it up.

Regards - MikeT
(Not to be confused with miket (my son) who posts actual helpful info.)

On Wed, Dec 16, 1998 at 12:44:15PM +0000, Patrick Colbeck wrote:
> 
> Recently I posted about smail being able to deliver mail via smtp to remote
> domains but not to users on my own domain unless they existed on the box smail
> was running on. Basically I wanted mail for these users to be delivered to the
> company mail server.
> 
> Several people have offered solutions using smartuser or smartrelay but for
> once I have come up with a simple solution myself so incase anyone else has
> the same problem here it is.
> 
> In /etc/smail/config as setup by debian there is a line like this
> 
> hostnames=hostname.domain:domain
> 
> eg
> 
> hostname=workstation1.somecompany.com:somecompany.com
> 
> change it to
> 
> hostname=hostname.domain.com
> 
> eg
> 
> hostname=workstation1.somecompany.com
> 
> Now it should work properly and hand off all mail for users not on
> workstation1 to whatever dns turns up as an mx record dor the domain.
> 
> If anyone has any comments about any negative effects of this solution please
> mail me.
> 

-- 
Michael E. Touloumtzis <toumi01@cai.com>


Reply to: