|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: HELO and FQDN
From: Mark Tiramani (markjt
fredo.co.uk)Date: Thu Nov 02 2000 - 10:17:35 CST
- Next message: jin: "complie with mysql"
- Previous message: Angel Luis Uruñuela: "RBL"
- Next in thread: Wietse Venema: "Re: HELO and FQDN"
- Reply: Wietse Venema: "Re: HELO and FQDN"
- Reply: Ralf Hildebrandt: "Re: HELO and FQDN"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More on the non-FQDN HELO rejection:
I had possibly misunderstood the generic restrictions and therefore used:
smtpd_client_restrictions = reject_non_fqdn_hostname, reject_invalid_hostname ...
Looking again I realise that reject_non_fqdn_hostname is not listed for smtpd_client_restrictions
However, postfix rejects a non-FQDN in the HELO with a '504 ... Helo command rejected: need fully....'
when reject_non_fqdn_hostname is used in smtpd_client_restrictions.
Do other smtpd client restrictions also map to smtpd HELO restrictions?
> Interesting, because the output lists no restriction that would
> reject non-FQDN hostnames in HELO/EHLO commands.
>
> When I apply these restrictions:
>
> % telnet localhost smtp
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> 220 hades.porcupine.org ESMTP Postfix
> helo foo
> 250 hades.porcupine.org
> quit
> 221 Bye
> Connection closed by foreign host.
>
> There is no complaint about the HELO command. So, unless there is
> a way to reproduce the problem I won't be able to fix it.
>
> Wietse
Mark
Mark Tiramani
FREDO Internet Services
markjt
fredo.co.uk
- Next message: jin: "complie with mysql"
- Previous message: Angel Luis Uruñuela: "RBL"
- Next in thread: Wietse Venema: "Re: HELO and FQDN"
- Reply: Wietse Venema: "Re: HELO and FQDN"
- Reply: Ralf Hildebrandt: "Re: HELO and FQDN"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]