admin2 wrote:

Somebody suggested me ask the mailman folks this question.

My google official account username is <blah@domain.com> but I have verified and activated another email address "sample@domain2.com" . I am able to originate email with "sample@domain2.com" in the "from" email but mailman still rejects the message claiming "Sorry, only subscribers may post."

Is the address sample@domain2.com a member of the list?

Mailman thinks I am not a member of the list and is considering me "blah@domain.com" even though I can see in the bounce that "sample@domain2.com" is in the From portion of the header.

I do not understand the above. Which of these addresses are members of the list. Mailman only goes by the exact email address. E.g. even if userx@example.com is a list member, userx@mail.example.com is not.

The SMTP header of the bounce claims "Received-SPF: pass", "Return-Path: <blah@domain.com>", and "Sender: <blah@domain.com>"

When I send the same mail through a domain I administer the email "sample@domain2.com" is properly identified.

Is there anything more I can configure to appease mailman's legitimacy checking?

As I said, I can't diagnose the issue without knowing what addresses are list members. The following is in Defaults.py

# Membership tests for posting purposes are usually performed by looking at a # set of headers, passing the test if any of their values match a member of # the list. Headers are checked in the order given in this variable. The # value None means use the From_ (envelope sender) header. Field names are # case insensitive. SENDER_HEADERS = ('from', None, 'reply-to', 'sender')

If this is unchanged in mm_cfg.py, a post will be considered to be from a list member if any of From:, the envelope sender (Return-Path:), Reply-To: or Sender: (in that order) contain an exact member address.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan