Sujet : Re: TEST June 2025
De : 333200007110-0201 (at) *nospam* ybtra.de (Marcel Logen)
Groupes : misc.testDate : 06. Jun 2025, 21:23:39
Autres entêtes
Organisation : Bureau Logen
Message-ID : <87jz5o62q5.fsf@pc-731.ybtra.de>
References : 1 2 3 4 5
User-Agent : Gnus/5.13 (Gnus v5.13) Emacs/28.2 (gnu/linux)
Marco Moock in misc.test:
On 04.06.2025 00:00 yeti yeti wrote:
That from line format just looks strange.
| From: rjac@shell02.TheWorld.com (Christians against SPAMMING,
sub-human devil worshiper, Andrew 'Andrzej' Baron)
>
A really long name, but that doesn't affect the technical address at
all.
<
https://www.rfc-editor.org/rfc/rfc5536.html#section-3.1.2>
Aus <
https://www.rfc-editor.org/rfc/rfc5322#section-3.4>:
| Normally, a mailbox is composed of two parts: (1) an optional display
| name that indicates the name of the recipient (which can be a person
| or a system) that could be displayed to the user of a mail
| application, and (2) an addr-spec address enclosed in angle brackets
| ("<" and ">"). There is an alternate simple form of a mailbox where
| the addr-spec address appears alone, without the recipient's name or
| the angle brackets. The Internet addr-spec address is described in
| section 3.4.1.
|
| Note: Some legacy implementations used the simple form where the
| addr-spec appears without the angle brackets, but included the
| name of the recipient in parentheses as a comment following the
| addr-spec. Since the meaning of the information in a comment is
| unspecified, implementations SHOULD use the full name-addr form of
| the mailbox, instead of the legacy form, to specify the display
| name associated with a mailbox. Also, because some legacy
| implementations interpret the comment, comments generally SHOULD
| NOT be used in address fields to avoid confusing such
| implementations.
Marcel
-- Fri Jun 6 22:23:39 2025 CEST (1749241419)pc-73187 jz5o 62q5Lines: 42