Re: [Mailman-Users] dnspython not found error

[Mark Sapiro]

On 05/04/2016 11:27 AM, David Newman wrote:
> Had to reinstall the Mailman port (not pkg) on a FreeBSD 10.3-RELEASE
> system after updating some ports due to security vulnerabilities.
> Several other packages also required rebuild to point to new shared objects.
> 
> The Mailman build failed, saying 'dnspython not found' even though that
> port is installed:
> 
> root@mail:/usr/ports/mail/mailman # pkg info | grep dnspython
> py27-dnspython-1.12.0  DNS toolkit for Python


what happens when you invoke /usr/local/bin/python2.7 and then do

import dns.resolver

Does that succeed or throw ImportError?

If it succeeds, then configure should too as that's what it's doing and
the python it's using.

If it throws ImportError, then something is wrong in that the python at
/usr/local/bin/python2.7 is not able to access the dnspython package.

-- 
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] Order of operation - config files

[Mark Sapiro]

On 05/04/2016 10:48 AM, Beu, Ed (DOA) wrote:
> 
> DEFAULT_DEFAULT_MEMBER_MODERATION = Yes
 The double DEFAULT_DEFAULT on this variable appears to be the only doubled 
 default in the Defaults.py file. And, using it in the same manner in the 
 MM_CFG.py file appears to be the only way to get it to work when creating 
 a new list.


That is correct. It is called DEFAULT_DEFAULT_MEMBER_MODERATION because
it establishes the new list default for the list attribute
default_member_moderation. For all list attributes named xxx which have
a default setting in Defaults.py, the Defaults.py setting is called
DEFAULT_XXX. For this one, the setting name begins with default... so
the Defaults.py default is DEFAULT_DEFAULT...

mm_cfg.py settings are overrides for the Defaults.py settings. Anything
defined in mm_cfg.py overrides the definition of the setting with the
same name in Defaults.py. Anything defined in mm_cfg.py which is not
defined in Defaults.py is not referenced in the code and is therefore
meaningless.


> For the occasional 'discussion' list I have created a config file 
> (discuss.config) to import into the new list to change 'Member Moderation' to 
> No, but it does not take effect.
> 
> For example, I'm using this command: .../bin> ./newlist -q testdiscuss 
> ed@alaska.gov 12345678;./config_list -i 
> discuss.config testdiscuss
 I change the entry in the MM_CFG.py file to:
> DEFAULT_DEFAULT_MEMBER_MODERATION = 1(1 rather than Yes)


That doesn't matter. Defaults.py defines Yes = yes = On = on = True and
those things and also 1 are all equivalent in this respect.


 used the following statement in my discuss.config file - and it's working 
 now
> default_member_moderation = 0


But config_list doesn't define things like Yes, yes, On, on, No, no,
Off, off so you can't use them in setting list attributes. You have to
use the actual (lower case) list attribute name, not a name from
Defaults.py and you have to use values like 0, 1, False or True, not
Yes, yes, On, on, No, no, Off or off.


> Is it not possible to override the mm_cfg.py file entries with a config_list 
> -i command?
 apparently the config_list -i does run after mm_cfg.py!!


The Defaults.py/mm_cfg.py DEFAULT settings set list attributes when a
list is created via newlist or the web UI. mm_cfg.py doesn't 'run' at
all in the sense that new_list or config_list run. pretty much
everything in Mailman imports mm_cfg.py (which in turn imports
Defaults.py before setting any of it's overrides. This establishes the
site configuration for Mailman.

When you run newlist, it creates the list and the list creation process
uses the DEFAULT... settings from Defaults.py/mm_cfg.py in establishing
the settings for that list. config_list -i operates on an existing list
and sets those list attributes that are in it's input. So yes,
config_list -i will set anything in it's input. mm_cfg.py DEFAULT
settings do not come into play at this point.

The important thing to note is that once a list is created, changes to
DEFAULT... settings in mm_cfg.py will not affect anything on an existing
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] Order of operation - config files

[Beu, Ed (DOA)]

Hi, I got it working... 

From: Beu, Ed (DOA)
Sent: Wednesday, May 04, 2016 8:49 AM
To: 'mailman-users@python.org' 
Subject: Order of operation - config files

Hello,

We have a test installation of Mailman 2.1.20 (CSW) running on Solaris 10. 
Production version will be running on CentOS.

Since most of our lists are 'Announcement' type lists, I have put the following 
in the mm_cfg.py file:

DEFAULT_DEFAULT_MEMBER_MODERATION = Yes
>>> The double DEFAULT_DEFAULT on this variable appears to be the only doubled 
>>> default in the Defaults.py file. And, using it in the same manner in the 
>>> MM_CFG.py file appears to be the only way to get it to work when creating a 
>>> new list.

For the occasional 'discussion' list I have created a config file 
(discuss.config) to import into the new list to change 'Member Moderation' to 
No, but it does not take effect.

For example, I'm using this command: .../bin> ./newlist -q testdiscuss 
ed@alaska.gov 12345678;./config_list -i 
discuss.config testdiscuss
>>> I change the entry in the MM_CFG.py file to:
DEFAULT_DEFAULT_MEMBER_MODERATION = 1(1 rather than Yes)

>>> used the following statement in my discuss.config file - and it's working 
>>> now
default_member_moderation = 0

Is it not possible to override the mm_cfg.py file entries with a config_list -i 
command?
>>> apparently the config_list -i does run after mm_cfg.py!!

Thanks in advance for any assistance!

~Ed

Ed Beu , Systems Programmer
Enterprise Technology Services
Department of Administration
619 E Shipcreek Ave., Ste 232
Anchorage, AK 99501-1677
[ETSLogo]
*Desk:(907)269-6790
?Fax: (907)269-6719
* ed@alaska.gov
" http://www.doa.alaska.gov/ets/



--
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] Order of operation - config files

[Beu, Ed (DOA)]

Hello,

We have a test installation of Mailman 2.1.20 (CSW) running on Solaris 10. 
Production version will be running on CentOS.

Since most of our lists are 'Announcement' type lists, I have put the following 
in the mm_cfg.py file:

DEFAULT_DEFAULT_MEMBER_MODERATION = Yes

For the occasional 'discussion' list I have created a config file 
(discuss.config) to import into the new list to change 'Member Moderation' to 
No, but it does not take effect.

For example, I'm using this command: .../bin> ./newlist -q testdiscuss 
ed@alaska.gov 12345678;./config_list -i discuss.config testdiscuss

Is it not possible to override the mm_cfg.py file entries with a config_list -i 
command?

Thanks in advance for any assistance!

~Ed

Ed Beu , Systems Programmer
Enterprise Technology Services
Department of Administration
619 E Shipcreek Ave., Ste 232
Anchorage, AK 99501-1677
[ETSLogo]
*Desk:(907)269-6790
?Fax: (907)269-6719
* ed@alaska.gov
" http://www.doa.alaska.gov/ets/



--
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] dnspython not found error

[David Newman]

Had to reinstall the Mailman port (not pkg) on a FreeBSD 10.3-RELEASE
system after updating some ports due to security vulnerabilities.
Several other packages also required rebuild to point to new shared objects.

The Mailman build failed, saying 'dnspython not found' even though that
port is installed:

root@mail:/usr/ports/mail/mailman # pkg info | grep dnspython
py27-dnspython-1.12.0  DNS toolkit for Python

I've attached the config log, and pasted below the list of installed ports.

How to get Mailman working again?

Thanks!

dn


root@mail:/usr/ports/mail/mailman # /usr/local/sbin/pkg-static info -g
-Ea | cut -d ' ' -f 1
altermime-0.3.11.a1
amavisd-new-2.10.1_1,1
ap24-mod_wsgi3-3.5
apache24-2.4.20_1
apr-1.5.2.1.5.4
arc-5.21p
arj-3.10.22_4
aspell-0.60.6.1_5
autoconf-2.69
autoconf-wrapper-20131203
automake-1.15_1
automake-wrapper-20131203
awstats-7.4,1
bacula-client-7.4.0_2
bash-static-4.3.42_1
bison-2.7.1,1
ca_root_nss-3.22.2
cabextract-1.6
cclient-2007f_2,1
clamav-0.99.1
cmake-3.5.2
cmake-modules-3.5.2
compat9x-amd64-9.3.903000.20160128
curl-7.47.0
cyrus-sasl-2.1.26_12
db5-5.3.28_3
dialog4ports-0.1.5_2
dovecot-pigeonhole-0.4.14
dovecot2-2.2.24
expat-2.1.0_3
fakeroot-1.20.2
file-5.25
freeze-2.5_2
gdbm-1.11_2
gettext-runtime-0.19.7
gettext-tools-0.19.7
gmake-4.1_2
gmake-lite-4.1_1
gnupg1-1.4.20
help2man-1.43.3_1
icu-55.1
indexinfo-0.2.4
json-c-0.12_2
jsoncpp-0.6.0.r2_2
lha-1.14i_6
libarchive-3.1.2_6,1
libcheck-0.10.0
libedit-3.1.20150325_2
libffi-3.2.1
libgcrypt-1.7.0
libgpg-error-1.22
libiconv-1.14_9
libidn-1.31
libltdl-2.4.6
libmcrypt-2.5.8_3
libressl-2.3.4
libssh2-1.7.0,2
libtool-2.4.6
libxml2-2.9.3
libxslt-1.1.28_8
logrotate-3.9.2
logwatch-7.4.0_1
lzo2-2.09
lzop-1.03
m4-1.4.17_1,1
mod_php55-5.5.35
mysql56-client-5.6.30
mysql56-server-5.6.30
nomarch-1.4
oniguruma5-5.9.6_1
p0f-3.09b
p5-Archive-Zip-1.57
p5-Authen-SASL-2.16_1
p5-BerkeleyDB-0.55_1
p5-CPAN-Meta-2.150005
p5-Cache-FastMmap-1.43
p5-Canary-Stability-2011
p5-Config-IniFiles-2.88
p5-Convert-BinHex-1.125
p5-Convert-TNEF-0.18_1
p5-Convert-UUlib-1.50,1
p5-Crypt-CBC-2.33_1
p5-Crypt-DES-2.07_1
p5-Crypt-OpenSSL-Bignum-0.06
p5-Crypt-OpenSSL-RSA-0.28_1
p5-Crypt-OpenSSL-Random-0.11
p5-DBD-SQLite-1.50
p5-DBD-mysql-4.033
p5-DBI-1.636
p5-Digest-HMAC-1.03_1
p5-Digest-SHA1-2.13_1
p5-Encode-Detect-1.01_1
p5-Exporter-Tiny-0.042_1
p5-GSSAPI-0.28_1
p5-HTML-Parser-3.72
p5-HTML-Tagset-3.20_1
p5-HTTP-Date-6.02_1
p5-IO-Multiplex-1.13_1
p5-IO-Socket-INET6-2.72_1
p5-IO-Socket-IP-0.37
p5-IO-Socket-SSL-2.025
p5-IO-stringy-2.111
p5-Locale-gettext-1.06
p5-MIME-Base64-3.15
p5-MIME-Tools-5.507,2
p5-Mail-DKIM-0.40_2
p5-Mail-Tools-2.14
p5-Module-Build-0.4218
p5-Mozilla-CA-20160104
p5-Net-CIDR-0.18
p5-Net-DNS-1.05_1,1
p5-Net-IP-1.26_1
p5-Net-LibIDN-0.12_4
p5-Net-SNMP-6.0.1_1
p5-Net-SSLeay-1.74
p5-Net-Server-2.008_1
p5-Net-XWhois-0.90_5
p5-NetAddr-IP-4.078
p5-Socket-2.021
p5-Socket6-0.27
p5-TimeDate-2.30_2,1
p5-URI-1.71
p5-Unix-Syslog-1.1_1
p7zip-15.14
pcre-8.38_1
pecl-intl-3.0.0_2
perl5-5.20.3_12
php55-5.5.35
php55-bz2-5.5.35
php55-ctype-5.5.35
php55-dom-5.5.35
php55-filter-5.5.35
php55-gettext-5.5.35
php55-hash-5.5.35
php55-iconv-5.5.35
php55-imap-5.5.35
php55-json-5.5.35
php55-mbstring-5.5.35
php55-mcrypt-5.5.35
php55-mysql-5.5.35
php55-mysqli-5.5.35
php55-openssl-5.5.35
php55-pdo-5.5.35
php55-pdo_mysql-5.5.35
php55-pspell-5.5.35
php55-session-5.5.35
php55-simplexml-5.5.35
php55-xml-5.5.35
php55-zip-5.5.35
php55-zlib-5.5.35
pkg-1.7.2
pkgconf-0.9.12_1
popt-1.16_1
portmaster-3.17.9_2
postfix-3.1.0,1
py27-Babel-2.3.3
py27-Jinja2-2.8
py27-MarkupSafe-0.23
py27-MySQLdb-1.2.5
py27-alabaster-0.7.6
py27-bcrypt-0.4_2
py27-beautifulsoup-4.4.1
py27-cffi-1.5.0
py27-dnspython-1.12.0
py27-docutils-0.12
py27-enum34-1.0.4
py27-funcsigs-0.4
py27-idna-2.0
py27-ipaddress-1.0.16
py27-lxml-3.5.0
py27-mock-1.3.0_1
py27-netifaces-0.10.4
py27-pbr-1.8.1
py27-pip-8.0.2
py27-pyasn1-0.1.9
py27-pycparser-2.10
py27-pygments-2.1.3
py27-pystemmer-1.3.0_1
py27-pytz-2016.1,1
py27-setuptools27-20.0
py27-six-1.10.0
py27-snowballstemmer-1.2.0_1
py27-sphinx-1.3.1_2
py27-sphinx_rtd_theme-0.1.9
py27-sqlalchemy-0.7.10_2
py27-werkzeug-0.11.9
py27-zope.event-4.1.0
python2-2_3
python27-2.7.11_2
rar-5.3.0,3
re2c-0.14.3
ripole-0.2.2
roundcube-1.1.4_1,1
rpm2cpio-1.4_2
rsync-3.1.2_3
scons-2.5.0
spamassassin-3.4.1_6
sshguard-1.6.4_1
sudo-1.8.16
tinycdb-0.78_2
tnef-1.4.11
unarj-2.65_2
unrar-5.31,5
unzoo-4.4_2
vim-lite-7.4.1743
webpy-0.37
zoo-2.10.1_3



This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by configure, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  $ ./configure --with-python=/usr/local/bin/python2.7 --with-username=mailman 
--with-groupname=mailman --with-mail-gid=mailman --with-cgi-gid=www 
--with-permcheck=no --prefix=/usr/local/mailman --localstatedir=/var 
--mandir=/usr/local/man --infodir=/usr/local/mailman/info/ 
--build=amd64-portbld-freebsd10.3

## - ##
## Platform. ##

Re: [Mailman-Users] resend - mailman 2.1.21 - dmarc check problem

[Mark Sapiro]

On 05/04/2016 09:27 AM, Curtis Villamizar wrote:
> I'm resending this with a new subject.  The last email just
> disappeared (no bounce).  Maybe having
> DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL in the subject tripped an all
> caps in subject test.  (Or the moderator is slacking?)


A moderator (me) approved your post and cleared your mod bit
approximately 2 hours before you posted this. My reply to that post is
at .

I don't know why you didn't receive it. It was successfully sent per

May  4 10:36:04 mail postfix/smtp[22778]: 3r0LDW0F1DzFqP0:
to=,
relay=mta2-em1.orleans.occnc.com[50.252.223.140]:25, delay=42,
delays=0.08/0/31/11, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as
316BF9DDA)

(time stamp is UTC - 0400)

Maybe the ALL CAPS filtered it at your end.

-- 
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] disable DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL in mailman 2.1

[Mark Sapiro]

On 05/03/2016 12:26 PM, Curtis Villamizar wrote:
> By default DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL is set to
> https://publicsuffix.org/list/public_suffix_list.dat
> 
> I have mailman set up on an IPv6 only host and publicsuffix.org has no
> IPv6 address.  A near identical configuration is set up on a dual
> stack host.  Any email to the IPv6 only host fails with an entry in
> logs/error of the form "Unable to retrieve data from
> https://publicsuffix.org/list/public_suffix_list.dat:  [Errno 43] Protocol not supported>"


The log entry seems correct for this situation. The mail delivery
failure is unrelated - see below.


> In the mean time I would like to disable the use of
> DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL by setting it empty.  To do this
> it seems that I would need the following change:
> 
> --- Mailman/Utils.py.orig   2016-04-09 04:08:56.0 -0400
> +++ Mailman/Utils.py2016-05-03 14:37:12.683904000 -0400
> @@ -1205,6 +1205,8 @@
>  Domain which may be the same as the input."""
>  global s_dict
>  if not s_dict:
> -get_suffixes(mm_cfg.DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL)
> +if mm_cfg.DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL:
> +get_suffixes(mm_cfg.DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL)
>  hits = []
>  d = domain.lower().split('.')
> 
> This works for .com, .org, .net, etc but not for things like co.uk,
> etc (which in my case is not an issue).


This is a bug. I've created
 and have fixed it, but
not as above, although as above should work. The fix is at



> A second question is why does failing to access publicsuffix.org
> result in a hard fail rather than a soft fail?  The change I made just
> skips over get_suffixes and leaves s_dict empty.  It seems that
> get_suffixes does do a try and except which logs and returns, but then
> the mail gets rejected and the reason is not clear to me.  In
> logs/smtp-failure there is a message of the form "failed with code
> 554: 5.7.1 : Client host rejected: Access denied".


The above message in smtp-failure is saying Mailman is trying to send
mail to the list or whatever and the recipient MX for this delivery does
not allow IPv6 access to its MTA, at least not from you. This has
nothing to do with the changes you made to skip loading
DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL. I think it is going to be a
serious problem if you are trying to send mail in general because not
every recipient domain is going to be listening on port 25 at an IPv6
address.

I think if your outgoing MTA is connecting only to IPv6 addresses, you
will have difficulty delivering mail in general regardless of the source
of the mail.

As for as why it's a 554: 5.7.1 hard fail, That's the status your MTA is
giving to this condition. If you think this should be a 4xx status, you
may be able to configure that in your MTA.

-- 
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] resend - mailman 2.1.21 - dmarc check problem

[Curtis Villamizar]

I'm resending this with a new subject.  The last email just
disappeared (no bounce).  Maybe having
DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL in the subject tripped an all
caps in subject test.  (Or the moderator is slacking?)

By default DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL is set to
https://publicsuffix.org/list/public_suffix_list.dat

I have mailman set up on an IPv6 only host and publicsuffix.org has no
IPv6 address.  A near identical configuration is set up on a dual
stack host.  Any email to the IPv6 only host fails with an entry in
logs/error of the form "Unable to retrieve data from
https://publicsuffix.org/list/public_suffix_list.dat: "

It doesn't look as if publicsuffix.org will be getting an IPv6 address
any time soon.  The alternative github.com also doesn't have an IPv6
address.  In the mean time I would like to disable the use of
DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL by setting it empty.  To do this
it seems that I would need the following change:

- --- Mailman/Utils.py.orig   2016-04-09 04:08:56.0 -0400
+++ Mailman/Utils.py2016-05-03 14:37:12.683904000 -0400
@@ -1205,6 +1205,8 @@
 Domain which may be the same as the input."""
 global s_dict
 if not s_dict:
-get_suffixes(mm_cfg.DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL)
+if mm_cfg.DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL:
+get_suffixes(mm_cfg.DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL)
 hits = []
 d = domain.lower().split('.')

In mm_sfg.py I just set "DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL = ''".

This works for .com, .org, .net, etc but not for things like co.uk,
etc (which in my case is not an issue).

A second question is why does failing to access publicsuffix.org
result in a hard fail rather than a soft fail?  The change I made just
skips over get_suffixes and leaves s_dict empty.  It seems that
get_suffixes does do a "try and except" which logs and returns, but
then the mail gets rejected and the reason is not clear to me by just
reading the code.  In logs/smtp-failure there is a message of the form
"failed with code 554: 5.7.1 : Client host rejected:
Access denied".  Skipping get_suffixes throws no error and leaves
s_dict empty.  At most an error in get_suffixes should put the email
in shunt but that seems to be in error handling upstream.

Curtis
--
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] Can users still receive digests when they are turned off?

[Mark Sapiro]

On 05/03/2016 02:22 PM, Danny Schmarsel wrote:
> Hello guys,
> 
> I'm running a mailing list without digests to keep the replies clean.
> 
> On the "Membership Management" page I can still enable digests for
> specific users even with digestable turned off.
> 
> The question: Will these users still receive digests or does digestable
> override user-specific settings?


They will receive no mail at all. They are set to 'digest' so they don't
receive individual messages, and the list's digestable is No so no
digests will be produced.

If you change a list from digestable = Yes to No and there are digest
members, you will be warned of this. If the list is already digestable =
No, and you try to set a member to digest via the admin UI "Membership
Management" page, the change is silently ignored.

-- 
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] Stop Backlogged Messages From Going Out

[Mark Sapiro]

On 05/04/2016 06:12 AM, Craig Pettersen wrote:
>   However after things went back up I've received two messages from the
> list and I have no idea where they've been hiding.  Since I can't have
> people upset with 20 emails from the list showing up in their inboxes I
> shut postfix and mailman down.  Now I need some help figuring out how to
> find and stop any old messages from going out and delete them.  Can anyone
> help me understand how to do that?


They've probably all been sent already, but any messages queued in
Mailman will be in Mailman's qfiles directory. In a source install the
queues are directories like $var_prefix/qfiles/in/,
$var_prefix/qfiles/out/ and so on, and the actual queued messages are
*.pck files in the directories.

Packages may or may not have a 'qfiles' directory. E.g., in the
RedHat/CentOS package the queues are /var/spool/mailman/in/,
/var/spool/mailman/out/, etc.

-- 
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] disable DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL in mailman 2.1

[Curtis Villamizar]

By default DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL is set to
https://publicsuffix.org/list/public_suffix_list.dat

I have mailman set up on an IPv6 only host and publicsuffix.org has no
IPv6 address.  A near identical configuration is set up on a dual
stack host.  Any email to the IPv6 only host fails with an entry in
logs/error of the form "Unable to retrieve data from
https://publicsuffix.org/list/public_suffix_list.dat: "

In the mean time I would like to disable the use of
DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL by setting it empty.  To do this
it seems that I would need the following change:

--- Mailman/Utils.py.orig   2016-04-09 04:08:56.0 -0400
+++ Mailman/Utils.py2016-05-03 14:37:12.683904000 -0400
@@ -1205,6 +1205,8 @@
 Domain which may be the same as the input."""
 global s_dict
 if not s_dict:
-get_suffixes(mm_cfg.DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL)
+if mm_cfg.DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL:
+get_suffixes(mm_cfg.DMARC_ORGANIZATIONAL_DOMAIN_DATA_URL)
 hits = []
 d = domain.lower().split('.')

This works for .com, .org, .net, etc but not for things like co.uk,
etc (which in my case is not an issue).

A second question is why does failing to access publicsuffix.org
result in a hard fail rather than a soft fail?  The change I made just
skips over get_suffixes and leaves s_dict empty.  It seems that
get_suffixes does do a try and except which logs and returns, but then
the mail gets rejected and the reason is not clear to me.  In
logs/smtp-failure there is a message of the form "failed with code
554: 5.7.1 : Client host rejected: Access denied".

Curtis
--
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] Can users still receive digests when they are turned off?

[Danny Schmarsel]

Hello guys,

I'm running a mailing list without digests to keep the replies clean.

On the "Membership Management" page I can still enable digests for 
specific users even with digestable turned off.


The question: Will these users still receive digests or does digestable 
override user-specific settings?


Thanks,
-Danny
--
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] Stop Backlogged Messages From Going Out

[Craig Pettersen]

Hello,
  I inherited a server that has a couple mailman lists that interface with
postfix and was alerted that daily messages from the list haven't been
going out for almost 3 weeks now.  I fixed the problem in postfix, and
before fixing it I checked queues and files in /var/spool/postfix and in
/home/mailman to see if any backlogged messages were set to go out and
didn't find any.
  However after things went back up I've received two messages from the
list and I have no idea where they've been hiding.  Since I can't have
people upset with 20 emails from the list showing up in their inboxes I
shut postfix and mailman down.  Now I need some help figuring out how to
find and stop any old messages from going out and delete them.  Can anyone
help me understand how to do that?
  Thanks,
  Craig
--
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