Re: exim HELO=fully qualified host name?

On 2004-03-02 12:48:47 -0500, Derrick 'dman' Hudson wrote: > On Tue, Mar 02, 2004 at 04:31:22PM +0100, Vincent Lefevre wrote: > | Before exim was fixed in Debian, several messages I'd sent were > | rejected by some SMTP server. > > When the rejects happeend you became aware of the issue and you fi

Re: exim HELO=fully qualified host name?

On Tue, Mar 02, 2004 at 04:31:22PM +0100, Vincent Lefevre wrote: | On 2004-03-02 09:02:23 -0500, Derrick 'dman' Hudson wrote: | > RFC 2821, section 4.1.1.1 Extended HELLO (EHLO) or HELLO (HELO) | > | >The argument field contains the fully-qualified domain name of the | >SMTP client if one

Re: exim HELO=fully qualified host name?

On 2004-03-02 09:02:23 -0500, Derrick 'dman' Hudson wrote: > RFC 2821, section 4.1.1.1 Extended HELLO (EHLO) or HELLO (HELO) > >The argument field contains the fully-qualified domain name of the >SMTP client if one is available. In situations in which the SMTP >client system does not

Re: exim HELO=fully qualified host name?

On Tue, Mar 02, 2004 at 10:31:58AM +0100, Vincent Lefevre wrote: | On 2004-03-01 15:08:17 -0500, Derrick 'dman' Hudson wrote: | > On Sun, Feb 29, 2004 at 10:16:23PM +0100, Vincent Lefevre wrote: | > | RFC 2821: | > | | > |An SMTP server MAY verify that the domain name parameter in the EHLO | >

Re: exim HELO=fully qualified host name?

On 2004-03-01 15:08:17 -0500, Derrick 'dman' Hudson wrote: > On Sun, Feb 29, 2004 at 10:16:23PM +0100, Vincent Lefevre wrote: > | RFC 2821: > | > |An SMTP server MAY verify that the domain name parameter in the EHLO > |command actually corresponds to the IP address of the client. > |Ho

Re: exim HELO=fully qualified host name?

On Sun, Feb 29, 2004 at 10:16:23PM +0100, Vincent Lefevre wrote: | On 2004-02-23 22:24:28 -0500, Derrick 'dman' Hudson wrote: | > That depends on who's mail server you connect to. Some admins require | > the HELO parameter to be resolvable, and some even require it to | > resolve to the IP of the

Re: exim HELO=fully qualified host name?

On 2004-02-23 22:24:28 -0500, Derrick 'dman' Hudson wrote: > That depends on who's mail server you connect to. Some admins require > the HELO parameter to be resolvable, and some even require it to > resolve to the IP of the machine making the connection. They should fix their configuration, then

Re: exim HELO=fully qualified host name?

On Wed, Feb 11, 2004 at 06:15:29AM +0100, Vincent Lefevre wrote: | On 2004-02-06 17:31:21 -0500, David Clymer wrote: | > for instance, when communicating with a remote host, it would seem to me | > that the logical hostname to supply (as a self reference) would be a | > hostname which is resolvable

Re: exim HELO=fully qualified host name?

On 2004-02-06 17:31:21 -0500, David Clymer wrote: > for instance, when communicating with a remote host, it would seem to me > that the logical hostname to supply (as a self reference) would be a > hostname which is resolvable via DNS rather than an /etc/hosts alias > which is inaccessable to the r

Re: exim HELO=fully qualified host name?

On 2004-02-06 10:11:32 -0700, Monique Y. Herman wrote: > I believe that exim will, by default, report the first entry in your > /etc/hosts file. No, it doesn't. This would be a bug if it did that. -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: - 100% validated (X)HTML - A

Re: exim HELO=fully qualified host name?

On Fri, 2004-02-06 at 14:32, Derrick 'dman' Hudson wrote: > On Fri, Feb 06, 2004 at 01:26:10PM -0500, David Clymer wrote: > | 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: > > | > >> I can not subsc

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 giv

Re: exim HELO=fully qualified host name?

On Fri, Feb 06, 2004 at 01:26:10PM -0500, David Clymer wrote: | 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: | > >> I can not subscribe to the pcmcia-cs mailing list on source forge | > >> because my h

Re: exim HELO=fully qualified host name?

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 >

Re: exim HELO=fully qualified host name?

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

Re: exim HELO=fully qualified host name?

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 FQD

Re: exim HELO=fully qualified host name?

I think I solved this problem on my server (not 100% sure) by updating /etc/hosts like that : 127.0.0.0localhost myserver myserver.mydomain.org Perhaps it helps.. Regards, Frédéric davis wrote: Hello I can not subscribe to the pcmcia-cs mailing list on source forge because my helo onl

exim HELO=fully qualified host name?

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 http://www.skink.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble