In article <2019082954.gd47...@symphytum.spacehopper.org> you write:
>On 2019/01/11 10:07, Michael Peddemors wrote:
>> For the record, we aren't speaking about 'Friendly Names', but the userpart
>> of the addr-spec address
>>
>> But a pointer to an RFC where it is permitted, that I don't
On 2019/01/11 10:07, Michael Peddemors wrote:
> For the record, we aren't speaking about 'Friendly Names', but the userpart
> of the addr-spec address
>
> But a pointer to an RFC where it is permitted, that I don't find..
RFC5322 and predecessors. Either dot-atom or quoted-string are permitted
Once upon a time, Michael Peddemors said:
> I don't know of this particular mailer, but can I get some feedback
> to confirm that the '*' character is not a permitted character in an
> email address? (user name portion)
You can always use this handy-dandy regular expression to validate email
. It is an allowed localpart character. Hence
why I stated he would be disappointed.
*From:* mailop on behalf of Al Iverson
*Sent:* Friday, January 11, 2019 10:52:10 AM
*To:* mailop
*Subject:* Re: [mailop] Mailing List
AM
To: mailop
Subject: Re: [mailop] Mailing List Address Formats..
I'm definitely disappointed by the giant chunks of excess HTML links and
previews added to your reply, for sure.
But the page you linked to clearly says that the asterisk is allowed in the
username portion, so nothing
https://www.jochentopf.com/email/chars.html
--
Benjamin
From: mailop On Behalf Of David Carriger
Sent: vendredi 11 janvier 2019 18:49
To: Al Iverson ; Michael Peddemors
Cc: mailop
Subject: Re: [mailop] Mailing List Address Formats..
I'm afraid you're going to be disappointed.
https
d you can do almost any stupid thing you want as long as you
> quote it.
>
>
>
> --
> *From:* mailop on behalf of Al Iverson <
> aiver...@wombatmail.com>
> *Sent:* Friday, January 11, 2019 10:45 AM
> *To:* Michael Peddemors
> *Cc:
ary 11, 2019 10:45 AM
To: Michael Peddemors
Cc: mailop
Subject: Re: [mailop] Mailing List Address Formats..
Return-path headers using VERP in this way, with asterisks in the
username part like this, can be traced all the way back to LISTSERV in
the 1990s. It's a long standing practice. If you block
Return-path headers using VERP in this way, with asterisks in the
username part like this, can be traced all the way back to LISTSERV in
the 1990s. It's a long standing practice. If you block based on this,
you'll block a few spammers or commercial mailers who used or use
LISTSERV, or who rolled
owner-nolist-cp_enews-190110p-gqfjbpue*username**domain*-suf...@digital.annexbusinessmedia.com
(Where 'username', 'domain','suffix' are placeholders)
I don't know of this particular mailer, but can I get some feedback to
confirm that the '*' character is not a permitted character in an email
10 matches
Mail list logo
