Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #17968

Re: Symfony 4 - problem z wykorzystaniem Doctrine

Show all headers | View raw

Thomas 'PointedEars' Lahn:

> Ben Bacarisse wrote:
> 
>> Thomas 'PointedEars' Lahn <PointedEars@web.de> writes:
>> <cut>
>>> Also, it is inappropriate to falsify address header fields.  The “From”
>>> (and “Reply-To”) header fields MUST contain a *working* e-mail *address*.
>>
>> Your use of MUST (in capitals) makes it seem you have the force of net
>> standards behind you on this, whereas relevant RFC in fact says:
> 
> You should have *cited* it, too.
> 
> RFC 5536 is not an Internet standard yet (then it would have a “STD” number, 
> like <https://tools.ietf.org/html/std1>), but a Proposed Standard on the 
> IETF Standards Track.  For practical purposes, it should be called a “quasi-
> standard”:
[...]
> The rules have changed a little in the meantime, indeed.  With that said, 
> using the “invalid” TlD for anything but testing purposes is anti-social, 
> too.  As a result, it is a killfile rule not only in my configuration.
Is it really needed to be available via e-mail if you want to
participate a public discussion?

In the past - which means at least 20 years ago - it was seen as polite
to answer postings with specific questions by sending an e-mail to the
poster, so he or she could then post a summary based on all answers he
or she got via e-mail later.

However nowadays this is completely unusual - posts are answered by
posts and sending an e-mail is a rare exception. I have a valid sender
address and the number of e-mails I got to that addess in the past 5
years is less than 1 e-mail per year.

That's the reason for RFC 5536 and a similar rules indivual.net to
adjust the rules to the reality many years ago.

See <http://individual.net/faq.php#5.3>, cite:

5.3
May I mangle my "From:" header address so that I do not get spam?

We recommend creating a special e-mail address for use with Usenet
articles only and protecting it with suitable filtering rules. This way
your regular mailbox will stay untroubled, but you can still receive
e-mail responses to your Usenet articles.

Another option is using the Top Level Domain ".invalid" (see RFC 2606).
The Top Level Domain ".invalid" is intended for construction of
obviously invalid addresses like "invalid@invalid.invalid". Such
addresses do not disturb and pollute regular name space and can easily
be identified as invalid by both humans and machines.



-- 
Arno Welzel
https://arnowelzel.de

Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Symfony 4 - problem z wykorzystaniem Doctrine Marek S <precz@spamowi.com> - 2019-06-07 01:39 +0200
  Re: Symfony 4 - problem z wykorzystaniem Doctrine Arno Welzel <usenet@arnowelzel.de> - 2019-06-09 14:33 +0200
    Re: Symfony 4 - problem z wykorzystaniem Doctrine Marek S <precz@spamowi.com> - 2019-06-09 16:12 +0200
      Re: Symfony 4 - problem z wykorzystaniem Doctrine Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2019-06-09 19:22 +0200
        Re: Symfony 4 - problem z wykorzystaniem Doctrine Ben Bacarisse <ben.usenet@bsb.me.uk> - 2019-06-09 21:40 +0100
          Re: Symfony 4 - problem z wykorzystaniem Doctrine Marek S <precz@spamowi.com> - 2019-06-09 23:46 +0200
          Re: Symfony 4 - problem z wykorzystaniem Doctrine Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2019-06-10 20:55 +0200
            Re: Symfony 4 - problem z wykorzystaniem Doctrine Arno Welzel <usenet@arnowelzel.de> - 2019-06-11 09:54 +0200
        Re: Symfony 4 - problem z wykorzystaniem Doctrine Arno Welzel <usenet@arnowelzel.de> - 2019-06-10 01:57 +0200

csiph-web