7 Apr
2022
7 Apr
'22
5:57 p.m.
I should actually have quoted a bit more.
"The
local-part of a mailbox MUST BE treated as case sensitive.
Therefore, SMTP implementations MUST take care to preserve the case
of mailbox local-parts. In particular, for some hosts, the user
"smith" is different from the user "Smith". However, exploiting
the
case sensitivity of mailbox local-parts impedes interoperability and
is discouraged. Mailbox domains follow normal DNS rules and are
hence not case sensitive."
Johnny
On 2022-04-07 17:54, Johnny Billquist wrote:
Actually incorrect. Hostnames are case insensitive,
but mailbox names
might not be.
This is very clearly stated in RFC 5321. Page 16, section 2.4 "General
Syntax Principles and Transaction Model".
In there it says:
"Verbs and argument values (e.g., "TO:" or "to:" in the RCPT
command
and extension name keywords) are not case sensitive, with the sole
exception in this specification of a mailbox local-part (SMTP
Extensions may explicitly specify case-sensitive elements)."
And don't get me started on gmail, which breaks the RFC in multiple ways
when dealing with the local part of a mail address for the sending part
(which it shouldn't try to understand at all).
Johnny
On 2022-04-07 17:45, Peter Lothberg wrote:
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Mark,
Welcome back whenever..
The mail RFC's clearly states that mail-address (and domain names) are
NOT
case sensitive, so if someone is matching case, they are out of spec.
-P
----- Original Message -----
From: "Mark G Thomas"
<mark(a)misty.com>
To: "The Hobbyist DECnet mailing list" <hecnet(a)lists.dfupdate.se>
Sent: Thursday, April 7, 2022 11:31:33 AM
Subject: [HECnet] try #4: area 23 will be offline for awhile
Hi,
I'm trying again, as I suspect maybe the mailing list has been rejecting
my prior attempts due to some case sensitivity in matching submitting
e-mail senders with subscriber addresses. If this message makes it,
maybe
someone can investigate, as I expect it might cause grief for others
too.
Due to a combination of things, I'm going to need to take down my
area 23 hecnet router, probably for a 3-6 months.
Near term, I'm short on hobby time, need to do some significant network
reconfiguration, and need to put back together one or several decnet
worthy systems, after some rather frustrating hardware failures.
Ideally, I should have more time late summer or fall, once my kid is in
school and some other pressures let up.
I'm not going anywhere, and appreciate the groupmembers here who have
been so helpful over the years about so many DEC and non-DEC things.
My current peers are as follows, though some of them are currently down.
interface Tunnel50
description HECnet tunnel for Brian Hechinger (Area 52) [Version:311]
interface Tunnel51
description HECnet tunnel for Ian McLaughlin (Area 42) [Version:311]
interface Tunnel52
description HECnet tunnel for Cory Smelosky (Area 9) [Version:311]
interface Tunnel53
description HECnet tunnel for Dave McGuire (Area 61) [Version:311]
interface Tunnel54
description HECnet tunnel for Supratim Sanyal (Area 31) [Version:311]
interface Tunnel57
description HECnet tunnel for Tim Sneddon (Area 12) [Version:311]
interface Tunnel58
description HECnet tunnel for Mark Darvill (Area 22) [Version:311]
interface Tunnel1098
description tunnel to Peter Lothberg <roll(a)Stupi.SE> (STORTR 59.61)
interface Tunnel1099
description tunnel to Peter Lothberg <roll(a)Stupi.SE> (IAD2 59.1020)
Mark
--
Mark G. Thomas <Mark(a)Misty.com>om>, KC3DRE
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se
_______________________________________________
HECnet mailing list -- hecnet(a)lists.dfupdate.se
To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se