From james at dorydesign.com  Tue Nov  1 22:48:53 2016
From: james at dorydesign.com (Jim Dory)
Date: Tue, 1 Nov 2016 18:48:53 -0800
Subject: [Mailman-Users] mailman sending password reminders to members no
 longer subscribed
Message-ID: <CAKhfoy3B=dmuzTvHi5c655JghehpbSOzh+9T+pL-iNTjui22WA@mail.gmail.com>

I've gotten a couple complaints today from ex-members on our subscription
only mailman list after they received password reminders. They are not
subscribed, so I can't honor their request to be removed from the mailing
list.

Any tips of ferreting out these members from some record that needs
updating?

cheers, Jim

From mark at msapiro.net  Wed Nov  2 10:11:20 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 2 Nov 2016 07:11:20 -0700
Subject: [Mailman-Users] mailman sending password reminders to members
 no longer subscribed
In-Reply-To: <CAKhfoy3B=dmuzTvHi5c655JghehpbSOzh+9T+pL-iNTjui22WA@mail.gmail.com>
References: <CAKhfoy3B=dmuzTvHi5c655JghehpbSOzh+9T+pL-iNTjui22WA@mail.gmail.com>
Message-ID: <efd685c6-8182-5028-f55f-1dea486b3fda@msapiro.net>

On 11/01/2016 07:48 PM, Jim Dory wrote:
> I've gotten a couple complaints today from ex-members on our subscription
> only mailman list after they received password reminders. They are not
> subscribed, so I can't honor their request to be removed from the mailing
> list.


You need to see the reminder. It will have the member's subscribed
address and the URL of the member's options page. If these are as you
expect including host and list name in the URL, you need to see the
Recevied: header chain in the notice to see what server sent the notice.
There may still be a prior incarnation of the list on another Mailman
installation on the current or a prior host machine that sent the notice.

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

From turnbull.stephen.fw at u.tsukuba.ac.jp  Wed Nov  2 10:25:23 2016
From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Wed, 2 Nov 2016 23:25:23 +0900
Subject: [Mailman-Users] mailman sending password reminders to members no
 longer subscribed
In-Reply-To: <CAKhfoy3B=dmuzTvHi5c655JghehpbSOzh+9T+pL-iNTjui22WA@mail.gmail.com>
References: <CAKhfoy3B=dmuzTvHi5c655JghehpbSOzh+9T+pL-iNTjui22WA@mail.gmail.com>
Message-ID: <22553.63315.67384.130909@turnbull.sk.tsukuba.ac.jp>

Jim Dory writes:

 > I've gotten a couple complaints today from ex-members on our subscription
 > only mailman list

What do you mean by "subscription only"?  That's not a term we define
as far as I know.

 > after they received password reminders. They are not subscribed,

How do you know that?  The users say so?  They don't appear in the
membership list in the user interface?

 > so I can't honor their request to be removed from the mailing list.

Well, they're subscribed *somewhere*.  Generally speaking, there are
two possibilities.  First is that in the process of an upgrade, you
ended up with two installations, one of which is basically dormant
except for sending out password reminders or something.  Are any users
reporting duplicate reminders?  If not, this is probably not the
case.  On the other hand, if some users are not getting reminders at
all, you probably do have a redundant installation that's still
active.

The second is that these users didn't unsubscribe the addresses that
are receiving the password reminders.  One possibility is that they
set their addresses to "no mail" rather than unsubscribing, which
would explain not receiving posts but receiving reminders.  A second
is that they had multiple addresses for the purpose of posting, but
all but one were set to "no mail", and the users didn't unsubscribe
their post-only addresses.

In a stock Mailman installation the reminder message is addressed to
the subscribed address in "To" in the header and the subscribed
address is also present in the body.  Ask these users to check that
these addresses are the one they unsubscribed.  Note that users may
have changed their preferred addresses, but are still receiving
reminders at the old address via some kind of forwarding setting.

Finally, it's possible that these messages aren't from Mailman at all,
but some kind of spoof to get them to click on a link.  Highly
unlikely, I guess, but to be complete I mention it.

Steve

From turnbull.stephen.fw at u.tsukuba.ac.jp  Wed Nov  2 10:26:39 2016
From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Wed, 2 Nov 2016 23:26:39 +0900
Subject: [Mailman-Users] mailman sending password reminders to members no
 longer subscribed
In-Reply-To: <CAKhfoy3B=dmuzTvHi5c655JghehpbSOzh+9T+pL-iNTjui22WA@mail.gmail.com>
References: <CAKhfoy3B=dmuzTvHi5c655JghehpbSOzh+9T+pL-iNTjui22WA@mail.gmail.com>
Message-ID: <22553.63391.551237.981788@turnbull.sk.tsukuba.ac.jp>

Jim Dory writes:

 > I've gotten a couple complaints today from ex-members on our subscription
 > only mailman list

What do you mean by "subscription only"?  That's not a term we use as
far as I know.

 > after they received password reminders. They are not subscribed,

How do you know that?

 > so I can't honor their request to be removed from the mailing list.

Well, they're subscribed *somewhere*.  Generally speaking, there are
two possibilities.  First is that in the process of an upgrade, you
ended up with two installations, one of which is basically dormant
except for sending out password reminders or something.  Are any users
reporting duplicate reminders?  If not, this is probably not the
case.  On the other hand, if some users are not getting reminders at
all, you probably do have a redundant installation that's still
active.

The second is that these users didn't unsubscribe the addresses that
are receiving the password reminders.  One possibility is that they
set their addresses to "no mail" rather than unsubscribing, which
would explain not receiving posts but receiving reminders.  A second
is that they had multiple addresses for the purpose of posting, but
all but one were set to "no mail", and the users didn't unsubscribe
their post-only addresses.

In a stock Mailman installation the reminder message is addressed to
the subscribed address in "To" in the header and the subscribed
address is also present in the body.  Ask these users to check that
these addresses are the one they unsubscribed.  Note that users may
have changed their preferred addresses, but are still receiving
reminders at the old address via some kind of forwarding setting.

Finally, it's possible that these messages aren't from Mailman at all,
but some kind of spoof to get them to click on a link.  Highly
unlikely, I guess, but to be complete.

From james at dorydesign.com  Wed Nov  2 12:08:06 2016
From: james at dorydesign.com (Jim Dory)
Date: Wed, 2 Nov 2016 08:08:06 -0800
Subject: [Mailman-Users] mailman sending password reminders to members
 no longer subscribed
In-Reply-To: <22553.63391.551237.981788@turnbull.sk.tsukuba.ac.jp>
References: <CAKhfoy3B=dmuzTvHi5c655JghehpbSOzh+9T+pL-iNTjui22WA@mail.gmail.com>
 <22553.63391.551237.981788@turnbull.sk.tsukuba.ac.jp>
Message-ID: <CAKhfoy1PSqHMTe2gJXJZPc6CnRB5gr269yqgp9YGn6iDN++ngg@mail.gmail.com>

Subscription only is simply emphasizing that one has to be a subscriber to
the list. Perhaps this is the only way, I don't know, nor care.

How do I know? Both users replied to the email reminder so it went to the
list owner - me. I could look at the email address on the reminder and the
email on the reminder does not exist in the list of subscribers, both cases.

Mark was helpful in his suggestions: I'll have to get one of the folks to
forward me the password reminder so I can look at the headers. We did
upgrade our package with our host company so maybe the old is still active.

thanks all, Jim



On Wed, Nov 2, 2016 at 6:26 AM, Stephen J. Turnbull <
turnbull.stephen.fw at u.tsukuba.ac.jp> wrote:

> Jim Dory writes:
>
>  > I've gotten a couple complaints today from ex-members on our
> subscription
>  > only mailman list
>
> What do you mean by "subscription only"?  That's not a term we use as
> far as I know.
>
>  > after they received password reminders. They are not subscribed,
>
> How do you know that?
>
>  > so I can't honor their request to be removed from the mailing list.
>
> Well, they're subscribed *somewhere*.  Generally speaking, there are
> two possibilities.  First is that in the process of an upgrade, you
> ended up with two installations, one of which is basically dormant
> except for sending out password reminders or something.  Are any users
> reporting duplicate reminders?  If not, this is probably not the
> case.  On the other hand, if some users are not getting reminders at
> all, you probably do have a redundant installation that's still
> active.
>
> The second is that these users didn't unsubscribe the addresses that
> are receiving the password reminders.  One possibility is that they
> set their addresses to "no mail" rather than unsubscribing, which
> would explain not receiving posts but receiving reminders.  A second
> is that they had multiple addresses for the purpose of posting, but
> all but one were set to "no mail", and the users didn't unsubscribe
> their post-only addresses.
>
> In a stock Mailman installation the reminder message is addressed to
> the subscribed address in "To" in the header and the subscribed
> address is also present in the body.  Ask these users to check that
> these addresses are the one they unsubscribed.  Note that users may
> have changed their preferred addresses, but are still receiving
> reminders at the old address via some kind of forwarding setting.
>
> Finally, it's possible that these messages aren't from Mailman at all,
> but some kind of spoof to get them to click on a link.  Highly
> unlikely, I guess, but to be complete.
>

From cpz at tuunq.com  Wed Nov  2 12:18:10 2016
From: cpz at tuunq.com (Carl Zwanzig)
Date: Wed, 2 Nov 2016 09:18:10 -0700
Subject: [Mailman-Users] mailman sending password reminders to members
 no longer subscribed
In-Reply-To: <CAKhfoy1PSqHMTe2gJXJZPc6CnRB5gr269yqgp9YGn6iDN++ngg@mail.gmail.com>
References: <CAKhfoy3B=dmuzTvHi5c655JghehpbSOzh+9T+pL-iNTjui22WA@mail.gmail.com>
 <22553.63391.551237.981788@turnbull.sk.tsukuba.ac.jp>
 <CAKhfoy1PSqHMTe2gJXJZPc6CnRB5gr269yqgp9YGn6iDN++ngg@mail.gmail.com>
Message-ID: <3c34527b-51b2-465d-a6b3-f17588472d90@tuunq.com>

On 11/2/2016 9:08 AM, Jim Dory wrote:
> Mark was helpful in his suggestions: I'll have to get one of the folks to
> forward me the password reminder so I can look at the headers. We did
> upgrade our package with our host company so maybe the old is still active.

Could also be something as simple as two memberships- joeuser at domain.com and 
joeuser at mail.domain.com. I've had that happen to me, both as a user and as a 
list admin.

(One case of that- the mail host sent as "user at saltmine.radix.net" but 
saltmine didn't directly receive mail; incoming had to go to 
"user at radix.net". I had two sub's to the same list, one set as nomail.)

Later,

z!


From james at dorydesign.com  Wed Nov  2 12:43:16 2016
From: james at dorydesign.com (Jim Dory)
Date: Wed, 2 Nov 2016 08:43:16 -0800
Subject: [Mailman-Users] mailman sending password reminders to members
 no longer subscribed
In-Reply-To: <3c34527b-51b2-465d-a6b3-f17588472d90@tuunq.com>
References: <CAKhfoy3B=dmuzTvHi5c655JghehpbSOzh+9T+pL-iNTjui22WA@mail.gmail.com>
 <22553.63391.551237.981788@turnbull.sk.tsukuba.ac.jp>
 <CAKhfoy1PSqHMTe2gJXJZPc6CnRB5gr269yqgp9YGn6iDN++ngg@mail.gmail.com>
 <3c34527b-51b2-465d-a6b3-f17588472d90@tuunq.com>
Message-ID: <CAKhfoy0XQWjss8fi1avcSeGxykwwfa+5drX3TPpZX7qo8pCVbA@mail.gmail.com>

Thanks Carl,

I did check that but the email reminder was specific on an unsubscribed
email address. I'm now pretty sure it was an old installation on another
server. Still waiting on a forward of the email reminder to be sure.

On Wed, Nov 2, 2016 at 8:18 AM, Carl Zwanzig <cpz at tuunq.com> wrote:

> On 11/2/2016 9:08 AM, Jim Dory wrote:
>
>> Mark was helpful in his suggestions: I'll have to get one of the folks to
>> forward me the password reminder so I can look at the headers. We did
>> upgrade our package with our host company so maybe the old is still
>> active.
>>
>
> Could also be something as simple as two memberships- joeuser at domain.com
> and joeuser at mail.domain.com. I've had that happen to me, both as a user
> and as a list admin.
>
> (One case of that- the mail host sent as "user at saltmine.radix.net" but
> saltmine didn't directly receive mail; incoming had to go to "
> user at radix.net". I had two sub's to the same list, one set as nomail.)
>
> Later,
>
> z!
>
>
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/ma
> ilman-users%40python.org/
> Unsubscribe: https://mail.python.org/mailman/options/mailman-users/james%
> 40dorydesign.com
>

From brennan at columbia.edu  Thu Nov  3 11:40:41 2016
From: brennan at columbia.edu (Joseph Brennan)
Date: Thu, 03 Nov 2016 11:40:41 -0400
Subject: [Mailman-Users] We lost a message
Message-ID: <6BFB94982206B0EB5413DCB7@082-JB51-M1>


We had an odd situation yesterday where Mailman lost a message.

The list is one that includes other lists ("Other mailing lists on
this site whose members are included") rather than having its own
subscribers. The list has existed for several years and has been
used many times. The last previous time was a week earlier.

A message was sent to the list address, and held for moderator
approval, as configured. The moderator approved. The approval action
is logged, so we know the right button was used. But then the message
disappeared. No Mailman logs recorded an action after approval, and
Postfix had no log of the message.

As a test we changed it to include only one small list instead, sent a
message, and got the same result, that is, moderator approved the
message and again the last trace was the log that it was approved.

As a second test we made the list unmoderated, and sent a message.
Postfix log shows it being accepted and passed to Mailman, but there
is nothing in Mailman's logs for this one.

We checked carefully for any configuration that would discard messages
automatically.

We deleted the problem list, and created a new list of the same name
including the small list, and then it worked normally. To the best of
our knowledge only this one list had the problem. Many other lists
were sending mail successfully during the same time.

We can't figure out what happened here. We never saw this before and I
don't remember anyone reporting it on this list either. I realize that
by deleting the list we destroyed some possible evidence, but all the
logs are still intact. Two of our tech staff spent some time yesterday
looking for any place the messages could be without success. I keep
thinking we missed something.

Has anyone EVER seen this? Where would you look for clues?

Joseph Brennan
Columbia U I T




From mark at msapiro.net  Thu Nov  3 12:59:43 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 3 Nov 2016 09:59:43 -0700
Subject: [Mailman-Users] We lost a message
In-Reply-To: <6BFB94982206B0EB5413DCB7@082-JB51-M1>
References: <6BFB94982206B0EB5413DCB7@082-JB51-M1>
Message-ID: <2005e7d9-f1ff-0b4c-c80c-50da0cd0bbc3@msapiro.net>

On 11/03/2016 08:40 AM, Joseph Brennan wrote:
> 
> A message was sent to the list address, and held for moderator
> approval, as configured. The moderator approved. The approval action
> is logged, so we know the right button was used. But then the message
> disappeared. No Mailman logs recorded an action after approval, and
> Postfix had no log of the message.


If there was nothing in any Mailman log including "error" following the
approval in the "vette" log, it's difficult to know what might have
happened.


> As a test we changed it to include only one small list instead, sent a
> message, and got the same result, that is, moderator approved the
> message and again the last trace was the log that it was approved.
> 
> As a second test we made the list unmoderated, and sent a message.
> Postfix log shows it being accepted and passed to Mailman, but there
> is nothing in Mailman's logs for this one.
> 
> We checked carefully for any configuration that would discard messages
> automatically.


I think that is the most likely thing. In particular, I'd suspect
Content filtering, but, but if any subsequent handler discarded the
message, there should be a 'discarded' entry in the vette log.


> We deleted the problem list, and created a new list of the same name
> including the small list, and then it worked normally. To the best of
> our knowledge only this one list had the problem. Many other lists
> were sending mail successfully during the same time.


So it had to be something in the config of the old list. Do you have a
backup of the lists/LISTNAME/config.pck file from before you deleted it
but after the problem appeared?

If so, create a new lists/TEMP_NAME/ directory and put the config.pck
there. Then run 'bin/config_list -o old.config TEMP_NAME' and also
'bin/config_list -o new.config LISTNAME' and diff the two config files.

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

From kippels at hhu.de  Fri Nov  4 06:40:39 2016
From: kippels at hhu.de (Julian Kippels)
Date: Fri, 4 Nov 2016 11:40:39 +0100
Subject: [Mailman-Users] Command line tools for virtualhosts
Message-ID: <20161104114039.53121083@kriemhild>

Hi,

we have a mailman installation with several virtual hosts. I would like
to give ssh access to the site admins of those virtual hosts so that
they can use the command line tools for their own virtual hosts. How
can I make sure, that the admin for site A cannot modify site B when
using command line access?

Thanks
Julian

From mark at msapiro.net  Fri Nov  4 12:49:48 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 4 Nov 2016 09:49:48 -0700
Subject: [Mailman-Users] Command line tools for virtualhosts
In-Reply-To: <20161104114039.53121083@kriemhild>
References: <20161104114039.53121083@kriemhild>
Message-ID: <9202ab54-4495-8b5f-39ae-24ef748cb3c2@msapiro.net>

On 11/4/16 3:40 AM, Julian Kippels wrote:
> 
> we have a mailman installation with several virtual hosts. I would like
> to give ssh access to the site admins of those virtual hosts so that
> they can use the command line tools for their own virtual hosts. How
> can I make sure, that the admin for site A cannot modify site B when
> using command line access?


You can't. If they have enough access to run the command line tools,
they have enough access to do almost anything to the Mailman installation.

Mailman doesn't actually separate anything by virtual host. All the
lists data are in the same file system hierarchy. Virtual hosts are just
a way of controlling which lists are shown on admin and listinfo
overviews and in the Postfix case at least, generating appropriate
virtual alias mappings.

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

From info at ckol.de  Sun Nov  6 11:06:05 2016
From: info at ckol.de (Christian)
Date: Sun, 6 Nov 2016 17:06:05 +0100
Subject: [Mailman-Users] postfix + mailman + mailboxes on the same domain
 and server
Message-ID: <581F54ED.2000406@ckol.de>

Hello,

I'm trying to get the mailing list to work with postfix and I read a lot
of information about the difficult usage of it.

-> It should be possible for a mailbox user 'user at domain.tld' to send at
the mailing list 'list at domain.tld'.

The only one I found in the archives that addresses my problem:
https://mail.python.org/pipermail/mailman-users/2012-February/072967.html

Actually I always get the same error message:
/var/log/mail.log
*************************************************************
Nov  6 15:50:42 mail postfix/smtpd[757]: connect from IP
Nov  6 15:50:43 mail postfix/smtpd[757]: Anonymous TLS connection
established from IP: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256
(128/128 bits)
Nov  6 15:50:43 mail postfix/smtpd[757]: NOQUEUE: reject: RCPT from IP:
550 5.1.1 <list at domain.tld>: Recipient address rejected: User unknown in
virtual mailbox table; from=<user at domain.tld> to=<list at domain.tld>
proto=ESMTP helo=<[local-IP]>
Nov  6 15:50:48 mail postfix/smtpd[757]: disconnect from IP
*************************************************************

I hope that my posted configs help you to address the issure.
The usual comments has been removed.


/etc/mailman/mm_cfg.py
*************************************************************
from Defaults import *
MAILMAN_SITE_LIST = 'mailman'
DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/'
IMAGE_LOGOS  = '/images/mailman/'
DEFAULT_EMAIL_HOST = 'domain.tld'
DEFAULT_URL_HOST   = 'www.domain.tld'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
DEFAULT_SERVER_LANGUAGE = 'de'
USE_ENVELOPE_SENDER    = 0              # Still used?
DEFAULT_SEND_REMINDERS = 0
MTA = None # So that mailman skips aliases generation
DEB_LISTMASTER = 'postmaster at domain.tld'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['domain.tld']
POSTFIX_MAP_CMD = '/var/lib/mailman/data/virtual_to_transport'
*************************************************************

root at mail:/var/lib/mailman/data# ls -l
insgesamt 64
-rw-rw-r-- 1 list list  1843 Nov  6 15:07 aliases
-rw-rw-r-- 1 list list 12288 Nov  6 15:07 aliases.db
-rw-rw-r-- 1 root list    10 Okt 20 11:48 last_mailman_version
-rw-r--r-- 1 root list 14100 Sep 15 08:04 sitelist.cfg
-rw-rw-r-- 1 list list  1606 Nov  6 15:07 transport-mailman
-rw-r--r-- 1 list list 12288 Nov  6 15:07 transport-mailman.db
-rw-rw---- 1 root list  1698 Nov  6 15:07 virtual-mailman
-rwxr-x--- 1 root list   149 Nov  6 15:07 virtual_to_transport

/var/lib/mailman/data/transport-mailman
*************************************************************
mailman-loop at domain.tld mailman:

mailman at domain.tld              mailman:
mailman-admin at domain.tld        mailman:
mailman-bounces at domain.tld      mailman:
mailman-confirm at domain.tld      mailman:
mailman-join at domain.tld         mailman:
mailman-leave at domain.tld        mailman:
mailman-owner at domain.tld        mailman:
mailman-request at domain.tld      mailman:
mailman-subscribe at domain.tld    mailman:
mailman-unsubscribe at domain.tld  mailman:

list at domain.tld              mailman:
list-admin at domain.tld        mailman:
list-bounces at domain.tld      mailman:
list-confirm at domain.tld      mailman:
list-join at domain.tld        mailman:
list-leave at domain.tld        mailman:
list-owner at domain.tld        mailman:
list-request at domain.tld      mailman:
list-subscribe at domain.tld    mailman:
list-unsubscribe at domain.tld  mailman:
*************************************************************

/etc/postfix/master.cf
*************************************************************
mailman unix  -       n       n       -       -       pipe
  flags=FR user=list
  argv=/var/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}
*************************************************************

/etc/postfix/main.cf
*************************************************************
smtpd_banner = $myhostname
biff = no
append_dot_mydomain = no
readme_directory = /usr/share/doc/postfix
html_directory = /usr/share/doc/postfix/html

myhostname = mail.domain.tld
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = mail.domain.tld
mydestination = mail.domain.tld, localhost
relayhost =
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
mailbox_size_limit = 0
virtual_mailbox_limit = 0
recipient_delimiter = +
inet_interfaces = all
inet_protocols = ipv4
disable_vrfy_command = yes

smtpd_helo_required = yes
smtpd_sasl_type=dovecot
smtpd_sasl_path=private/auth_dovecot
smtpd_sasl_auth_enable = yes
smtpd_sasl_authenticated_header = yes
broken_sasl_auth_clients = yes

proxy_read_maps = $local_recipient_maps $mydestination
$virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps
$virtual_mailbox_domains $relay_recipient_maps $relay_domains
$canonical_maps $sender_canonical_maps $recipient_canonical_maps
$relocated_maps $transport_maps $mynetworks $smtpd_sender_login_maps
virtual_mailbox_base = /
virtual_mailbox_domains =
proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_domains_maps.cf
virtual_alias_maps =
proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf
virtual_mailbox_maps =
proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_mailbox_maps.cf
virtual_minimum_uid = 5000
virtual_uid_maps = static:5000
virtual_gid_maps = static:5000
virtual_transport = lmtps:unix:private/dovecot-lmtp
transport_maps = hash:/var/lib/mailman/data/transport-mailman,
mysql:/etc/postfix/mysql/postfix-mysql-virtual_transport_maps.cf

maximal_queue_lifetime = 1d
bounce_queue_lifetime = 1d
queue_run_delay = 300s
maximal_backoff_time = 1800s
minimal_backoff_time = 300s
message_size_limit = 524288000
smtpd_soft_error_limit = 3
smtpd_error_sleep_time = 10s
smtpd_hard_error_limit = ${stress?1}${stress:5}

mailman_destination_recipient_limit = 1
relay_recipient_maps = hash:/var/lib/mailman/data/transport-mailman
*************************************************************
The only edit here was in transport_maps and the last both lines.

I don't know which steps in the manuals are important for me and which not.
Please help me to correct that.

Greetings Christian



From beta at admilon.net  Mon Nov  7 20:02:49 2016
From: beta at admilon.net (Matthias Schmidt)
Date: Tue, 8 Nov 2016 10:02:49 +0900
Subject: [Mailman-Users] postfix + mailman + mailboxes on the same
 domain and server
In-Reply-To: <581F54ED.2000406@ckol.de>
References: <581F54ED.2000406@ckol.de>
Message-ID: <08CE0439-98AA-4ABE-A7BA-9EC2110E2E26@admilon.net>


> Am 07.11.2016 um 01:06 schrieb Christian <info at ckol.de>:
> 
> Hello,
> 
> I'm trying to get the mailing list to work with postfix and I read a lot
> of information about the difficult usage of it.
> 
> -> It should be possible for a mailbox user 'user at domain.tld' to send at
> the mailing list 'list at domain.tld'.
> 
> The only one I found in the archives that addresses my problem:
> https://mail.python.org/pipermail/mailman-users/2012-February/072967.html
> 
> Actually I always get the same error message:
> /var/log/mail.log
> *************************************************************
> Nov  6 15:50:42 mail postfix/smtpd[757]: connect from IP
> Nov  6 15:50:43 mail postfix/smtpd[757]: Anonymous TLS connection
> established from IP: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256
> (128/128 bits)
> Nov  6 15:50:43 mail postfix/smtpd[757]: NOQUEUE: reject: RCPT from IP:
> 550 5.1.1 <list at domain.tld>: Recipient address rejected: User unknown in
> virtual mailbox table; from=<user at domain.tld> to=<list at domain.tld>
> proto=ESMTP helo=<[local-IP]>
> Nov  6 15:50:48 mail postfix/smtpd[757]: disconnect from IP
> *************************************************************
> 
> I hope that my posted configs help you to address the issure.

Postfix doesn?t know about the maiman users so imho your main.cf is missing this here:
alias_maps = hash:/private/var/mailman/data/aliases
as well as this:
virtual_alias_maps = hash:/private/var/mailman/data/virtual-mailman

imho the postfix-to-mailman.py script is outdated and not needed anymore.
Therefore you don?t need to modify master.cf.

http://www.list.org/mailman-install/node12.html

cheers
Matthias


> 
> The usual comments has been removed.
> 
> 
> /etc/mailman/mm_cfg.py
> *************************************************************
> from Defaults import *
> MAILMAN_SITE_LIST = 'mailman'
> DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/'
> IMAGE_LOGOS  = '/images/mailman/'
> DEFAULT_EMAIL_HOST = 'domain.tld'
> DEFAULT_URL_HOST   = 'www.domain.tld'
> add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> DEFAULT_SERVER_LANGUAGE = 'de'
> USE_ENVELOPE_SENDER    = 0              # Still used?
> DEFAULT_SEND_REMINDERS = 0
> MTA = None # So that mailman skips aliases generation
> DEB_LISTMASTER = 'postmaster at domain.tld'
> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['domain.tld']
> POSTFIX_MAP_CMD = '/var/lib/mailman/data/virtual_to_transport'
> *************************************************************
> 
> root at mail:/var/lib/mailman/data# ls -l
> insgesamt 64
> -rw-rw-r-- 1 list list  1843 Nov  6 15:07 aliases
> -rw-rw-r-- 1 list list 12288 Nov  6 15:07 aliases.db
> -rw-rw-r-- 1 root list    10 Okt 20 11:48 last_mailman_version
> -rw-r--r-- 1 root list 14100 Sep 15 08:04 sitelist.cfg
> -rw-rw-r-- 1 list list  1606 Nov  6 15:07 transport-mailman
> -rw-r--r-- 1 list list 12288 Nov  6 15:07 transport-mailman.db
> -rw-rw---- 1 root list  1698 Nov  6 15:07 virtual-mailman
> -rwxr-x--- 1 root list   149 Nov  6 15:07 virtual_to_transport
> 
> /var/lib/mailman/data/transport-mailman
> *************************************************************
> mailman-loop at domain.tld mailman:
> 
> mailman at domain.tld              mailman:
> mailman-admin at domain.tld        mailman:
> mailman-bounces at domain.tld      mailman:
> mailman-confirm at domain.tld      mailman:
> mailman-join at domain.tld         mailman:
> mailman-leave at domain.tld        mailman:
> mailman-owner at domain.tld        mailman:
> mailman-request at domain.tld      mailman:
> mailman-subscribe at domain.tld    mailman:
> mailman-unsubscribe at domain.tld  mailman:
> 
> list at domain.tld              mailman:
> list-admin at domain.tld        mailman:
> list-bounces at domain.tld      mailman:
> list-confirm at domain.tld      mailman:
> list-join at domain.tld        mailman:
> list-leave at domain.tld        mailman:
> list-owner at domain.tld        mailman:
> list-request at domain.tld      mailman:
> list-subscribe at domain.tld    mailman:
> list-unsubscribe at domain.tld  mailman:
> *************************************************************
> 
> /etc/postfix/master.cf
> *************************************************************
> mailman unix  -       n       n       -       -       pipe
>  flags=FR user=list
>  argv=/var/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}
> *************************************************************
> 
> /etc/postfix/main.cf
> *************************************************************
> smtpd_banner = $myhostname
> biff = no
> append_dot_mydomain = no
> readme_directory = /usr/share/doc/postfix
> html_directory = /usr/share/doc/postfix/html
> 
> myhostname = mail.domain.tld
> alias_maps = hash:/etc/aliases
> alias_database = hash:/etc/aliases
> myorigin = mail.domain.tld
> mydestination = mail.domain.tld, localhost
> relayhost =
> mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
> mailbox_size_limit = 0
> virtual_mailbox_limit = 0
> recipient_delimiter = +
> inet_interfaces = all
> inet_protocols = ipv4
> disable_vrfy_command = yes
> 
> smtpd_helo_required = yes
> smtpd_sasl_type=dovecot
> smtpd_sasl_path=private/auth_dovecot
> smtpd_sasl_auth_enable = yes
> smtpd_sasl_authenticated_header = yes
> broken_sasl_auth_clients = yes
> 
> proxy_read_maps = $local_recipient_maps $mydestination
> $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps
> $virtual_mailbox_domains $relay_recipient_maps $relay_domains
> $canonical_maps $sender_canonical_maps $recipient_canonical_maps
> $relocated_maps $transport_maps $mynetworks $smtpd_sender_login_maps
> virtual_mailbox_base = /
> virtual_mailbox_domains =
> proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_domains_maps.cf
> virtual_alias_maps =
> proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf
> virtual_mailbox_maps =
> proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_mailbox_maps.cf
> virtual_minimum_uid = 5000
> virtual_uid_maps = static:5000
> virtual_gid_maps = static:5000
> virtual_transport = lmtps:unix:private/dovecot-lmtp
> transport_maps = hash:/var/lib/mailman/data/transport-mailman,
> mysql:/etc/postfix/mysql/postfix-mysql-virtual_transport_maps.cf
> 
> maximal_queue_lifetime = 1d
> bounce_queue_lifetime = 1d
> queue_run_delay = 300s
> maximal_backoff_time = 1800s
> minimal_backoff_time = 300s
> message_size_limit = 524288000
> smtpd_soft_error_limit = 3
> smtpd_error_sleep_time = 10s
> smtpd_hard_error_limit = ${stress?1}${stress:5}
> 
> mailman_destination_recipient_limit = 1
> relay_recipient_maps = hash:/var/lib/mailman/data/transport-mailman
> *************************************************************
> The only edit here was in transport_maps and the last both lines.
> 
> I don't know which steps in the manuals are important for me and which not.
> Please help me to correct that.
> 
> Greetings Christian
> 
> 
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/beta%40admilon.net

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20161108/6cfa0d27/attachment.sig>

From info at ckol.de  Mon Nov  7 20:51:34 2016
From: info at ckol.de (Christian)
Date: Tue, 8 Nov 2016 02:51:34 +0100
Subject: [Mailman-Users] postfix + mailman + mailboxes on the same
 domain and server
In-Reply-To: <08CE0439-98AA-4ABE-A7BA-9EC2110E2E26@admilon.net>
References: <581F54ED.2000406@ckol.de>
 <08CE0439-98AA-4ABE-A7BA-9EC2110E2E26@admilon.net>
Message-ID: <58212FA6.3020702@ckol.de>

It works!

-> It should be possible for a mailbox user 'user at domain.tld' to send at
the mailing list 'list at domain.tld'.

Deboian 8 jessie, postfix, dovecot, mailman

For all who want to do the same as me :)

_Summary:_

You only need to change/add these lines in main.cf:
*************************************************************
alias_maps = ... hash:/private/var/mailman/data/aliases
virtual_alias_maps = ... hash:/var/lib/mailman/data/virtual-mailman
transport_maps = ... hash:/var/lib/mailman/data/transport-mailman
mailman_destination_recipient_limit = 1
recipient_delimiter = +
unknown_local_recipient_reject_code = 550
*************************************************************

nothing to add in master.cf


_Ignore the postfix-to-mailman.py script!_


simple and clean /etc/mailman/mm_cfg.py:
*************************************************************
from Defaults import *
MAILMAN_SITE_LIST = 'mailman'
DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/'
IMAGE_LOGOS  = '/images/mailman/'
DEFAULT_EMAIL_HOST = 'domain.tld'
DEFAULT_URL_HOST   = 'www.domain.tld'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
DEFAULT_SERVER_LANGUAGE = 'de'
USE_ENVELOPE_SENDER    = 0              # Still used?
DEFAULT_SEND_REMINDERS = 0
MTA='Postfix'
DEB_LISTMASTER = 'postmaster at domain.tld'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['domain.tld']
POSTFIX_MAP_CMD = '/var/lib/mailman/data/virtual_to_transport'
*************************************************************

All three _maps_ must have a .db! (with the same timecode)

_Finally these:_
/usr/lib/mailman/bin/genaliases

postmap /var/lib/mailman/data/virtual-mailman <- these line has to be
added to the file virtual_to_transport
If POSTFIX_MAP_CMD is used the database of virtual-mailman doesn't get
updated anymore.

The FAQ at http://wiki.list.org/x/ZoCj may help.


Thank you all very much for the help!

I hope that I have all above correct.

Christian


Am 08.11.2016 um 02:02 schrieb Matthias Schmidt:
> 
>> Am 07.11.2016 um 01:06 schrieb Christian <info at ckol.de>:
>>
>> Hello,
>>
>> I'm trying to get the mailing list to work with postfix and I read a lot
>> of information about the difficult usage of it.
>>
>> -> It should be possible for a mailbox user 'user at domain.tld' to send at
>> the mailing list 'list at domain.tld'.
>>
>> The only one I found in the archives that addresses my problem:
>> https://mail.python.org/pipermail/mailman-users/2012-February/072967.html
>>
>> Actually I always get the same error message:
>> /var/log/mail.log
>> *************************************************************
>> Nov  6 15:50:42 mail postfix/smtpd[757]: connect from IP
>> Nov  6 15:50:43 mail postfix/smtpd[757]: Anonymous TLS connection
>> established from IP: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256
>> (128/128 bits)
>> Nov  6 15:50:43 mail postfix/smtpd[757]: NOQUEUE: reject: RCPT from IP:
>> 550 5.1.1 <list at domain.tld>: Recipient address rejected: User unknown in
>> virtual mailbox table; from=<user at domain.tld> to=<list at domain.tld>
>> proto=ESMTP helo=<[local-IP]>
>> Nov  6 15:50:48 mail postfix/smtpd[757]: disconnect from IP
>> *************************************************************
>>
>> I hope that my posted configs help you to address the issure.
> 
> Postfix doesn?t know about the maiman users so imho your main.cf is missing this here:
> alias_maps = hash:/private/var/mailman/data/aliases
> as well as this:
> virtual_alias_maps = hash:/private/var/mailman/data/virtual-mailman
> 
> imho the postfix-to-mailman.py script is outdated and not needed anymore.
> Therefore you don?t need to modify master.cf.
> 
> http://www.list.org/mailman-install/node12.html
> 
> cheers
> Matthias
> 
> 
>>
>> The usual comments has been removed.
>>
>>
>> /etc/mailman/mm_cfg.py
>> *************************************************************
>> from Defaults import *
>> MAILMAN_SITE_LIST = 'mailman'
>> DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/'
>> IMAGE_LOGOS  = '/images/mailman/'
>> DEFAULT_EMAIL_HOST = 'domain.tld'
>> DEFAULT_URL_HOST   = 'www.domain.tld'
>> add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>> DEFAULT_SERVER_LANGUAGE = 'de'
>> USE_ENVELOPE_SENDER    = 0              # Still used?
>> DEFAULT_SEND_REMINDERS = 0
>> MTA = None # So that mailman skips aliases generation
>> DEB_LISTMASTER = 'postmaster at domain.tld'
>> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['domain.tld']
>> POSTFIX_MAP_CMD = '/var/lib/mailman/data/virtual_to_transport'
>> *************************************************************
>>
>> root at mail:/var/lib/mailman/data# ls -l
>> insgesamt 64
>> -rw-rw-r-- 1 list list  1843 Nov  6 15:07 aliases
>> -rw-rw-r-- 1 list list 12288 Nov  6 15:07 aliases.db
>> -rw-rw-r-- 1 root list    10 Okt 20 11:48 last_mailman_version
>> -rw-r--r-- 1 root list 14100 Sep 15 08:04 sitelist.cfg
>> -rw-rw-r-- 1 list list  1606 Nov  6 15:07 transport-mailman
>> -rw-r--r-- 1 list list 12288 Nov  6 15:07 transport-mailman.db
>> -rw-rw---- 1 root list  1698 Nov  6 15:07 virtual-mailman
>> -rwxr-x--- 1 root list   149 Nov  6 15:07 virtual_to_transport
>>
>> /var/lib/mailman/data/transport-mailman
>> *************************************************************
>> mailman-loop at domain.tld mailman:
>>
>> mailman at domain.tld              mailman:
>> mailman-admin at domain.tld        mailman:
>> mailman-bounces at domain.tld      mailman:
>> mailman-confirm at domain.tld      mailman:
>> mailman-join at domain.tld         mailman:
>> mailman-leave at domain.tld        mailman:
>> mailman-owner at domain.tld        mailman:
>> mailman-request at domain.tld      mailman:
>> mailman-subscribe at domain.tld    mailman:
>> mailman-unsubscribe at domain.tld  mailman:
>>
>> list at domain.tld              mailman:
>> list-admin at domain.tld        mailman:
>> list-bounces at domain.tld      mailman:
>> list-confirm at domain.tld      mailman:
>> list-join at domain.tld        mailman:
>> list-leave at domain.tld        mailman:
>> list-owner at domain.tld        mailman:
>> list-request at domain.tld      mailman:
>> list-subscribe at domain.tld    mailman:
>> list-unsubscribe at domain.tld  mailman:
>> *************************************************************
>>
>> /etc/postfix/master.cf
>> *************************************************************
>> mailman unix  -       n       n       -       -       pipe
>>  flags=FR user=list
>>  argv=/var/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}
>> *************************************************************
>>
>> /etc/postfix/main.cf
>> *************************************************************
>> smtpd_banner = $myhostname
>> biff = no
>> append_dot_mydomain = no
>> readme_directory = /usr/share/doc/postfix
>> html_directory = /usr/share/doc/postfix/html
>>
>> myhostname = mail.domain.tld
>> alias_maps = hash:/etc/aliases
>> alias_database = hash:/etc/aliases
>> myorigin = mail.domain.tld
>> mydestination = mail.domain.tld, localhost
>> relayhost =
>> mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
>> mailbox_size_limit = 0
>> virtual_mailbox_limit = 0
>> recipient_delimiter = +
>> inet_interfaces = all
>> inet_protocols = ipv4
>> disable_vrfy_command = yes
>>
>> smtpd_helo_required = yes
>> smtpd_sasl_type=dovecot
>> smtpd_sasl_path=private/auth_dovecot
>> smtpd_sasl_auth_enable = yes
>> smtpd_sasl_authenticated_header = yes
>> broken_sasl_auth_clients = yes
>>
>> proxy_read_maps = $local_recipient_maps $mydestination
>> $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps
>> $virtual_mailbox_domains $relay_recipient_maps $relay_domains
>> $canonical_maps $sender_canonical_maps $recipient_canonical_maps
>> $relocated_maps $transport_maps $mynetworks $smtpd_sender_login_maps
>> virtual_mailbox_base = /
>> virtual_mailbox_domains =
>> proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_domains_maps.cf
>> virtual_alias_maps =
>> proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf
>> virtual_mailbox_maps =
>> proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_mailbox_maps.cf
>> virtual_minimum_uid = 5000
>> virtual_uid_maps = static:5000
>> virtual_gid_maps = static:5000
>> virtual_transport = lmtps:unix:private/dovecot-lmtp
>> transport_maps = hash:/var/lib/mailman/data/transport-mailman,
>> mysql:/etc/postfix/mysql/postfix-mysql-virtual_transport_maps.cf
>>
>> maximal_queue_lifetime = 1d
>> bounce_queue_lifetime = 1d
>> queue_run_delay = 300s
>> maximal_backoff_time = 1800s
>> minimal_backoff_time = 300s
>> message_size_limit = 524288000
>> smtpd_soft_error_limit = 3
>> smtpd_error_sleep_time = 10s
>> smtpd_hard_error_limit = ${stress?1}${stress:5}
>>
>> mailman_destination_recipient_limit = 1
>> relay_recipient_maps = hash:/var/lib/mailman/data/transport-mailman
>> *************************************************************
>> The only edit here was in transport_maps and the last both lines.
>>
>> I don't know which steps in the manuals are important for me and which not.
>> Please help me to correct that.
>>
>> Greetings Christian
>>
>>
>> ------------------------------------------------------
>> Mailman-Users mailing list Mailman-Users at 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/beta%40admilon.net
> 

From info at ckol.de  Mon Nov  7 17:01:08 2016
From: info at ckol.de (Christian)
Date: Mon, 7 Nov 2016 23:01:08 +0100
Subject: [Mailman-Users] postfix + mailman + mailboxes on the same
 domain and server
In-Reply-To: <031b01d23907$a6642160$f32c6420$@acbradio.org>
References: <581F54ED.2000406@ckol.de>
 <031b01d23907$a6642160$f32c6420$@acbradio.org>
Message-ID: <5820F9A4.308@ckol.de>

Thanks I changed it back to Postfix. 'transport-mailman' get's created
correctly again.
The error message is still the same.

So I added a verbose log from postfix down here.
Postfix seems to read the transport-mailman but dont forward it to mailman.
Almost in the middle of the log is this line:
Nov 7 22:06:06 mail postfix/smtpd[18815]: resolve_clnt: `' ->
`lists at domain.tld' -> transp=`mailman' host=`domain.tld'
rcpt=`lists at domain.tld' flags= class=virtual

Why it is searching further and doesn't forward the mail?
It can't find the mailaddress because certainly no mailaccout exists.
Only the transport_maps =  hash:/var/lib/mailman/data/transport-mailman
has the mailing-list address

 
>From the archive mailing.list:
"So mail to my-list at foo.bar.com
<http://mail.python.org/mailman/listinfo/mailman-users> should use a
'mailman' transport, presumably defined in master.cf as
postfix_to_mailman.py. If you want to use this, there should be no
aliases for Mailman at all there should only be transport maps entries
of the form my-list at foo.bar.com
<http://mail.python.org/mailman/listinfo/mailman-users> mailman:
my-list-admin at foo.bar.com
<http://mail.python.org/mailman/listinfo/mailman-users> mailman:
my-list-bounces at foo.bar.com
<http://mail.python.org/mailman/listinfo/mailman-users> mailman: etc. A
total of 10 per list since non-list mail for this domain should be
handled by the 'virtual' transport."
See link in my first mail.

Greetings
Christian

_Postfix verbose logging - trying to send to lists at domain.tld:_
Nov 7 22:06:01 mail postfix/master[18812]: daemon started -- version
2.11.3, configuration /etc/postfix
Nov 7 22:06:05 mail postfix/smtpd[18815]: name_mask: ipv4
Nov 7 22:06:05 mail postfix/smtpd[18815]: inet_addr_local: configured 2
IPv4 addresses
Nov 7 22:06:05 mail postfix/smtpd[18815]: process generation: 3 (3)
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string: mynetworks ~?
debug_peer_list
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string: mynetworks ~?
fast_flush_domains
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string: mynetworks ~?
mynetworks
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string: relay_domains ~?
debug_peer_list
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string: relay_domains ~?
fast_flush_domains
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string: relay_domains ~?
mynetworks
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string: relay_domains ~?
permit_mx_backup_networks
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string: relay_domains ~?
qmqpd_authorized_clients
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string: relay_domains ~?
relay_domains
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string:
permit_mx_backup_networks ~? debug_peer_list
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string:
permit_mx_backup_networks ~? fast_flush_domains
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string:
permit_mx_backup_networks ~? mynetworks
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string:
permit_mx_backup_networks ~? permit_mx_backup_networks
Nov 7 22:06:05 mail postfix/smtpd[18815]: connect to subsystem
private/proxymap
Nov 7 22:06:05 mail postfix/smtpd[18815]: send attr request = open
Nov 7 22:06:05 mail postfix/smtpd[18815]: send attr table =
unix:passwd.byname
Nov 7 22:06:05 mail postfix/smtpd[18815]: send attr flags = 0
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: status
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: status
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute value: 0
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: flags
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: flags
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute value: 16
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: (list terminator)
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:05 mail postfix/smtpd[18815]: dict_proxy_open: connect to
map=unix:passwd.byname status=0 server_flags=fixed
Nov 7 22:06:05 mail postfix/smtpd[18815]: dict_open:
proxy:unix:passwd.byname
Nov 7 22:06:05 mail postfix/smtpd[18815]: Compiled against Berkeley DB:
5.3.28?
Nov 7 22:06:05 mail postfix/smtpd[18815]: Run-time linked against
Berkeley DB: 5.3.28?
Nov 7 22:06:05 mail postfix/smtpd[18815]: dict_open: hash:/etc/aliases
Nov 7 22:06:05 mail postfix/smtpd[18815]: send attr request = open
Nov 7 22:06:05 mail postfix/smtpd[18815]: send attr table =
mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf
Nov 7 22:06:05 mail postfix/smtpd[18815]: send attr flags = 0
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: status
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: status
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute value: 0
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: flags
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: flags
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute value: 16
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: (list terminator)
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:05 mail postfix/smtpd[18815]: dict_proxy_open: connect to
map=mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf
status=0 server_flags=fixed
Nov 7 22:06:05 mail postfix/smtpd[18815]: dict_open:
proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf
Nov 7 22:06:05 mail postfix/smtpd[18815]: send attr request = open
Nov 7 22:06:05 mail postfix/smtpd[18815]: send attr table =
mysql:/etc/postfix/mysql/postfix-mysql-virtual_mailbox_maps.cf
Nov 7 22:06:05 mail postfix/smtpd[18815]: send attr flags = 0
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: status
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: status
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute value: 0
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: flags
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: flags
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute value: 16
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: (list terminator)
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:05 mail postfix/smtpd[18815]: dict_proxy_open: connect to
map=mysql:/etc/postfix/mysql/postfix-mysql-virtual_mailbox_maps.cf
status=0 server_flags=fixed
Nov 7 22:06:05 mail postfix/smtpd[18815]: dict_open:
proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_mailbox_maps.cf
Nov 7 22:06:05 mail postfix/smtpd[18815]: Compiled against Berkeley DB:
5.3.28?
Nov 7 22:06:05 mail postfix/smtpd[18815]: Run-time linked against
Berkeley DB: 5.3.28?
Nov 7 22:06:05 mail postfix/smtpd[18815]: dict_open:
hash:/var/lib/mailman/data/transport-mailman
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string:
smtpd_access_maps ~? debug_peer_list
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string:
smtpd_access_maps ~? fast_flush_domains
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string:
smtpd_access_maps ~? mynetworks
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string:
smtpd_access_maps ~? permit_mx_backup_networks
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string:
smtpd_access_maps ~? qmqpd_authorized_clients
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string:
smtpd_access_maps ~? relay_domains
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string:
smtpd_access_maps ~? smtpd_access_maps
Nov 7 22:06:05 mail postfix/smtpd[18815]: auto_clnt_create:
transport=unix endpoint=private/quota-status
Nov 7 22:06:05 mail postfix/smtpd[18815]:
unknown_helo_hostname_tempfail_action = defer_if_permit
Nov 7 22:06:05 mail postfix/smtpd[18815]:
unknown_address_tempfail_action = defer_if_permit
Nov 7 22:06:05 mail postfix/smtpd[18815]:
unverified_recipient_tempfail_action = defer_if_permit
Nov 7 22:06:05 mail postfix/smtpd[18815]:
unverified_sender_tempfail_action = defer_if_permit
Nov 7 22:06:05 mail postfix/smtpd[18815]: name_mask: 1
Nov 7 22:06:05 mail postfix/smtpd[18815]: auto_clnt_create:
transport=local endpoint=private/tlsmgr
Nov 7 22:06:05 mail postfix/smtpd[18815]: auto_clnt_open: connected to
private/tlsmgr
Nov 7 22:06:05 mail postfix/smtpd[18815]: send attr request = seed
Nov 7 22:06:05 mail postfix/smtpd[18815]: send attr size = 32
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: status
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: status
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute value: 0
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: seed
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: seed
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute value:
fNetk0YSqWZnkC5s1eZ7SntiYIJDqRbzjql1jCfe2Xg=
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: (list terminator)
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:05 mail postfix/smtpd[18815]: send attr request = policy
Nov 7 22:06:05 mail postfix/smtpd[18815]: send attr cache_type = smtpd
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: status
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: status
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute value: 0
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: cachable
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: cachable
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute value: 1
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: timeout
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: timeout
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute value: 3600
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: (list terminator)
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string:
fast_flush_domains ~? debug_peer_list
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_string:
fast_flush_domains ~? fast_flush_domains
Nov 7 22:06:05 mail postfix/smtpd[18815]: name_mask: speed_adjust
Nov 7 22:06:05 mail postfix/smtpd[18815]: auto_clnt_create:
transport=local endpoint=private/anvil
Nov 7 22:06:05 mail postfix/smtpd[18815]: connection established
Nov 7 22:06:05 mail postfix/smtpd[18815]: master_notify: status 0
Nov 7 22:06:05 mail postfix/smtpd[18815]: name_mask: resource
Nov 7 22:06:05 mail postfix/smtpd[18815]: name_mask: software
Nov 7 22:06:05 mail postfix/smtpd[18815]: connect from myDOMAIN[myIP]
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_list_match: myDOMAIN: no
match
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_list_match: myIP: no match
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_list_match: myDOMAIN: no
match
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_list_match: myIP: no match
Nov 7 22:06:05 mail postfix/smtpd[18815]: smtp_stream_setup: maxtime=300
enable_deadline=0
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_hostname: myDOMAIN ~?
127.0.0.0/8
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_hostaddr: myIP ~?
127.0.0.0/8
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_hostname: myDOMAIN ~?
[::ffff:127.0.0.0]/104
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_hostaddr: myIP ~?
[::ffff:127.0.0.0]/104
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_hostname: myDOMAIN ~?
[::1]/128
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_hostaddr: myIP ~? [::1]/128
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_list_match: myDOMAIN: no
match
Nov 7 22:06:05 mail postfix/smtpd[18815]: match_list_match: myIP: no match
Nov 7 22:06:05 mail postfix/smtpd[18815]: auto_clnt_open: connected to
private/anvil
Nov 7 22:06:05 mail postfix/smtpd[18815]: send attr request = connect
Nov 7 22:06:05 mail postfix/smtpd[18815]: send attr ident = submission:myIP
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/anvil: wanted
attribute: status
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: status
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute value: 0
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/anvil: wanted
attribute: count
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: count
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute value: 1
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/anvil: wanted
attribute: rate
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: rate
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute value: 1
Nov 7 22:06:05 mail postfix/smtpd[18815]: private/anvil: wanted
attribute: (list terminator)
Nov 7 22:06:05 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:05 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 220
mail.domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: < myDOMAIN[myIP]: EHLO
[192.168.1.26]
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match: myDOMAIN: no
match
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match: myIP: no match
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]:
250-mail.domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 250-PIPELINING
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 250-SIZE
524288000
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 250-ETRN
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 250-STARTTLS
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]:
250-ENHANCEDSTATUSCODES
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 250-8BITMIME
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 250 DSN
Nov 7 22:06:06 mail postfix/smtpd[18815]: < myDOMAIN[myIP]: STARTTLS
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 220 2.0.0
Ready to start TLS
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr request = seed
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr size = 32
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 0
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: seed
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: seed
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value:
piaBTGtY2+f+X0yj7lbgqpgBottMVuf/6fO+GZ4kDfA=
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: (list terminator)
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr request = tktkey
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr keyname = [data 16
bytes]
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 4294967295
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: keybuf
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: keybuf
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value:
KR6ue9gIDFM5AYyb3VppkA==
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: (list terminator)
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr request = tktkey
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr keyname = [data 0 bytes]
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 0
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: keybuf
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: keybuf
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value:
f+UTVINn9y7TgxmmdQ/KimmbKopZpmtWZF8V2LfhtNxkAQ+KPVGGZUGp82LdmC1nxfMgWAAAAAA=
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/tlsmgr: wanted
attribute: (list terminator)
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: Anonymous TLS connection
established from myDOMAIN[myIP]: TLSv1.2 with cipher
ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)
Nov 7 22:06:06 mail postfix/smtpd[18815]: xsasl_dovecot_server_create:
SASL service=smtp, realm=(null)
Nov 7 22:06:06 mail postfix/smtpd[18815]: name_mask: noanonymous
Nov 7 22:06:06 mail postfix/smtpd[18815]: xsasl_dovecot_server_connect:
Connecting
Nov 7 22:06:06 mail postfix/smtpd[18815]: xsasl_dovecot_server_connect:
auth reply: VERSION?1?1
Nov 7 22:06:06 mail postfix/smtpd[18815]: xsasl_dovecot_server_connect:
auth reply: MECH?PLAIN?plaintext
Nov 7 22:06:06 mail postfix/smtpd[18815]: name_mask: plaintext
Nov 7 22:06:06 mail postfix/smtpd[18815]: xsasl_dovecot_server_connect:
auth reply: MECH?LOGIN?plaintext
Nov 7 22:06:06 mail postfix/smtpd[18815]: name_mask: plaintext
Nov 7 22:06:06 mail postfix/smtpd[18815]: xsasl_dovecot_server_connect:
auth reply: SPID?15347
Nov 7 22:06:06 mail postfix/smtpd[18815]: xsasl_dovecot_server_connect:
auth reply: CUID?6469
Nov 7 22:06:06 mail postfix/smtpd[18815]: xsasl_dovecot_server_connect:
auth reply: COOKIE?8651f5db3a12f5e20316f8501a11b72c
Nov 7 22:06:06 mail postfix/smtpd[18815]: xsasl_dovecot_server_connect:
auth reply: DONE
Nov 7 22:06:06 mail postfix/smtpd[18815]:
xsasl_dovecot_server_mech_filter: keep mechanism: PLAIN
Nov 7 22:06:06 mail postfix/smtpd[18815]:
xsasl_dovecot_server_mech_filter: keep mechanism: LOGIN
Nov 7 22:06:06 mail postfix/smtpd[18815]: < myDOMAIN[myIP]: EHLO
[192.168.1.26]
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match: myDOMAIN: no
match
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match: myIP: no match
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]:
250-mail.domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 250-PIPELINING
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 250-SIZE
524288000
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 250-ETRN
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 250-AUTH
PLAIN LOGIN
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]:
250-AUTH=PLAIN LOGIN
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]:
250-ENHANCEDSTATUSCODES
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 250-8BITMIME
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 250 DSN
Nov 7 22:06:06 mail postfix/smtpd[18815]: < myDOMAIN[myIP]: AUTH PLAIN
AENocmlzdGlhbi5Lb2xlc2FAc2NoYW56ZXItcmFjaW5nLmRlADBWaXBCQUx3eFdWRlZicTZ6dUU3
Nov 7 22:06:06 mail postfix/smtpd[18815]: xsasl_dovecot_server_first:
sasl_method PLAIN, init_response
AENocmlzdGlhbi5Lb2xlc2FAc2NoYW56ZXItcmFjaW5nLmRlADBWaXBCQUx3eFdWRlZicTZ6dUU3
Nov 7 22:06:06 mail postfix/smtpd[18815]: xsasl_dovecot_handle_reply:
auth reply:
OK?1?user=user at domain.tld?home=/var/vmail/domain.tld/user?mail=maildir:/var/vmail/domain.tld/user/Maildir:LAYOUT=fs?uid=5000?gid=5000?quota_rule=*:bytes=536870912?original_user=user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 235 2.7.0
Authentication successful
Nov 7 22:06:06 mail postfix/smtpd[18815]: < myDOMAIN[myIP]: MAIL
FROM:<user at domain.tld> SIZE=2516
Nov 7 22:06:06 mail postfix/smtpd[18815]: extract_addr: input:
<user at domain.tld>
Nov 7 22:06:06 mail postfix/smtpd[18815]: smtpd_check_addr:
addr=user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: connect to subsystem
private/rewrite
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr request = rewrite
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr rule = local
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr address =
user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: flags
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: flags
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 0
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: address
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: address
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value:
user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: (list terminator)
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: rewrite_clnt: local:
user at domain.tld -> user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr request = resolve
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr sender =
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr address =
user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: flags
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: flags
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 0
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: transport
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: transport
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: lmtps
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: nexthop
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: nexthop
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value:
unix:private/dovecot-lmtp
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: recipient
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: recipient
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value:
user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: flags
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: flags
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 1024
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: (list terminator)
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: resolve_clnt: `' ->
`user at domain.tld' -> transp=`lmtps' host=`unix:private/dovecot-lmtp'
rcpt=`user at domain.tld' flags= class=virtual
Nov 7 22:06:06 mail postfix/smtpd[18815]: ctable_locate: install entry
key user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: extract_addr: in:
<user at domain.tld>, result: user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr request = rewrite
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr rule = local
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr address = double-bounce
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: flags
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: flags
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 0
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: address
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: address
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value:
double-bounce at mail.domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: (list terminator)
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: rewrite_clnt: local:
double-bounce -> double-bounce at mail.domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: smtpd_check_rewrite: trying:
permit_inet_interfaces
Nov 7 22:06:06 mail postfix/smtpd[18815]: permit_inet_interfaces:
myDOMAIN myIP
Nov 7 22:06:06 mail postfix/smtpd[18815]: fsspace: .: block size 4096,
blocks free 71224286
Nov 7 22:06:06 mail postfix/smtpd[18815]: smtpd_check_queue: blocks 4096
avail 71224286 min_free 0 msg_size_limit 524288000
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 250 2.1.0 Ok
Nov 7 22:06:06 mail postfix/smtpd[18815]: < myDOMAIN[myIP]: RCPT
TO:<lists at domain.tld>
Nov 7 22:06:06 mail postfix/smtpd[18815]: extract_addr: input:
<lists at domain.tld>
Nov 7 22:06:06 mail postfix/smtpd[18815]: smtpd_check_addr:
addr=lists at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr request = rewrite
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr rule = local
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr address =
lists at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: flags
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: flags
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 0
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: address
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: address
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value:
lists at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: (list terminator)
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: rewrite_clnt: local:
lists at domain.tld -> lists at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr request = resolve
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr sender =
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr address =
lists at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: flags
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: flags
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 0
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: transport
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: transport
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: mailman
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: nexthop
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: nexthop
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: recipient
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: recipient
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value:
lists at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: flags
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: flags
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 1024
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/rewrite socket: wanted
attribute: (list terminator)
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: resolve_clnt: `' ->
`lists at domain.tld' -> transp=`mailman' host=`domain.tld'
rcpt=`lists at domain.tld' flags= class=virtual
Nov 7 22:06:06 mail postfix/smtpd[18815]: ctable_locate: install entry
key lists at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: extract_addr: in:
<lists at domain.tld>, result: lists at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: >>> START Client host
RESTRICTIONS <<<
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=permit_sasl_authenticated
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match:
permit_sasl_authenticated: no match
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=permit_sasl_authenticated status=1
Nov 7 22:06:06 mail postfix/smtpd[18815]: >>> END Client host
RESTRICTIONS <<<
Nov 7 22:06:06 mail postfix/smtpd[18815]: >>> START Sender address
RESTRICTIONS <<<
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=reject_authenticated_sender_login_mismatch
Nov 7 22:06:06 mail postfix/smtpd[18815]: ctable_locate: move existing
entry key user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr request = lookup
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr table =
mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr flags = 16448
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr key = user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 0
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: value
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: value
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value:
user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: (list terminator)
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: dict_proxy_lookup:
table=mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf
flags=lock|fold_fix key=user at domain.tld -> status=0 result=user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: maps_find:
smtpd_sender_login_maps:
proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf(0,lock|fold_fix):
user at domain.tld = user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: mail_addr_find:
user at domain.tld -> user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=reject_authenticated_sender_login_mismatch status=0
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=permit_mynetworks
Nov 7 22:06:06 mail postfix/smtpd[18815]: permit_mynetworks: myDOMAIN myIP
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_hostname: myDOMAIN ~?
127.0.0.0/8
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_hostaddr: myIP ~?
127.0.0.0/8
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_hostname: myDOMAIN ~?
[::ffff:127.0.0.0]/104
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_hostaddr: myIP ~?
[::ffff:127.0.0.0]/104
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_hostname: myDOMAIN ~?
[::1]/128
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_hostaddr: myIP ~? [::1]/128
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match: myDOMAIN: no
match
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match: myIP: no match
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=permit_mynetworks status=0
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=reject_sender_login_mismatch
Nov 7 22:06:06 mail postfix/smtpd[18815]: >>> START Sender address
RESTRICTIONS <<<
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=reject_authenticated_sender_login_mismatch
Nov 7 22:06:06 mail postfix/smtpd[18815]: ctable_locate: leave existing
entry key user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr request = lookup
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr table =
mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr flags = 16448
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr key = user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 0
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: value
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: value
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value:
user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: (list terminator)
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: dict_proxy_lookup:
table=mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf
flags=lock|fold_fix key=user at domain.tld -> status=0 result=user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: maps_find:
smtpd_sender_login_maps:
proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf(0,lock|fold_fix):
user at domain.tld = user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: mail_addr_find:
user at domain.tld -> user at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=reject_authenticated_sender_login_mismatch status=0
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=reject_unauthenticated_sender_login_mismatch
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=reject_unauthenticated_sender_login_mismatch status=0
Nov 7 22:06:06 mail postfix/smtpd[18815]: >>> END Sender address
RESTRICTIONS <<<
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=reject_sender_login_mismatch status=0
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=permit_sasl_authenticated
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match:
permit_sasl_authenticated: no match
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=permit_sasl_authenticated status=1
Nov 7 22:06:06 mail postfix/smtpd[18815]: >>> END Sender address
RESTRICTIONS <<<
Nov 7 22:06:06 mail postfix/smtpd[18815]: >>> START Recipient address
RESTRICTIONS <<<
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=permit_mynetworks
Nov 7 22:06:06 mail postfix/smtpd[18815]: permit_mynetworks: myDOMAIN myIP
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_hostname: myDOMAIN ~?
127.0.0.0/8
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_hostaddr: myIP ~?
127.0.0.0/8
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_hostname: myDOMAIN ~?
[::ffff:127.0.0.0]/104
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_hostaddr: myIP ~?
[::ffff:127.0.0.0]/104
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_hostname: myDOMAIN ~?
[::1]/128
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_hostaddr: myIP ~? [::1]/128
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match: myDOMAIN: no
match
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match: myIP: no match
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=permit_mynetworks status=0
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=permit_sasl_authenticated
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match:
permit_sasl_authenticated: no match
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=permit_sasl_authenticated status=1
Nov 7 22:06:06 mail postfix/smtpd[18815]: >>> END Recipient address
RESTRICTIONS <<<
Nov 7 22:06:06 mail postfix/smtpd[18815]: >>> START Recipient address
RESTRICTIONS <<<
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=permit_sasl_authenticated
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match:
permit_sasl_authenticated: no match
Nov 7 22:06:06 mail postfix/smtpd[18815]: generic_checks:
name=permit_sasl_authenticated status=1
Nov 7 22:06:06 mail postfix/smtpd[18815]: >>> END Recipient address
RESTRICTIONS <<<
Nov 7 22:06:06 mail postfix/smtpd[18815]: >>> CHECKING RECIPIENT MAPS <<<
Nov 7 22:06:06 mail postfix/smtpd[18815]: ctable_locate: move existing
entry key lists at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: maps_find:
recipient_canonical_maps: lists at domain.tld: not found
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_string: domain.tld ~?
mail.domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_string: domain.tld ~?
localhost
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_string: domain.tld ~?
127.0.0.1
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match: domain.tld:
no match
Nov 7 22:06:06 mail postfix/smtpd[18815]: maps_find:
recipient_canonical_maps: @domain.tld: not found
Nov 7 22:06:06 mail postfix/smtpd[18815]: mail_addr_find:
lists at domain.tld -> (not found)
Nov 7 22:06:06 mail postfix/smtpd[18815]: maps_find: canonical_maps:
lists at domain.tld: not found
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_string: domain.tld ~?
mail.domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_string: domain.tld ~?
localhost
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_string: domain.tld ~?
127.0.0.1
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match: domain.tld:
no match
Nov 7 22:06:06 mail postfix/smtpd[18815]: maps_find: canonical_maps:
@domain.tld: not found
Nov 7 22:06:06 mail postfix/smtpd[18815]: mail_addr_find:
lists at domain.tld -> (not found)
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr request = lookup
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr table =
mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr flags = 16448
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr key = lists at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 1
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: value
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: value
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: (list terminator)
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: dict_proxy_lookup:
table=mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf
flags=lock|fold_fix key=lists at domain.tld -> status=1 result=
Nov 7 22:06:06 mail postfix/smtpd[18815]: maps_find: virtual_alias_maps:
lists at domain.tld: not found
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_string: domain.tld ~?
mail.domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_string: domain.tld ~?
localhost
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_string: domain.tld ~?
127.0.0.1
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match: domain.tld:
no match
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr request = lookup
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr table =
mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr flags = 16448
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr key = @domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 1
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: value
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: value
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: (list terminator)
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: dict_proxy_lookup:
table=mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf
flags=lock|fold_fix key=@domain.tld -> status=1 result=
Nov 7 22:06:06 mail postfix/smtpd[18815]: maps_find: virtual_alias_maps:
@domain.tld: not found
Nov 7 22:06:06 mail postfix/smtpd[18815]: mail_addr_find:
lists at domain.tld -> (not found)
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr request = lookup
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr table =
mysql:/etc/postfix/mysql/postfix-mysql-virtual_mailbox_maps.cf
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr flags = 16448
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr key = lists at domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 1
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: value
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: value
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: (list terminator)
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: dict_proxy_lookup:
table=mysql:/etc/postfix/mysql/postfix-mysql-virtual_mailbox_maps.cf
flags=lock|fold_fix key=lists at domain.tld -> status=1 result=
Nov 7 22:06:06 mail postfix/smtpd[18815]: maps_find:
virtual_mailbox_maps: lists at domain.tld: not found
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_string: domain.tld ~?
mail.domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_string: domain.tld ~?
localhost
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_string: domain.tld ~?
127.0.0.1
Nov 7 22:06:06 mail postfix/smtpd[18815]: match_list_match: domain.tld:
no match
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr request = lookup
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr table =
mysql:/etc/postfix/mysql/postfix-mysql-virtual_mailbox_maps.cf
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr flags = 16448
Nov 7 22:06:06 mail postfix/smtpd[18815]: send attr key = @domain.tld
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: status
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: 1
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: value
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: value
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute value: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: private/proxymap socket:
wanted attribute: (list terminator)
Nov 7 22:06:06 mail postfix/smtpd[18815]: input attribute name: (end)
Nov 7 22:06:06 mail postfix/smtpd[18815]: dict_proxy_lookup:
table=mysql:/etc/postfix/mysql/postfix-mysql-virtual_mailbox_maps.cf
flags=lock|fold_fix key=@domain.tld -> status=1 result=
Nov 7 22:06:06 mail postfix/smtpd[18815]: maps_find:
virtual_mailbox_maps: @domain.tld: not found
Nov 7 22:06:06 mail postfix/smtpd[18815]: mail_addr_find:
lists at domain.tld -> (not found)
Nov 7 22:06:06 mail postfix/smtpd[18815]: NOQUEUE: reject: RCPT from
myDOMAIN[myIP]: 550 5.1.1 <lists at domain.tld>: Recipient address
rejected: User unknown in virtual mailbox table; from=<user at domain.tld>
to=<lists at domain.tld> proto=ESMTP helo=<[192.168.1.26]>
Nov 7 22:06:06 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 550 5.1.1
<lists at domain.tld>: Recipient address rejected: User unknown in virtual
mailbox table
Nov 7 22:06:08 mail postfix/smtpd[18815]: < myDOMAIN[myIP]: QUIT
Nov 7 22:06:08 mail postfix/smtpd[18815]: > myDOMAIN[myIP]: 221 2.0.0 Bye


Am 07.11.2016 um 16:00 schrieb Larry Turnbull:
> I would change the MTA from None to Postfix.
>
> Then run the genaliases to generate the list aliases that postfix needs to
> find.
>
> Larry
>
>
> -----Original Message-----
> From: Mailman-Users
> [mailto:mailman-users-bounces+larry=acbradio.org at python.org] On Behalf Of
> Christian
> Sent: Sunday, November 6, 2016 10:06 AM
> To: Mailman-Users at python.org
> Subject: [Mailman-Users] postfix + mailman + mailboxes on the same domain
> and server
>
> Hello,
>
> I'm trying to get the mailing list to work with postfix and I read a lot of
> information about the difficult usage of it.
>
> -> It should be possible for a mailbox user 'user at domain.tld' to send at
> the mailing list 'list at domain.tld'.
>
> The only one I found in the archives that addresses my problem:
>
>
> Actually I always get the same error message:
> /var/log/mail.log
> *************************************************************
> Nov  6 15:50:42 mail postfix/smtpd[757]: connect from IP Nov  6 15:50:43
> mail postfix/smtpd[757]: Anonymous TLS connection established from IP:
> TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256
> (128/128 bits)
> Nov  6 15:50:43 mail postfix/smtpd[757]: NOQUEUE: reject: RCPT from IP:
> 550 5.1.1 <list at domain.tld>: Recipient address rejected: User unknown in
> virtual mailbox table; from=<user at domain.tld> to=<list at domain.tld>
> proto=ESMTP helo=<[local-IP]> Nov  6 15:50:48 mail postfix/smtpd[757]:
> disconnect from IP
> *************************************************************
>
> I hope that my posted configs help you to address the issure.
> The usual comments has been removed.
>
>
> /etc/mailman/mm_cfg.py
> *************************************************************
> from Defaults import *
> MAILMAN_SITE_LIST = 'mailman'
> DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/'
> IMAGE_LOGOS  = '/images/mailman/'
> DEFAULT_EMAIL_HOST = 'domain.tld'
> DEFAULT_URL_HOST   = 'www.domain.tld'
> add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> DEFAULT_SERVER_LANGUAGE = 'de'
> USE_ENVELOPE_SENDER    = 0              # Still used?
> DEFAULT_SEND_REMINDERS = 0
> MTA = None # So that mailman skips aliases generation DEB_LISTMASTER =
> 'postmaster at domain.tld'
> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['domain.tld'] POSTFIX_MAP_CMD =
> '/var/lib/mailman/data/virtual_to_transport'
> *************************************************************
>
> root at mail:/var/lib/mailman/data# ls -l
> insgesamt 64
> -rw-rw-r-- 1 list list  1843 Nov  6 15:07 aliases
> -rw-rw-r-- 1 list list 12288 Nov  6 15:07 aliases.db
> -rw-rw-r-- 1 root list    10 Okt 20 11:48 last_mailman_version
> -rw-r--r-- 1 root list 14100 Sep 15 08:04 sitelist.cfg
> -rw-rw-r-- 1 list list  1606 Nov  6 15:07 transport-mailman
> -rw-r--r-- 1 list list 12288 Nov  6 15:07 transport-mailman.db
> -rw-rw---- 1 root list  1698 Nov  6 15:07 virtual-mailman
> -rwxr-x--- 1 root list   149 Nov  6 15:07 virtual_to_transport
>
> /var/lib/mailman/data/transport-mailman
> *************************************************************
> mailman-loop at domain.tld mailman:
>
> mailman at domain.tld              mailman:
> mailman-admin at domain.tld        mailman:
> mailman-bounces at domain.tld      mailman:
> mailman-confirm at domain.tld      mailman:
> mailman-join at domain.tld         mailman:
> mailman-leave at domain.tld        mailman:
> mailman-owner at domain.tld        mailman:
> mailman-request at domain.tld      mailman:
> mailman-subscribe at domain.tld    mailman:
> mailman-unsubscribe at domain.tld  mailman:
>
> list at domain.tld              mailman:
> list-admin at domain.tld        mailman:
> list-bounces at domain.tld      mailman:
> list-confirm at domain.tld      mailman:
> list-join at domain.tld        mailman:
> list-leave at domain.tld        mailman:
> list-owner at domain.tld        mailman:
> list-request at domain.tld      mailman:
> list-subscribe at domain.tld    mailman:
> list-unsubscribe at domain.tld  mailman:
> *************************************************************
>
> /etc/postfix/master.cf
> *************************************************************
> mailman unix  -       n       n       -       -       pipe
>   flags=FR user=list
>   argv=/var/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user}
> *************************************************************
>
> /etc/postfix/main.cf
> *************************************************************
> smtpd_banner = $myhostname
> biff = no
> append_dot_mydomain = no
> readme_directory = /usr/share/doc/postfix html_directory =
> /usr/share/doc/postfix/html
>
> myhostname = mail.domain.tld
> alias_maps = hash:/etc/aliases
> alias_database = hash:/etc/aliases
> myorigin = mail.domain.tld
> mydestination = mail.domain.tld, localhost relayhost = mynetworks =
> 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mailbox_size_limit = 0
> virtual_mailbox_limit = 0 recipient_delimiter = + inet_interfaces = all
> inet_protocols = ipv4 disable_vrfy_command = yes
>
> smtpd_helo_required = yes
> smtpd_sasl_type=dovecot
> smtpd_sasl_path=private/auth_dovecot
> smtpd_sasl_auth_enable = yes
> smtpd_sasl_authenticated_header = yes
> broken_sasl_auth_clients = yes
>
> proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps
> $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains
> $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps
> $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks
> $smtpd_sender_login_maps virtual_mailbox_base = / virtual_mailbox_domains =
> proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_domains_maps.cf
> virtual_alias_maps =
> proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_alias_maps.cf
> virtual_mailbox_maps =
> proxy:mysql:/etc/postfix/mysql/postfix-mysql-virtual_mailbox_maps.cf
> virtual_minimum_uid = 5000
> virtual_uid_maps = static:5000
> virtual_gid_maps = static:5000
> virtual_transport = lmtps:unix:private/dovecot-lmtp transport_maps =
> hash:/var/lib/mailman/data/transport-mailman,
> mysql:/etc/postfix/mysql/postfix-mysql-virtual_transport_maps.cf
>
> maximal_queue_lifetime = 1d
> bounce_queue_lifetime = 1d
> queue_run_delay = 300s
> maximal_backoff_time = 1800s
> minimal_backoff_time = 300s
> message_size_limit = 524288000
> smtpd_soft_error_limit = 3
> smtpd_error_sleep_time = 10s
> smtpd_hard_error_limit = ${stress?1}${stress:5}
>
> mailman_destination_recipient_limit = 1
> relay_recipient_maps = hash:/var/lib/mailman/data/transport-mailman
> *************************************************************
> The only edit here was in transport_maps and the last both lines.
>
> I don't know which steps in the manuals are important for me and which not.
> Please help me to correct that.
>
> Greetings Christian
>
>
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/larry%40acbradio.org


From startrekcafe at gmail.com  Mon Nov  7 20:51:40 2016
From: startrekcafe at gmail.com (Marvin Hunkin)
Date: Tue, 8 Nov 2016 12:21:40 +1030
Subject: [Mailman-Users] how to set up mailman with gmail and outlook 2010
 for windows 10
Message-ID: <005e01d23962$ab9f0770$02dd1650$@gmail.com>

Hi. a blind computer user using the jaws for windows screen reader from
http://www.freedomscientific.com, and using a Toshiba satellite pro c-50-a
laptop , running windows 10 64 bit, and using 32 bit office 2010 pro. Tried
to post to a mailing list run by mail man, and when I post and set up for
digest, my postings are not getting posted. So is there a step by step guide
to set it up with gmail and outlook 2010, and with mailman, how to do this.

Thanks.

 

Marvin Hunkin

Blind Information Technology Student

 <http://www.upskilled.edu.au> http://www.upskilled.edu.au

 


From mark at msapiro.net  Tue Nov  8 11:29:06 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 8 Nov 2016 08:29:06 -0800
Subject: [Mailman-Users] how to set up mailman with gmail and outlook
 2010 for windows 10
In-Reply-To: <005e01d23962$ab9f0770$02dd1650$@gmail.com>
References: <005e01d23962$ab9f0770$02dd1650$@gmail.com>
Message-ID: <9a813548-59c4-ead1-58dd-b1373911e22d@msapiro.net>

On 11/07/2016 05:51 PM, Marvin Hunkin wrote:
> Hi. a blind computer user using the jaws for windows screen reader from
> http://www.freedomscientific.com, and using a Toshiba satellite pro c-50-a
> laptop , running windows 10 64 bit, and using 32 bit office 2010 pro. Tried
> to post to a mailing list run by mail man, and when I post and set up for
> digest, my postings are not getting posted. So is there a step by step guide
> to set it up with gmail and outlook 2010, and with mailman, how to do this.


The Mailman members manual is at <https://wiki.list.org/x/786442>. There
are links there to other formats as well in case you have difficulty
reading that.

However, there is no specific guide for what you are asking. You need to
contact the list owner to find why your posts are not reaching the list.
If the list posting address is listname at example.com, you should be able
to reach the owner at listname-owner at example.com.

Also note that your post reached this list with no problem, although it
was initially held for moderation because all posts to this list from
new subscribers are held.

Finally, see <https://wiki.list.org/x/4030680> for information on why
gmail users don't see their own list posts, although this only affects
individual messages, not digests.

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

From gerald.niel at gegeweb.eu  Tue Nov  8 12:28:58 2016
From: gerald.niel at gegeweb.eu (=?UTF-8?Q?G=c3=a9rald_Niel?=)
Date: Tue, 8 Nov 2016 18:28:58 +0100
Subject: [Mailman-Users] postfix + mailman + mailboxes on the same
 domain and server
In-Reply-To: <5820F9A4.308@ckol.de>
References: <581F54ED.2000406@ckol.de>
 <031b01d23907$a6642160$f32c6420$@acbradio.org> <5820F9A4.308@ckol.de>
Message-ID: <932fe27d-1138-9278-1aef-b22d2a9869a0@gegeweb.eu>

Hi,

Le 07/11/2016 ? 23:01, Christian a ?crit :
> Thanks I changed it back to Postfix. 'transport-mailman' get's created
> correctly again.
> The error message is still the same.

I've this about mailman on my config (main.cf):

virtual_alias_maps = hash:/usr/local/etc/postfix/virtual_alias, hash:/usr/local/mailman/data/virtual-mailman
                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
alias_maps = hash:/etc/mail/aliases, hash:/usr/local/mailman/data/aliases
                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

alias_database = hash:/etc/mail/aliases, hash:/usr/local/mailman/data/aliases
                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Nothing else. Nothing in transport sections.

And in mm_cfg.py (I've three domains) :

MTA = 'Postfix'

DEFAULT_URL_HOST="listes.gegeweb.org"
DEFAULT_EMAIL_HOST="listes.gegeweb.org"
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('ml.scasb.org', 'ml.scasb.org')
add_virtualhost('listes.grisbi.org','listes.grisbi.org')
POSTFIX_STYLE_VIRTUAL_DOMAINS = [
        'listes.gegeweb.org',
        'listes.grisbi.org',
        'ml.scasb.org',
]

And domains are listed, one per line in the virtual_domains file (in main.cf) :
virtual_alias_domains = /usr/local/etc/postfix/virtual_domains

And I've some aliases configured as destination address on the list's config in the virtual_alias table lilke this :
## Moderators grisbi.admin
## Mailman List Aliases
#
grisbi-admin at listes.grisbi.org          admin at listes.grisbi.org
grisbi-info at listes.grisbi.org           info at listes.grisbi.org

And, make by mailman in data/aliases for the devel at listes.grisbi.org list :

# STANZA START: devel
# CREATED: Fri Jul  6 23:10:51 2012
devel:             "|/usr/local/mailman/mail/mailman post devel"
devel-admin:       "|/usr/local/mailman/mail/mailman admin devel"
devel-bounces:     "|/usr/local/mailman/mail/mailman bounces devel"
devel-confirm:     "|/usr/local/mailman/mail/mailman confirm devel"
devel-join:        "|/usr/local/mailman/mail/mailman join devel"
devel-leave:       "|/usr/local/mailman/mail/mailman leave devel"
devel-owner:       "|/usr/local/mailman/mail/mailman owner devel"
devel-request:     "|/usr/local/mailman/mail/mailman request devel"
devel-subscribe:   "|/usr/local/mailman/mail/mailman subscribe devel"
devel-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe devel"
# STANZA END: devel

And in data/virtual-mailman
# STANZA START: devel
# CREATED: Fri Jul  6 23:10:51 2012
devel at listes.grisbi.org              devel
devel-admin at listes.grisbi.org        devel-admin
devel-bounces at listes.grisbi.org      devel-bounces
devel-confirm at listes.grisbi.org      devel-confirm
devel-join at listes.grisbi.org         devel-join
devel-leave at listes.grisbi.org        devel-leave
devel-owner at listes.grisbi.org        devel-owner
devel-request at listes.grisbi.org      devel-request
devel-subscribe at listes.grisbi.org    devel-subscribe
devel-unsubscribe at listes.grisbi.org  devel-unsubscribe
# STANZA END: devel

This two files, aliases en virtual-mailman and the db are created and updated by mailman without have something to do.

-- 
G?rald Niel
<gerald.niel at gegeweb.eu>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20161108/9fef9445/attachment.sig>

From karl at freefriends.org  Tue Nov  8 16:47:54 2016
From: karl at freefriends.org (Karl Berry)
Date: Tue, 8 Nov 2016 21:47:54 GMT
Subject: [Mailman-Users] automatic decode of base64 text/plain
Message-ID: <201611082147.uA8LlsY7000649@freefriends.org>

Some mailers annoyingly send text/plain parts in base64 encoding, making
grep and all other standard tools ineffective.

I wonder if it would be feasible for mailman to automatically decode
such back into normal text, at least for the archives. Maybe also for
sending out, though clearly that is more intrusive.

I could also imagine this being done at the MTA level, but that seems
even more likely to be too intrusive.

I looked around a bit for methods with no luck.  Any thoughts?  --thanks, karl.

P.S. Here's an example fragment, with a leading "> " to avoid misparsing.

> Content-Type: text/plain; charset="utf-8"
> Content-Transfer-Encoding: base64
> 
> PiBBcmUgeW91IHNheWluZyB0aGF0IEkgbmVlZCB0byBjaGFuZ2UgbXkgcHJvZmlsZT8gDQo+ICAg
> bGFjZSB3aGVyZSB3ZSBjb3VsZA0KPiBkbyBiZXR0ZXI6IHN1cHBvc2UgYSBzY2hlbWUtZnVsbCAo
..

From mark at msapiro.net  Tue Nov  8 17:36:59 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 8 Nov 2016 14:36:59 -0800
Subject: [Mailman-Users] automatic decode of base64 text/plain
In-Reply-To: <201611082147.uA8LlsY7000649@freefriends.org>
References: <201611082147.uA8LlsY7000649@freefriends.org>
Message-ID: <36d97607-2804-4cf7-3eac-94e82016c714@msapiro.net>

On 11/08/2016 01:47 PM, Karl Berry wrote:
> 
> I wonder if it would be feasible for mailman to automatically decode
> such back into normal text, at least for the archives. Maybe also for
> sending out, though clearly that is more intrusive.


Mailman already does this for the archives, at least for a plain text
message body, but not for scrubbed attachments. Do you see cases where
this isn't done?


> I could also imagine this being done at the MTA level, but that seems
> even more likely to be too intrusive.


Neither Mailman nor the MTA can do this for messages to be sent. The
message part is base64 encoded in the first place because it contains or
could contain non-ascii characters (utf-8 in your example fragment)
which can't be included in message parts "on the wire" if the message is
going to be acceptable to all MTAs.

Plus, such recoding would just add one more way in which Mailman would
break DKIM or PGP signatures.

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

From startrekcafe at gmail.com  Tue Nov  8 17:43:05 2016
From: startrekcafe at gmail.com (Marvin Hunkin)
Date: Wed, 9 Nov 2016 09:13:05 +1030
Subject: [Mailman-Users] how to set up mailman with gmail and outlook
 2010 for windows 10
In-Reply-To: <9a813548-59c4-ead1-58dd-b1373911e22d@msapiro.net>
References: <005e01d23962$ab9f0770$02dd1650$@gmail.com>
 <9a813548-59c4-ead1-58dd-b1373911e22d@msapiro.net>
Message-ID: <004801d23a11$7ad57430$70805c90$@gmail.com>

Hi mark, thanks for the links, will take a look.
Thanks.

Marvin Hunkin
Blind Information Technology Student
http://www.upskilled.edu.au

-----Original Message-----
From: Mark Sapiro [mailto:mark at msapiro.net] 
Sent: Wednesday, 9 November 2016 2:59 AM
To: mailman-users at python.org
Subject: Re: [Mailman-Users] how to set up mailman with gmail and outlook
2010 for windows 10

On 11/07/2016 05:51 PM, Marvin Hunkin wrote:
> Hi. a blind computer user using the jaws for windows screen reader 
> from http://www.freedomscientific.com, and using a Toshiba satellite 
> pro c-50-a laptop , running windows 10 64 bit, and using 32 bit office 
> 2010 pro. Tried to post to a mailing list run by mail man, and when I 
> post and set up for digest, my postings are not getting posted. So is 
> there a step by step guide to set it up with gmail and outlook 2010, and
with mailman, how to do this.


The Mailman members manual is at <https://wiki.list.org/x/786442>. There are
links there to other formats as well in case you have difficulty reading
that.

However, there is no specific guide for what you are asking. You need to
contact the list owner to find why your posts are not reaching the list.
If the list posting address is listname at example.com, you should be able to
reach the owner at listname-owner at example.com.

Also note that your post reached this list with no problem, although it was
initially held for moderation because all posts to this list from new
subscribers are held.

Finally, see <https://wiki.list.org/x/4030680> for information on why gmail
users don't see their own list posts, although this only affects individual
messages, not digests.

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



From camelia.botez at weizmann.ac.il  Thu Nov 10 04:41:56 2016
From: camelia.botez at weizmann.ac.il (Camelia Botez)
Date: Thu, 10 Nov 2016 09:41:56 +0000
Subject: [Mailman-Users] new password not saved
Message-ID: <74B33B2DD6D2A148967C7ECBEBF842CF0113E6DAAE@IBWMBX02>

I am trying to reset administrator password for a list using web interface.
Our server works https.
Trying to use on the next login the new password I get error:
Authorization failed.

what shall i do?
thank you

From mark at msapiro.net  Thu Nov 10 09:57:59 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 10 Nov 2016 06:57:59 -0800
Subject: [Mailman-Users] new password not saved
In-Reply-To: <74B33B2DD6D2A148967C7ECBEBF842CF0113E6DAAE@IBWMBX02>
References: <74B33B2DD6D2A148967C7ECBEBF842CF0113E6DAAE@IBWMBX02>
Message-ID: <233e9ea2-2b1e-ab44-9ec3-f599d126b38e@msapiro.net>

On 11/10/2016 01:41 AM, Camelia Botez wrote:
> I am trying to reset administrator password for a list using web interface.
> Our server works https.
> Trying to use on the next login the new password I get error:
> Authorization failed.
> 
> what shall i do?


See <https://wiki.list.org/x/4030602> and steps 2. and 3. at
<https://wiki.list.org/x/4030702>.

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

From luscheina at yahoo.de  Thu Nov 10 13:49:34 2016
From: luscheina at yahoo.de (Christian F Buser)
Date: Thu, 10 Nov 2016 19:49:34 +0100
Subject: [Mailman-Users] Mail delivery gets congested
Message-ID: <20161110194934460995.538536bf@yahoo.de>

Hi all 

We have Mailman 2.1.21 running on a cPanel (58.0.34) installation. Our biggest "regular" list has something over 200 subscribers. 

On September 2, I asked here about a problem that subsciber's email addresses were displayed in the message headers, and you advised me to change the delivery method of Mailman to "Full Personalization". 

Having one this, it seems that Mailman is now having problems to send out the messages within a useful time frame. The porvider told us that SMTP is currently set to accept only 30 messages per individual connection. So with 200 subscribers it would take 7 connections to get out one single message.  I do not know about the time between two connections, but I saw that it takes at least 20 minutes and in several cases has taken more than one out until the messages are out. 

The provider said that he can increase the numnber of messages per connection but thinks that this is also a security issue (spam) and the amount can only be set server-wide (no possibility to make an exception rule for mailing lists). 

What could I do from my side to increase delivery speed? 

Thank you, Christian 

 
-- 
Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland)      
Hilfe fuer Strassenkinder in Ghana: http://www.chance-for-children.org

From cpz at tuunq.com  Thu Nov 10 14:44:48 2016
From: cpz at tuunq.com (Carl Zwanzig)
Date: Thu, 10 Nov 2016 11:44:48 -0800
Subject: [Mailman-Users] Mail delivery gets congested
In-Reply-To: <20161110194934460995.538536bf@yahoo.de>
References: <20161110194934460995.538536bf@yahoo.de>
Message-ID: <cfa62a79-1b4b-c80a-4b5f-27583ef670a1@tuunq.com>

Hi,

On 11/10/2016 10:49 AM, Christian F Buser via Mailman-Users wrote:
> The provider said that he can increase the numnber of messages per
> connection but thinks that this is also a security issue (spam) and the
> amount can only be set server-wide (no possibility to make an exception
> rule for mailing lists).

Is the cpanel instance being hosted by the same provider as the SMTP 
service? If they are, they should be able to trust their own systems and 
allow larger batches of mail per connection (does depend on their email 
setup). (That is- config'd so that my system A accepts all mail from my 
systems B/C/D, but only small batches from anyone else's systems.)

If they're different providers, does the cpanel host have an email gateway 
you can push the outbound mail through?

Later,

z!


From mark at msapiro.net  Thu Nov 10 14:59:04 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 10 Nov 2016 11:59:04 -0800
Subject: [Mailman-Users] Mail delivery gets congested
In-Reply-To: <20161110194934460995.538536bf@yahoo.de>
References: <20161110194934460995.538536bf@yahoo.de>
Message-ID: <18479314-8a9c-2351-2a10-50c2a7175702@msapiro.net>

On 11/10/2016 10:49 AM, Christian F Buser via Mailman-Users wrote:
> 
> On September 2, I asked here about a problem that subsciber's email addresses were displayed in the message headers, and you advised me to change the delivery method of Mailman to "Full Personalization". 

What I said on Sept 2 was:

> change Mailman to send only one recipient per transaction. This can
> be accomplished in multiple ways:
>   a) If personalize is available in Non-Digest options, set it to Yes.
>   b) add
> VERP_DELIVERY_INTERVAL = 1
>      to mm_cfg.py
>   c) add
> SMTP_MAX_RCPTS = 1
>      to mm_cfg.py
> 
> (I recommend b)


See
<https://mail.python.org/pipermail/mailman-users/2016-September/081248.html>.

Note that personalize = Yes is not the same as personalize = Full
Personalization, although they will both solve your address exposure
problem and both have the same effect  on SMTP transactions.

The difference is Full Personalization also changes the To: header of
each delivered message to the recipient's address whereas Yes leaves it
unchanged.


> Having one this, it seems that Mailman is now having problems to send out the messages within a useful time frame. The porvider told us that SMTP is currently set to accept only 30 messages per individual connection. So with 200 subscribers it would take 7 connections to get out one single message.  I do not know about the time between two connections, but I saw that it takes at least 20 minutes and in several cases has taken more than one out until the messages are out. 


Actually the whole point of any of the changes I suggested was to cause
Mailman to send only one recipient per SMTP transaction because your
original issue was apparently due to the MTA adding an Envelope-To:
header with all the transaction's recipients.


> The provider said that he can increase the numnber of messages per connection but thinks that this is also a security issue (spam) and the amount can only be set server-wide (no possibility to make an exception rule for mailing lists). 


That's irrelevant at this point because you are sending to only one
recipient per transaction.

The issue is the MTA is taking too much time to process a transaction
and your SMTPD delivery for 200 recipients has gone from about 7
transactions with about 30 recipients each to 200 transactions with 1
recipient each. You needed to do this because of the MTA's putting all
the transaction's recipients into the Envelope-To: header.


> What could I do from my side to increase delivery speed? 


Set personalize = No to go back to the original issue.

This has to be addressed in the MTA configuration. Only the host can do
that.

There are many cPanel Mailman installations with much bigger lists that
200 members that don't have these issues.

If your host is willing, they can join this list and ask for help here
and we will do our best to help. They may also benefit from
<http://www.exim.org/howto/mailman21.html>, although there are cPanel
specific differences in the Mailman router and transport which are
required for cPanel's virtual domain support. The section at
<http://www.exim.org/howto/mailman21.html#batune> could be useful, and
of course as I suggested in my Sept 2 reply, they can remove the
envelope_to_add option from the mailman transport and quit exposing all
the recipients in an Envelope-To: header (see
<http://www.exim.org/exim-html-current/doc/html/spec_html/ch-message_processing.html#SECID225>
and the envelope_to_add setting at
<http://www.exim.org/exim-html-current/doc/html/spec_html/ch-generic_options_for_transports.html>).

As a list admin with no ability to change the host, you have only the
options of leaving things as they are and tolerating the delivery delay
or going back to personalize = No and tolerating the address exposure.

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

From clement at forumanalogue.fr  Sat Nov 12 15:30:57 2016
From: clement at forumanalogue.fr (=?UTF-8?B?Q2zDqW1lbnQgRsOpdnJpZXI=?=)
Date: Sat, 12 Nov 2016 21:30:57 +0100
Subject: [Mailman-Users] UnpicklingError: bad pickle data
Message-ID: <6690017c-565b-bd23-3a4f-c9d0daaaf463@forumanalogue.fr>

Hello,

I'm trying to access the url to admin email waiting for moderation for
my list staff:
http://mail.forumanalogue.fr/cgi-bin/mailman/admindb/staff
I received the following message:

Bug in Mailman version 2.1.16

We're sorry, we hit a bug!

Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited,
but the webmaster can find this information in the Mailman error logs.

I'm running Ubuntu 16.04, in the log file /var/lob/mailman/error, there is
UnpicklingError: bad pickle data
(see full log below)
I tried check_db staff, but it doesn't return anything. I guess this is
the normal behavior.

I don't know what this error means nor how to fix it.

Thank you in advance for your help. Regards,
Cl?ment



Full log:

Nov 12 20:31:27 2016 admin(18405):
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
admin(18405): [----- Mailman Version: 2.1.16 -----]
admin(18405): [----- Traceback ------]
admin(18405): Traceback (most recent call last):
admin(18405):   File "/var/lib/mailman/scripts/driver", line 117, in
run_main
admin(18405):     main()
admin(18405):   File "/var/lib/mailman/Mailman/Cgi/admindb.py", line
207, in main
admin(18405):     if not mlist.NumRequestsPending():
admin(18405):   File "/var/lib/mailman/Mailman/ListAdmin.py", line 132,
in NumRequestsPending
admin(18405):     self.__opendb()
admin(18405):   File "/var/lib/mailman/Mailman/ListAdmin.py", line 86,
in __opendb
admin(18405):     self.__db = cPickle.load(fp)
admin(18405): UnpicklingError: bad pickle data
admin(18405): [----- Python Information -----]
admin(18405): sys.version     =   2.7.6 (default, Jun 22 2015, 17:58:13)
[GCC 4.8.2]
admin(18405): sys.executable  =   /usr/bin/python
admin(18405): sys.prefix      =   /usr
admin(18405): sys.exec_prefix =   /usr
admin(18405): sys.path        =   ['/var/lib/mailman/pythonlib',
'/var/lib/mailman', '/usr/lib/mailman/scripts', '/var/lib/mailman',
'/usr/lib/python2.7/', '/usr/lib/python2.7/
plat-x86_64-linux-gnu', '/usr/lib/python2.7/lib-tk',
'/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload',
'/usr/lib/python2.7/site-packages']
admin(18405): sys.platform    =   linux2
admin(18405): [----- Environment Variables -----]
admin(18405):   HTTP_REFERER: http://*****r/cgi-bin/mailman/admindb/staff
admin(18405):   CONTEXT_DOCUMENT_ROOT: /usr/lib/cgi-bin/
admin(18405):   SERVER_SOFTWARE: Apache/2.4.7 (Ubuntu)
admin(18405):   CONTEXT_PREFIX: /cgi-bin/
admin(18405):   SERVER_SIGNATURE: <address>Apache/2.4.7 (Ubuntu) Server
at ***** Port 80</address>
admin(18405):
admin(18405):   REQUEST_METHOD: POST
admin(18405):   PATH_INFO: /staff
admin(18405):   SERVER_PROTOCOL: HTTP/1.1
admin(18405):   QUERY_STRING: 
admin(18405):   CONTENT_LENGTH: 37
admin(18405):   HTTP_USER_AGENT: Mozilla/5.0 (X11; Ubuntu; Linux x86_64;
rv:49.0) Gecko/20100101 Firefox/49.0
admin(18405):   HTTP_CONNECTION: keep-alive
admin(18405):   SERVER_NAME: *****
admin(18405):   REMOTE_ADDR: 192.168.1.a
admin(18405):   PATH_TRANSLATED: /var/www/html/staff
admin(18405):   SERVER_PORT: 80
admin(18405):   SERVER_ADDR: 192.168.1.b
admin(18405):   DOCUMENT_ROOT: /var/www/html
admin(18405):   PYTHONPATH: /var/lib/mailman
admin(18405):   SCRIPT_FILENAME: /usr/lib/cgi-bin/mailman/admindb
admin(18405):   SERVER_ADMIN: webmaster at localhost
admin(18405):   HTTP_DNT: 1
admin(18405):   HTTP_HOST: ******
admin(18405):   SCRIPT_NAME: /cgi-bin/mailman/admindb
admin(18405):   HTTP_UPGRADE_INSECURE_REQUESTS: 1
admin(18405):   REQUEST_URI: /cgi-bin/mailman/admindb/staff
admin(18405):   HTTP_ACCEPT:
text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
admin(18405):   GATEWAY_INTERFACE: CGI/1.1
admin(18405):   REMOTE_PORT: 44084
admin(18405):   HTTP_ACCEPT_LANGUAGE: en-US,en;q=0.5
admin(18405):   REQUEST_SCHEME: http
admin(18405):   CONTENT_TYPE: application/x-www-form-urlencoded
admin(18405):   HTTP_ACCEPT_ENCODING: gzip, deflate

From mark at msapiro.net  Sun Nov 13 02:42:07 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 12 Nov 2016 23:42:07 -0800
Subject: [Mailman-Users] UnpicklingError: bad pickle data
In-Reply-To: <6690017c-565b-bd23-3a4f-c9d0daaaf463@forumanalogue.fr>
References: <6690017c-565b-bd23-3a4f-c9d0daaaf463@forumanalogue.fr>
Message-ID: <c6eb8d8c-1805-c86f-8509-864b481ee8f7@msapiro.net>

On 11/12/2016 12:30 PM, Cl?ment F?vrier wrote:
> Hello,
> 
> I'm trying to access the url to admin email waiting for moderation for
> my list staff:
> http://mail.forumanalogue.fr/cgi-bin/mailman/admindb/staff
> I received the following message:
> 
> Bug in Mailman version 2.1.16
...
> I'm running Ubuntu 16.04, in the log file /var/lob/mailman/error, there is
> UnpicklingError: bad pickle data
> (see full log below)
> I tried check_db staff, but it doesn't return anything. I guess this is
> the normal behavior.


check_db only checks the list configuration files lists/staff/config.*


> I don't know what this error means nor how to fix it.


It means the lists/staff/request.pck file is corrupt. This file holds
information about the outstanding moderator requests for the list.

If you just remove the file, it will be recreated in an initialized
state, but you will lose any outstanding requests. These could be held
messages, subscriptions or unsubscriptions.

If you have a backup that's not corrupt, you could restore it, but if it
contains requests that have already been handled, that could be a problem.

If you aren't concerned about held (un)subscription requests, you could
see if there are any data/heldmsg-staff-*.pck files. If not, there are
no held messages for the staff list. If so, you can still delete the
corrupt lists/staff/request.pck file and use the script at
<https://www.msapiro.net/scripts/hold_again> (mirrored at
<https://fog.ccsf.edu/~msapiro/scripts/hold_again>) to reprocess those
messages.

> 
> Full log:
> 
...
> admin(18405):     self.__opendb()
> admin(18405):   File "/var/lib/mailman/Mailman/ListAdmin.py", line 86,
> in __opendb
> admin(18405):     self.__db = cPickle.load(fp)
> admin(18405): UnpicklingError: bad pickle data


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

From clement at forumanalogue.fr  Sun Nov 13 05:29:26 2016
From: clement at forumanalogue.fr (=?UTF-8?B?Q2zDqW1lbnQgRsOpdnJpZXI=?=)
Date: Sun, 13 Nov 2016 11:29:26 +0100
Subject: [Mailman-Users] UnpicklingError: bad pickle data
In-Reply-To: <c6eb8d8c-1805-c86f-8509-864b481ee8f7@msapiro.net>
References: <6690017c-565b-bd23-3a4f-c9d0daaaf463@forumanalogue.fr>
 <c6eb8d8c-1805-c86f-8509-864b481ee8f7@msapiro.net>
Message-ID: <8d573556-14fd-9b63-e90f-f0d6dcdc2431@forumanalogue.fr>

On 11/13/2016 08:42 AM, Mark Sapiro wrote:
> It means the lists/staff/request.pck file is corrupt. This file holds
> information about the outstanding moderator requests for the list.
> 
> If you just remove the file, it will be recreated in an initialized
> state, but you will lose any outstanding requests. These could be held
> messages, subscriptions or unsubscriptions.
> 
> If you have a backup that's not corrupt, you could restore it, but if it
> contains requests that have already been handled, that could be a problem.
> 
> If you aren't concerned about held (un)subscription requests, you could
> see if there are any data/heldmsg-staff-*.pck files. If not, there are
> no held messages for the staff list. If so, you can still delete the
> corrupt lists/staff/request.pck file and use the script at
> <https://www.msapiro.net/scripts/hold_again> (mirrored at
> <https://fog.ccsf.edu/~msapiro/scripts/hold_again>) to reprocess those
> messages.

Great answer! It seems I have this corrupted file for a while since I
don't have a uncorrupted backuped of this file. I had no
(un)subscription and the couple of messages were spams, so I just
removed the request.pck.


Thank you a lot for your answer!
Cl?ment

From cyndi at norwitz.net  Sun Nov 13 17:17:26 2016
From: cyndi at norwitz.net (Cyndi Norwitz)
Date: Sun, 13 Nov 2016 14:17:26 -0800
Subject: [Mailman-Users] Expressions to reduce spam
Message-ID: <4A621402-DB1B-4650-BA56-F0F810ABCC72@norwitz.net>

Hi, I use the "List of non-member addresses whose postings will be automatically discarded? feature a ton.  In the past you have helped me to figure out the correct expressions to use to discard emails from the following:

1) The whole email (no help needed, this one is obvious).
2) Addresses that begin with X.  I say ?^phrase? and that does the trick.
3) Domain names.   I use the method Mark showed me years ago, which is (for example): ^[^@]+@(.*\.)?energydatagroup\.net$
	I was later told there was an easier version of this, but this works and I just cut and paste anyway.

Now I need one more.  Addresses that end in X.  For example, I get TONS of attempted posts to one of my lists from the top level domain top.  They?re 100% spam and the domain names are completely different and random.  Nothing I tried works.  I haven?t kept track of all my attempts so I can?t tell you what they are.  My latest failure is: ^[^@]+@(.*\.)*\.top$

Note that I have researched this and read sites on regular expressions and still could not make heads or tails of it.

If I can get this working, I will be able to eliminate a lot of spam because there are so many that come from fake (or at least not legit) top level domains.  .site, .win, and so on.

Can anyone give me the correct formula?

And can a future update to Mailman give us listowners more tools for this feature?  I shouldn?t have to know regular expressions to be able to get rid of spam.  Apple Mail, for example, lets you choose the type of match it is (starts with, ends with, contains); I have tons of spam direction rules that filter by top level domain (ends with .top).

Thanks!
Cyndi


From Richard at Damon-Family.org  Sun Nov 13 18:15:08 2016
From: Richard at Damon-Family.org (Richard Damon)
Date: Sun, 13 Nov 2016 18:15:08 -0500
Subject: [Mailman-Users] Expressions to reduce spam
In-Reply-To: <4A621402-DB1B-4650-BA56-F0F810ABCC72@norwitz.net>
References: <4A621402-DB1B-4650-BA56-F0F810ABCC72@norwitz.net>
Message-ID: <105a7d5e-210c-bc5d-fab6-54e514efdee3@Damon-Family.org>

On 11/13/16 5:17 PM, Cyndi Norwitz wrote:
> Hi, I use the "List of non-member addresses whose postings will be automatically discarded? feature a ton.  In the past you have helped me to figure out the correct expressions to use to discard emails from the following:
>
> 1) The whole email (no help needed, this one is obvious).
> 2) Addresses that begin with X.  I say ?^phrase? and that does the trick.
> 3) Domain names.   I use the method Mark showed me years ago, which is (for example): ^[^@]+@(.*\.)?energydatagroup\.net$
> 	I was later told there was an easier version of this, but this works and I just cut and paste anyway.
>
> Now I need one more.  Addresses that end in X.  For example, I get TONS of attempted posts to one of my lists from the top level domain top.  They?re 100% spam and the domain names are completely different and random.  Nothing I tried works.  I haven?t kept track of all my attempts so I can?t tell you what they are.  My latest failure is: ^[^@]+@(.*\.)*\.top$
>
> Note that I have researched this and read sites on regular expressions and still could not make heads or tails of it.
>
> If I can get this working, I will be able to eliminate a lot of spam because there are so many that come from fake (or at least not legit) top level domains.  .site, .win, and so on.
>
> Can anyone give me the correct formula?
>
> And can a future update to Mailman give us listowners more tools for this feature?  I shouldn?t have to know regular expressions to be able to get rid of spam.  Apple Mail, for example, lets you choose the type of match it is (starts with, ends with, contains); I have tons of spam direction rules that filter by top level domain (ends with .top).
>
> Thanks!
> Cyndi
If you look at your regex, just replace the energydateagroup with [^@]. 
(There are lots of other ways to do it)

As an alternative, if you look at your example do ea domain and your 
example for begin with you get "\.top$"

Learning regular expressions really shouldn't be that hard, and can be 
important when fighting spam (since that is the way most tools work).


-- 
Richard Damon


From dlj04 at josephson.com  Sun Nov 13 18:08:37 2016
From: dlj04 at josephson.com (D L Josephson)
Date: Sun, 13 Nov 2016 15:08:37 -0800
Subject: [Mailman-Users] Expressions to reduce spam
In-Reply-To: <4A621402-DB1B-4650-BA56-F0F810ABCC72@norwitz.net>
References: <4A621402-DB1B-4650-BA56-F0F810ABCC72@norwitz.net>
Message-ID: <0ce751ee-ce92-bcb0-f7b3-761afac2544d@josephson.com>

On 11/13/16 2:17 PM, Cyndi Norwitz wrote:

> Now I need one more.  Addresses that end in X.  For example, I get
> TONS of attempted posts to one of my lists from the top level domain
> top.  They?re 100% spam and the domain names are completely different
> and random.  Nothing I tried works.  I haven?t kept track of all my
> attempts so I can?t tell you what they are.  My latest failure is:
> ^[^@]+@(.*\.)*\.top$
>

We implement junk-domain filtering ahead of Mailman. No reason to let a 
message get any further in your server than it has to. We use iptables 
to block connections from IP address ranges in countries where we know 
we have no users, and then a minimal spamassassin installation to filter 
top level domains and other 100% junk senders. This makes Mailman's job 
a lot easier.

From larry at qhpress.org  Sun Nov 13 18:57:58 2016
From: larry at qhpress.org (Larry Kuenning)
Date: Sun, 13 Nov 2016 18:57:58 -0500
Subject: [Mailman-Users] Expressions to reduce spam
In-Reply-To: <4A621402-DB1B-4650-BA56-F0F810ABCC72@norwitz.net>
References: <4A621402-DB1B-4650-BA56-F0F810ABCC72@norwitz.net>
Message-ID: <5828FE06.8030504@qhpress.org>

On 11/13/2016 5:17 PM, Cyndi Norwitz wrote:

> My latest failure is: ^[^@]+@(.*\.)*\.top$

It looks like what fails here is that the expression requires two dots 
before "top":  someone at something..top would be caught but not 
someone at something.top.  So try this:

^[^@]+@(.*\.)*top$

Or probably better:

^[^@]+@[^@]+\.top$

-- 
Larry Kuenning
larry at qhpress.org


From mark at msapiro.net  Sun Nov 13 22:55:02 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 13 Nov 2016 19:55:02 -0800
Subject: [Mailman-Users] Expressions to reduce spam
In-Reply-To: <5828FE06.8030504@qhpress.org>
References: <4A621402-DB1B-4650-BA56-F0F810ABCC72@norwitz.net>
 <5828FE06.8030504@qhpress.org>
Message-ID: <f18faf68-4a4f-073e-d30a-f8adbb30c196@msapiro.net>

On 11/13/2016 03:57 PM, Larry Kuenning wrote:
> On 11/13/2016 5:17 PM, Cyndi Norwitz wrote:
> 
>> My latest failure is: ^[^@]+@(.*\.)*\.top$
> 
> It looks like what fails here is that the expression requires two dots
> before "top":  someone at something..top would be caught but not
> someone at something.top.  So try this:
> 
> ^[^@]+@(.*\.)*top$
> 
> Or probably better:
> 
> ^[^@]+@[^@]+\.top$
> 


Or even just

^.*\.top$

Or to get more than one tld with one regexp

*.*\.(site|win|othertop)$

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

From mark at msapiro.net  Sun Nov 13 23:04:30 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 13 Nov 2016 20:04:30 -0800
Subject: [Mailman-Users] Expressions to reduce spam
In-Reply-To: <f18faf68-4a4f-073e-d30a-f8adbb30c196@msapiro.net>
References: <4A621402-DB1B-4650-BA56-F0F810ABCC72@norwitz.net>
 <5828FE06.8030504@qhpress.org>
 <f18faf68-4a4f-073e-d30a-f8adbb30c196@msapiro.net>
Message-ID: <8d1e84e2-1f49-0b48-878e-12f32cc3e6b9@msapiro.net>

On 11/13/2016 07:55 PM, Mark Sapiro wrote:
> 
> Or to get more than one tld with one regexp
> 
> *.*\.(site|win|othertop)$


Ooops. Should be

^.*\.(site|win|othertop)$

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

From geek at uniserve.com  Wed Nov 16 14:17:57 2016
From: geek at uniserve.com (Dave Stevens)
Date: Wed, 16 Nov 2016 11:17:57 -0800
Subject: [Mailman-Users] subscribe to mailman for someone else
Message-ID: <20161116111757.74905n8u995eyep1@webmail.uniserve.com>

I have a web form that gathers user data, including their email  
address for the purpose of, among other things, subscribing them to a  
mailman list. I don't see how to do this. Is it possible? This is for  
people who already want to be on the list. Confirmation as usual to  
the new subscriber. Mailman 2.1.16

Dave


-- 
"As long as politics is the shadow cast on society by big business,
the attenuation of the shadow will not change the substance."

-- John Dewey






From mark at msapiro.net  Wed Nov 16 15:49:34 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 16 Nov 2016 12:49:34 -0800
Subject: [Mailman-Users] subscribe to mailman for someone else
In-Reply-To: <20161116111757.74905n8u995eyep1@webmail.uniserve.com>
References: <20161116111757.74905n8u995eyep1@webmail.uniserve.com>
Message-ID: <8fe41b23-0f07-c05c-8594-647b0576784b@msapiro.net>

On 11/16/2016 11:17 AM, Dave Stevens wrote:
> I have a web form that gathers user data, including their email address
> for the purpose of, among other things, subscribing them to a mailman
> list. I don't see how to do this. Is it possible? This is for people who
> already want to be on the list. Confirmation as usual to the new
> subscriber. Mailman 2.1.16


It's difficult to answer without knowing how you do subscribes, but if
you do them by email commands, you can send a message to
LISTNAME-request at example.com with the command

subscribe [password] [digest|nodigest] [address=<address>]

  Subscribe to this mailing list.  Your password must be given to
  unsubscribe or change your options, but if you omit the password, one
  will be generated for you.  You may be periodically reminded of your
  password.

  The next argument may be either: `nodigest' or `digest' (no quotes!).
  If you wish to subscribe an address other than the address you sent
  this request from, you may specify `address=<address>' (no brackets
  around the email address, and no quotes!)

And, there are various web ways to do it. See
<https://wiki.list.org/x/4030648>.

If this isn't what you're looking for, blease be more specific as to how
you want to do this.

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

From geek at uniserve.com  Wed Nov 16 16:44:06 2016
From: geek at uniserve.com (Dave Stevens)
Date: Wed, 16 Nov 2016 13:44:06 -0800
Subject: [Mailman-Users] subscribe to mailman for someone else
In-Reply-To: <8fe41b23-0f07-c05c-8594-647b0576784b@msapiro.net>
References: <20161116111757.74905n8u995eyep1@webmail.uniserve.com>
 <8fe41b23-0f07-c05c-8594-647b0576784b@msapiro.net>
Message-ID: <20161116134406.4f5d6176@user-Satellite-A100>

On Wed, 16 Nov 2016 12:49:34 -0800
Mark Sapiro <mark at msapiro.net> wrote:

> On 11/16/2016 11:17 AM, Dave Stevens wrote:
> > I have a web form that gathers user data, including their email
> > address for the purpose of, among other things, subscribing them to
> > a mailman list. I don't see how to do this. Is it possible? This is
> > for people who already want to be on the list. Confirmation as
> > usual to the new subscriber. Mailman 2.1.16  
> 
> 
> It's difficult to answer without knowing how you do subscribes, but if
> you do them by email commands, you can send a message to
> LISTNAME-request at example.com with the command
> 
> subscribe [password] [digest|nodigest] [address=<address>]
> 
>   Subscribe to this mailing list.  Your password must be given to
>   unsubscribe or change your options, but if you omit the password,
> one will be generated for you.  You may be periodically reminded of
> your password.
> 
>   The next argument may be either: `nodigest' or `digest' (no
> quotes!). If you wish to subscribe an address other than the address
> you sent this request from, you may specify `address=<address>' (no
> brackets around the email address, and no quotes!)
> 
> And, there are various web ways to do it. See
> <https://wiki.list.org/x/4030648>.
> 
> If this isn't what you're looking for, blease be more specific as to
> how you want to do this.

sorry not to have been more specific Mark, but what you say is in fact
very close and may be what I want, I'll need to do a test. When you say
above send a message with the command, where is the command? in the
subject line? or body?

Dave

> 



-- 
Reporter to Mahatma Ghandi after his tour of east London
"What do you think of western civilization, Mr. Ghandi?"
Ghandi - "I think it would be an excellent idea!"


From mark at msapiro.net  Wed Nov 16 17:40:04 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 16 Nov 2016 14:40:04 -0800
Subject: [Mailman-Users] subscribe to mailman for someone else
In-Reply-To: <20161116134406.4f5d6176@user-Satellite-A100>
References: <20161116111757.74905n8u995eyep1@webmail.uniserve.com>
 <8fe41b23-0f07-c05c-8594-647b0576784b@msapiro.net>
 <20161116134406.4f5d6176@user-Satellite-A100>
Message-ID: <0bd1ea13-364c-c960-b935-ed2850e6df54@msapiro.net>

On 11/16/2016 01:44 PM, Dave Stevens wrote:
> 
> sorry not to have been more specific Mark, but what you say is in fact
> very close and may be what I want, I'll need to do a test. When you say
> above send a message with the command, where is the command? in the
> subject line? or body?


Either one.

Mail sent to the LISTNAME-request address is processed as follows:

If the Subject: contains a valid command or a valid command preceded by
a single 'word' such as Re:, Fwd:, etc., that command is processed.
Otherwise the Subject: is ignored.

Then, regardless of the Subject:, Mailman continues to process body
lines from the first text/plain part in the message as commands until
one of the following occurs:

1) a non-blank line does not contain a valid command or
2) an 'end' command is processed or
3) a total of DEFAULT_MAIL_COMMANDS_MAX_LINES (default = 25) including
   blank lines is seen or
4) the end of the message part is reached.

Thus, with the default DEFAULT_MAIL_COMMANDS_MAX_LINES = 25 not
overridden in mm_cfg.py, you could send up to 26 subscribe commands, one
in the Subject: and 25 in the body, in one message.

Send a 'help' command to the LISTNAME-request address for more info on
email commands.

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

From geek at uniserve.com  Wed Nov 16 17:48:44 2016
From: geek at uniserve.com (Dave Stevens)
Date: Wed, 16 Nov 2016 14:48:44 -0800
Subject: [Mailman-Users] subscribe to mailman for someone else
In-Reply-To: <0bd1ea13-364c-c960-b935-ed2850e6df54@msapiro.net>
References: <20161116111757.74905n8u995eyep1@webmail.uniserve.com>
 <8fe41b23-0f07-c05c-8594-647b0576784b@msapiro.net>
 <20161116134406.4f5d6176@user-Satellite-A100>
 <0bd1ea13-364c-c960-b935-ed2850e6df54@msapiro.net>
Message-ID: <20161116144844.139331okb3u2gtak@webmail.uniserve.com>

Quoting Mark Sapiro <mark at msapiro.net>:

> On 11/16/2016 01:44 PM, Dave Stevens wrote:
>>
>> sorry not to have been more specific Mark, but what you say is in fact
>> very close and may be what I want, I'll need to do a test. When you say
>> above send a message with the command, where is the command? in the
>> subject line? or body?
>
>
> Either one.
>
> Mail sent to the LISTNAME-request address is processed as follows:
>
> If the Subject: contains a valid command or a valid command preceded by
> a single 'word' such as Re:, Fwd:, etc., that command is processed.
> Otherwise the Subject: is ignored.
>
> Then, regardless of the Subject:, Mailman continues to process body
> lines from the first text/plain part in the message as commands until
> one of the following occurs:
>
> 1) a non-blank line does not contain a valid command or
> 2) an 'end' command is processed or
> 3) a total of DEFAULT_MAIL_COMMANDS_MAX_LINES (default = 25) including
>    blank lines is seen or
> 4) the end of the message part is reached.
>
> Thus, with the default DEFAULT_MAIL_COMMANDS_MAX_LINES = 25 not
> overridden in mm_cfg.py, you could send up to 26 subscribe commands, one
> in the Subject: and 25 in the body, in one message.
>
> Send a 'help' command to the LISTNAME-request address for more info on
> email commands.

will do, thanks very much!

d

>
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/geek%40uniserve.com
>



-- 
"As long as politics is the shadow cast on society by big business,
the attenuation of the shadow will not change the substance."

-- John Dewey






From raimue at codingfarm.de  Fri Nov 18 09:22:24 2016
From: raimue at codingfarm.de (=?UTF-8?Q?Rainer_M=c3=bcller?=)
Date: Fri, 18 Nov 2016 15:22:24 +0100
Subject: [Mailman-Users] Regenerate HTML pages for new URLs in pipermail
Message-ID: <f572978b-54ce-9560-30a5-02e653b9ca27@codingfarm.de>

Hello,

I recently moved a Mailman mailing list from one host to another as
outlined in the FAQ [1]. This involved changing the URL of the archives
on the web. Mail delivery and the web interface itself is working just fine.

However, every old mail in the HTML archive of pipermail still contains
the old URL at the very end in the "More information about the ...
mailing list" link. For new mails, the URL is correct.

I already tried to regenerate the archive with 'arch --wipe'. This would
update the URL, however, this would also re-index the mbox and will
break URLs to posts in the archive, which I would like to avoid.

Is there some way to update this URL while keeping the archive URLs
stable? Do I really need to go over all HTML files in the archive with a
sed expression?

Running Mailman 2.1.18 on Debian 8 jessie.

Rainer

[1]
https://wiki.list.org/DOC/How%20do%20I%20move%20a%20list%20to%20a%20different%20server-Mailman%20installation.

From sandy.8925 at gmail.com  Thu Nov 17 11:37:03 2016
From: sandy.8925 at gmail.com (Sandeep)
Date: Thu, 17 Nov 2016 16:37:03 +0000
Subject: [Mailman-Users] Digest option - only get 1 email for all posts in a
 day?
Message-ID: <CAGPDPzC0K1dO+0iTb0Kv0B-+-jabXyj9g=PWBybkeoFAZa8yug@mail.gmail.com>

Hello,

It appears that digest mode only batches a set number of emails together
(5) in a single digest. So, if a mailing list I am subscribed to, gets 20
posts in a day, I get 4 emails. Is there a way for me as a subscriber to
get 1 digest email per day, containing all the posts for that day?

Yours sincerely,
Sandeep

From mark at msapiro.net  Fri Nov 18 12:07:14 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 18 Nov 2016 09:07:14 -0800
Subject: [Mailman-Users] Digest option - only get 1 email for all posts
 in a day?
In-Reply-To: <CAGPDPzC0K1dO+0iTb0Kv0B-+-jabXyj9g=PWBybkeoFAZa8yug@mail.gmail.com>
References: <CAGPDPzC0K1dO+0iTb0Kv0B-+-jabXyj9g=PWBybkeoFAZa8yug@mail.gmail.com>
Message-ID: <8397b191-4676-7fce-782f-f836d6643d3c@msapiro.net>

On 11/17/2016 08:37 AM, Sandeep wrote:
> 
> It appears that digest mode only batches a set number of emails together
> (5) in a single digest. So, if a mailing list I am subscribed to, gets 20
> posts in a day, I get 4 emails. Is there a way for me as a subscriber to
> get 1 digest email per day, containing all the posts for that day?


As a list member, there's nothing you can do to affect when digests are
sent.

Digests are never sent based on the number of messages they contain.
They are sent periodically (default daily) and/or when they reach a
certain size (number of Kbytes, not number of messages).

The list admin can control both the size and the periodic sending
through these settings:

How big in Kb should a digest be before it gets sent out? 0 implies no
maximum size.
(Edit digest_size_threshhold)

Should a digest be dispatched daily when the size threshold isn't reached?
(Edit digest_send_periodic)

The periodic (daily) sending is done by a cron job so the frequency and
timing of the periodic digest is controlled by the site admins. It
defaults to noon daily (server local time).

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

From mark at msapiro.net  Fri Nov 18 12:27:09 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 18 Nov 2016 09:27:09 -0800
Subject: [Mailman-Users] Regenerate HTML pages for new URLs in pipermail
In-Reply-To: <f572978b-54ce-9560-30a5-02e653b9ca27@codingfarm.de>
References: <f572978b-54ce-9560-30a5-02e653b9ca27@codingfarm.de>
Message-ID: <296f176d-fe68-6340-01b9-4c4ab9c8a72c@msapiro.net>

On 11/18/2016 06:22 AM, Rainer M?ller wrote:
> 
> However, every old mail in the HTML archive of pipermail still contains
> the old URL at the very end in the "More information about the ...
> mailing list" link. For new mails, the URL is correct.
> 
> I already tried to regenerate the archive with 'arch --wipe'. This would
> update the URL, however, this would also re-index the mbox and will
> break URLs to posts in the archive, which I would like to avoid.


If the listinfo URL has changed, Other saved URLs to archived messages
are probably already broken :(


> Is there some way to update this URL while keeping the archive URLs
> stable?


If the cumulative archives/private/listname.mbox/listname.mbox has not
been manually modified, and it contains no spurious unescaped "^From "
lines in message bodies (see bin/cleanarch and maybe
<https://www.msapiro.net/scripts/check_arch>), rebuilding the archive
with 'bin/arch --wipe' should not change the archived message numbers.


> Do I really need to go over all HTML files in the archive with a
> sed expression?


Yes. The only way to fix the listinfo URLs in the HTML archive without
running 'bin/arch --wipe' is to creat a script to do the editing on all
the files.

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

From phirayam at fredhutch.org  Fri Nov 18 12:42:41 2016
From: phirayam at fredhutch.org (Hirayama, Pat)
Date: Fri, 18 Nov 2016 17:42:41 +0000
Subject: [Mailman-Users] Mailman and Mimecast
Message-ID: <AE5F7147890F3544BFCDB1594A4329C9ECBA05F4@adama.fhcrc.org>

Greetings,

I am having issues with some addresses on a couple of the few thousand lists that I am hosting in mailman.  The addresses in question are using Mimecast for their email protection.  So, I'm asking all of you for your opinion/advice.  

Problem 1:  One list gets their email rejected with a 550 Rejected by header based Anti-Spoofing policy: ... https://community.mimecast.com/docs/DOC-1369#550

If I am reading the referenced (https://community.mimecast.com/docs/DOC-1419-anti-spoofing-policies) page correctly, the problem is that the sender of the list is at domain A, the recipients of the lists are at domain A, but the listserv itself is in domain B, and from Mimecast's POV, there shouldn't be mail from A to A being relayed by B.  And then it goes on to say that you should reconfigure your Mimecast to put in a bypass policy for this server. 

What the mail folks at domain A would prefer is that I (domain B) fix this.  I'm thinking that I could fix this by using either anonymous_list or changing the setting of from_is_list.  But, what isn't clear to me is if this is really the correct step to take (my initial inclination is that they should follow Mimecast's direction of putting in a bypass policy).  

Problem 2:  Another list I have -- they actually accept the mail, and then send it back.  So, I see status=sent in my postfix logs, but the members don't get it.  Apparently, it is running into a problem because the HELO greeting from my mail gateways (MX) doesn't match the FQDN of the mailman server.  

So, the mailman server is smarthosted to my MX servers, which do some scanning of the message before sending it out.  Apparently, what these Mimecast users want me to do is to rewrite the envelope so that instead of the mailman server's FQDN, I replace it with either the FQDN of the MX server, or just my domain.  

In the /etc/aliases file on my MX servers, I have the 'post' address listed, so mail sent to listname at domain gets routed to the mailman server.  I haven't listed any of the other 9 mailman addresses (i.e. -admin, -bounces, -confirm, -join, -leave, -owner, -request, -subscribe, -unsubscribe).  So, my thinking is that if I do the rewrite, so the message comes from listname-bounces at domain, instead of listname-bounces at lists.domain, I will need to add this and the other addresses on my MX server so that mail routing will work. Since I have 3000+ lists, that's like 27k more lines in /etc/aliases to add/manage.  

Again, I'm thinking that they should put in some exception in their Mimecast configuration. 

Am I just being obstinate here for no reason?  Should I just assume the pain and change the behavior of my mailman server?  Thoughts?

Thanks!

				-p
--
Pat Hirayama
Systems Engineer / 206.667.4856 / phirayam at fredhutch.org / Fred Hutch / Cures Start Here 
CIT | Advancing IT and Data Services to Accelerate the Elimination of Disease



From mark at msapiro.net  Fri Nov 18 16:02:48 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 18 Nov 2016 13:02:48 -0800
Subject: [Mailman-Users] Mailman and Mimecast
In-Reply-To: <AE5F7147890F3544BFCDB1594A4329C9ECBA05F4@adama.fhcrc.org>
References: <AE5F7147890F3544BFCDB1594A4329C9ECBA05F4@adama.fhcrc.org>
Message-ID: <dc3d7cc9-71a2-2b6d-4086-9ec183ca1e2f@msapiro.net>

On 11/18/2016 09:42 AM, Hirayama, Pat wrote:
> 
> Problem 1:  One list gets their email rejected with a 550 Rejected by
> header based Anti-Spoofing policy: ...
> https://community.mimecast.com/docs/DOC-1369#550
> 
> If I am reading the referenced
> (https://community.mimecast.com/docs/DOC-1419-anti-spoofing-policies)
> page correctly, the problem is that the sender of the list is at
> domain A, the recipients of the lists are at domain A, but the
> listserv itself is in domain B, and from Mimecast's POV, there
> shouldn't be mail from A to A being relayed by B.  And then it goes
> on to say that you should reconfigure your Mimecast to put in a
> bypass policy for this server.


There is a generic problem here. It is that various entities try to
enforce various anti-spam, anti-spoofing, anti-phishing measures without
considering a) how effective their measures will really be and b) the
adverse effects on mailing lists and other types of mail forwarding.


> What the mail folks at domain A would prefer is that I (domain B) fix
> this.  I'm thinking that I could fix this by using either
> anonymous_list or changing the setting of from_is_list.  But, what
> isn't clear to me is if this is really the correct step to take (my
> initial inclination is that they should follow Mimecast's direction
> of putting in a bypass policy).


I agree with you. They (domain A) have put policies in place that
negatively impact their users and are asking you to change your behavior
to mitigate the impacts on their users instead of doing what Mimecast
suggests.

However, getting them to see the light and behave responsibly to their
users may be futile.

I wouldn't use anonymous_list for this, because it really makes your
list anonymous which is not something most list's want.

You can use from_is_list, but there is another issue with that. Various
Microsoft services have started adding "spoofing" warnings to received
messages which are both To: and From: the same address. This will be the
case with most from_is_list = Munge From or Wrap Message messages unless
you also enable Full personalization for the list.

It is probably only a matter of time before this "spoofing" test becomes
more widespread and results in message rejection rather than just
addition of a warning.


> Problem 2:  Another list I have -- they actually accept the mail, and
> then send it back.  So, I see status=sent in my postfix logs, but the
> members don't get it.  Apparently, it is running into a problem
> because the HELO greeting from my mail gateways (MX) doesn't match
> the FQDN of the mailman server.
> 
> So, the mailman server is smarthosted to my MX servers, which do some
> scanning of the message before sending it out.  Apparently, what
> these Mimecast users want me to do is to rewrite the envelope so that
> instead of the mailman server's FQDN, I replace it with either the
> FQDN of the MX server, or just my domain.


The envelope sender needs to be LISTNAME-bounces at maillist.domain or in
the VERP case, LISTNAME-bounces+user=users.domain at maillist.domain for
Mailman's bounce processing to work, and these addresses need to be
deliverable.


> In the /etc/aliases file on my MX servers, I have the 'post' address
> listed, so mail sent to listname at domain gets routed to the mailman
> server.  I haven't listed any of the other 9 mailman addresses (i.e.
> -admin, -bounces, -confirm, -join, -leave, -owner, -request,
> -subscribe, -unsubscribe).  So, my thinking is that if I do the
> rewrite, so the message comes from listname-bounces at domain, instead
> of listname-bounces at lists.domain, I will need to add this and the
> other addresses on my MX server so that mail routing will work. Since
> I have 3000+ lists, that's like 27k more lines in /etc/aliases to
> add/manage.


So are you saying that currently the other LISTNAME-xxx@ addresses are
undeliverable or what?

I'm having trouble understanding the configuration.

As I said above, if bounce processing is going to work, mail to
LISTNAME-bounces at maillist.domain must be deliverable.

The -admin address is a historical artifact and you don't need it, byt
the other -xxx addresses are all documented and should work.

If they do work by direct delivery to the Mailman server, then maybe all
is OK in that respect.

I'm having difficulty in wrapping my head around this.

I'm now thinking that Mailman thinks it's email domain is what you are
calling lists.domain and that mail to that domain goes directly to the
Mailman server. If so, that's good so far.

Then you have aliases in the MX for 'domain' so mail to LIST at domain gets
relayed to Mailman for 'convenience.

So if that's all correct, the issue is the mail is not delivered because
the outgoing smarthost identifies itself as 'domain' in HELO/EHLO and
the envelope is from a sub-domain lists.domain.


> Again, I'm thinking that they should put in some exception in their
> Mimecast configuration.


If my understanding above is correct, my mind boggles at the stupidity
of rejecting mail because the envelope sender domain is a sub-domain of
the HELO/EHLO domain.

I have an MX which sends mail with envelopes from various virtual
domains that aren't the MXs canonical domain. This is supposed to work.


> Am I just being obstinate here for no reason?  Should I just assume
> the pain and change the behavior of my mailman server?  Thoughts?


I agree that "they" not you should change, but getting them to is
another issue. What you do depends on how badly you want this mail
delivered.

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

From turnbull.stephen.fw at u.tsukuba.ac.jp  Sat Nov 19 11:31:28 2016
From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Sun, 20 Nov 2016 01:31:28 +0900
Subject: [Mailman-Users] Mailman and Mimecast
In-Reply-To: <dc3d7cc9-71a2-2b6d-4086-9ec183ca1e2f@msapiro.net>
References: <AE5F7147890F3544BFCDB1594A4329C9ECBA05F4@adama.fhcrc.org>
 <dc3d7cc9-71a2-2b6d-4086-9ec183ca1e2f@msapiro.net>
Message-ID: <22576.32352.385681.29613@turnbull.sk.tsukuba.ac.jp>

Mark Sapiro writes:
 > On 11/18/2016 09:42 AM, Hirayama, Pat wrote:

 > > Problem 1:  One list gets their email rejected with a 550 Rejected by
 > > header based Anti-Spoofing policy: ...
 > > https://community.mimecast.com/docs/DOC-1369#550
 > > 
 > > If I am reading the referenced
 > > (https://community.mimecast.com/docs/DOC-1419-anti-spoofing-policies)
 > > page correctly, the problem is that the sender of the list is at
 > > domain A, the recipients of the lists are at domain A, but the
 > > listserv itself is in domain B, and from Mimecast's POV, there
 > > shouldn't be mail from A to A being relayed by B.  And then it goes
 > > on to say that you should reconfigure your Mimecast to put in a
 > > bypass policy for this server.

This is the approach most in the interest of the mail recipients.
However, it is somewhat problematic to configure a bypass, because
many domains that host mailing lists also host ordinary users.  Any of
those users could be a spam source.  On the other hand, it's rather
unlikely that mailing list hosts will be spam sources in this way (the
well-known best practice is to filter outgoing personal mail for spam,
and list hosts are fairly likely to implement that practice).
Furthermore, there is currently an Internet Draft proposal called
Authenticated Received Chain (ARC) to help authenticate such
bypasses.  The ARC signature would only be on mailing list traffic, so
the recipient can distinguish ARC mail from ordinary personal mail.

Unfortunately, many admins would prefer to drop legitimate mail in
quantity rather than risk a spam incident.

 > > What the mail folks at domain A would prefer is that I (domain B) fix
 > > this.

*You* can't *fix* it.  Only they can.  You can install workarounds,
but once you swallow the principle, you are at their mercy.  Any time
they change their filtering policy, you may be asked to adjust.

 > They (domain A) have put policies in place that negatively impact
 > their users and are asking you to change your behavior to mitigate
 > the impacts on their users instead of doing what Mimecast suggests.

Right.  They basically have abdicated responsibility for reliable
delivery of their users' mail, in favor of an infinitesimal
improvement in malmail rejection rates.

 > However, getting them to see the light and behave responsibly to their
 > users may be futile.

Indeed.  Since the facts don't reflect well on them, they're likely to
deny that they're doing anything that adversely affects their users,
and blame you.

Unfortunately, it doesn't help to go to the users, either.  They don't
understand the technology, are willing to believe in magic, and
yelling at you is a lot less disruptive to their lives than changing
email providers.

 > > Problem 2:  Another list I have -- they actually accept the mail, and
 > > then send it back.  So, I see status=sent in my postfix logs, but the
 > > members don't get it.  Apparently, it is running into a problem
 > > because the HELO greeting from my mail gateways (MX) doesn't match
 > > the FQDN of the mailman server.

That is really broken.  There must be another factor involved, because
smarthosting is very common, and presumably the same problem would
arise with virtual hosting in many configurations.  In the absence of
another protocol, HELO should validate against the IP address of the
gateway, and that's all.  What's worse, AIUI the envelope from is a
mailbox at the Mailman server, so the MTA should be able to reject at
the MAIL FROM command if HELO != MAIL FROM is really the problem.

I suspect you can fix this at your end by providing an SPF record
saying that your MX's IP is an authorized source for mail apparently
from your list-host domain.  If you already have such an SPF record,
then the Mimecast system[1] is really broken.

 > I'm now thinking that Mailman thinks it's email domain is what you are
 > calling lists.domain and that mail to that domain goes directly to the
 > Mailman server. If so, that's good so far.
 > 
 > Then you have aliases in the MX for 'domain' so mail to LIST at domain gets
 > relayed to Mailman for 'convenience.

I don't see how the above would be relevant, since it's not visible to
the Mimecast system.

 > > Am I just being obstinate here for no reason?

No, you may have some configuration problems you could and should fix,
but you haven't mentioned any yet that I can see.  The requirements
that Mimecast places on incoming mail are far more strict than
anything in the RFCs.  It's their responsibility to own up to their
users that that is the case.

 > > Should I just assume the pain and change the behavior of my
 > > mailman server?  Thoughts?

 > I agree that "they" not you should change, but getting them to is
 > another issue. What you do depends on how badly you want this mail
 > delivered.

Indeed.

"Just" assume, no.  Admins who install Mimecast have a legitimate
interest in reducing the spam received by their users.  However, they
are trying to impose much of the cost on innocent third parties like
you.  You may wish to absorb that cost, but IMHO you have the right
to protest it.

You may wish to raise price of subscription in some way (including the
option of raising prices for those subscribers affected by Mimecast
only!)  You could start a Kickstarter project to compensate you for
the effort (and suggest that their mail provider do the paying, not
them ;-).  Or you could just no-mail their subscriptions and tell them
to subscribe from another address.  (That's what my employer, the
Japanese Ministry of Education, did in response to the DMARC fiasco of
2014 -- ironically, yahoo.co.jp is the only yahoo.* domain that
doesn't publish the problematic p=reject DMARC policy!)

Note that Mimecast sites are also imposing costs on their own users,
since there is no way for mail sources to see Mimecast's upraised
middle finger.  Mail sources don't find out about these policies until
the recipients have already lost mail.


Footnotes: 
[1]  "Mimecast system" refers to the host, operating system, and
configuration running Mimecast, not to Mimecast itself.  I don't know
enough about Mimecast to criticize it.


From raimue at codingfarm.de  Mon Nov 21 08:27:50 2016
From: raimue at codingfarm.de (=?UTF-8?Q?Rainer_M=c3=bcller?=)
Date: Mon, 21 Nov 2016 14:27:50 +0100
Subject: [Mailman-Users] Regenerate HTML pages for new URLs in pipermail
In-Reply-To: <296f176d-fe68-6340-01b9-4c4ab9c8a72c@msapiro.net>
References: <f572978b-54ce-9560-30a5-02e653b9ca27@codingfarm.de>
 <296f176d-fe68-6340-01b9-4c4ab9c8a72c@msapiro.net>
Message-ID: <d09a0ba0-d68c-c13f-777e-631b500700a9@codingfarm.de>

On 2016-11-18 18:27, Mark Sapiro wrote:
> If the listinfo URL has changed, Other saved URLs to archived messages
> are probably already broken :(

There are redirects from the old listinfo URL to the new one, so that
should work for the time being. I just do not want to spread any more
links to the old URLs.

> If the cumulative archives/private/listname.mbox/listname.mbox has not
> been manually modified, and it contains no spurious unescaped "^From "
> lines in message bodies (see bin/cleanarch and maybe
> <https://www.msapiro.net/scripts/check_arch>), rebuilding the archive
> with 'bin/arch --wipe' should not change the archived message numbers.

Thank you for the hint. I checked that the mbox file itself is clean.
However, with the help of the check_arch script I could determine that
the mbox contains mails without corresponding HTML output files in the
archive. That caused the sequence numbers in the mbox and the HTML files
to be out of sync. As I took this over from others and this happened
years ago without anyone noticing, I have no idea what went wrong at
this point.

Based on this I will keep the old (corrupted) archive as a read-only
copy at a different URL, with redirects from the old archive URLs
pointing to this. Then I can start fresh with a proper archive from the
existing mbox files.

Thank you for the assistance,
Rainer

From mark at mailmanlists.net  Mon Nov 21 02:37:20 2016
From: mark at mailmanlists.net (Mark Dale)
Date: Mon, 21 Nov 2016 18:37:20 +1100
Subject: [Mailman-Users] list_members when listname has a period
Message-ID: <10e677c3-0fb3-48f0-4d7e-78abda4b0400@mailmanlists.net>

Hi,

If a list's name has a period in it, the "bin/list_members" doesn't seem 
to like it. For example:

$PATH/bin/list_members -f acme_widgets (works fine)

$PATH/bin/list_members -f acme.widgets (gets ignored)

I've tried escaping the period, wrapping the name in quotes, and I'm not 
seeing anything in the bin file - list_members - as an obvious place to 
hack.

Any clues from anyone would be greatly appreciated.

Thanks,
Mark




From mailman-admin at uni-konstanz.de  Mon Nov 21 11:33:50 2016
From: mailman-admin at uni-konstanz.de (mailman-admin)
Date: Mon, 21 Nov 2016 17:33:50 +0100
Subject: [Mailman-Users] list_members when listname has a period
In-Reply-To: <10e677c3-0fb3-48f0-4d7e-78abda4b0400@mailmanlists.net>
References: <10e677c3-0fb3-48f0-4d7e-78abda4b0400@mailmanlists.net>
Message-ID: <07f6dc02-9f39-472a-e58d-30956af479e5@uni-konstanz.de>

Am 21.11.2016 um 08:37 schrieb Mark Dale:
> Hi,
> 
> If a list's name has a period in it, the "bin/list_members" doesn't seem
> to like it. For example:
> 
> $PATH/bin/list_members -f acme_widgets (works fine)
> 
> $PATH/bin/list_members -f acme.widgets (gets ignored)
> 
> I've tried escaping the period, wrapping the name in quotes, and I'm not
> seeing anything in the bin file - list_members - as an obvious place to
> hack.
> 
> Any clues from anyone would be greatly appreciated.
> 

Works for me.
Which version of mailman are you using?


Kind regards,
Christian Mack

From mark at mailmanlists.net  Mon Nov 21 15:14:56 2016
From: mark at mailmanlists.net (Mark Dale)
Date: Tue, 22 Nov 2016 07:14:56 +1100
Subject: [Mailman-Users] list_members when listname has a period
In-Reply-To: <07f6dc02-9f39-472a-e58d-30956af479e5@uni-konstanz.de>
References: <10e677c3-0fb3-48f0-4d7e-78abda4b0400@mailmanlists.net>
 <07f6dc02-9f39-472a-e58d-30956af479e5@uni-konstanz.de>
Message-ID: <8e80f288-980b-676c-cce2-e0db3fa47c74@mailmanlists.net>

Hi,

I'm using version 2.1.23

Regards,
Mark

On 22/11/16 03:33, mailman-admin wrote:

>
> Works for me.
> Which version of mailman are you using?
>
>
> Kind regards,
> Christian Mack

From carbonnb at gmail.com  Mon Nov 21 16:08:43 2016
From: carbonnb at gmail.com (Bryan Carbonnell)
Date: Mon, 21 Nov 2016 14:08:43 -0700
Subject: [Mailman-Users] Changing MTAs on Mailman box
Message-ID: <CAAZtbWE6foOLWqjKTfi1NgaLrm_C4ZS-LJjAvxdYgbPgVoQwGA@mail.gmail.com>

Hi All,

I am looking at changing our MTA from Sendmail to Postfix. The
physical box is staying the same, nothing is changing other than the
MTA on the box.

Is there anything on the Mailman side that I need to do after the change?

I looked at the Postfix integration section in the installation
manual, http://www.list.org/mailman-install/postfix-integration.html
and am just a bit unsure if these are the steps to take since this is
an existing Mailman installation.

Thanks for an pointers.
Bryan

-- 
Bryan Carbonnell - carbonnb at gmail.com
Life's journey is not to arrive at the grave safely in a
well-preserved body, but rather to skid in sideways, totally worn out,
shouting "What a great ride!"

From turnbull.stephen.fw at u.tsukuba.ac.jp  Mon Nov 21 18:47:30 2016
From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Tue, 22 Nov 2016 08:47:30 +0900
Subject: [Mailman-Users] list_members when listname has a period
In-Reply-To: <8e80f288-980b-676c-cce2-e0db3fa47c74@mailmanlists.net>
References: <10e677c3-0fb3-48f0-4d7e-78abda4b0400@mailmanlists.net>
 <07f6dc02-9f39-472a-e58d-30956af479e5@uni-konstanz.de>
 <8e80f288-980b-676c-cce2-e0db3fa47c74@mailmanlists.net>
Message-ID: <22579.34706.604900.509283@turnbull.sk.tsukuba.ac.jp>

Mark Dale writes:
 > Hi,
 > 
 > I'm using version 2.1.23

What operating system is used by your host?  What is your MTA?  Are
you using a service manager such as cPanel or Plesk?  Have you applied
any patches to Mailman?

While I cannot rule out a Mailman problem, as far as I know embedded
periods in list names should work in recent Mailman 2.1.  However,
operating systems and service configuration managers often distribute
Mailman with patches.  If patches are used to improve Mailman's
compatibility with virtual hosting, it's possible that the list's real
name is different from the apparent name, and that the withlist
scripts haven't been updated correctly to handle both virtual hosts
and list post addresses with embedded periods.


From turnbull.stephen.fw at u.tsukuba.ac.jp  Mon Nov 21 18:47:35 2016
From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Tue, 22 Nov 2016 08:47:35 +0900
Subject: [Mailman-Users]  Changing MTAs on Mailman box
In-Reply-To: <CAAZtbWE6foOLWqjKTfi1NgaLrm_C4ZS-LJjAvxdYgbPgVoQwGA@mail.gmail.com>
References: <CAAZtbWE6foOLWqjKTfi1NgaLrm_C4ZS-LJjAvxdYgbPgVoQwGA@mail.gmail.com>
Message-ID: <22579.34711.628680.170916@turnbull.sk.tsukuba.ac.jp>

Bryan Carbonnell writes:

 > Is there anything on the Mailman side that I need to do after the
 > change?

The Postfix integration may recommend putting cron scripts and init
scripts in a different place.  Make sure that any such scripts and
their invocations installed for Sendmail are removed or moved to the
locations expected by Postscript.  You probably don't even have to
move them since Mailman is presumably not going to change, so there
may be nothing to worry about, but duplicated scripts are a common
source of problems.

Other than that as far as I know the only thing you need to do is
configure Postfix to forward mail to Mailman.

 > I looked at the Postfix integration section in the installation
 > manual, http://www.list.org/mailman-install/postfix-integration.html
 > and am just a bit unsure if these are the steps to take since this is
 > an existing Mailman installation.

There shouldn't be any difference.  If you're on a Debian system or
derived there may be a postfix-to-mailman script around somewhere;
make sure that is not active.  The installation in the Postfix
integration page you cite is preferred.  And it is easier for us to
help you with any problems if you use that rather than the Debian
script.

Mark S. may have further advice, but I'm sufficiently confident that I
recommend that you just get started. :-)

Steve

From mark at msapiro.net  Mon Nov 21 21:12:20 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 21 Nov 2016 18:12:20 -0800
Subject: [Mailman-Users] list_members when listname has a period
In-Reply-To: <10e677c3-0fb3-48f0-4d7e-78abda4b0400@mailmanlists.net>
References: <10e677c3-0fb3-48f0-4d7e-78abda4b0400@mailmanlists.net>
Message-ID: <2008fe55-d169-08a3-e3f2-b75798daba05@msapiro.net>

On 11/20/2016 11:37 PM, Mark Dale wrote:
> 
> $PATH/bin/list_members -f acme_widgets (works fine)
> 
> $PATH/bin/list_members -f acme.widgets (gets ignored)
> 
> Any clues from anyone would be greatly appreciated.


I just verified that it works for me.

As Steve suggests, if this is cPanel or possibly some other virtual
hosting patched Mailman, the name may include a domain.

I.e., if it's cPanel, the listname could be something like
acme.widgets_virt.domain.

What is the contents if the $PATH/lists/ directory?

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

From mark at msapiro.net  Mon Nov 21 21:31:22 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 21 Nov 2016 18:31:22 -0800
Subject: [Mailman-Users] Changing MTAs on Mailman box
In-Reply-To: <22579.34711.628680.170916@turnbull.sk.tsukuba.ac.jp>
References: <CAAZtbWE6foOLWqjKTfi1NgaLrm_C4ZS-LJjAvxdYgbPgVoQwGA@mail.gmail.com>
 <22579.34711.628680.170916@turnbull.sk.tsukuba.ac.jp>
Message-ID: <17b2cc69-2be6-5cdc-adeb-22c5b5aa7f53@msapiro.net>

On 11/21/2016 03:47 PM, Stephen J. Turnbull wrote:
> Bryan Carbonnell writes:
> 
>  > Is there anything on the Mailman side that I need to do after the
>  > change?


> Mark S. may have further advice, but I'm sufficiently confident that I
> recommend that you just get started. :-)


The first question is how does your sendmail deliver to Mailman. The
"normal" configuration uses aliases which are maintained manually as
lists are created and deleted.

If you have a set of Mailman aliases in, e.g., /etc/aliases, You may not
need to do anything and things may work fine, but it is also possible
you will get "group mismatch errors" from Mailman's mail wrapper.

You can set up Mailman/Postfix integration. To do that, you should do
the generic Postfix things at
<http://list.org/mailman-install/node12.html> and the integration
specific things at
<http://list.org/mailman-install/postfix-integration.html>.

In addition if you have lists in Postfix virtual domains you need to do
the things in <http://list.org/mailman-install/postfix-virtual.html>.

But you can ignore all that and continue to do aliases as you've done
for Sendmail.

If you have further questions, pleas tell us how Sendmail is currently
delivering to Mailman, and if via aliases, how those are generated.

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

From best.sum at gmail.com  Mon Nov 21 21:26:19 2016
From: best.sum at gmail.com (Leon)
Date: Mon, 21 Nov 2016 21:26:19 -0500
Subject: [Mailman-Users] How to stop bounces emails
Message-ID: <CAPDq0P0N_gQ8o4+w++_o1qYuvfVKeE3QgR2B6epAwGXRE-SzJQ@mail.gmail.com>

Hi, everyone. Subscribers in mailing list always get bounces emails like
"the results of your email commands". How do I stop mailman sending out
them?

Thank you.

-- 
Leon

From willi.uebelherr at gmail.com  Tue Nov 22 14:13:09 2016
From: willi.uebelherr at gmail.com (willi uebelherr)
Date: Tue, 22 Nov 2016 16:13:09 -0300
Subject: [Mailman-Users] How to stop bounces emails
In-Reply-To: <CAPDq0P0N_gQ8o4+w++_o1qYuvfVKeE3QgR2B6epAwGXRE-SzJQ@mail.gmail.com>
References: <CAPDq0P0N_gQ8o4+w++_o1qYuvfVKeE3QgR2B6epAwGXRE-SzJQ@mail.gmail.com>
Message-ID: <5202ed16-2448-2468-ea5b-a88d7b4b232a@gmail.com>

On 21/11/2016 23:26, Leon wrote:
> Hi, everyone. Subscribers in mailing list always get bounces emails like
> "the results of your email commands". How do I stop mailman sending out
> them?
>
> Thank you.

Dear Leon,
i am not a expert. But "bounced mail" are mails, that can't transmit to 
the receiver. But in your example, the receiver take the mails.

Mostly, with my experience, this answers comes from mails that are send 
also to lists and groups, where the sender of the mail is not 
subscribed. But this is a problem of the sender (reponse to all) and not 
of mailman.

I am also waiting for an answer of our experts.

many greetings, willi



From mark at msapiro.net  Tue Nov 22 15:05:21 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 22 Nov 2016 12:05:21 -0800
Subject: [Mailman-Users] How to stop bounces emails
In-Reply-To: <CAPDq0P0N_gQ8o4+w++_o1qYuvfVKeE3QgR2B6epAwGXRE-SzJQ@mail.gmail.com>
References: <CAPDq0P0N_gQ8o4+w++_o1qYuvfVKeE3QgR2B6epAwGXRE-SzJQ@mail.gmail.com>
Message-ID: <5811ecce-786e-30c9-320a-b03362e9d795@msapiro.net>

On 11/21/2016 06:26 PM, Leon wrote:
> Hi, everyone. Subscribers in mailing list always get bounces emails like
> "the results of your email commands". How do I stop mailman sending out
> them?


First question. Is this regarding Mailman 2.1 or Mailman 3? (I ask
because you recently posted a MM3 issue to mailman-developers.) This
list is primarily for Mailman 2.1 user's issues. If your issue relates
to Mailman 3, a more appropriate list is mailman-users at mailman3.org
<https://lists.mailman3.org/mailman3/lists/mailman-users at mailman3.org/>.

Please use that list for Mailman 3 user's issues.

As to your question. Are these messages responses to a message that the
subscribers send to the list-request address (or other list-* addresses)
or are they responses to spam that is sent to the list-request address
spoofing the subscriber as From:?

If the former and this is Mailman 3, there are known issues with
redundant responses from list-request. See
<https://gitlab.com/mailman/mailman/issues/212>

If the latter, the way to stop this is with effective spam filtering at
the incoming MTA before the messages ever get to Mailman.

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

From heller at deepsoft.com  Tue Nov 22 18:31:08 2016
From: heller at deepsoft.com (Robert Heller)
Date: Tue, 22 Nov 2016 18:31:08 -0500 (EST)
Subject: [Mailman-Users] Google not delivering E-Mail from an mailling
 list...
Message-ID: <20161122233108.6FB9473243E@sharky3.deepsoft.com>

I have a subscriber of a Mailman email list that is NOT getting mail sent to 
the list.  My MTA (Postfix under CentOS 6) is logging that the mail is being 
sent to Google's inbound MTA:

Nov 22 17:00:23 sharky3 postfix/smtpd[2459]: 71357732494: client=localhost[::1]
Nov 22 17:00:24 sharky3 postfix/cleanup[2453]: 71357732494: message-id=<CANyDLLtegMOEE_69FugpVh401cY28XH+PbS83kqyEagGu0=_-g at mail.gmail.com>
Nov 22 17:00:25 sharky3 opendkim[755]: 71357732494: DKIM-Signature field added (s=deepsoft.com, d=deepsoft.com)
Nov 22 17:00:25 sharky3 postfix/qmgr[1926]: 71357732494: from=<wendell-townsfolk-bounces at deepsoft.com>, size=4165, nrcpt=216 (queue active)
...
Nov 22 17:01:02 sharky3 postfix/smtp[3083]: 71357732494: to=<XXXXXX at gmail.com>, relay=gmail-smtp-in.l.google.com[74.125.196.26]:25, delay=39, delays=2/1.3/35/0.63, dsn=2.0.0, status=sent (250 2.0.0 OK 1479852062 b19si6789198ybg.241 - gsmtp)
...

but the mail is not getting to the subscriber -- it is not showing up in her
inbox. What should this user do? Is there some sort of setting or something
that this subscriber needs to do with her gmail account? The subscriber is not
a techie and probably needs help dealing with Google's weirdnesses.

-- 
Robert Heller             -- 978-544-6933
Deepwoods Software        -- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
heller at deepsoft.com       -- Webhosting Services
                          

From mark at msapiro.net  Tue Nov 22 19:00:45 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 22 Nov 2016 16:00:45 -0800
Subject: [Mailman-Users] Google not delivering E-Mail from an mailling
 list...
In-Reply-To: <20161122233108.6FB9473243E@sharky3.deepsoft.com>
References: <20161122233108.6FB9473243E@sharky3.deepsoft.com>
Message-ID: <c3720744-c9b0-1b7b-e8f8-4249c2bd73a6@msapiro.net>

On 11/22/2016 03:31 PM, Robert Heller wrote:
> I have a subscriber of a Mailman email list that is NOT getting mail sent to 
> the list.  My MTA (Postfix under CentOS 6) is logging that the mail is being 
> sent to Google's inbound MTA:
> ...
> but the mail is not getting to the subscriber -- it is not showing up in her
> inbox. What should this user do? Is there some sort of setting or something
> that this subscriber needs to do with her gmail account? The subscriber is not
> a techie and probably needs help dealing with Google's weirdnesses.


Is it all list posts she doesn't receive or only her own. If it's only
her own, see <https://wiki.list.org/x/4030680>.

If she doesn't receive other list posts, has she looked in her spam
folder? Do other gmail users receive the posts?

If she finds posts in spam, she should go to her gmail settings (in the
gmail web UI, click the 'gear' icon and then 'settings')

Then on the 'inbox' tab select 'Filtered mail: -> Override filters' and
on the 'Filters and Blocked Addresses' tab make sure there are no list
related addresses in 'blocked addresses'.

The old standby of adding 'wendell-townsfolk-bounces at deepsoft.com' to
her gmail address book may help.

Bottom line is this is a Google issue. We can guess and suggest, but
only Google actually knows.

Also, if no gmail users get list mail, see
<https://wiki.list.org/x/4030690>.

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

From mark at mailmanlists.net  Tue Nov 22 19:23:28 2016
From: mark at mailmanlists.net (Mark Dale)
Date: Wed, 23 Nov 2016 11:23:28 +1100
Subject: [Mailman-Users] list_members when listname has a period
In-Reply-To: <2008fe55-d169-08a3-e3f2-b75798daba05@msapiro.net>
References: <10e677c3-0fb3-48f0-4d7e-78abda4b0400@mailmanlists.net>
 <2008fe55-d169-08a3-e3f2-b75798daba05@msapiro.net>
Message-ID: <bbcb4415-cb23-7f50-3aa3-33092d510e23@mailmanlists.net>

Thanks Mark and Steve.

It is indeed as you said - the real listname was not the advertised 
listname.

The list has now been moved, named as it should be, and all is well.

Regards,
Mark


========================================


On 22/11/16 13:12, Mark Sapiro wrote:

>>
>> $PATH/bin/list_members -f acme_widgets (works fine)
>>
>> $PATH/bin/list_members -f acme.widgets (gets ignored)
>>
>> Any clues from anyone would be greatly appreciated.
>
>
> I just verified that it works for me.
>
> As Steve suggests, if this is cPanel or possibly some other virtual
> hosting patched Mailman, the name may include a domain.
>
> I.e., if it's cPanel, the listname could be something like
> acme.widgets_virt.domain.
>
> What is the contents if the $PATH/lists/ directory?
>

From startrekcafe at gmail.com  Tue Nov 22 17:32:52 2016
From: startrekcafe at gmail.com (Marvin Hunkin)
Date: Wed, 23 Nov 2016 09:02:52 +1030
Subject: [Mailman-Users] my messages not appearing on the digest or single
 messages
Message-ID: <005501d24510$5f160e80$1d422b80$@gmail.com>

Hi. subscribe to a list called chat-request at list.ntxability.org, when I send
my messae and get a digest or individual messages, I do not see my message.
So any ideas. Have contacted the owner, joe Hudson, but he says that having
a copy of my own message is enabled. Any ideas.

Marvin.

 

Marvin Hunkin

Blind Information Technology Student

 <http://www.upskilled.edu.au> http://www.upskilled.edu.au

 


From Richard at Damon-Family.org  Tue Nov 22 19:30:12 2016
From: Richard at Damon-Family.org (Richard Damon)
Date: Tue, 22 Nov 2016 19:30:12 -0500
Subject: [Mailman-Users] Google not delivering E-Mail from an mailling
 list...
In-Reply-To: <20161122233108.6FB9473243E@sharky3.deepsoft.com>
References: <20161122233108.6FB9473243E@sharky3.deepsoft.com>
Message-ID: <db499dab-d4d0-22cb-affe-3e29b3beb941@Damon-Family.org>

On 11/22/16 6:31 PM, Robert Heller wrote:
> I have a subscriber of a Mailman email list that is NOT getting mail sent to
> the list.  My MTA (Postfix under CentOS 6) is logging that the mail is being
> sent to Google's inbound MTA:
>
> Nov 22 17:00:23 sharky3 postfix/smtpd[2459]: 71357732494: client=localhost[::1]
> Nov 22 17:00:24 sharky3 postfix/cleanup[2453]: 71357732494: message-id=<CANyDLLtegMOEE_69FugpVh401cY28XH+PbS83kqyEagGu0=_-g at mail.gmail.com>
> Nov 22 17:00:25 sharky3 opendkim[755]: 71357732494: DKIM-Signature field added (s=deepsoft.com, d=deepsoft.com)
> Nov 22 17:00:25 sharky3 postfix/qmgr[1926]: 71357732494: from=<wendell-townsfolk-bounces at deepsoft.com>, size=4165, nrcpt=216 (queue active)
> ...
> Nov 22 17:01:02 sharky3 postfix/smtp[3083]: 71357732494: to=<XXXXXX at gmail.com>, relay=gmail-smtp-in.l.google.com[74.125.196.26]:25, delay=39, delays=2/1.3/35/0.63, dsn=2.0.0, status=sent (250 2.0.0 OK 1479852062 b19si6789198ybg.241 - gsmtp)
> ...
>
> but the mail is not getting to the subscriber -- it is not showing up in her
> inbox. What should this user do? Is there some sort of setting or something
> that this subscriber needs to do with her gmail account? The subscriber is not
> a techie and probably needs help dealing with Google's weirdnesses.
>
One issue I sometimes see with GMail is that list messages get placed in 
one of the 'alternate' inboxes (like social or forum).


-- 
Richard Damon


From Richard at Damon-Family.org  Tue Nov 22 19:50:53 2016
From: Richard at Damon-Family.org (Richard Damon)
Date: Tue, 22 Nov 2016 19:50:53 -0500
Subject: [Mailman-Users] my messages not appearing on the digest or
 single messages
In-Reply-To: <005501d24510$5f160e80$1d422b80$@gmail.com>
References: <005501d24510$5f160e80$1d422b80$@gmail.com>
Message-ID: <8f1287ed-7d5a-d61d-197a-d70680b02db7@Damon-Family.org>

On 11/22/16 5:32 PM, Marvin Hunkin wrote:
> Hi. subscribe to a list called chat-request at list.ntxability.org, when I send
> my messae and get a digest or individual messages, I do not see my message.
> So any ideas. Have contacted the owner, joe Hudson, but he says that having
> a copy of my own message is enabled. Any ideas.
>
> Marvin.
>
>   
>
> Marvin Hunkin
>
> Blind Information Technology Student
>
>   <http://www.upskilled.edu.au> http://www.upskilled.edu.au
>
is the list name really 'chat-request' or could it be just 'chat'. Lists 
has auxiliary email addresses for special operations, based on the list 
name and and added suffix, one of which is -request, which allows you to 
manipulate your email subscription via email (including the initial 
subscription).

How did you subscribe to this list?


-- 
Richard Damon


From heller at deepsoft.com  Tue Nov 22 20:04:37 2016
From: heller at deepsoft.com (Robert Heller)
Date: Tue, 22 Nov 2016 20:04:37 -0500 (EST)
Subject: [Mailman-Users] Google not delivering E-Mail from an mailling
 list...
In-Reply-To: <c3720744-c9b0-1b7b-e8f8-4249c2bd73a6@msapiro.net>
References: <20161122233108.6FB9473243E@sharky3.deepsoft.com> 
 <c3720744-c9b0-1b7b-e8f8-4249c2bd73a6@msapiro.net>
Message-ID: <20161123010437.5BE44732454@sharky3.deepsoft.com>

At Tue, 22 Nov 2016 16:00:45 -0800 Mark Sapiro <mark at msapiro.net> wrote:

> 
> On 11/22/2016 03:31 PM, Robert Heller wrote:
> > I have a subscriber of a Mailman email list that is NOT getting mail sent to 
> > the list.  My MTA (Postfix under CentOS 6) is logging that the mail is being 
> > sent to Google's inbound MTA:
> > ...
> > but the mail is not getting to the subscriber -- it is not showing up in her
> > inbox. What should this user do? Is there some sort of setting or something
> > that this subscriber needs to do with her gmail account? The subscriber is not
> > a techie and probably needs help dealing with Google's weirdnesses.
> 
> 
> Is it all list posts she doesn't receive or only her own. If it's only
> her own, see <https://wiki.list.org/x/4030680>.

She hasn't posted anything.  She also did not receive the E-Mail confirmation 
message -- I ended up adding her manually ("Bulk Subscribtions").

> 
> If she doesn't receive other list posts, has she looked in her spam
> folder? Do other gmail users receive the posts?

It is not in her spam folder.  I believe other gmail users are receiving posts 
(I have not received any complaints).

> 
> If she finds posts in spam, she should go to her gmail settings (in the
> gmail web UI, click the 'gear' icon and then 'settings')
> 
> Then on the 'inbox' tab select 'Filtered mail: -> Override filters' and
> on the 'Filters and Blocked Addresses' tab make sure there are no list
> related addresses in 'blocked addresses'.
> 
> The old standby of adding 'wendell-townsfolk-bounces at deepsoft.com' to
> her gmail address book may help.
> 
> Bottom line is this is a Google issue. We can guess and suggest, but
> only Google actually knows.

I know, but Google generally is not really telling and does not really have 
much in the way of customer support.  *I* don't use Google, but I figured 
someone here might have had this problem and might know how to troubleshoot 
it.

> 
> Also, if no gmail users get list mail, see
> <https://wiki.list.org/x/4030690>.
> 

-- 
Robert Heller             -- 978-544-6933
Deepwoods Software        -- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
heller at deepsoft.com       -- Webhosting Services
                                                                                                 

From mark at msapiro.net  Tue Nov 22 20:23:57 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 22 Nov 2016 17:23:57 -0800
Subject: [Mailman-Users] my messages not appearing on the digest or
 single messages
In-Reply-To: <8f1287ed-7d5a-d61d-197a-d70680b02db7@Damon-Family.org>
References: <005501d24510$5f160e80$1d422b80$@gmail.com>
 <8f1287ed-7d5a-d61d-197a-d70680b02db7@Damon-Family.org>
Message-ID: <3f12adb3-3362-e538-9f82-02f3be788d0a@msapiro.net>

On 11/22/2016 04:50 PM, Richard Damon wrote:
> On 11/22/16 5:32 PM, Marvin Hunkin wrote:
>> Hi. subscribe to a list called chat-request at list.ntxability.org, when
>> I send
>> my messae and get a digest or individual messages, I do not see my
>> message.
>>
> is the list name really 'chat-request' or could it be just 'chat'.


I think Richard has the answer. According to
<list.ntxability.org/mailman/listinfo/> there is a
chat at list.ntxability.org list, but no chat-request at list.ntxability.org.

If you are posting to chat-request at list.ntxability.org, your 'posts' are
probably just being discarded as email requests that contain no commands.

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

From mark at msapiro.net  Tue Nov 22 20:32:19 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 22 Nov 2016 17:32:19 -0800
Subject: [Mailman-Users] Google not delivering E-Mail from an mailling
 list...
In-Reply-To: <20161123010437.5BE44732454@sharky3.deepsoft.com>
References: <20161122233108.6FB9473243E@sharky3.deepsoft.com>
 <c3720744-c9b0-1b7b-e8f8-4249c2bd73a6@msapiro.net>
 <20161123010437.5BE44732454@sharky3.deepsoft.com>
Message-ID: <b6672752-ebda-28f5-d7ee-937d923a2a77@msapiro.net>

On 11/22/2016 05:04 PM, Robert Heller wrote:
> 
> I know, but Google generally is not really telling and does not really have 
> much in the way of customer support.  *I* don't use Google, but I figured 
> someone here might have had this problem and might know how to troubleshoot 
> it.


I feel your pain, but I can't help. I have seen the issue, but I just
suggest checking spam which often works. If not, I just refer people to
Google. Richard has suggested places other than 'spam' where the
messages might be going. Possibly others have other insights.

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

From carbonnb at gmail.com  Wed Nov 23 09:31:40 2016
From: carbonnb at gmail.com (Bryan Carbonnell)
Date: Wed, 23 Nov 2016 07:31:40 -0700
Subject: [Mailman-Users] Changing MTAs on Mailman box
In-Reply-To: <17b2cc69-2be6-5cdc-adeb-22c5b5aa7f53@msapiro.net>
References: <CAAZtbWE6foOLWqjKTfi1NgaLrm_C4ZS-LJjAvxdYgbPgVoQwGA@mail.gmail.com>
 <22579.34711.628680.170916@turnbull.sk.tsukuba.ac.jp>
 <17b2cc69-2be6-5cdc-adeb-22c5b5aa7f53@msapiro.net>
Message-ID: <CAAZtbWFk0c6DOOr6h_snCsZBBd0M2K7xv69wKP9vYdbriDeVJg@mail.gmail.com>

Thanks Stephen & Mark.

Mark, Sendmail uses the manually created Aliases to deliver to
Mailman. But I think I'd rather have the integration with the aliases
automatically created.

I'm sure that I'll have further questions since this will be my first
Postfix install, but I'll find a proper Postfix mailing list to ask
the stupid Postfix questions. I'll reserve the stupid Mailman question
for here ;)

Thanks,
Bryan

On 21 November 2016 at 19:31, Mark Sapiro <mark at msapiro.net> wrote:
> On 11/21/2016 03:47 PM, Stephen J. Turnbull wrote:
>> Bryan Carbonnell writes:
>>
>>  > Is there anything on the Mailman side that I need to do after the
>>  > change?
>
>
>> Mark S. may have further advice, but I'm sufficiently confident that I
>> recommend that you just get started. :-)
>
>
> The first question is how does your sendmail deliver to Mailman. The
> "normal" configuration uses aliases which are maintained manually as
> lists are created and deleted.
>
> If you have a set of Mailman aliases in, e.g., /etc/aliases, You may not
> need to do anything and things may work fine, but it is also possible
> you will get "group mismatch errors" from Mailman's mail wrapper.
>
> You can set up Mailman/Postfix integration. To do that, you should do
> the generic Postfix things at
> <http://list.org/mailman-install/node12.html> and the integration
> specific things at
> <http://list.org/mailman-install/postfix-integration.html>.
>
> In addition if you have lists in Postfix virtual domains you need to do
> the things in <http://list.org/mailman-install/postfix-virtual.html>.
>
> But you can ignore all that and continue to do aliases as you've done
> for Sendmail.
>
> If you have further questions, pleas tell us how Sendmail is currently
> delivering to Mailman, and if via aliases, how those are generated.
>
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/carbonnb%40gmail.com



-- 
Bryan Carbonnell - carbonnb at gmail.com
Life's journey is not to arrive at the grave safely in a
well-preserved body, but rather to skid in sideways, totally worn out,
shouting "What a great ride!"

From larry at qhpress.org  Wed Nov 23 10:21:26 2016
From: larry at qhpress.org (Larry Kuenning)
Date: Wed, 23 Nov 2016 10:21:26 -0500
Subject: [Mailman-Users] Changing MTAs on Mailman box
In-Reply-To: <CAAZtbWFk0c6DOOr6h_snCsZBBd0M2K7xv69wKP9vYdbriDeVJg@mail.gmail.com>
References: <CAAZtbWE6foOLWqjKTfi1NgaLrm_C4ZS-LJjAvxdYgbPgVoQwGA@mail.gmail.com>
 <22579.34711.628680.170916@turnbull.sk.tsukuba.ac.jp>
 <17b2cc69-2be6-5cdc-adeb-22c5b5aa7f53@msapiro.net>
 <CAAZtbWFk0c6DOOr6h_snCsZBBd0M2K7xv69wKP9vYdbriDeVJg@mail.gmail.com>
Message-ID: <5835B3F6.4040306@qhpress.org>

On 11/23/2016 9:31 AM, Bryan Carbonnell wrote:

> ... I'll find a proper Postfix mailing list to ask
> the stupid Postfix questions. ...

If you find one, could you tell this list where it is?  The one I found 
a few years ago, postfix-users at yahoogroups.com, hasn't had any messages 
since July 2014.

-- 
Larry Kuenning
larry at qhpress.org


From ler at lerctr.org  Wed Nov 23 10:54:02 2016
From: ler at lerctr.org (Larry Rosenman)
Date: Wed, 23 Nov 2016 09:54:02 -0600
Subject: [Mailman-Users] Changing MTAs on Mailman box
In-Reply-To: <5835B3F6.4040306@qhpress.org>
References: <CAAZtbWE6foOLWqjKTfi1NgaLrm_C4ZS-LJjAvxdYgbPgVoQwGA@mail.gmail.com>
 <22579.34711.628680.170916@turnbull.sk.tsukuba.ac.jp>
 <17b2cc69-2be6-5cdc-adeb-22c5b5aa7f53@msapiro.net>
 <CAAZtbWFk0c6DOOr6h_snCsZBBd0M2K7xv69wKP9vYdbriDeVJg@mail.gmail.com>
 <5835B3F6.4040306@qhpress.org>
Message-ID: <867e31bf0062439600884cbc6385306e@lerctr.org>

On 2016-11-23 09:21, Larry Kuenning wrote:
> On 11/23/2016 9:31 AM, Bryan Carbonnell wrote:
> 
>> ... I'll find a proper Postfix mailing list to ask
>> the stupid Postfix questions. ...
> 
> If you find one, could you tell this list where it is?  The one I
> found a few years ago, postfix-users at yahoogroups.com, hasn't had any
> messages since July 2014.

[resend including the list]
http://www.postfix.org/lists.html

-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 214-642-9640                 E-Mail: ler at lerctr.org
US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

From turnbull.stephen.fw at u.tsukuba.ac.jp  Wed Nov 23 11:09:51 2016
From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Thu, 24 Nov 2016 01:09:51 +0900
Subject: [Mailman-Users] my messages not appearing on the digest or
 single messages
In-Reply-To: <3f12adb3-3362-e538-9f82-02f3be788d0a@msapiro.net>
References: <005501d24510$5f160e80$1d422b80$@gmail.com>
 <8f1287ed-7d5a-d61d-197a-d70680b02db7@Damon-Family.org>
 <3f12adb3-3362-e538-9f82-02f3be788d0a@msapiro.net>
Message-ID: <22581.48975.612232.632169@turnbull.sk.tsukuba.ac.jp>

Mark Sapiro writes:
 > On 11/22/2016 04:50 PM, Richard Damon wrote:
 > > On 11/22/16 5:32 PM, Marvin Hunkin wrote:
 > >> Hi. subscribe to a list called chat-request at list.ntxability.org, when
 > >> I send
 > >> my messae and get a digest or individual messages, I do not see my
 > >> message.
 > >>
 > > is the list name really 'chat-request' or could it be just 'chat'.
 > 
 > 
 > I think Richard has the answer. According to
 > <list.ntxability.org/mailman/listinfo/> there is a
 > chat at list.ntxability.org list, but no chat-request at list.ntxability.org.
 > 
 > If you are posting to chat-request at list.ntxability.org, your 'posts' are
 > probably just being discarded as email requests that contain no
 > commands.

Also, if Marvin uses his GMail address to post, he will see his posts
in the digest distribution, but GMail will most likely suppress his
posts when he receives them separately.  This is a GMail behavior that
cannot be turned off as far as I know.

From brett at twobikes.ottawa.on.ca  Tue Nov 22 21:40:32 2016
From: brett at twobikes.ottawa.on.ca (Brett Delmage)
Date: Tue, 22 Nov 2016 21:40:32 -0500 (EST)
Subject: [Mailman-Users] Google not delivering E-Mail from an mailling
 list...
In-Reply-To: <db499dab-d4d0-22cb-affe-3e29b3beb941@Damon-Family.org>
References: <20161122233108.6FB9473243E@sharky3.deepsoft.com>
 <db499dab-d4d0-22cb-affe-3e29b3beb941@Damon-Family.org>
Message-ID: <alpine.DEB.2.20.1611222133170.13025@pannier.local>

On Tue, 22 Nov 2016, Richard Damon wrote:

> On 11/22/16 6:31 PM, Robert Heller wrote:
>> I have a subscriber of a Mailman email list that is NOT getting mail 
>> sent to the list.  My MTA (Postfix under CentOS 6) is logging that the 
>> mail is being sent to Google's inbound MTA:

> One issue I sometimes see with Gmail is that list messages get placed in one 
> of the 'alternate' inboxes (like social or forum).

This. I have seen messages from my list filed in alternate inboxes 
suddenly..

One thing Gmail is about is reliable and easy seach. Use it as a tool.

Have your subscriber enter search items like "Subject: Confirm" or 
subject: [list name] or from: list address and gmail should find the 
message, no matter what folder it's hidden in.

Also, because of the amount of spam it is subject to, Gmail does pay more 
attention to the presence of proper DKIM headers and SPF records.

Brett

From minxmertzmomo at gmail.com  Wed Nov 23 11:53:15 2016
From: minxmertzmomo at gmail.com (Matt Morgan)
Date: Wed, 23 Nov 2016 11:53:15 -0500
Subject: [Mailman-Users] DMARC-related bounces due to AOL sender;
 from_is_list or anonymous_list?
Message-ID: <CABTRqU4cy+EDh_RAyd3n1zdiY2xO4=8+buapXsErKGw+6mBuGQ@mail.gmail.com>

On one of our lists, we are recently getting a lot of bounces related to
AOL's DMARC policy. We're probably getting them on all our lists, actually,
it's just that this list had a pretty stiff bounce-disabling config, so we
noticed it more there.

I understand that my choices for fixing this are either from_is_list or
anonymous_list, and since this is an old server (2.1.12) that I recently
took over (I have to stop using that excuse soon, I know), I can't do
from_is_list.

I need to update desperately. In other recent discussions, though, I seen
that Microsoft in particular is starting to make trouble even with
from_is_list, i.e., when the sender and reply-to don't match, with the
expectation being that one day their warnings will become rejections.

In that light, should I just be moving to anonymous_list anyway? Training
users to identify themselves in the body of their messages seems like the
potential big issue there. Anything else?

Thanks,
Matt

From mark at msapiro.net  Wed Nov 23 13:37:36 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 23 Nov 2016 10:37:36 -0800
Subject: [Mailman-Users] DMARC-related bounces due to AOL sender;
 from_is_list or anonymous_list?
In-Reply-To: <CABTRqU4cy+EDh_RAyd3n1zdiY2xO4=8+buapXsErKGw+6mBuGQ@mail.gmail.com>
References: <CABTRqU4cy+EDh_RAyd3n1zdiY2xO4=8+buapXsErKGw+6mBuGQ@mail.gmail.com>
Message-ID: <688167de-8e25-8ce6-38d1-dab59c8103a0@msapiro.net>

On 11/23/2016 08:53 AM, Matt Morgan wrote:
> 
> I understand that my choices for fixing this are either from_is_list or
> anonymous_list, and since this is an old server (2.1.12) that I recently
> took over (I have to stop using that excuse soon, I know), I can't do
> from_is_list.


Actually, in 2.1.18+ dmarc_moderation_action is more often than not
preferable to from_is_list.

See <https://wiki.list.org/x/17891458> for other possible mitigations
some of which apply to older Mailman versions.


> I need to update desperately. In other recent discussions, though, I seen
> that Microsoft in particular is starting to make trouble even with
> from_is_list, i.e., when the sender and reply-to don't match, with the
> expectation being that one day their warnings will become rejections.


Actually, the current Microsoft warning is issued when the From: and To:
(or Cc:) addresses are the same. This affects anonymous_list as well as
DMARC mitigations.

It seems the (partial) way around all of this is to apply DMARC
mitigations when necessary or always (via dmarc_moderation_action or
from_is_list) and to set personalize to Full personalization so that To:
is the recipient, not the list.

Without better knowledge of Microsoft's rule, it's difficult to know how
to deal with it, and I'm sure Microsoft would consider such information
to be proprietary.


> In that light, should I just be moving to anonymous_list anyway? Training
> users to identify themselves in the body of their messages seems like the
> potential big issue there. Anything else?


As noted above, anonymous_list is not a solution in general. You might
consider anonymous_list as a DMARC mitigation in pre-2.1.16 only, but
better to upgrade.

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

From cyndi at norwitz.net  Mon Nov 28 14:39:10 2016
From: cyndi at norwitz.net (Cyndi Norwitz)
Date: Mon, 28 Nov 2016 11:39:10 -0800
Subject: [Mailman-Users] Expressions to reduce spam
References: <mailman.702.1480361316.2071.mailman-users@python.org>
Message-ID: <62B17C80-0C87-4FF7-B043-CA77C1159AA1@norwitz.net>

> On Nov 13, 2016, at 8:04 PM, Mark Sapiro <mark at msapiro.net> wrote:
> 
> On 11/13/2016 07:55 PM, Mark Sapiro wrote:
>> 
>> Or to get more than one tld with one regexp
>> 
>> *.*\.(site|win|othertop)$
> 
> Ooops. Should be
> 
> ^.*\.(site|win|othertop)$

Thanks to everyone who replied!

I want to clarify that I don?t own or run the server.  My ISP (sonic.net) has Mailman installed for customers to use.  I can not configure it and I can?t affect what emails reach the Mailman software.  Sonic is pretty good at walking that line between getting rid of spam and not having false positives, but there?s a lot that still gets through.

As for "everyone should learn regular expressions?... Sure, maybe.  But I think it?s overkill.  I mean I don?t require all my soap customers to learn the chemistry of saponification.

Doing it all from scratch every time also leads to mistakes.  Example: Mark?s simple typo above.  If even an expert can mess it up...

I mean, when I started making websites back in the mid-1990's, I hand-coded in HTML.  I could switch to my browser to see where I messed up (cause you will always mess up), go back, fix, try again.  Now I use Dreamweaver.  I can still go into the code whenever I want to tweak things, but I don?t have to for the day to day stuff (thank God) and I can do things that are a lot more complex because of it.

I don't know what percentage of Mailman list owners are those who have this skillset.  I?m going to guess a fairly low percentage because when someone takes the time to install it on their own server, they often invite friends, family, and people they work with (orgs, etc) to make lists.  Then there are all the list owners using it from an ISP or a server they don?t have a personal connection with.  It would be nice to be able to reduce the amount of spam that comes in for moderation without having to learn a brand new skill or bother the root access person each time.

Anyway, I know you have a lot on your plate, just putting it out there.

Cyndi






From turnbull.stephen.fw at u.tsukuba.ac.jp  Mon Nov 28 21:46:41 2016
From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Tue, 29 Nov 2016 11:46:41 +0900
Subject: [Mailman-Users] Expressions to reduce spam
In-Reply-To: <62B17C80-0C87-4FF7-B043-CA77C1159AA1@norwitz.net>
References: <mailman.702.1480361316.2071.mailman-users@python.org>
 <62B17C80-0C87-4FF7-B043-CA77C1159AA1@norwitz.net>
Message-ID: <22588.60433.618160.108147@turnbull.sk.tsukuba.ac.jp>

Cyndi Norwitz writes:

 > As for "everyone should learn regular expressions?...

Not everyone.  Just *some* list admins whose security professionals
are unresponsive, or who are their own security admins.

 > Sure, maybe. But I think it?s overkill.  I mean I don?t require
 > all my soap customers to learn the chemistry of saponification.
 > I mean, when I started making websites back in the mid-1990's, I
 > hand-coded in HTML.  I could switch to my browser to see where I
 > messed up (cause you will always mess up), go back, fix, try again.
 > Now I use Dreamweaver.

Your metaphors are not valid.  Selling soap and creating HTML are
cooperative activities.  Both of you *want* simple, and the
combination of soap and customer's skin, or you with Dreamweaver and a
reader with a reasonably modern browser, gives a win-win outcome.  But
spamming is a zero-sum game, and spammers are intelligent opponents,
not reducible to counting the number of electrons in the outermost
orbit.  There *may* be ways to simplify, but they will be rare, and
spammer- and list-specific.

The most important point is that, while human beings can reliably
recognize spam before they have time to think about why they think
it's spam, computers can't do that at all.  They have to specifically
apply heuristic rules, all of which frequently fail very badly.  Each
rule frequently allows whole streams of spam through, and sometimes
identifies whole streams of authentic mail as spam.  That's why the
effective applications like SpamAssassin and SpamBayes use scoring of
many rules, and site-specific tweaks to scores, rather than using
litmus tests that trigger a discard on one feature as Mailman does.

There is a clear and present danger that each simple litmus test will
throw away authentic posts without stopping enough spam to make that
risk worthwhile.  It is that danger that leads us to prefer consulting
for each admin who needs an apparently simple rule, and setting a high
bar (regexps) for DIY spam-fighting.  Providing a way to configure
simple rules would most likely be an attractive nuisance.  But people
who have the knowledge and experience to use regexps not only can
write more sophisticated (though still risky) rules, but also have
experienced the limits of automated filters.

We could make it easier, but it's not at all clear to me that we
should.

Steve


From luscheina at yahoo.de  Wed Nov 30 15:22:11 2016
From: luscheina at yahoo.de (Christian F Buser)
Date: Wed, 30 Nov 2016 21:22:11 +0100
Subject: [Mailman-Users] Time needed to deliver list messages
Message-ID: <20161130212211213321.5188c2b4@yahoo.de>

Hi all 

Our lists run on a cPanel installation of Mailman (cPanel version 60.0.25, Mailman version 2.1.23). Messages sent to the list take some long time to be delivered to the subscribers - in the best case it is about 10 minutes, but it can take up to over 40 minutes.

We asked our provider about it, and he tried to finetune some settings on the server - so far without success. He said he also contacted cPanel support and their response was "this is normal - there is nothing they can do about it", he said.

My question to all who run Mailman on cPanel: Is it true? Are you also experiencing delivery delays? 

Thank you, Christian 

-- 
Christian F. Buser, Hohle Gasse 6, CH-5507 Mellingen (Switzerland)      
Hilfe fuer Strassenkinder in Ghana: http://www.chance-for-children.org

From mark at msapiro.net  Wed Nov 30 16:11:33 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 30 Nov 2016 13:11:33 -0800
Subject: [Mailman-Users] Time needed to deliver list messages
In-Reply-To: <20161130212211213321.5188c2b4@yahoo.de>
References: <20161130212211213321.5188c2b4@yahoo.de>
Message-ID: <e53f9cd9-c935-7b6f-2d7d-e08770df409f@msapiro.net>

On 11/30/2016 12:22 PM, Christian F Buser via Mailman-Users wrote:
> 
> Our lists run on a cPanel installation of Mailman (cPanel version
> 60.0.25, Mailman version 2.1.23). Messages sent to the list take some
> long time to be delivered to the subscribers - in the best case it is
> about 10 minutes, but it can take up to over 40 minutes.
> 
> We asked our provider about it, and he tried to finetune some
> settings on the server - so far without success. He said he also
> contacted cPanel support and their response was "this is normal -
> there is nothing they can do about it", he said.
> 
> My question to all who run Mailman on cPanel: Is it true? Are you
> also experiencing delivery delays?


I don't have direct experience with cPanel, but there are a number of
hosting services that provide Mailman via cPanel, and as far as I know,
this is not a systemic problem.

As I tried to indicate in my earlier reply at
<https://mail.python.org/pipermail/mailman-users/2016-November/081539.html>,
this is an Exim issue. I'm certain that the Exim configuration on the
host server can be tuned so this is not a problem. If your hosting
provider is unable or unwilling to do this, you should investigate other
hosting services.

Also, please see the next to last paragraph in my earlier reply for
specific information about what the host can do.

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

From brian at emwd.com  Wed Nov 30 16:24:42 2016
From: brian at emwd.com (Brian Carpenter)
Date: Wed, 30 Nov 2016 16:24:42 -0500
Subject: [Mailman-Users] Time needed to deliver list messages
In-Reply-To: <20161130212211213321.5188c2b4@yahoo.de>
References: <20161130212211213321.5188c2b4@yahoo.de>
Message-ID: <4c6901d24b50$2ab2e640$8018b2c0$@emwd.com>

> Hi all
> 
> Our lists run on a cPanel installation of Mailman (cPanel version 60.0.25,
> Mailman version 2.1.23). Messages sent to the list take some long time to
be
> delivered to the subscribers - in the best case it is about 10 minutes,
but it
> can take up to over 40 minutes.
> 
> We asked our provider about it, and he tried to finetune some settings on
the
> server - so far without success. He said he also contacted cPanel support
and
> their response was "this is normal - there is nothing they can do about
it", he
> said.
> 
> My question to all who run Mailman on cPanel: Is it true? Are you also
> experiencing delivery delays?

Hi Christian,

We run a mailman hosting service and none of our clients have any issues in
delivery. I suggest the first issue that may be causing the delay is your
messages are being queued instead of being delivered right away. On a
cPanel/Exim server, a high server load can cause messages to be queued. Also
Exim comes with some pre-set settings that can cause a busy mailman list's
messages to be queued:

smtp_accept_queue_per_connection
queue_only_load

Once a message is queued, there will be a delay in delivery as a result. The
settings we have come up with due to our past experience in Mailman hosting
has served our clients (and us!) very well. 


Brian Carpenter
Owner

Providing Cloud Services and more for over 15 years.

T: 336.755.0685
E: brian at emwd.com
www.emwd.com


From adamsca at gmail.com  Wed Nov 30 19:22:16 2016
From: adamsca at gmail.com (Christopher Adams)
Date: Wed, 30 Nov 2016 16:22:16 -0800
Subject: [Mailman-Users] subscribers being unsubscribed at wrong time based
 on bounce settings.
Message-ID: <CAA13W+8TqnpZwUSSbnieNKsnT8TRRLL1V-P9zbNVy0rBYjEzXg@mail.gmail.com>

Hello,

I have done some fairly extensive examination of logs and list settings for
one of the lists hosted here, and I can't come up with a sensible
explanation to tell a customer.

The list is set to not send messages when a person unsubscribes.

The bounce settings are set so that 2 warning messages are sent after the
address is disabled and those messages should be 7 days apart.

A message was sent to the list on 11/1. I see in the logs that a
substantial number of addresses reached the bounce limit and were disabled.
So, based on the bounce settings, many of these should have been
unsubscribed 14 days later. They were not.

However, on 11/24, there was a mass unsubscribe of addresses that had been
disabled. Additionally, many (including some that turned out to have valid
addresses) received unsubscribe notices.

I tend to think that these are not related, but are two issues that I have
not been able to explain.

Many thanks,

Christopher Adams

From mark at msapiro.net  Wed Nov 30 20:03:46 2016
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 30 Nov 2016 17:03:46 -0800
Subject: [Mailman-Users] subscribers being unsubscribed at wrong time
 based on bounce settings.
In-Reply-To: <CAA13W+8TqnpZwUSSbnieNKsnT8TRRLL1V-P9zbNVy0rBYjEzXg@mail.gmail.com>
References: <CAA13W+8TqnpZwUSSbnieNKsnT8TRRLL1V-P9zbNVy0rBYjEzXg@mail.gmail.com>
Message-ID: <7c398afd-2230-3b57-eece-2fc94e5cf677@msapiro.net>

On 11/30/2016 04:22 PM, Christopher Adams wrote:
> 
> I have done some fairly extensive examination of logs and list settings for
> one of the lists hosted here, and I can't come up with a sensible
> explanation to tell a customer.


What is in the logs. In particular, the entire 'bounce' log from 11/1
thru 11/24.


> The list is set to not send messages when a person unsubscribes.


Do you mean admin_notify_mchanges is No, bounce_notify_owner_on_removal
is No or something else. When cron/disabled removes a member, it always
tries to notify the member. There's no setting for that.
	

> The bounce settings are set so that 2 warning messages are sent after the
> address is disabled and those messages should be 7 days apart.
> 
> A message was sent to the list on 11/1. I see in the logs that a
> substantial number of addresses reached the bounce limit and were disabled.
> So, based on the bounce settings, many of these should have been
> unsubscribed 14 days later. They were not.
> 
> However, on 11/24, there was a mass unsubscribe of addresses that had been
> disabled. Additionally, many (including some that turned out to have valid
> addresses) received unsubscribe notices.


Was cron/disabled running between 11/15 and 11/24?

Were changes made to the list's bounce settings after 11/1. In
particular, the number of notices (bounce_you_are_disabled_warnings) is
set in the user's bounce info when deliverry is first disabled and
subsequent changes to the list setting won't affect the number of
notices for that user.

	
> I tend to think that these are not related, but are two issues that I have
> not been able to explain.


Also what's in the subscribe log on 11/24. Where the 'unrelated'
unsubscribes all done at the time cron/disabled ran (default 09:00)?


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

From joseph at pfeifferfamily.net  Wed Nov 30 21:16:32 2016
From: joseph at pfeifferfamily.net (Joe Pfeiffer)
Date: Wed, 30 Nov 2016 19:16:32 -0700
Subject: [Mailman-Users] munging the To: line?
Message-ID: <22591.34816.31257.537328@pfeifferfamily.net>

I've searched the archives and the FAQs; if I've missed something
please point me to it.

I've got From: munging turned on, so posts to a list I administer come
"from" addresses like
John Smith via mylist <mylist at example.com>

Frequently, list users will post to the list by replying to a previous
message, and I'll end up getting a message with a To: header like

To: John Smith via mylist <mylist at example.com>

and it goes out to the list with that To: header.

Since this can be confusing, I'd like to munge the To: line as it
comes through so it ends up saying

To: My List <mylist at example.com>

Is there a way to do this through standard configuration options (and
how?), or do I need to write a handler?
-- 
Joe Pfeiffer                                   575.525.2764 (H)
1440 Tierra del Sol Dr                         575.496.3501 (C)
Las Cruces, NM 88007-5548