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)
[email protected] = List email address
[email protected] = Google group (google group has one email address which
is [email protected]
[email protected] is a member of the mailman list and is set for nomail
User [email protected] sends email to [email protected]
List receives email and bounces with:
List: [email protected]
From: [email protected]
Subject: Testing
Reason: Post by non-member to a members-only list
The above is correct as user [email protected] 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: <[email protected]>
I have in acceptable_aliases (tried various things)
[email protected]
"[email protected]"
.*[email protected].*
and require_explicit_destination is yes
I believe that should allow email sent to [email protected] 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 [email protected] is a member of
the [email protected] 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
'[email protected]' where the
'bncbcn2p7unuujrbfxhspsakgqe7gew6fa' may not be constant. However,
messages from Google Groups have a
Reply-To: [email protected]
I don't have googlegroup in the email anywhere.
And the Reply-To: is the original sender in my example: [email protected]
header. If that address is a member of your list, it should be OK. You
say [email protected] is a member of your list. Is that an address you
control which forwards to the google group?. If so, you want to make
[email protected] a member of your list set to nomail. If in
fact by [email protected] you mean the actual [email protected]
address, then I don't know what the problem is.
[email protected] is a member of the list [email protected] 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: [email protected] 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. \\\
---------------------------------------------------
------------------------------------------------------
Mailman-Users mailing list [email protected]
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
