HUGE RETRACTION: I've really messed this up...
At the time of the HELO/EHLO command, SMTPD_FLAG_SMTPUTF8 should always
be false, that feature may be negotiated after HELO/EHLO.
As such, the UTF8 handling code of reject_non_fqdn_hostname is ALWAYS
DISABLED during HELO/EHLO and so
"reject_non
On Sat, Apr 08, 2023 at 11:49:49AM +1000, Sean Gallagher via Postfix-users
wrote:
> I think the outcome of the discussion in this thread was that
> valid_utf8_hostname() really has no "official" use case.
Not all hostnames are HELO hostnames. The domain part of an email
address is a "hostname"
raf via Postfix-users:
> > From reading the code, these two restrictions seem equivalent except when
> > SMTPUTF8 extension is used.
> > when the SMTPUTF8 is in play, reject_non_fqdn_helo_hostname will convert a
> > hostname containing UTF to an internationalized domain name
> > before checking. ht
On 8/04/2023 10:31 am, raf via Postfix-users wrote:
On Thu, Apr 06, 2023 at 11:28:07AM +1000, Sean Gallagher
wrote:
On 6/04/2023 10:39 am, raf via Postfix-users wrote:
On Thu, Apr 06, 2023 at 07:33:28AM +0800, Corey Hickman via Postfix-users
wrote:
Hello
for these two statements,
reje
On Thu, Apr 06, 2023 at 11:28:07AM +1000, Sean Gallagher
wrote:
> On 6/04/2023 10:39 am, raf via Postfix-users wrote:
> > On Thu, Apr 06, 2023 at 07:33:28AM +0800, Corey Hickman via Postfix-users
> > wrote:
> >
> > > Hello
> > >
> > > for these two statements,
> > >
> > > reject_invalid_hel
On Fri, Apr 07, 2023 at 10:07:08AM +0800, Ken Peng via Postfix-users wrote:
> i have the similar questions on these two clauses:
>
> reject_unknown_reverse_client_hostname
> reject_unknown_client_hostname
>
> I know the first one require the sender IP has a valid PTR.
> but for the second one, wh
i have the similar questions on these two clauses:
reject_unknown_reverse_client_hostname
reject_unknown_client_hostname
I know the first one require the sender IP has a valid PTR.
but for the second one, what's unknown client hostname?
does it mean the PTR hostname must point to the sender IP a
On 7/04/2023 12:32 am, Viktor Dukhovni via Postfix-users wrote:
On Thu, Apr 06, 2023 at 04:57:51PM +1000, Sean Gallagher via Postfix-users
wrote:
What a can of worms..
IDNA2003 allowed UTF8 in domain names
IDNA specified an encoding system for mapping UTF8 labels to
ACE-prefixed LDH labels th
Le 06/04/2023 à 16:44, Emmanuel Fusté a écrit :
Le 06/04/2023 à 14:09, Emmanuel Fusté a écrit :
Le 06/04/2023 à 13:35, Ken Peng via Postfix-users a écrit :
On 2023-04-06 19:07, Jaroslaw Rafa via Postfix-users wrote:
I just now learned about the UTF8 thing, I would never think of using
non-AS
Le 06/04/2023 à 14:09, Emmanuel Fusté a écrit :
Le 06/04/2023 à 13:35, Ken Peng via Postfix-users a écrit :
On 2023-04-06 19:07, Jaroslaw Rafa via Postfix-users wrote:
I just now learned about the UTF8 thing, I would never think of using
non-ASCII characters in host/domain names :)
You can
On Thu, Apr 06, 2023 at 04:57:51PM +1000, Sean Gallagher via Postfix-users
wrote:
> What a can of worms..
> IDNA2003 allowed UTF8 in domain names
IDNA specified an encoding system for mapping UTF8 labels to
ACE-prefixed LDH labels that can be used in DNS. The resulting data in
DNS (in zone file
On 2023-04-06 20:09, Emmanuel Fusté via Postfix-users wrote:
If we are ignoring the remaining IDNA2003 UTF8 domains corner case
(which are practically unusable in real world if there is still
sommes), there is no good reason to see utf8 fqdn in the HELO/EHLO
context.
Postfix is right.
I got
Le 06/04/2023 à 13:35, Ken Peng via Postfix-users a écrit :
On 2023-04-06 19:07, Jaroslaw Rafa via Postfix-users wrote:
I just now learned about the UTF8 thing, I would never think of using
non-ASCII characters in host/domain names :)
You can dig the UTF8 hostname, they are valid for query.
On 2023-04-06 19:07, Jaroslaw Rafa via Postfix-users wrote:
I just now learned about the UTF8 thing, I would never think of using
non-ASCII characters in host/domain names :)
You can dig the UTF8 hostname, they are valid for query.
$ dig 腾讯.公司 ns +short
ns1.brandcloudns.com.
ns2.brandcloudns
Dnia 6.04.2023 o godz. 16:57:51 Sean Gallagher via Postfix-users pisze:
> allows top-level domain names (without any dots) to be used.
[...]
> reject_invalid_helo_hostname seems to fit with modern standards but
> will reject IDNA2003
> domain names that were legal between 2003 and 2008. It will al
What a can of worms..
IDNA2003 allowed UTF8 in domain names
IDNA2008 subsequently forbid non-ASCII characters in domain names.
RFC6531 (which defines the SMTPUTF8 extension) Allows internationalized
domain names in headers and the "envelope" - taken to mean the RCPT (to
address) and MAIL (from a
On Thu, Apr 06, 2023 at 07:33:28AM +0800, Corey Hickman via Postfix-users wrote:
> reject_invalid_helo_hostname
> reject_non_fqdn_helo_hostname
>
> what are the differences between them? does the second one hold the
> first one already?
Neither subsumes the other, perhaps due to an implementati
Ken Peng via Postfix-users writes:
> (...)
> for instance, 腾讯.公司 is a invalid hostname, but it is a fqdn
> hostname which will pass the check by the second clause.
Good example, thanks!
Sincerely,
--
^고맙습니다 _地平天成_ 감사합니다_^))//
___
Postfix-users maili
On 2023-04-06 09:32, Sean Gallagher via Postfix-users wrote:
From reading the code, these two restrictions seem equivalent except
when SMTPUTF8 extension is used.
when the SMTPUTF8 is in play, reject_non_fqdn_helo_hostname will
convert a hostname containing UTF to an internationalized domain nam
From reading the code, these two restrictions seem equivalent except
when SMTPUTF8 extension is used.
when the SMTPUTF8 is in play, reject_non_fqdn_helo_hostname will convert
a hostname containing UTF to an internationalized domain name
before checking. https://en.wikipedia.org/wiki/Internationa
On Thu, Apr 06, 2023 at 07:33:28AM +0800, Corey Hickman via Postfix-users
wrote:
> Hello
>
> for these two statements,
>
> reject_invalid_helo_hostname
> reject_non_fqdn_helo_hostname
>
> what are the differences between them? does the second one hold the first
> one already?
>
> Thanks.
re
21 matches
Mail list logo