Hallo.

Am Samstag, 10. November 2007 schrieb niclas:
> mailx.courier-mta.com[216.254.115.190] just told me that:
> > 517 HELO someservername2.domain.de does not match
> > ::ffff:123.123.12.12 (in reply to MAIL FROM command)
> actually the dns-entry for that address is someservername2-1.domain.de

No. The Host someservername2.domain.de does not even exist.

I think you messed something up in quoting the error because nonexisting host 
names should cause another error message.


> this lokks like the HELO name is compared to the DNS entry.
> (instead of the (reverse-)DNS lookups mentioned in
> http://www.courier-mta.org/FAQ.html#esmtptimeout .)

Two different things. 

The thing mentioned in the FAQ is just for recording in the "Received" header 
field.
The one causing your error is a spam-protection feature.


> i use my provider's smtp as smarthost and complained, but they told me
> that this check SHOULD NOT be done according to the RFCs. (they did not
> say which RFC they refer to.)

I cannot see this "SHOULD NOT" in RFC 2821 or RFC 821. And I don't know of any 
other RFC that applies here.

Read by yourself:

RFC 2821             Simple Mail Transfer Protocol            April 2001
[...]
4.1.1.1  Extended HELLO (EHLO) or HELLO (HELO)

   These commands are used to identify the SMTP client to the SMTP
   server.  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 have a meaningful domain name (e.g., when
   its address is dynamically allocated and no reverse mapping record is
   available), the client SHOULD send an address literal (see section
   4.1.3), optionally followed by information that will help to identify
   the client system. 


The older one, RFC 821, is just simpler:

         HELLO (HELO)

            This command is used to identify the sender-SMTP to the
            receiver-SMTP.  The argument field contains the host name of
            the sender-SMTP.


There is no word about "the HELO argument contains some funny random name" but 
just the FQDN of the sending entity.


> i guess they are right, otherwise they would have been flooded with
> complaints.

Oh, I think they should have been flooded with complaints.
And, of course, they really should fix their setup.

cu, Bernd

-- 
Fettflecke werden wie neu,
wenn man sie regelmäßig mit Butter einreibt.

Attachment: signature.asc
Description: This is a digitally signed message part.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to