Comment 7 for bug 266389

Originator: NO

I'm not sure you understand what require_explicit_destination and
acceptable_aliases do.

If require explicit destination is Yes, some address in the To: or Cc:
headers of the post must be either the list posting address or match an
address or re in acceptable aliases.

If you put ^[^@]+@(.*\.)?qchron\.(?=com$|net$).*$ in acceptable aliases,
it will only have an effect if a matching address (e.g.
<email address hidden>) is in the To: or Cc: of a post to the list. If any
address that can deliver to your list is in the qchron.com or qchron.net
domain, then yes, this will allow them all to be accepted as well as a
whole bunch more IF the address that got to the list was in a To: or Cc:
header. But, I suspect the problem in this case was that no list address
was in a To: or Cc: of the post.

This has nothing to do with who the post is From: or whether or not it is
from a list member. If a member or an acceptable non-member sends a post
To: <email address hidden> with a Bcc: to your list, your list is
going to hold it for implicit destination.

The question you have to answer for yourself is do you want to accept
without moderator action, posts which aren't explicitly addressed in To: or
Cc: to your list or to some other address that gets to your list. If you
do, then set require_explicit_destination to No. If you don't, then set
require_explicit_destination to Yes and make sure that any 'other'
addresses that will deliver to your list are in acceptable_aliases (this
should be very few addresses).

In the later case posters will be required to explicitly name the list or
an acceptable alias in To: or Cc: or the post will be held.