acceptable_aliases does not seem to work (or more likely I don't understand) V2.1.23
G'day all,
I can't seem to get acceptable_aliases to work...
(domain names changed to protect the innocent, but all match up)
comm@lists.lf.me = List email address info@lf.me = Google group (google group has one email address which is comm@lists.lf.me info@lf.me is a member of the mailman list and is set for nomail
User another@domain.com sends email to info@lf.me
List receives email and bounces with:
List: comm@lists.lf.me
From: another@domain.com
Subject: Testing
Reason: Post by non-member to a members-only listThe above is correct as user another@domain.com is not a member of the mailman list
In the email header there is To: <info@lf.me>
I have in acceptable_aliases (tried various things) info@lf.me "info@lf.me" .*info@lf.me.*
and require_explicit_destination is yes
I believe that should allow email sent to info@lf.me to be accepted by the list, maybe I am reading this all wrong?
If I am doing this wrong how do I get a google email to send to mailman and be accepted? info@lf.me was a real email address and I converted to a group so that all on the list could see it rather than person having to deal with the email. (I could have just forwarded the email in google but I didn;t want to have to deal with the email account that would never be looked at.)
-- 'ooroo
Stinga...(:)-)
Email: stinga@wolf-rock.com o
You need only two tools. o /////
A hammer and duct tape. If it /@ \ /) ~ doesn't move and it should use > (O) X< ~ Fish!! the hammer. If it moves and \___/' \) ~
shouldn't, use the tape. \\\
On 1/30/20 7:29 PM, stinga wrote:
G'day all,
I can't seem to get acceptable_aliases to work...
(domain names changed to protect the innocent, but all match up)
comm@lists.lf.me = List email address info@lf.me = Google group (google group has one email address which is comm@lists.lf.me info@lf.me is a member of the mailman list and is set for nomail
User another@domain.com sends email to info@lf.me
List receives email and bounces with:
List: comm@lists.lf.me From: another@domain.com Subject: Testing Reason: Post by non-member to a members-only list
The above is correct as user another@domain.com is not a member of the mailman list
And that is the entire issue. acceptable_aliases and require_explicit_destination have nothing to do with this.
In the email header there is To: <info@lf.me>
I have in acceptable_aliases (tried various things) info@lf.me "info@lf.me" .*info@lf.me.*
and require_explicit_destination is yes
I believe that should allow email sent to info@lf.me to be accepted by the list, maybe I am reading this all wrong?
All that does is avoid the message's being held for "implicit destination" it doesn't bypass other checks.
If I am doing this wrong how do I get a google email to send to mailman and be accepted?
There are a few of choices.
You can set Privacy options... -> Sender filters -> generic_nonmember_action to Accept in order to accept posts from any nonmember, but you may not want that.
You can ensure that everyone sending mail to info@lf.me is a member of the comm@lists.lf.me list.
You can make use of the fact that mailman considers a post to be from a member if any of the From:, Reply-To: Sender: or envelope sender addresses is a list member. Posts from google groups generally have no Sender: header, and the envelope sender is something like 'info+bncbcn2p7unuujrbfxhspsakgqe7gew6fa@googlegroups.com' where the 'bncbcn2p7unuujrbfxhspsakgqe7gew6fa' may not be constant. However, messages from Google Groups have a
Reply-To: groupname@googlegroups.com
header. If that address is a member of your list, it should be OK. You say info@lf.me is a member of your list. Is that an address you control which forwards to the google group?. If so, you want to make groupname@googlegroups.com a member of your list set to nomail. If in fact by info@lf.me you mean the actual groupname@googlegroups.com address, then I don't know what the problem is.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 01/02/2020 02:26, Mark Sapiro wrote:
On 1/30/20 7:29 PM, stinga wrote:
G'day all,
I can't seem to get acceptable_aliases to work...
(domain names changed to protect the innocent, but all match up)
comm@lists.lf.me = List email address info@lf.me = Google group (google group has one email address which is comm@lists.lf.me info@lf.me is a member of the mailman list and is set for nomail
User another@domain.com sends email to info@lf.me
List receives email and bounces with:
List: comm@lists.lf.me From: another@domain.com Subject: Testing Reason: Post by non-member to a members-only list
The above is correct as user another@domain.com is not a member of the mailman list
And that is the entire issue. acceptable_aliases and require_explicit_destination have nothing to do with this.
Yeah, that dawned on me shortly after sending. :-)
In the email header there is To: <info@lf.me>
I have in acceptable_aliases (tried various things) info@lf.me "info@lf.me" .*info@lf.me.*
and require_explicit_destination is yes
I believe that should allow email sent to info@lf.me to be accepted by the list, maybe I am reading this all wrong?
All that does is avoid the message's being held for "implicit destination" it doesn't bypass other checks.
Yeah, that dawned on me soon after hitting send, I have removed all of the stuff in the setup
If I am doing this wrong how do I get a google email to send to mailman and be accepted?
There are a few of choices.
You can set Privacy options... -> Sender filters -> generic_nonmember_action to Accept in order to accept posts from any nonmember, but you may not want that. No don't want that
You can ensure that everyone sending mail to info@lf.me is a member of the comm@lists.lf.me list. Can't do this really
You can make use of the fact that mailman considers a post to be from a member if any of the From:, Reply-To: Sender: or envelope sender addresses is a list member. Posts from google groups generally have no Sender: header, and the envelope sender is something like 'info+bncbcn2p7unuujrbfxhspsakgqe7gew6fa@googlegroups.com' where the 'bncbcn2p7unuujrbfxhspsakgqe7gew6fa' may not be constant. However, messages from Google Groups have a
Reply-To: groupname@googlegroups.com I don't have googlegroup in the email anywhere. And the Reply-To: is the original sender in my example: another@domain.com
header. If that address is a member of your list, it should be OK. You say info@lf.me is a member of your list. Is that an address you control which forwards to the google group?. If so, you want to make groupname@googlegroups.com a member of your list set to nomail. If in fact by info@lf.me you mean the actual groupname@googlegroups.com address, then I don't know what the problem is.
info@lf.me is a member of the list info@lf.me is the actual googlegroup email, so not forwarded to the group but is the email you - hmm.. thinking.....
The only google strings are:
me@shark:~$ grep -i google blobby helo=mail-wr1-f70.google.com; Received: from mail-wr1-f70.google.com (mail-wr1-f70.google.com Received: by mail-wr1-f70.google.com with SMTP id z15sf2361825wrw.0 d=google.com; s=arc-20160816; ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; ARC-Authentication-Results: i=2; mx.google.com; spf=neutral (google.com: 83.223.99.6 is neither permitted nor denied by best X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; X-Google-Smtp-Source: APXvYqyKisHZvFWpohBRwPsvt40r94Ro4WY604SjLb9Rw2YE/6H94rxWLjbpM/T9vccnjBUH9ona4Q== d=google.com; s=arc-20160816; ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; ARC-Authentication-Results: i=1; mx.google.com; spf=neutral (google.com: 83.223.99.6 is neither permitted nor denied by best by mx.google.com with ESMTPS id n16si5340484wrp.218.2020.01.30.14.03.44 Received-SPF: neutral (google.com: 83.223.99.6 is neither permitted nor denied X-Original-Authentication-Results: mx.google.com; spf=neutral (google.com: 83.223.99.6 is neither permitted nor denied by best guess record X-Google-Group-Id: 631184299376
-- 'ooroo
Stinga...(:)-)
Email: stinga@wolf-rock.com o
You need only two tools. o /////
A hammer and duct tape. If it /@ \ /) ~ doesn't move and it should use > (O) X< ~ Fish!! the hammer. If it moves and \___/' \) ~
shouldn't, use the tape. \\\
On 2/1/20 1:58 AM, stinga wrote:
On 01/02/2020 02:26, Mark Sapiro wrote:
You can make use of the fact that mailman considers a post to be from a member if any of the From:, Reply-To: Sender: or envelope sender addresses is a list member. Posts from google groups generally have no Sender: header, and the envelope sender is something like 'info+bncbcn2p7unuujrbfxhspsakgqe7gew6fa@googlegroups.com' where the 'bncbcn2p7unuujrbfxhspsakgqe7gew6fa' may not be constant. However, messages from Google Groups have a
Reply-To: groupname@googlegroups.com
I don't have googlegroup in the email anywhere. And the Reply-To: is the original sender in my example: another@domain.com
In order to enable that Reply-To: you need to go to your group Settings -> Email options and set Post replies to "To the entire group". There are other options "To the owners of the group" and "To the managers of the group" which probably also generate fixed Reply-To: headers.
If you don't want to use one of those to create a fixed Reply-To: address that you can add to your list as a member with no mail, you'll have to live with the messages being held.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2/1/20 1:58 AM, stinga wrote:
On 01/02/2020 02:26, Mark Sapiro wrote:
You can make use of the fact that mailman considers a post to be from a member if any of the From:, Reply-To: Sender: or envelope sender addresses is a list member. Posts from google groups generally have no Sender: header, and the envelope sender is something like 'info+bncbcn2p7unuujrbfxhspsakgqe7gew6fa@googlegroups.com' where the 'bncbcn2p7unuujrbfxhspsakgqe7gew6fa' may not be constant. However, messages from Google Groups have a
Reply-To: groupname@googlegroups.com
I don't have googlegroup in the email anywhere. And the Reply-To: is the original sender in my example: another@domain.com
In order to enable that Reply-To: you need to go to your group Settings -> Email options and set Post replies to "To the entire group". There are other options "To the owners of the group" and "To the managers of the group" which probably also generate fixed Reply-To: headers.
If you don't want to use one of those to create a fixed Reply-To: address that you can add to your list as a member with no mail, you'll have to live with the messages being held. Many thanks, I had discovered that and was waiting for a message to arrive to test! I note that the email received from the email list was cc: to the original sender, but I am not sure if that is real or just a way to get
On 02/02/2020 03:19, Mark Sapiro wrote: the sender in the email header somewhere.
Tanks again, I believe the change to google group settings is the answer.
-- 'ooroo
Stinga...(:)-)
Email: stinga@wolf-rock.com o
You need only two tools. o /////
A hammer and duct tape. If it /@ \ /) ~ doesn't move and it should use > (O) X< ~ Fish!! the hammer. If it moves and \___/' \) ~
shouldn't, use the tape. \\\
participants (2)
-
Mark Sapiro -
stinga