Getting implicit destinattion even though To: field is correct

I just installed mailman 2.1.20 using the Ubuntu provided package for 16.04.
I'm setting this up as a replacement for an older mailman server. Right now, the lists are just using the machine name for the addresses, but whenever I send a message to a list address, it gets held for moderator approval, claiming it has an "implicit destination". The server name is (not really) mail01.example.com. mm_cfg.py has DEFAULT_EMAIL_HOST of "mail01.example.com", and I set up the necessary configuration to have the aliases generated (MTA=POSTFIX) and commented out the postfix_to_mailman.ph transport line in postfix. However, if I send a message to testlist@mail01.example.com<mailto:testlist@mail01.example.com>, it is moderated for implicit destination. Every single time. And I KNOW that the To: field has the correct email address because I'm typing it in myself during a telnet session to port 25! What am I missing here?

On 04/21/2017 12:15 PM, Aaron Smith wrote:
... However, if I send a message to testlist@mail01.example.com, it is moderated for implicit destination. Every single time. And I KNOW that the To: field has the correct email address because I'm typing it in myself during a telnet session to port 25! What am I missing here?
The addresses in any To:, Cc:, Resent-To: or Resent-Cc: headers are lower cased and if the local part of any of these matches the list's internal name (which should be the lower case list name, i.e. the list's real_name attribute lower cased), you should not get an implicit destination hold.
I.e., if the list's internal name it 'testlist' and the To: header contains the address testlist@... in any combination of upper/lower case, the message should not be held for implicit destination.
When the message is held for implicit destination, look at the Message Headers: in the held message view in the list's admindb interface. Do they have the To: header you expect?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

At Sat, 22 Apr 2017 10:23:59 -0700 Mark Sapiro <mark@msapiro.net> wrote:
On 04/21/2017 12:15 PM, Aaron Smith wrote:
... However, if I send a message to testlist@mail01.example.com, it is moderated for implicit destination. Every single time. And I KNOW that the To: field has the correct email address because I'm typing it in myself during a telnet session to port 25! What am I missing here?
The addresses in any To:, Cc:, Resent-To: or Resent-Cc: headers are lower cased and if the local part of any of these matches the list's internal name (which should be the lower case list name, i.e. the list's real_name attribute lower cased), you should not get an implicit destination hold.
I.e., if the list's internal name it 'testlist' and the To: header contains the address testlist@... in any combination of upper/lower case, the message should not be held for implicit destination.
When the message is held for implicit destination, look at the Message Headers: in the held message view in the list's admindb interface. Do they have the To: header you expect?
Since the OP is using a "telnet session to port 25" I wonder if he is confusing an *envelope header" with a message header.
If in the "telnet session to port 25" he is typing:
RCPT To testlist@mail01.example.com
And *failing* to include in the DATA section a line like:
To: testlist@mail01.example.com
Even though the RCPT To is correct, *mailman* still needs the "To: testlist@mail01.example.com" *in the message itself* (in the header in the DATA part).
-- Robert Heller -- 978-544-6933 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller@deepsoft.com -- Webhosting Services

*FacePalm* Well...that's embarrassing. You are, of course, completely right. I forgot to put the actual To: header in there. Nothing to see here folks.....move along...move along....
-----Original Message----- From: Mailman-Users [mailto:mailman-users-bounces+aaron.smith=kzoo.edu@python.org] On Behalf Of Robert Heller Sent: Saturday, April 22, 2017 1:39 PM To: Mark Sapiro <mark@msapiro.net> Cc: mailman-users@python.org Subject: Re: [Mailman-Users] Getting implicit destinattion even though To: field is correct
At Sat, 22 Apr 2017 10:23:59 -0700 Mark Sapiro <mark@msapiro.net> wrote:
On 04/21/2017 12:15 PM, Aaron Smith wrote:
... However, if I send a message to testlist@mail01.example.com, it is moderated for implicit destination. Every single time. And I KNOW that the To: field has the correct email address because I'm typing it in myself during a telnet session to port 25! What am I missing here?
The addresses in any To:, Cc:, Resent-To: or Resent-Cc: headers are lower cased and if the local part of any of these matches the list's internal name (which should be the lower case list name, i.e. the list's real_name attribute lower cased), you should not get an implicit destination hold.
I.e., if the list's internal name it 'testlist' and the To: header contains the address testlist@... in any combination of upper/lower case, the message should not be held for implicit destination.
When the message is held for implicit destination, look at the Message Headers: in the held message view in the list's admindb interface. Do they have the To: header you expect?
Since the OP is using a "telnet session to port 25" I wonder if he is confusing an *envelope header" with a message header.
If in the "telnet session to port 25" he is typing:
RCPT To testlist@mail01.example.com
And *failing* to include in the DATA section a line like:
To: testlist@mail01.example.com
Even though the RCPT To is correct, *mailman* still needs the "To: testlist@mail01.example.com" *in the message itself* (in the header in the DATA part).
-- Robert Heller -- 978-544-6933 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller@deepsoft.com -- Webhosting Services
Mailman-Users mailing list Mailman-Users@python.org 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/aaron.smith%40kzoo.edu
participants (3)
-
Aaron Smith
-
Mark Sapiro
-
Robert Heller