We should try making this plainer, somehow. Sure, we can say that it is in the docs, and that anyone administering a mail server ought to know already, but that won't change the fact that we get this problem every week! Obviously, the notices we have about this simpy don't do the trick.

Initially, I thought that maybe we ought to make James fail on startup with a big plain message written to both the log and the console when there are no DNS servers configured. Then I realised that that might get me fired. We actually use James with no DNS servers in order to process inbound-only mail, with no possibility of relaying. I think it would be good to be able to keep that deployment scenario in our bag of tricks.

We could, however, tone down the fail on startup to a simple warning in the log and on the console. Does anyone have any objections?

Cheers

ADK

Noel J. Bergman wrote:

My best guess is that your DNS server entry needs to be configured.

--- Noel

-----Original Message-----
From: Pierre Grimaud [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 10, 2003 20:27
To: [EMAIL PROTECTED]
Subject: Re: Bugzilla 16949


Something must be wrong with my config then, sorry about the inconvenience...

I'll try to look up some infos in the forums/faq

Thanks!

Pierre GRIMAUD
1035 Valerian Way
Sunnyvale, California 94086
408-730-1533
[EMAIL PROTECTED]


----Original Message Follows----
From: "Noel J. Bergman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: Bugzilla 16949
Date: Mon, 10 Feb 2003 20:25:01 -0500

As you can see, James sends to Hotmail just fine.

--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to