Re: add sender without mail if mail is in some ignored-list?

"Roland Winkler" <[email protected]> writes:

> On Fri Mar 27 2020 Michael Richardson wrote:
>> so, what do you wind up for [email protected], which I also have a
>> problem with.
>
> I may have missed the point in the 1st email of this thread:
>
> What is the problem here and what would be the most meaningful
> strategy for BBDB to deal with this?  Is the problem that one email
> address is used by different senders and BBDB should keep track of
> this?  Or should BBDB merge the emails from different senders?

[starting form the beginning to be clear; not trying to talk down to you]

The problem is that the norm is that normally mail is sent from

   John Doe <[email protected]>

and that one can usually conclude that [email protected] is an email
address belonging to John Doe.

However, there are multiple cases where senders behave badly relative to
this norm.

One is things like

  John Doe <[email protected]>
  Jane Smith <[email protected]>

where there is a sender address which is sort of a role and sort of
faux, but a real person's name is misassociated with it.  This seems
pretty common in big company announcement lists.


The other, that mcr@ refers to, is gitbub's practice of sending email
that looks like

  John Doe <[email protected]>

This is broken in two ways.  One, it implies that
[email protected] is John's address, and this is the point for
bbdb.  Second, one can't reply.


So, bbdb should have some sort of list of email addresses that should
always be ignored and never auto-added in any way, because there is no
reason to think they are validly asssociated with a person.

[email protected] and any similar mis-used forge sender addresses
should be on this default list.