Evolution not sending FQDN

[Troy]

Guys,

I originally started E-mailing with the Ximian team and figured to send
it to you as well.  I have attached the thread below.  When I send
E-mail from Evolution, it's not properly getting the hostname of my
workstation and sending EHLO with localhost.localdomain.  I think we
need to examine the way Evolution tries to get the hostname and modify
it so it works properly for FreeBSD.  

Thoughts?

-Troy




On Sun, 2005-03-06 at 21:16 -0600, Troy wrote:
> Jeff,
> 
> I'm not sure what functions you are using, but we need to modify those
> functions accordingly.  I have tested three other MUA's and all of them
> get the hostname of the machine properly.  The operating system is
> FreeBSD using the stable train of RELENG_5 (currently 5.4).  FreeBSD
> also uses Linux emulation so I imagine that using basic Linux calls
> should work as well. We can test/verify based on what you are using to
> call the hostname if you let me know.
> 
> Is there a place I can statically put in the hostname of the machine so
> you don't send a non-RFC compliant EHLO using localhost.localdomain
> 
> Thanks,
> -Troy
> 
> On Sun, 2005-03-06 at 21:55 -0500, Jeffrey Stedfast wrote:
> > if it uses "localhost.localdomain" then the functions to get your system
> > hostname are failing. there's nothing we can do about that.
> > 
> > Jeff
> > 
> > On Sun, 2005-03-06 at 16:39 -0600, Troy wrote:
> > > Jeff,
> > > 
> > > I found your thread with a previous user about Evolution not sending the
> > > FQDN of the workstation.  I have a strange scenario.  My evolution
> > > client is constantly sending EHLO localhost.localdomain to my mailserver
> > > rather than it's FQDN. Nowhwere in my machine (i.e. hosts file) is the
> > > localhost.localdomain used.
> > > 
> > > The client I'm using clearly has a DNS name and certainly should  be
> > > using that as it's EHLO.  
> > > 
> > > I've tried searching for a resolution, but because so many people use
> > > evolution and it's been using that nomenclature for so long, I cannot
> > > get any type of solution.  
> > > 
> > > Please let me know if there is already a patch or how I can fix this.
> > > Evolution should clearly send EHLO as it's FQDN.
> > > 
> > > Thanks,
> > > 
> > > -Troy
> > > 
> > > 
> > >