On 03/20/2013 11:46 AM, jdd wrote:

so the problem may be only with this particular user. I have to wait for the next failure. But then what will I have exactly to look at, and first where is the source mail stored? oir is the headers in the moderation message enough?

The headers in the admindb interface detail page are enough (click the message # link on the summary listing).

look at From: and Sender:, but actually the address in the From:user@example.com heading in the Held Messages section of the admindb page or the email notification will tell you the address that was not matched against accept_these_nonmembers. From: and Sender: should tell you where it came from.

On 4/3/13 2:21 AM, jdd wrote:

Le 20/03/2013 20:23, Mark Sapiro a écrit :

...

The headers in the admindb interface detail page are enough (click the message # link on the summary listing).

well finally I received one such mail (it's more or less monthly :-)

it appears to be from a subscriber mailing list (not mine). The "from" is in my "to be accepted" list, but its moderated. I would like to have these mails accepted without moderation (but not all bulk messages from anywhere :-().

part of the headers below (I removed the domain part of the amails adresses).

Can I manage this?

thanks jdd

part of the mailman comments:

comments in the aministrative page:

De: fcouchet@april.org Objet: [Lettre April] Lettre d'information interne des adhérents de l'April du 1er avril 2013 Motif: Message avec destination implicite Reçus: Tue Apr 2 09:27:01 2013

reject message proposed:

Blind carbon copies or other implicit destinations are not allowed. Try reposting your message by explicitly including the list address in the To: or Cc: fields.

This indicates that your list is setup to not allow bcc, and that the destination address is not consider a valid destination address for this list. Add it to

Privacy / Recipient Filters / Alias names (regexps) which qualify as explicit to or cc destination names for this list.

Adding the list to the accepted sender list just says it will pass the sender must be a member test, it doesn't bypass the other tests.

On 4/3/13 8:35 AM, jdd wrote:

Le 03/04/2013 14:11, Richard Damon a écrit :

...

...

De: fcouchet@aprixxxx

...

This indicates that your list is setup to not allow bcc, and that the destination address

I added the "from" adress (fcouchet@aprixxxx) in the said field, is this you call "destination adress"?

thanks jdd

The "Blind CC" message indicates that the list address is not seen in the TO or CC fields of the message (so it must have gotten to the list via a BCC type action). If the list is configured to not allow BCCs, then any address that can be legitimately sent to inorder to post on the list needs to be listed in the list aliases list.

It looks like this message was sent to the list via the email address all-april@ (which looks like a local address, since it doesn't have a domain), this is generally not a good idea for a message that is going to be distributed in the wild, as it will not be a valid email address for people to reply to. If you want to all that anyway, you need to add this address as a list alias.

On 4/4/13 1:42 AM, jdd wrote:

Le 04/04/2013 03:58, Richard Damon a écrit :

...

It looks like this message was sent to the list via the email address all-april@ (which looks like a local address, since it doesn't have a domain),

as I said, I removed the domain part (on my report) to prevent spam

Missed that note, the normal procedure isn't to just delete the information but to replace it with a placeholder, the domain example.com being a good one.

this is generally not a good idea for a message that is going

...

to be distributed in the wild, as it will not be a valid email address for people to reply to. If you want to all that anyway, you need to add this address as a list alias.

list alias? aceptable aliases, I guess? I will do this according to what marc said.

Yes, acceptable list aliases, as entered in

Privacy Options / Recipient Filters / Alias names (regexps) which qualify as explicit to or cc destination names for this list.

This is designed to handle cases where the list has alternate names that people can use to submit mail to it. Some entry in this list MUST be found in either the To or CC fields of the message, or the Blind Carbon Copy filter will be triggered. http://six.pairlist.net/mailman/admin/arlington/?VARHELP=privacy/recipient/acceptable_aliases

I don't knox how to test :-(, I have to wait to next post (mponthly :-()

thanks jdd

On 4/2/2013 11:21 PM, jdd wrote:

it appears to be from a subscriber mailing list (not mine). The "from" is in my "to be accepted" list, but its moderated. I would like to have these mails accepted without moderation (but not all bulk messages from anywhere :-().

[...]

comments in the aministrative page:

De: fcouchet@april.org Objet: [Lettre April] Lettre d'information interne des adhérents de l'April du 1er avril 2013 Motif: Message avec destination implicite

The message has an implicit destination. This means that the list is not explicitly addressed in a To: or Cc: header of the message.

As it says [...]

Blind carbon copies or other implicit destinations are not allowed. Try reposting your message by explicitly including the list address in the To: or Cc: fields.

Since you don't have control over this message, you have to do it another way.

[...]

From: Frederic Couchet <fcouchet@ To: all-april@

This is problematic. To pass this email you'd need to do one of two things. You can go to Privacy options -> Recipient filters and put all-april in acceptable_aliases, but that probably won't work because next month's will be all-may. These are regexps so you could try

all-.*@example.com$

where example.com is the real domain.

The other choice is to just set require_explicit_destination to No, but that may allow some spam that would otherwise get held by this check.