Re: [Mailman-Users] MailMan won't send list emails

[Mark Sapiro]

On 07/13/2016 09:18 PM, Caesar Samsi wrote:
> [including list]
> 
> The log for an inbound email to t...@yugi.us  list
> 
> Jul 13 20:48:09 mail postfix/smtpd[10666]: connect from macpro[192.168.1.253]
> Jul 13 20:48:09 mail postfix/smtpd[10666]: Anonymous TLS connection 
> established from macpro[192.168.1.253]: TLSv1 with cipher 
> ECDHE-RSA-AES256-SHA (256/256 bits)
> Jul 13 20:48:09 mail postfix/smtpd[10666]: E31B13FFF3: 
> client=macpro[192.168.1.253], sasl_method=PLAIN, sasl_username=cae...@samsi.us
> Jul 13 20:48:09 mail postfix/cleanup[10656]: E31B13FFF3: 
> message-id=
> Jul 13 20:48:09 mail postfix/qmgr[10476]: E31B13FFF3: from=, 
> size=316, nrcpt=1 (queue active)
> Jul 13 20:48:10 mail postfix/smtpd[10684]: connect from localhost[127.0.0.1]
> Jul 13 20:48:11 mail postfix/smtpd[10684]: disconnect from 
> localhost[127.0.0.1]
> Jul 13 20:48:11 mail postfix/smtpd[10684]: connect from localhost[127.0.0.1]
> Jul 13 20:48:11 mail postfix/smtpd[10684]: disconnect from 
> localhost[127.0.0.1]
> Jul 13 20:48:12 mail postfix/smtpd[10687]: connect from localhost[127.0.0.1]
> Jul 13 20:48:12 mail postfix/smtpd[10687]: A44093FFF4: 
> client=localhost[127.0.0.1]
> Jul 13 20:48:12 mail postfix/cleanup[10656]: A44093FFF4: 
> message-id=
> Jul 13 20:48:12 mail postfix/qmgr[10476]: A44093FFF4: from=, 
> size=933, nrcpt=1 (queue active)
> Jul 13 20:48:12 mail amavis[9530]: (09530-14) Passed CLEAN {RelayedInternal}, 
> LOCAL [192.168.1.253]:65462  -> , Queue-ID: 
> E31B13FFF3, Message-ID: , 
> mail_id: lnzQpKxIXYKy, Hits: -0.002, size: 316, queued_as: A44093FFF4, 2809 ms
> Jul 13 20:48:12 mail postfix/smtp[10658]: E31B13FFF3: to=, 
> relay=127.0.0.1[127.0.0.1]:10024, delay=2.9, delays=0.03/0.01/0.02/2.8, 
> dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 
> Ok: queued as A44093FFF4)
> Jul 13 20:48:12 mail postfix/qmgr[10476]: E31B13FFF3: removed
> Jul 13 20:48:12 mail dovecot: lda(t...@yugi.us): 
> msgid=: saved mail to INBOX
> Jul 13 20:48:12 mail postfix/pipe[10664]: A44093FFF4: to=, 
> relay=dovecot, delay=0.18, delays=0.03/0.01/0/0.14, dsn=2.0.0, status=sent 
> (delivered via dovecot service)
> Jul 13 20:48:12 mail postfix/qmgr[10476]: A44093FFF4: removed


Dovecot delivery does not look at aliases.

> Postfix config:
> 
...
> virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf,
> mysql:/etc/postfix/mysql_virtual_alias_domainaliases_maps.cf,
> hash:/var/lib/mailman/data/virtual-mailman

Adding

virtual_alias_domains = yugi.us

may help if yugi.us is not a virtual_mailbox_domain, but it may not and
if it does help, it may break delivery to non-mailman addresses @yugi.us.

If yugi.us is a virtual_mailbox_domain, i.e. is in
mysql:/etc/postfix/mysql_virtual_domains_maps.cf and can't be removed,
you may need to use the method at  to
generate transport maps to the local: transport, or you could possibly
use some other domain which is not a virtual_mailbox_domain for your
list mail.

Note that all of this is because of using the Dovecot LDA as
virtual_transport. The default Postfix virtual transport will use
virtual_alias_maps for virtual_mailbox_domains.


> virtual_gid_maps = static:8
> virtual_mailbox_base = /var/vmail
> virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf
> virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf,
> mysql:/etc/postfix/mysql_virtual_mailbox_domainaliases_maps.cf
> virtual_transport = dovecot
> virtual_uid_maps = static:150

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] MailMan won't send list emails

[Caesar Samsi]

[including list]

The log for an inbound email to t...@yugi.us  list

Jul 13 20:48:09 mail postfix/smtpd[10666]: connect from macpro[192.168.1.253]
Jul 13 20:48:09 mail postfix/smtpd[10666]: Anonymous TLS connection established 
from macpro[192.168.1.253]: TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 
bits)
Jul 13 20:48:09 mail postfix/smtpd[10666]: E31B13FFF3: 
client=macpro[192.168.1.253], sasl_method=PLAIN, sasl_username=cae...@samsi.us 

Jul 13 20:48:09 mail postfix/cleanup[10656]: E31B13FFF3: 
message-id=>
Jul 13 20:48:09 mail postfix/qmgr[10476]: E31B13FFF3: from=>, size=316, nrcpt=1 (queue active)
Jul 13 20:48:10 mail postfix/smtpd[10684]: connect from localhost[127.0.0.1]
Jul 13 20:48:11 mail postfix/smtpd[10684]: disconnect from localhost[127.0.0.1]
Jul 13 20:48:11 mail postfix/smtpd[10684]: connect from localhost[127.0.0.1]
Jul 13 20:48:11 mail postfix/smtpd[10684]: disconnect from localhost[127.0.0.1]
Jul 13 20:48:12 mail postfix/smtpd[10687]: connect from localhost[127.0.0.1]
Jul 13 20:48:12 mail postfix/smtpd[10687]: A44093FFF4: 
client=localhost[127.0.0.1]
Jul 13 20:48:12 mail postfix/cleanup[10656]: A44093FFF4: 
message-id=>
Jul 13 20:48:12 mail postfix/qmgr[10476]: A44093FFF4: from=>, size=933, nrcpt=1 (queue active)
Jul 13 20:48:12 mail amavis[9530]: (09530-14) Passed CLEAN {RelayedInternal}, 
LOCAL [192.168.1.253]:65462 > -> 
>, Queue-ID: E31B13FFF3, Message-ID: 
>, mail_id: lnzQpKxIXYKy, 
Hits: -0.002, size: 316, queued_as: A44093FFF4, 2809 ms
Jul 13 20:48:12 mail postfix/smtp[10658]: E31B13FFF3: to=>, relay=127.0.0.1[127.0.0.1]:10024, delay=2.9, 
delays=0.03/0.01/0.02/2.8, dsn=2.0.0, status=sent (250 2.0.0 from 
MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as A44093FFF4)
Jul 13 20:48:12 mail postfix/qmgr[10476]: E31B13FFF3: removed
Jul 13 20:48:12 mail dovecot: lda(t...@yugi.us ): 
msgid=>: saved mail to INBOX
Jul 13 20:48:12 mail postfix/pipe[10664]: A44093FFF4: to=>, relay=dovecot, delay=0.18, delays=0.03/0.01/0/0.14, 
dsn=2.0.0, status=sent (delivered via dovecot service)
Jul 13 20:48:12 mail postfix/qmgr[10476]: A44093FFF4: removed

Postfix config:

alias_maps = hash:/etc/aliases,hash:/var/lib/mailman/data/aliases
append_dot_mydomain = no
biff = no
broken_sasl_auth_clients = yes
config_directory = /etc/postfix
content_filter = amavis:[127.0.0.1]:10024
disable_vrfy_command = yes
dovecot_destination_recipient_limit = 1
enable_original_recipient = no
header_checks = regexp:/etc/postfix/header_checks
inet_interfaces = all
mailbox_size_limit = 0
mailman_destination_recipient_limit = 1
maximal_backoff_time = 8000s
maximal_queue_lifetime = 7d
minimal_backoff_time = 1000s
mydestination =
myhostname = mail.samsi.us 
mynetworks = 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
mynetworks_style = host
myorigin = /etc/hostname
readme_directory = no
recipient_delimiter = +
relay_domains = mail.samsi.us 
smtp_helo_timeout = 60s
smtpd_banner = $myhostname ESMTP $mail_name
smtpd_delay_reject = yes
smtpd_hard_error_limit = 12
smtpd_helo_required = yes
smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated, 
reject_invalid_helo_hostname, reject_non_fqdn_helo_hostname, 
reject_unknown_helo_hostname, reject_non_fqdn_hostname, reject_invalid_hostname
smtpd_recipient_limit = 16
smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, 
reject_unauth_destination, reject_invalid_hostname, reject_non_fqdn_hostname, 
reject_non_fqdn_sender, reject_non_fqdn_recipient, 
reject_unknown_sender_domain, reject_unknown_recipient_domain, 
reject_rbl_client sbl.spamhaus.org , 
reject_rbl_client cbl.abuseat.org , reject_rbl_client 
dul.dnsbl.sorbs.net 
smtpd_sasl_auth_enable = yes
smtpd_sasl_authenticated_header = yes
smtpd_sasl_local_domain =
smtpd_sasl_path = private/auth
smtpd_sasl_security_options = noanonymous
smtpd_sasl_type = dovecot
smtpd_soft_error_limit = 3
smtpd_tls_auth_only = yes
smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_exclude_ciphers = aNULL, eNULL, EXPORT, DES, RC4, MD5, PSK, aECDH, 
EDH-DSS-DES-CBC3-SHA, EDH-RSA-DES-CDC3-SHA, KRB5-DE5, CBC3-SHA
smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key

Re: [Mailman-Users] MailMan won't send list emails

[Mark Sapiro]

On 07/13/2016 05:35 PM, Caesar Samsi wrote:
> Hi Mark,
> 
> Thank you for rendering aid.
> 
> Caesar.
> 
>> On Jul 13, 2016, at 12:28 PM, Mark Sapiro > > wrote:
>>
>>
>> I don't know where this comes from.
>>
>>
>>> /etc/aliases: - *Caesar*: I’ve removed it from the configuration


My remark was about the contents of
/var/lib/mailman/data/virtual-mailman, not /etc/aliases. You probably do
want /etc/aliases in your Postfix config.


>>> /var/lib/mailman/data/aliases: *Caesar*: This is generated by
>>> bin/genaliases, what should I do with this?

See below.


>>> /etc/postfix/transport:
>>>
>>> mail.samsi.us    mailman:

You will want to remove /etc/postfix/transport from transport_maps in
main.cf.


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


The above in master.cf will be unnecessary, but leaving it won't matter
if you don't reference the mailman transport in transport_maps.


>> You are using postfix-to-mailman.py for all mail to the mail.samsi.us
>> 
>> domain.
>>
>> See  and decide whether you want to
>> use postfix-to-mailman.py or Postfix-Mailman integration. *Caesar*:
>> I’d like to use the official Postfix-Mailman integration


OK.
...

> mm_cfg.py attached.
> 
> 
> 
> Log entries for list message (list address: t...@yugi.us)
> 
> Jul 11 17:06:14 mail postfix/cleanup[7937]: 2737340147:
> message-id=
> Jul 11 17:06:14 mail postfix/qmgr[7604]: 2737340147:
> from=, size=2232,
> nrcpt=1 (queue active)
> Jul 11 17:06:14 mail postfix/smtpd[7933]: disconnect from localhost[::1]
> Jul 11 17:06:17 mail postfix/smtpd[7944]: connect from localhost[127.0.0.1]
> Jul 11 17:06:17 mail postfix/smtpd[7944]: 9634C40148:
> client=localhost[127.0.0.1]
> Jul 11 17:06:17 mail postfix/cleanup[7937]: 9634C40148:
> message-id=
> Jul 11 17:06:17 mail postfix/qmgr[7604]: 9634C40148:
> from=, size=2873,
> nrcpt=1 (queue active)
> Jul 11 17:06:17 mail amavis[7745]: (07745-03) Passed CLEAN
> {RelayedInternal}, LOCAL [::1]:55664  -> 
> , Queue-ID: 2737340147, Message-ID:
> , mail_id: 5M0RPAagfqDZ, Hits:
> 0.274, size: 2232, queued_as: 9634C40148, 3472 ms
> Jul 11 17:06:17 mail postfix/smtp[7939]: 2737340147: to=, 
> relay=127.0.0.1[127.0.0.1]:10024, delay=3.6,
> delays=0.1/0.04/0.02/3.5, dsn=2.0.0, status=sent (250 2.0.0 from
> MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 9634C40148)
> Jul 11 17:06:17 mail postfix/qmgr[7604]: 2737340147: removed
> Jul 11 17:06:17 mail dovecot: lda(cae...@samsi.us):
> msgid=: saved mail to INBOX
> Jul 11 17:06:17 mail postfix/pipe[7945]: 9634C40148: to=, 
> relay=dovecot, delay=0.18,
> delays=0.03/0.03/0/0.13, dsn=2.0.0, status=sent (delivered via dovecot
> service)
> Jul 11 17:06:17 mail postfix/qmgr[7604]: 9634C40148: removed
> 


All these messages are from a message from Mailman to cae...@samsi.us
which was apparently delivered appropriately.

Are you able to send mail to t...@yugi.us and have it delivered to
Mailman? If not, what are the log messages related to that?

Re: mm_cfg.py It all looks OK. I'm only quoting what I'm commenting about.


> #-
> # Default domain for email addresses of newly created MLs
> DEFAULT_EMAIL_HOST = 'yugi.us'
> #-
> # Default host for web interface of newly created MLs
> DEFAULT_URL_HOST   = 'mail.samsi.us'
> #-
> # Required when setting any of its arguments.
> #add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)


The above is good.



> MTA='Postfix'
> SMTPHOST = 'localhost'
> SMTPPORT = 25

The above are good although only MTA='Postfix' is not a default.


> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['yugi.us']

This is good if yugi.us is a Postfix virtual alias domain. It also
explains the

t...@yugi.us test

entry in /var/lib/mailman/data/virtual-mailman but it doesn't explain
why there aren't 9 more entries like

test-ad...@yugi.us test-admin
test-boun...@yugi.us test-bounces
...


See the manual at ,
 and
 for
information on configuring Postfix, and if you continue to have trouble,
post the output of 'postconf -n' and the relevant Postfix log entries.

-- 
Mark Sapiro The highway is for 

Re: [Mailman-Users] MailMan won't send list emails

[Caesar Samsi]

Hi Mark,

Thank you for rendering aid.

Caesar.

> On Jul 13, 2016, at 12:28 PM, Mark Sapiro  wrote:
> 
> 
> I don't know where this comes from.
> 
> 
>> /etc/aliases: - Caesar: I’ve removed it from the configuration
> ...
>> /var/lib/mailman/data/aliases: Caesar: This is generated by bin/genaliases, 
>> what should I do with this?
> ...
>> 
> 
> 
> aliases look OK, but...
> 
> 
>> /etc/postfix/transport:
>> 
>> mail.samsi.us   mailman:
>> 
>> /etc/postfix/master.cf
>> 
>> mailman   unix  -   n   n   -   -   pipe
>>  flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
>>  ${nexthop} ${user}
> 
> 
> You are using postfix-to-mailman.py for all mail to the mail.samsi.us
> domain.
> 
> See  and decide whether you want to
> use postfix-to-mailman.py or Postfix-Mailman integration. Caesar: I’d like to 
> use the official Postfix-Mailman integration
> 
> Once you have decided that, if you are still having problems, please
> provide the contents of mm_cfg.py and the Postfix log entries for a
> message sent to a mailman list.
> 
> -- 
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> --
> Mailman-Users mailing list Mailman-Users@python.org
> https://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> Unsubscribe: 
> https://mail.python.org/mailman/options/mailman-users/mailinglist%40samsi.us

mm_cfg.py attached.


Log entries for list message (list address: t...@yugi.us)

Jul 11 17:06:14 mail postfix/cleanup[7937]: 2737340147: 
message-id=
Jul 11 17:06:14 mail postfix/qmgr[7604]: 2737340147: 
from=, size=2232, nrcpt=1 (queue active)
Jul 11 17:06:14 mail postfix/smtpd[7933]: disconnect from localhost[::1]
Jul 11 17:06:17 mail postfix/smtpd[7944]: connect from localhost[127.0.0.1]
Jul 11 17:06:17 mail postfix/smtpd[7944]: 9634C40148: 
client=localhost[127.0.0.1]
Jul 11 17:06:17 mail postfix/cleanup[7937]: 9634C40148: 
message-id=
Jul 11 17:06:17 mail postfix/qmgr[7604]: 9634C40148: 
from=, size=2873, nrcpt=1 (queue active)
Jul 11 17:06:17 mail amavis[7745]: (07745-03) Passed CLEAN {RelayedInternal}, 
LOCAL [::1]:55664  -> , Queue-ID: 
2737340147, Message-ID: , mail_id: 
5M0RPAagfqDZ, Hits: 0.274, size: 2232, queued_as: 9634C40148, 3472 ms
Jul 11 17:06:17 mail postfix/smtp[7939]: 2737340147: to=, 
relay=127.0.0.1[127.0.0.1]:10024, delay=3.6, delays=0.1/0.04/0.02/3.5, 
dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 
Ok: queued as 9634C40148)
Jul 11 17:06:17 mail postfix/qmgr[7604]: 2737340147: removed
Jul 11 17:06:17 mail dovecot: lda(cae...@samsi.us): 
msgid=: saved mail to INBOX
Jul 11 17:06:17 mail postfix/pipe[7945]: 9634C40148: to=, 
relay=dovecot, delay=0.18, delays=0.03/0.03/0/0.13, dsn=2.0.0, status=sent 
(delivered via dovecot service)
Jul 11 17:06:17 mail postfix/qmgr[7604]: 9634C40148: removed

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] MailMan won't send list emails

[Mark Sapiro]

On 07/12/2016 03:55 PM, Caesar Samsi wrote:
> [Adding information]
> 
> Postfix /etc/postfix/main.cf configuration:
> 
> virtual_alias_maps =
> mysql:/etc/postfix/mysql_virtual_alias_maps.cf,
> mysql:/etc/postfix/mysql_virtual_alias_domainaliases_maps.cf,
> hash:/var/lib/mailman/data/virtual-mailman
> 
> alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases
> relay_domains = mail.samsi.us
> mailman_destination_recipient_limit = 1
> transport_maps = hash:/etc/postfix/transport
> smtpd_reject_unlisted_sender = no
> 
> /var/lib/mailman/data/virtual-mailman:
> 
> t...@yugi.ustest


I don't know where this comes from.


> /etc/aliases:
...
> /var/lib/mailman/data/aliases:
...
> 


aliases look OK, but...


> /etc/postfix/transport:
> 
> mail.samsi.us   mailman:
> 
> /etc/postfix/master.cf
> 
> mailman   unix  -   n   n   -   -   pipe
>   flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
>   ${nexthop} ${user}


You are using postfix-to-mailman.py for all mail to the mail.samsi.us
domain.

See  and decide whether you want to
use postfix-to-mailman.py or Postfix-Mailman integration.

Once you have decided that, if you are still having problems, please
provide the contents of mm_cfg.py and the Postfix log entries for a
message sent to a mailman list.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Chinese characters spam filter?

[Mark Sapiro]

On 07/13/2016 04:38 AM, Yasuhito FUTATSUKI wrote:
>  
>> I think it is better to hold string attributes of mm_cfg and mlist class
>> as Unicode than site_language code or list's preferred language code
>> encoded (but I know it is so trouble to do so).
> And then on pattern matching on message pipeline is done with Unicode
> rather than list's prefered language.


I have been working on a change to do exactly that. I.e. collect the
headers for matching with header_filter_rules as unicode and match the
patterns as unicode.

This is very difficult to do on a list whose preferred_language
character set doesn't support the characters in the header_filter_rules
patterns, e.g., trying to match Chinese characters in Subject: headers
on an English language list.

The major issue is when the character set of the form is say us-ascii
and one enters non-ascii as a pattern, it is up to the browser to decide
how to encode that. In at least one case with Firefox, characters which
are in the windows-1252 character set are encoded as that and others as
XML numeric references. I can easily deal with converting the XML
numeric references to unicodes, but I don't know in what charset the
other characters are encoded.

 Yes, I know that everything should be unicode and utf-8 encoded
regardless of language, but that isn't going to happen in MM 2.1.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problems with Mail Delivery - was: Mailman-Users Digest, Vol 149, Issue 16

[Mark Sapiro]

On 07/13/2016 04:00 AM, Gines Granados Bayona wrote:


Please do not 'reply' to digests or if replying to a digest, provide a
meaningful Subject:.


> Hello, well to everybody, thank you very much Mark Sapiro m...@msapiro.net,
> i do  the steps and it has worked effectively, but It weirdest other error
> has occurred, I now send email that is outside the local network on
> Internet but lan I can not send email giving errors like that attached,
> what do I lacked configure now?
...
> Jul 13 12:43:29 2016 (8111) All recipients refused: {'ginesgb@**.net':
> (550, '5.1.1 : Recipient address rejected: User unknown
> in local recipient table')}, msgid:
> 
> Jul 13 12:43:29 2016 (8111) delivery to ginesgb@**.net failed with code
> 550: 5.1.1 : Recipient address rejected: User unknown
> in local recipient table


This is a Postfix configuration issue. Your local MTA can't deliver to
this local recipient.

We may be able to help, but in order to do so, we need more information.

Is 'ginesgb' a user on this server with a mailbox on this server, or
just elsewhere on your LAN?

What is the output from 'postconf -n'?


> 2016-07-12 21:22 GMT+02:00 :
> 
>> Send Mailman-Users mailing list submissions to
>> mailman-users@python.org
...
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Mailman-Users digest..."


And please NEVER quote an entire digest in your reply,

And legal disclaimers such as attached to your mail are not appropriate
for mail to a publicly archived mailman list.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] MailMan won't send list emails

[Caesar Samsi]

Hi there,

I’ve been working on this for 1 day and getting frustrated.

Everything appears to be setup correctly (lists can be created, list emails are 
received, I can see emails received in the list mailbox.

MailMan sends out notification emails to owners and subscribers. Confirmation 
email is sent out and processed via web page. 

The only thing left is sending out received emails.

I don’t know where to begin troubleshooting this.

Thanks, Caesar.
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] MailMan won't send list emails

[Caesar Samsi]

[Adding information]

Postfix /etc/postfix/main.cf configuration:

virtual_alias_maps =
mysql:/etc/postfix/mysql_virtual_alias_maps.cf,
mysql:/etc/postfix/mysql_virtual_alias_domainaliases_maps.cf,
hash:/var/lib/mailman/data/virtual-mailman

alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases
relay_domains = mail.samsi.us
mailman_destination_recipient_limit = 1
transport_maps = hash:/etc/postfix/transport
smtpd_reject_unlisted_sender = no

/var/lib/mailman/data/virtual-mailman:

t...@yugi.ustest

/etc/aliases:

# /etc/aliases
mailer-daemon: postmaster
postmaster: root
nobody: root
hostmaster: root
usenet: root
news: root
webmaster: root
www: root
ftp: root
abuse: root
noc: root
security: root
clamav: root
monit: root

/var/lib/mailman/data/aliases:

# This file is generated by Mailman, and is kept in sync with the
# binary hash file aliases.db.  YOU SHOULD NOT MANUALLY EDIT THIS FILE
# unless you know what you're doing, and can keep the two files properly
# in sync.  If you screw it up, you're on your own.

# The ultimate loop stopper address
mailman-loop: /var/lib/mailman/data/owner-bounces.mbox

# STANZA START: mailman
# CREATED: Tue Jul 12 12:31:00 2016
mailman: "|/var/lib/mailman/mail/mailman post mailman"
mailman-admin:   "|/var/lib/mailman/mail/mailman admin mailman"
mailman-bounces: "|/var/lib/mailman/mail/mailman bounces mailman"
mailman-confirm: "|/var/lib/mailman/mail/mailman confirm mailman"
mailman-join:"|/var/lib/mailman/mail/mailman join mailman"
mailman-leave:   "|/var/lib/mailman/mail/mailman leave mailman"
mailman-owner:   "|/var/lib/mailman/mail/mailman owner mailman"
mailman-request: "|/var/lib/mailman/mail/mailman request mailman"
mailman-subscribe:   "|/var/lib/mailman/mail/mailman subscribe mailman"
mailman-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe mailman"
# STANZA END: mailman

# STANZA START: test
# CREATED: Tue Jul 12 12:31:00 2016
test: "|/var/lib/mailman/mail/mailman post test"
test-admin:   "|/var/lib/mailman/mail/mailman admin test"
test-bounces: "|/var/lib/mailman/mail/mailman bounces test"
test-confirm: "|/var/lib/mailman/mail/mailman confirm test"
test-join:"|/var/lib/mailman/mail/mailman join test"
test-leave:   "|/var/lib/mailman/mail/mailman leave test"
test-owner:   "|/var/lib/mailman/mail/mailman owner test"
test-request: "|/var/lib/mailman/mail/mailman request test"
test-subscribe:   "|/var/lib/mailman/mail/mailman subscribe test"
test-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe test"
# STANZA END: test

/etc/postfix/transport:

mail.samsi.us   mailman:

/etc/postfix/master.cf

mailman   unix  -   n   n   -   -   pipe
  flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
  ${nexthop} ${user}

> On Jul 12, 2016, at 1:10 PM, Caesar Samsi  wrote:
> 
> [resending, sent it before confirmation was completed earlier]
> 
> Hi there,
> 
> I’ve been working on this for 1 day and getting frustrated.
> 
> Everything appears to be setup correctly (lists can be created, list emails 
> are received, I can see emails received in the list mailbox.
> 
> MailMan sends out notification emails to owners and subscribers. Confirmation 
> email is sent out and processed via web page. 
> 
> The only thing left is sending out received emails.
> 
> I don’t know where to begin troubleshooting this.
> 
> Thanks, Caesar.
> 

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 2's future (was Re: Filtering out Digest replies)

[Richard Shetron]

On 7/13/2016 12:16 PM, Barry Warsaw wrote:

On Jul 12, 2016, at 12:22 PM, Mark Sapiro wrote:

[snip end of life comments]

One thing that makes end of life either easier to handle or harder is:

1)  Documentation of the changes and the new system.

2)  Conversion aids.  At least a program to check a prior system and 
report all the problems in converting to the new system.  Best is a 
program that can do a full conversion from the old system to the new one 
with the minimal operator intervention.  Yes, I've done that, I worked 
for a company for 10 years and one of the standard things was converting 
new customers to our system, exporting data for those going away, and 
upgrading those on older versions to the newest version.


3)  Documentation.  I say this twice to emphasis it!


--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman 2's future (was Re: Filtering out Digest replies)

[Barry Warsaw]

On Jul 12, 2016, at 12:22 PM, Mark Sapiro wrote:

>It depends on how you define "end of life". Granted there will be MM 2.1
>lists in use for a very long time. There may still even be Mailman 2.0
>lists in active use.
>
>The real question is not how long there will be users, but how long will
>Mailman 2.1 be actively supported and maintained, and whether it makes
>sense for new installations to use a package with little or no further
>development in sight vs. one with an active and growing development and
>support community.

Like all FLOSS software, future development and support is highly dependent on
finding volunteers interested enough to donate their time to work on it.  It's
rare to be paid to work on FLOSS, and I can only say that *I* am not paid to
work on Mailman.

Mark is my hero, for long ago having taken over the task of maintaining
Mailman 2.1 and allowing me to concentrate on Mailman 3.  I greatly appreciate
Steve and all of you who continue to dedicate your time to help each other,
solve problems, and keep the Mailman community thriving.

I have no interest or time to devote to Mailman 2.  The code is 20 years old,
and like Python 2, I find it very hard to get motivated to wade into it.  Mark
knows way more about it than I remember at this point anyway.  I am spending
my free time trying to make Mailman 3 a compelling and stable upgrade path,
with code that's a joy to work in, an architecture that is clean, flexible,
and robust, and a universe of tools and subprojects that bring the Mailman we
love forward to modern practices, and which integrate better with all the
other outlets people have for online communication.

Just like with Python 2, Mailman 2.1 will continue to be actively and happily
used for many years to come.  If and when Mark decides to spend more time on
Mailman 3 (\o/) others in this community can rise to the challenge of
continuing to support Mailman 2.  That's what a volunteer community is all
about.

There is lots of fun stuff to do, and I call on you to find areas of interest
to get involved in.  Almost anything you *want* to do *needs* to be done, and
we developers are a nice bunch of people, so please join us!

Cheers,
-Barry


pgp0x1WbwS4lG.pgp
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Command line access to Mailman 3 (was Re: Filtering out Digest replies)

[Barry Warsaw]

On Jul 12, 2016, at 04:04 PM, Stephen J. Turnbull wrote:

>Thomas Gramstad writes:
>
> > There is also the issue of listadmin, the script for command line 
> > processing of list moderation requests. I'm not sure this script 
> > is being updated currently, and so probably does not work with 
> > Mailman 3(?).  
>
>I don't know if it's been integrated yet, but mailmanclient has a nice
>command interpreter that a GSoC student built for us.  Even if your
>particular use case isn't supported yet, it will be easy to do so.
>
>I think you'll also find Postorius much more efficient than the
>current web interface.  That may not be enough since you say managing
>moderation with the current interface is out of the question, but
>since moderation is an activity that needs human input, and UI changes
>(ie, use of command line) were enough to make it feasible, Postorius
>is something you should look at before deciding to stay with a product
>after end-of-line.

Mailman 3 has a very rich REST API which can control and administer the core
system.  In fact, this is exactly how Postorius and HyperKitty work, via
mailmanclient, the official Python bindings for the REST API.  Being
HTTP+JSON, you can in fact talk to Core's REST API using any language you want
(even curl for example).

However, it's also important to understand that Core's REST API is an
administrative API with full access and no authentication (other than Basic
AUTH).  It is intended to be exposed on localhost only.

It's long been discussed to create an "authenticating proxy" which could be
exposed on any public IP, and which would allow site admins, list admins,
moderators, and users to script the Core, performing any operations that their
authorization level permits.  Andrew Stuart wrote a project called mailmania
(available on GitLab) which implements one take on this.  At Pycon 2016, the
Mailman sprinters discussed how to move forward on an official proxy, taking
inspiration from mailmania.  I think we fleshed out a good approach which will
be much richer than any MM2 scripting facility, and could be one of the killer
apps for MM3 (including IMHO HyperKitty's ability to post from the web, and
Postorius's vastly better U/I).

We even have name for the project, Lemme and a project page:
https://gitlab.com/mailman/lemme/tree/master

Several of us are going to start working on this after the MM3.1 release goes
out (hopefully in the next month or so).  It will take work in the Core as
well as work on Lemme, so we invite anybody interested in helping out to join
us over in mailman-developers.

Cheers,
-Barry


pgp_88uGAML0H.pgp
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Filtering out Digest replies

[Jim Popovitch]

On Tue, Jul 12, 2016 at 10:00 PM, Stephen J. Turnbull
 wrote:
> Whose interest in this task is waxing?  I'm not going to say that
> user-supported software whose core developers have moved
> on can't work (eg, qmail), but it's rare.  And this particular thread
> requires a programmer to hack on it.  Are there volunteers?

Is the issue really lack of people who can commit?  Every time I look
at launchpad I'm amazed at the number of active participants.

> If not, the way forward is Mailman 3.

No one doubts that.   The timing for that is what is in question.
Considering LTS releases, MM2.1 could be in some level of production
until 2019.   Someone from the MM team will have to deal with CVEs,
etc., and I guess everybody is presuming that will still be Mark.
What I doubt we will see is a mass migration to MM3, people just don't
normally do that until in-house milestones (new infrastructure,
hardware crashed and all data is lost, etc.)

-Jim P.
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] How to actively read the list online?

[Lucio Chiappetti]

On Wed, 13 Jul 2016, Stephen J. Turnbull wrote:

Lucio Chiappetti writes:



> Anyhow, getting a self-refreshing html page is just a matter of adding a
>  tag to the 

Sure, but if the page itself is static (as in a conventional mailing
list archive), that won't help.  The archive host has to be prepared
to feed *new* pages, not refresh the old one, when accessed.


Might be not that different (although perhaps is an overkill).

There is no much difference in refreshing a page with a click of the user, 
and having the browser requesting a refresh with a meta-equiv-refresh if 
the underlying page has changed.


I do use the trick with some of my pages, some are CGI scripts which 
auto-refresh, but in other cases the page can be modified by a crontab 
script (I say overkill because if the meta-equiv-refresh asks for a 
refresh every minute, and the crontab updates the page every 15-30 min 
most of the refresh will be void)


Consider a standard mailman thread archive like e.g.
https://listmgr.nrao.edu/pipermail/fitsbits/2016-July/thread.html

If somebody will make a new post, and I reload the archive page, I will 
see the new message (I use this trick to verify a message was archived 
after I sent it).


If one could MODIFY the standard format of the archive page in mailman to 
prepend the meta-equiv-refresh (and I do not know how easy is that. I've 
never personalised any of the mailman HTML pages although I know for some

is possible, maybe one has to patch code) ... that would do the trick.

--

Lucio Chiappetti - INAF/IASF - via Bassini 15 - I-20133 Milano (Italy)
For more info : http://www.iasf-milano.inaf.it/~lucio/personal.html

Do not like Firefox >=29 ?  Get Pale Moon !  http://www.palemoon.org
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Chinese characters spam filter?

[Yasuhito FUTATSUKI]

On 07/13/16 13:15, I wrote:
> On 07/13/16 03:47, Mark Sapiro wrote:
>> On 07/12/2016 12:03 AM, Stephen J. Turnbull wrote:
>>> At an earlier stage, you could also just do a trial re-encoding with
>>> the list preferred codec, set errors = 'strict', catch the Exception,
>>> and re-raise as a Hold (or Discard, according to per-list policy).
>>> (Then discard the output.)  I would prefer this solution, I think, as
>>> creating regexps turns out to be an issue for many list owners.
>>>
>>> People would have to learn not to use emoji in headers, of course, or
>>> suffer moderation delays or even discards.
>>
>> I think this will have too many undesired effects. Not just emoji, but
>> accented latin or CJK characters, etc. in display names would I think be
>> real problems, even on English language lists.
> 
> I suggest to use variable to select handler from 'replace' (for backword
> compatibility), 'xmlcharrefreplace', or 'backslashreplace'
or 'strict' with catching Exception
>   in mm_cfg.py.
 
> I think it is better to hold string attributes of mm_cfg and mlist class
> as Unicode than site_language code or list's preferred language code
> encoded (but I know it is so trouble to do so).
And then on pattern matching on message pipeline is done with Unicode
rather than list's prefered language.
-- 
Yasuhito FUTATSUKI 
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org