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

Re: exim HELO=fully qualified host name?

On 2004-02-06, David Clymer penned:
> On Fri, 2004-02-06 at 12:11, Monique Y. Herman wrote:
>> On 2004-02-06, David Clymer penned:
>> > On Fri, 2004-02-06 at 09:07, davis wrote:
>> >> Hello
>> >> 
>> >> I can not subscribe to the pcmcia-cs mailing list on source forge
>> >> because my helo only gives my host name and not my fully qualified
>> >> hostname.  How do I resolve this problem?
>> >> 
>> >> JD
>> >> 
>> >
>> > You need to set exim's primary_hostname to your FQDN (or the
>> > equivilant configuration variable for your choice of MTA).
>> >
>> I believe that exim will, by default, report the first entry in your
>> /etc/hosts file.  So if you have
>>	booger yoda www.sticky.net
>> I believe exim will report the machine as booger.
>> Just move the FQDN into the first slot and you should be fine.
>> My understanding is that exim's primary_hostname setting is
>> considered a kludge and that it's "better" to use the above method.
> I learn something new every day, it seems. I suppose I should modify
> my own server, if thats the case. Could you expound apon the
> "kludge-ness" of primary_hostname?

I wish I could.  I just remember having this same problem and asking on
a list ... I think it was the exim-user mailing list, but I can't seem
to find the answer in the archives.  I think the implication was "if
your canonical hostname isn't fully qualified, you have bigger problems
than exim.  Don't patch exim's config -- fix the problem at its source."


Reply to: