[Mailman-Users] zero-length config.pck file
mailman-2.1.29_6, FreeBSD 12.0-RELEASE-p10 After an unscheduled power cut by our hosting provider, one of the mailing lists hosted on this server came back up with a config.pck file containing 0 bytes. The file's timestamp corresponded to the time of the power loss. As a result, bin commands such as 'list_lists' would return a corrupt database error, and overnight cron jobs wouldn't run. This was only for one list; other lists on the same server were OK. I've restored the config.pck file from a backup and things seem to be OK now. Just checking, though: 1. Have others encountered config.pck corruption from power loss? 2. (putting on my tinfoil paranoid hat) Is there any chance the file corruption occurred due to an intrusion attempt, and not the power loss? Thanks! dn -- 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] admindb pages redirect to localhost
On 1/4/19 5:10 PM, Mark Sapiro wrote:
> On 1/4/19 4:40 PM, David Newman wrote:
>>
>> Actually, the localhost issue began _after_ I ran "bin/withlist -l -a -r
>> fix_url" from the /usr/local/mailman directory and restarted the Mailman
>> service.
>
>
> In your OP you said
>
>> mm_cfg.py mods:
>>
>> ##
>> # Put YOUR site-specific settings below this line.
>> MTA = 'Postfix'
>> DEFAULT_URL_PATTERN = 'https://%s/mailman/'
>> PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'
>> PRIVATE_ARCHIVE_URL = '/mailman/private'
>>
>> # Clear the Defaults.py VIRTUAL_HOSTS entry
>> # VIRTUAL_HOSTS.clear()
>>
>> # other vhosts omitted from following line
>> POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'lists.networktest.com' ]
>>
>> # other vhosts omitted after following line
>> add_virtualhost('lists.networktest.com','lists.networktest.com')
>>
>> DEB_LISTMASTER = 'postmaster at networktest.com'
>>
>> ALLOW_FROM_IS_LIST = Yes
>
> Absent from this is
>
> DEFAULT_URL_HOST = 'lists.networktest.com'
> DEFAULT_EMAIL_HOST = 'lists.networktest.com'
>
> If those are set to 'localhost' in Defaults.py, that could explain some
> of this.
>
> However, you also have comments about "other vhosts omitted". If you
> actually have multiple vhosts, you can't run
>
> bin/withlist -l -a -r fix_url
>
> because that will set every list to whatever DEFAULT_URL_HOST is. You
> need to run
>
> bin/withlist -l -r fix_url LISTNAME --urlhost=HOST_FOR_THAT_LIST
Yup. Sorry I missed this.
dn
>
> for each list.
>
> What do you get from
>
> for list in `bin/list_lists --bare`; do
> echo $list
> bin/dumpdb lists/$list/config.pck|grep \'web_page_url\'
> done
>
>
--
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] admindb pages redirect to localhost
On 1/4/19 4:40 PM, David Newman wrote: > > > On 1/4/19 12:19 PM, Mark Sapiro wrote: >> On 1/3/19 2:18 PM, David Newman wrote: >>> FreeBSD 12.0-RELEASE-p1, mailman-2.1.29_5, postfix-3.3.2_1,1, >>> nginx-1.14.2_3,2 >>> >>> Greetings. Could use help understanding two issues after migrating from >>> Apache to nginx: >>> >>> 1. All Mailman web pages load as expect except links from the admindb >>> page (for pending moderator request), which redirect to localhost. >> ... >>> 2. Also on the admindb page, clicking the submit button to tend to >>> pending requests triggers a warning in Firefox that the info is about to >>> be submitted insecurely, even though the admindb URL begins with >>> https:// - how to fix this? >> >> >> I'm only answering the second issue here because it may also answer the >> first. The issue here is the action= URL in the form tag has an http >> (not https) scheme. >> >> But, you have >> >> >>> mm_cfg.py mods: >>> >>> ## >>> # Put YOUR site-specific settings below this line. >>> MTA = 'Postfix' >>> DEFAULT_URL_PATTERN = 'https://%s/mailman/' >> >> >> This indicates you need to run fix_url to update existing lists with >> this information. See <https://wiki.list.org/x/4030616>. >> >> If this doesn't fix the first issue too, let us know and we'll look further. >> > > Actually, the localhost issue began _after_ I ran "bin/withlist -l -a -r > fix_url" from the /usr/local/mailman directory and restarted the Mailman > service. Answering my own question: That command as written was a really bad idea. There are multiple virtual hosts on this server, and no lists defined on the server's canonical hostname. Running fix_url without calling out each virtual host resulted in 'localhost' instead. When I reran the command multiple times with the -u switch like this: bin/withlist -l -r fix_url listname -u lists.vhost1.com bin/withlist -l -r fix_url listname -u lists.vhost2.com ... bin/withlist -l -r fix_url listname -u lists.vhostN.com and restarted mailman, all was good with the world once again. Moral: If you have virtual hosts, run fix_url multiple times and use the -u switch multiple times, once for each list and each virtual host. Sorry for the waste of bandwidth. dn > > Thanks in advance for further clues on getting both issues sorted out. > > dn > > > > -- > 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/dnewman%40networktest.com > -- 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] admindb pages redirect to localhost
On 1/4/19 12:19 PM, Mark Sapiro wrote: > On 1/3/19 2:18 PM, David Newman wrote: >> FreeBSD 12.0-RELEASE-p1, mailman-2.1.29_5, postfix-3.3.2_1,1, >> nginx-1.14.2_3,2 >> >> Greetings. Could use help understanding two issues after migrating from >> Apache to nginx: >> >> 1. All Mailman web pages load as expect except links from the admindb >> page (for pending moderator request), which redirect to localhost. > ... >> 2. Also on the admindb page, clicking the submit button to tend to >> pending requests triggers a warning in Firefox that the info is about to >> be submitted insecurely, even though the admindb URL begins with >> https:// - how to fix this? > > > I'm only answering the second issue here because it may also answer the > first. The issue here is the action= URL in the form tag has an http > (not https) scheme. > > But, you have > > >> mm_cfg.py mods: >> >> ## >> # Put YOUR site-specific settings below this line. >> MTA = 'Postfix' >> DEFAULT_URL_PATTERN = 'https://%s/mailman/' > > > This indicates you need to run fix_url to update existing lists with > this information. See <https://wiki.list.org/x/4030616>. > > If this doesn't fix the first issue too, let us know and we'll look further. > Actually, the localhost issue began _after_ I ran "bin/withlist -l -a -r fix_url" from the /usr/local/mailman directory and restarted the Mailman service. Thanks in advance for further clues on getting both issues sorted out. dn -- 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] admindb pages redirect to localhost
FreeBSD 12.0-RELEASE-p1, mailman-2.1.29_5, postfix-3.3.2_1,1,
nginx-1.14.2_3,2
Greetings. Could use help understanding two issues after migrating from
Apache to nginx:
1. All Mailman web pages load as expect except links from the admindb
page (for pending moderator request), which redirect to localhost.
For example, for the admindb page for the list networktest-announce on
the host lists.networktest.com, the link for "Click here to reload this
page" goes here:
https://localhost/mailman/admindb/networktest-announce
Similar localhost links appear in admin emails about pending moderator
requests.
I've pasted below snippets from mm_cfg.py and the Nginx config -- please
let me know if you need other info.
I suspect the issue may be a lack of an Nginx location for admindb, but
I'm not sure how to address that.
2. Also on the admindb page, clicking the submit button to tend to
pending requests triggers a warning in Firefox that the info is about to
be submitted insecurely, even though the admindb URL begins with
https:// - how to fix this?
Thanks in advance for troubleshooting clues on both points.
dn
mm_cfg.py mods:
##
# Put YOUR site-specific settings below this line.
MTA = 'Postfix'
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'
PRIVATE_ARCHIVE_URL = '/mailman/private'
# Clear the Defaults.py VIRTUAL_HOSTS entry
# VIRTUAL_HOSTS.clear()
# other vhosts omitted from following line
POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'lists.networktest.com' ]
# other vhosts omitted after following line
add_virtualhost('lists.networktest.com','lists.networktest.com')
DEB_LISTMASTER = 'postmas...@networktest.com'
ALLOW_FROM_IS_LIST = Yes
-
lists.networktest.com.conf in Nginx:
root@mail8:/usr/local/etc/nginx/vhosts # cat lists.networktest.com.conf
server {
listen 80;
server_name lists.networktest.com;
# Lets encrypt
location ^~ /.well-known/acme-challenge/ {
alias /usr/local/www/.well-known/acme-challenge/;
}
# Redirect other HTTP connections to HTTPS
location / {
return 301 https://$server_name$request_uri;
}
access_log /var/log/lists.networktest.com.access.log;
error_log /var/log/lists.networktest.com.error.log;
}
server {
listen 443;
server_name lists.networktest.com;
access_log /var/log/lists.networktest.com.access.log;
error_log /var/log/lists.networktest.com.error.log;
ssl on;
ssl_certificate /etc/ssl/certs/lists.networktest.com.pem;
ssl_certificate_key /etc/ssl/priv/lists.networktest.com.key;
ssl_session_timeout 5m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers HIGH:!aNULL:!MD5;
ssl_prefer_server_ciphers on;
root /usr/local/mailman/cgi-bin;
location = / {
rewrite ^ /mailman/listinfo permanent;
}
location / {
rewrite ^ /mailman$uri;
}
location ~ ^/mailman(/[^/]*)(/.*)?$ {
fastcgi_split_path_info (^/mailman/[^/]*)(.*)$;
include fastcgi_params;
fastcgi_param GATEWAY_INTERFACE CGI/1.1;
fastcgi_param SCRIPT_FILENAME $document_root$1;
fastcgi_param PATH_INFO $fastcgi_path_info;
fastcgi_param PATH_TRANSLATED $document_root$2;
fastcgi_pass unix:/var/run/fcgiwrap/fcgiwrap.sock;
}
location /images/mailman {
alias /usr/local/mailman/icons;
}
location /icons {
alias /usr/local/mailman/icons;
}
location /pipermail {
alias /usr/local/mailman/archives/public;
autoindex on;
}
}
--
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] Cloning a Mailman server to a virtual machine.
On 8/16/16 1:19 PM, The Mailing List Server Admin wrote: > Dear Mailman Cognoscenti, > > We have Mailman (and ListProc) running on a physical machine which > needs to be decommissioned. Cloning the system to a virtual machine > (VM) shouldn't be a problem, but I am unsure about the tasks needed to > make a smooth transition. I've looked at several articles about > moving Mailman to new hardware, but a lot of the lower level service > details are not mentioned. Here's my first stab at what I think needs > to be done. > > Mailman v2.1.20 > RHEL v5.11 > Semdmail v8.13.8 > Apache v2.2.3 > > After informing the list owners of date/time mailing list services > will be unavailable, at the appointed time... > > On the existing machine: > >1. stop cronsudo service crond stop >2. stop Sendmailsudo service sendmail stop >3. stop Apachesudo apachectl stop >4. stop Mailmansudo service mailmain stop >5. stop ListProcsu --command=/home/server/stop server >6. check mail queuesudo mailq > >7. Wait ?? for machine to quiet down? Shouldn't be necessary because of steps 2 and 5 -- the old system can't send or receive list messages or other email. > > Clone existing system to VM. > >8. shutdown old machine >9. boot VM clone > 10. test email and lists > 11. alert list owners Provided the VM is an exact copy with the same IP address(es) this should be OK. If the address changes, don't forget to update your DNS zone files. dn > > My concern is that a mailing list server is a very stateful beast, so > I want to avoid sending duplicate posts/digests, or accidentally > dropping new postings on the floor. Thanks for any insights you may > have to offer on the process. > -- 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] including all domains in virtual-mailman
Greetings. How to get the data/virtual-mailman file to include all
virtual domains after running bin/genaliases?
This is on a FreeBSD 10.3 system running mailman 2.1.22 from ports.
The system has mailing lists defined from 3 domains -- let's call them
domain1.tld, domain2.tld, and domain3.tld.
After running bin/genaliases, the data/virtual-mailman file only
includes whichever virtual domain is defined _last_ in Mailman/mm_cfg.py.
I have tried moving the domain definitions around. In each case,
genaliases only picks up the final one.
Thanks in advance for clues on getting all domains' lists included.
The end of Mailman/mm_cfg.py looks like this:
--
..
# Put YOUR site-specific settings below this line.
MTA = 'Postfix'
# Clear the Defaults.py VIRTUAL_HOSTS entry
# VIRTUAL_HOSTS.clear()
add_virtualhost('lists.domain1.tld','lists.domain1.tld')
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.domain1.tld']
add_virtualhost('lists.domain2.tld','lists.domain2.tld')
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.domain2.tld']
add_virtualhost('mail.domain3.tld','mail.domain3.tld')
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.domain3.tld']
DEB_LISTMASTER = 'postmas...@domain2.tld'
# dn 20140423
# adding DMARC workaround here
# see http://wiki.list.org/pages/viewpage.action?pageId=17891458
# for more details
ALLOW_FROM_IS_LIST = Yes
--
The Postfix main.cf file has these mailman-specific settings:
--
..
alias_maps = hash:/usr/local/etc/postfix/aliases,
hash:/usr/local/mailman/data/aliases
..
virtual_alias_maps =
proxy:mysql:/usr/local/etc/postfix/mysql/virtual_alias_maps.cf
proxy:mysql:/usr/local/etc/postfix/mysql/domain_alias_maps.cf
proxy:mysql:/usr/local/etc/postfix/mysql/catchall_maps.cf
proxy:mysql:/usr/local/etc/postfix/mysql/domain_alias_catchall_maps.cf
hash:/usr/local/mailman/data/virtual-mailman
..
recipient_delimiter = +
--
Thanks again for clues on getting virtual-mailman to include all lists
from all virtual domains.
dn
--
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
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. ##
[Mailman-Users] https and virtual domains
How to configure Mailman to handle https redirects to public archives
for virtual domains?
This is for a server with a canonical name of mail.domain1.tld, and
virtual names of lists.domain2.tld, lists.domain3.tld, etc.
With the mm.cfg config pasted below, clicking the archives link on a
list page for lists.domain2.tld redirects to
https://mail.domain1.tld/pipermail/listname
which fails because the list name is associated with domain2.tld and not
domain1.tld.
Not sure if this is related, but this is after running 'withlist -l -r
fix_url listname' on domain2.tld's mailing list and restarting mailman.
Thanks in advance for configuration clues.
dn
# Put YOUR site-specific settings below this line.
MTA = 'Postfix'
MAILMAN_SITE_LIST = 'mailman'
DEFAULT_EMAIL_HOST = 'mail.domain1.tld'
DEFAULT_URL_HOST = 'mail.domain1.tld'
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'
# Clear the Defaults.py VIRTUAL_HOSTS entry
VIRTUAL_HOSTS.clear()
add_virtualhost('lists.domain2.tld','lists.domain2.tld')
add_virtualhost('lists.domain3.tld','lists.domain3.tld')
add_virtualhost('lists.domain4.tld','lists.domain4.tld')
add_virtualhost('lists.domain5.tld','lists.domain5.tld')
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = Yes
VERP_CONFIRMATIONS = Yes
VERP_DELIVERY_INTERVAL = 1
OWNERS_CAN_ENABLE_PERSONALIZATION = 1
--
Mailman-Users mailing list Mailman-Users@python.org
http://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:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] https and virtual domains
On 2/19/11 6:57 AM, Mark Sapiro wrote:
David Newman wrote:
With the mm.cfg config pasted below, clicking the archives link on a
list page for lists.domain2.tld redirects to
https://mail.domain1.tld/pipermail/listname
which fails because the list name is associated with domain2.tld and not
domain1.tld.
Do you mean the link points to
https://mail.domain1.tld/pipermail/listname or that the link points to
https://lists.domain2.tld/pipermail/listname but when you follow it,
it is redirected.
If you mean the former, run Mailman's
bin/withlist -l -r fix_url listname -u lists.domain2.tld
and that should fix it.
Thanks, Mark. Adding '-u hostname' did the trick.
I'd suggest adding this to the FAQ, which currently does not mention the
-u switch:
http://wiki.list.org/display/DOC/4.27+Securing+Mailman%27s+web+GUI+by+using+Secure+HTTP-SSL
dn
If you mean the latter, it is your web server configuration doing this.
To say more, we'd need to see the relevant pieces of your web server
configuration.
Not sure if this is related, but this is after running 'withlist -l -r
fix_url listname' on domain2.tld's mailing list and restarting mailman.
If you mean the above literally, that's the problem. You're missing the
-u lists.domain2.tld at the end of the above so fix_url used the
DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST values. Also, it is not
necessary to restart Mailman after running fix_url unless you also
made mm_cfg.py changes.
Thanks in advance for configuration clues.
The following looks good.
# Put YOUR site-specific settings below this line.
MTA = 'Postfix'
MAILMAN_SITE_LIST = 'mailman'
DEFAULT_EMAIL_HOST = 'mail.domain1.tld'
DEFAULT_URL_HOST = 'mail.domain1.tld'
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'
# Clear the Defaults.py VIRTUAL_HOSTS entry
VIRTUAL_HOSTS.clear()
add_virtualhost('lists.domain2.tld','lists.domain2.tld')
add_virtualhost('lists.domain3.tld','lists.domain3.tld')
add_virtualhost('lists.domain4.tld','lists.domain4.tld')
add_virtualhost('lists.domain5.tld','lists.domain5.tld')
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = Yes
VERP_CONFIRMATIONS = Yes
VERP_DELIVERY_INTERVAL = 1
OWNERS_CAN_ENABLE_PERSONALIZATION = 1
--
Mailman-Users mailing list Mailman-Users@python.org
http://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:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] non-delivery to virtual domain
On 11/2/10 8:13 AM, Mark Sapiro wrote: David Newman wrote: On 10/31/10 10:22 PM, Mark Sapiro wrote: On 10/31/10 4:56 PM, David Newman wrote: On 10/31/10 9:09 AM, Mark Sapiro wrote: [...] Here's a log snapshot of a message sent to s...@domain1.tld, a Mailman list with subscribers 'dnew...@networktest.com' and 'dnew...@domain1.tld'. This is after removing 'hash:/usr/local/mailman/data/domain1-tld' from virtual_alias_maps as you suggested and reloading Mailman and postfix. I'm embedded one comment and one question: Nov 1 11:51:29 mail postfix/postfix-script[5384]: refreshing the Postfix mail system Nov 1 11:51:29 mail postfix/master[19348]: reload -- version 2.6.5, configuration /etc/postfix Nov 1 11:51:59 mail postfix/smtpd[32434]: connect from mail3.networktest.com[69.55.234.104] Nov 1 11:51:59 mail postfix/trivial-rewrite[29411]: warning: do not list domain domain1.tld in BOTH mydestination and virtual_mailbox_domains This is a possible clue. I think postfix is set up so that domain1.tld *is* a virtual domain. The server -- Mailserver, an email server appliance from Allard Software -- stores domain info in a SQL database and postfix calls that database here: virtual_mailbox_domains = proxy:mysql:/etc/postfix/sql/domains.cf Right. domain1.tld is defined to be a local domain because it is (indirectly) in mydestination. It is also in virtual_mailbox_domains and Postfix wants it to be in one or the other (either local or virtual) not both. Note that if you remove it from mydestination and make it strictly a virtual_mailbox_domain, delivery TO s...@domain1.com will stop working. See the FAQ at http://wiki.list.org/x/ZoCj. Anyway, carrying on: Nov 1 11:51:59 mail postfix/smtpd[32434]: A91E1130CB: client=mail3.networktest.com[69.55.234.104] Nov 1 11:51:59 mail postfix/cleanup[25359]: A91E1130CB: message-id=4ccf0c4e.8000...@networktest.com Nov 1 11:51:59 mail postfix/smtpd[32434]: disconnect from mail3.networktest.com[69.55.234.104] Nov 1 11:51:59 mail postfix/qmgr[20853]: A91E1130CB: from=dnew...@networktest.com, size=1495, nrcpt=1 (queue active) Nov 1 11:51:59 mail spamd[10619]: spamd: connection from localhost [127.0.0.1] at port 45013 Nov 1 11:51:59 mail spamd[10619]: spamd: processing message 4ccf0c4e.8000...@networktest.com for s...@mail.domain1.tld:62 Nov 1 11:52:00 mail spamd[10619]: spamd: clean message (-0.0/5.0) for s...@mail.domain1.tld:62 in 1.1 seconds, 1467 bytes. Nov 1 11:52:00 mail spamd[10619]: spamd: result: . 0 - T_RP_MATCHES_RCVD scantime=1.1,size=1467,use...@mail.domain1.tld,uid=62,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=45013,mid=4ccf0c4e.8000...@networktest.com,autolearn=ham Nov 1 11:52:01 mail postfix/pickup[1233]: 03422130CD: uid=506 from=dnew...@networktest.com Nov 1 11:52:01 mail postfix/pipe[16800]: A91E1130CB: to=s...@mail.domain1.tld, orig_to=s...@domain1.tld, relay=spamassassin, delay=1.6, delays=0.33/0.02/0/1.2, dsn=2.0.0, status=sent (delivered via spamassassin service) Nov 1 11:52:01 mail postfix/qmgr[20853]: A91E1130CB: removed These (A91E1130CB) messages are the receipt if the mail from dnew...@networktest.com to s...@domain1.com and its delivery to spamassassin. Nov 1 11:52:01 mail postfix/cleanup[25359]: 03422130CD: message-id=4ccf0c4e.8000...@networktest.com Nov 1 11:52:01 mail postfix/qmgr[20853]: 03422130CD: from=dnew...@networktest.com, size=1762, nrcpt=1 (queue active) Nov 1 11:52:01 mail spamd[18056]: prefork: child states: II Nov 1 11:52:01 mail postfix/local[28131]: 03422130CD: to=s...@mail.domain1.tld, relay=local, delay=0.32, delays=0.03/0.02/0/0.26, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman post s) Nov 1 11:52:01 mail postfix/qmgr[20853]: 03422130CD: removed And these (03422130CD) are the mail being requeued after spamassassin and delivered vi the local alias to Mailman. Nov 1 11:52:02 mail postfix/smtpd[32434]: connect from localhost[127.0.0.1] Nov 1 11:52:02 mail postfix/trivial-rewrite[29411]: warning: do not list domain domain1.tld in BOTH mydestination and virtual_mailbox_domains Nov 1 11:52:02 mail postfix/smtpd[32434]: 80A72130CB: client=localhost[127.0.0.1] Nov 1 11:52:02 mail postfix/trivial-rewrite[29411]: warning: do not list domain domain1.tld in BOTH mydestination and virtual_mailbox_domains Nov 1 11:52:02 mail postfix/cleanup[25359]: 80A72130CB: message-id=4ccf0c4e.8000...@networktest.com Nov 1 11:52:02 mail postfix/smtpd[32434]: disconnect from localhost[127.0.0.1] Nov 1 11:52:02 mail postfix/qmgr[20853]: 80A72130CB: from=s-boun...@domain1.tld, size=2697, nrcpt=2 (queue active) Nov 1 11:52:02 mail spamd[10619]: spamd: connection from localhost [127.0.0.1] at port 5435 Nov 1 11:52:02 mail spamd[10619]: spamd: processing message 4ccf0c4e.8000...@networktest.com for dnew...@domain1.tld:62 Nov 1 11:52:07 mail spamd[10619]: spamd: clean message
Re: [Mailman-Users] non-delivery to virtual domain
On 10/31/10 10:22 PM, Mark Sapiro wrote: On 10/31/10 4:56 PM, David Newman wrote: On 10/31/10 9:09 AM, Mark Sapiro wrote: What exactly does the Postfix log (maillog) say about the delivery to one of these addresses? maillog says status is sent to all list subscribers. The test list, called s, has one subscriber in domain1.tld on this server (who got the initial welcome to this list message from Mailman but not any messages) and one subscriber in another domain somewhere else (who gets all messages. Again, postfix tells the maillog that a message sent to the list address is status=sent to both subscribers. And what is the rest of the information in those log messages, i.e. the remainder of the sent= and the relay= for example. Please post the entire log line. Here's a log snapshot of a message sent to s...@domain1.tld, a Mailman list with subscribers 'dnew...@networktest.com' and 'dnew...@domain1.tld'. This is after removing 'hash:/usr/local/mailman/data/domain1-tld' from virtual_alias_maps as you suggested and reloading Mailman and postfix. I'm embedded one comment and one question: Nov 1 11:51:29 mail postfix/postfix-script[5384]: refreshing the Postfix mail system Nov 1 11:51:29 mail postfix/master[19348]: reload -- version 2.6.5, configuration /etc/postfix Nov 1 11:51:59 mail postfix/smtpd[32434]: connect from mail3.networktest.com[69.55.234.104] Nov 1 11:51:59 mail postfix/trivial-rewrite[29411]: warning: do not list domain domain1.tld in BOTH mydestination and virtual_mailbox_domains This is a possible clue. I think postfix is set up so that domain1.tld *is* a virtual domain. The server -- Mailserver, an email server appliance from Allard Software -- stores domain info in a SQL database and postfix calls that database here: virtual_mailbox_domains = proxy:mysql:/etc/postfix/sql/domains.cf Anyway, carrying on: Nov 1 11:51:59 mail postfix/smtpd[32434]: A91E1130CB: client=mail3.networktest.com[69.55.234.104] Nov 1 11:51:59 mail postfix/cleanup[25359]: A91E1130CB: message-id=4ccf0c4e.8000...@networktest.com Nov 1 11:51:59 mail postfix/smtpd[32434]: disconnect from mail3.networktest.com[69.55.234.104] Nov 1 11:51:59 mail postfix/qmgr[20853]: A91E1130CB: from=dnew...@networktest.com, size=1495, nrcpt=1 (queue active) Nov 1 11:51:59 mail spamd[10619]: spamd: connection from localhost [127.0.0.1] at port 45013 Nov 1 11:51:59 mail spamd[10619]: spamd: processing message 4ccf0c4e.8000...@networktest.com for s...@mail.domain1.tld:62 Nov 1 11:52:00 mail spamd[10619]: spamd: clean message (-0.0/5.0) for s...@mail.domain1.tld:62 in 1.1 seconds, 1467 bytes. Nov 1 11:52:00 mail spamd[10619]: spamd: result: . 0 - T_RP_MATCHES_RCVD scantime=1.1,size=1467,use...@mail.domain1.tld,uid=62,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=45013,mid=4ccf0c4e.8000...@networktest.com,autolearn=ham Nov 1 11:52:01 mail postfix/pickup[1233]: 03422130CD: uid=506 from=dnew...@networktest.com Nov 1 11:52:01 mail postfix/pipe[16800]: A91E1130CB: to=s...@mail.domain1.tld, orig_to=s...@domain1.tld, relay=spamassassin, delay=1.6, delays=0.33/0.02/0/1.2, dsn=2.0.0, status=sent (delivered via spamassassin service) Nov 1 11:52:01 mail postfix/qmgr[20853]: A91E1130CB: removed Nov 1 11:52:01 mail postfix/cleanup[25359]: 03422130CD: message-id=4ccf0c4e.8000...@networktest.com Nov 1 11:52:01 mail postfix/qmgr[20853]: 03422130CD: from=dnew...@networktest.com, size=1762, nrcpt=1 (queue active) Nov 1 11:52:01 mail spamd[18056]: prefork: child states: II Nov 1 11:52:01 mail postfix/local[28131]: 03422130CD: to=s...@mail.domain1.tld, relay=local, delay=0.32, delays=0.03/0.02/0/0.26, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman post s) Nov 1 11:52:01 mail postfix/qmgr[20853]: 03422130CD: removed Nov 1 11:52:02 mail postfix/smtpd[32434]: connect from localhost[127.0.0.1] Nov 1 11:52:02 mail postfix/trivial-rewrite[29411]: warning: do not list domain domain1.tld in BOTH mydestination and virtual_mailbox_domains Nov 1 11:52:02 mail postfix/smtpd[32434]: 80A72130CB: client=localhost[127.0.0.1] Nov 1 11:52:02 mail postfix/trivial-rewrite[29411]: warning: do not list domain domain1.tld in BOTH mydestination and virtual_mailbox_domains Nov 1 11:52:02 mail postfix/cleanup[25359]: 80A72130CB: message-id=4ccf0c4e.8000...@networktest.com Nov 1 11:52:02 mail postfix/smtpd[32434]: disconnect from localhost[127.0.0.1] Nov 1 11:52:02 mail postfix/qmgr[20853]: 80A72130CB: from=s-boun...@domain1.tld, size=2697, nrcpt=2 (queue active) Nov 1 11:52:02 mail spamd[10619]: spamd: connection from localhost [127.0.0.1] at port 5435 Nov 1 11:52:02 mail spamd[10619]: spamd: processing message 4ccf0c4e.8000...@networktest.com for dnew...@domain1.tld:62 Nov 1 11:52:07 mail spamd[10619]: spamd: clean message (0.0/5.0) for dnew...@domain1.tld:62 in 4.8 seconds, 2638 bytes. Nov 1 11:52:07 mail spamd[10619]: spamd: result: . 0 - scantime=4.8,size=2638,user=dnew...@domain1.tld
[Mailman-Users] non-delivery to virtual domain
(Apologies for re-raising a topic I asked about here a couple of years
ago. The instructions on Sourceforge have changed a bit since then.)
New server runs OpenBSD 4.7, postfix 2.65, mailman 2.1.14, and virtual
domains. Mail sent to/from virtual domains works fine.
Different story with Mailman. Although postfix says a message addressed
to a list is sent to all addresses, subscribers from virtual domains
on this server do not receive the message. Subscribers on other domains
not on this server do receive the message. There's no indication of
trouble in the Mailman logs or in maillog.
I've followed the setup instructions here, doing section 6.1.2 before
6.1.1 (given the link about doing virtual stuff first):
http://mailman.sourceforge.net/mailman-install/postfix-virtual.html
http://mailman.sourceforge.net/mailman-install/postfix-integration.html
I've pasted the config files below.
Thanks in advance for clues on getting Mailman to deliver to virtual
addresses on this server.
dn
server hostname:
mail.domain1.tld
virtual domains:
domain1.tld # (not its real name!)
domain2.tld
domain3.tld
-
from /etc/postfix/main.cf:
..
myhostname = mail.domain1.tld
mydomain = domain1.tld
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
..
alias_maps = hash:/etc/mail/aliases, hash:/usr/local/mailman/data/aliases
virtual_alias_maps =
proxy:mysql:/etc/postfix/sql/forwardings.cf
proxy:mysql:/etc/postfix/sql/email2email.cf
hash:/usr/local/mailman/data/domain1-tld
hash:/usr/local/mailman/data/virtual-mailman
-
from /usr/local/mailman/Mailman/mm_cfg.py:
MTA = 'Postfix'
MAILMAN_SITE_LIST = 'mailman'
DEFAULT_EMAIL_HOST = 'domain1.tld'
DEFAULT_URL_HOST = 'mail.domain1.tld'
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'
IMAGE_LOGOS = '/icons/'
POSTFIX_ALIAS_CMD = '/usr/local/sbin/postalias'
POSTFIX_MAP_CMD = '/usr/local/sbin/postmap'
POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'domain2.tld', 'domain3.tld' ]
# Clear the Defaults.py VIRTUAL_HOSTS entry
VIRTUAL_HOSTS.clear()
add_virtualhost('DEFAULT_EMAIL_HOST', 'DEFAULT_URL_HOST')
add_virtualhost('domain2.tld', 'domain2.tld')
add_virtualhost('domain3.tld', 'domain3.tld')
-
/usr/local/mailman/data/aliases
# The ultimate loop stopper address
mailman-loop: /usr/local/mailman/data/owner-bounces.mbox
# STANZA START: mailman
# CREATED: Sat Oct 30 11:23:37 2010
mailman: |/usr/local/mailman/mail/mailman post mailman
mailman-admin: |/usr/local/mailman/mail/mailman admin mailman
mailman-bounces: |/usr/local/mailman/mail/mailman bounces mailman
mailman-confirm: |/usr/local/mailman/mail/mailman confirm mailman
mailman-join:|/usr/local/mailman/mail/mailman join mailman
mailman-leave: |/usr/local/mailman/mail/mailman leave mailman
mailman-owner: |/usr/local/mailman/mail/mailman owner mailman
mailman-request: |/usr/local/mailman/mail/mailman request mailman
mailman-subscribe: |/usr/local/mailman/mail/mailman subscribe mailman
mailman-unsubscribe: |/usr/local/mailman/mail/mailman unsubscribe mailman
# STANZA END: mailman
# STANZA START: s
# CREATED: Sat Oct 30 11:35:12 2010
s: |/usr/local/mailman/mail/mailman post s
s-admin: |/usr/local/mailman/mail/mailman admin s
s-bounces: |/usr/local/mailman/mail/mailman bounces s
s-confirm: |/usr/local/mailman/mail/mailman confirm s
s-join:|/usr/local/mailman/mail/mailman join s
s-leave: |/usr/local/mailman/mail/mailman leave s
s-owner: |/usr/local/mailman/mail/mailman owner s
s-request: |/usr/local/mailman/mail/mailman request s
s-subscribe: |/usr/local/mailman/mail/mailman subscribe s
s-unsubscribe: |/usr/local/mailman/mail/mailman unsubscribe s
# STANZA END: s
-
/usr/local/etc/mailman/data/domain1-tld:
domain1.tld IGNORE
@domain1.tld @mail.domain1.tld
-
/usr/local/mailman/data/virtual-mailman:
# LOOP ADDRESSES START
mailman-l...@domain1.tldmailman-loop
# LOOP ADDRESSES END
# STANZA START: s
# CREATED: Sat Oct 30 11:35:12 2010
s...@domain1.tld s
s-ad...@domain1.tlds-admin
s-boun...@domain1.tld s-bounces
s-conf...@domain1.tld s-confirm
s-j...@domain1.tld s-join
s-le...@domain1.tlds-leave
s-ow...@domain1.tlds-owner
s-requ...@domain1.tld s-request
s-subscr...@domain1.tlds-subscribe
s-unsubscr...@domain1.tld s-unsubscribe
# STANZA END: s
-
--
Mailman-Users mailing list Mailman-Users@python.org
http://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:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] non-delivery to virtual domain
On 10/31/10 9:09 AM, Mark Sapiro wrote:
David Newman wrote:
(Apologies for re-raising a topic I asked about here a couple of years
ago. The instructions on Sourceforge have changed a bit since then.)
New server runs OpenBSD 4.7, postfix 2.65, mailman 2.1.14, and virtual
domains. Mail sent to/from virtual domains works fine.
Different story with Mailman. Although postfix says a message addressed
to a list is sent to all addresses, subscribers from virtual domains
on this server do not receive the message. Subscribers on other domains
not on this server do receive the message. There's no indication of
trouble in the Mailman logs or in maillog.
What exactly does the Postfix log (maillog) say about the delivery to
one of these addresses?
maillog says status is sent to all list subscribers. The test list,
called s, has one subscriber in domain1.tld on this server (who got
the initial welcome to this list message from Mailman but not any
messages) and one subscriber in another domain somewhere else (who gets
all messages.
Again, postfix tells the maillog that a message sent to the list address
is status=sent to both subscribers.
I've followed the setup instructions here, doing section 6.1.2 before
6.1.1 (given the link about doing virtual stuff first):
http://mailman.sourceforge.net/mailman-install/postfix-virtual.html
http://mailman.sourceforge.net/mailman-install/postfix-integration.html
This normally only affects delivery TO a list in a virtual domain. If
done properly, it should not affect delivery to any non-list address
in the virtual domains.
Sorry if I was unclear. Mail delivery to and from non-list addresses in
virtual domains on this server works fine. The only messages that are
not being delivered are those to a subscriber in domain1.tld on this
server. (I haven't yet tried subscribing anyone in domain2.tld or
domain3.tld.)
I've pasted the config files below.
Thanks in advance for clues on getting Mailman to deliver to virtual
addresses on this server.
This is almost certainly a Postfix issue rather than a Mailman issue.
If there is nothing in Mailman's smtp-failure log, Mailman has
delivered the message whith the local virtual recipients included to
Postfix and Postfix has accepted it.
See additional comments inline below.
server hostname:
mail.domain1.tld
virtual domains:
domain1.tld # (not its real name!)
domain2.tld
domain3.tld
Just to clarify: domain1.tld is not virtual, in the sense that the
server's canonical hostname is mail.domain1.tld. However, addresses
defined in this domain are virtual -- these users do not have local
accounts on this server. Again, non-list mail to and from these users
works as expected.
-
from /etc/postfix/main.cf:
..
myhostname = mail.domain1.tld
mydomain = domain1.tld
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
..
alias_maps = hash:/etc/mail/aliases, hash:/usr/local/mailman/data/aliases
virtual_alias_maps =
proxy:mysql:/etc/postfix/sql/forwardings.cf
proxy:mysql:/etc/postfix/sql/email2email.cf
hash:/usr/local/mailman/data/domain1-tld
hash:/usr/local/mailman/data/virtual-mailman
Full output from postconf -n might help.
Here you go:
alias_database = hash:/etc/mail/aliases
alias_maps = hash:/etc/mail/aliases, hash:/usr/local/mailman/data/aliases
command_directory = /usr/local/sbin
config_directory = /etc/postfix
daemon_directory = /usr/local/libexec/postfix
header_checks = pcre:/etc/postfix/header_checks.pcre
mail_owner = _postfix
mailq_path = /usr/local/sbin/mailq
manpage_directory = /usr/local/man
message_size_limit = 27962027
milter_connect_macros = j {daemon_name} v _
milter_default_action = tempfail
milter_header_checks = pcre:/etc/postfix/milter_header_checks
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
mydomain = domain1.tld
myhostname = mail.domain1.tld
mynetworks = 127.0.0.0/8
newaliases_path = /usr/bin/newaliases
proxy_read_maps = proxy:mysql:/etc/postfix/sql/routing.cf
proxy:mysql:/etc/postfix/sql/domains.cf
proxy:mysql:/etc/postfix/sql/mailboxes.cf
proxy:mysql:/etc/postfix/sql/user.cf
proxy:mysql:/etc/postfix/sql/group.cf
proxy:mysql:/etc/postfix/sql/forwardings.cf
proxy:mysql:/etc/postfix/sql/email2email.cfproxy:unix:passwd.byname
unix:passwd.byname
queue_directory = /var/spool/postfix
readme_directory = /usr/local/share/doc/postfix/readme
recipient_delimiter = +
relay_domains = proxy:mysql:/etc/postfix/sql/routing.cf
sample_directory = /etc/postfix
sendmail_path = /usr/local/sbin/sendmail
setgid_group = _postdrop
smtp_tls_cert_file = /etc/ssl/server.crt
smtp_tls_key_file = /etc/ssl/private/server.key
smtp_tls_security_level = may
smtpd_delay_reject = yes
smtpd_helo_required = yes
smtpd_milters = unix:/tmp/clamav-milter.sock
smtpd_recipient_restrictions = permit_mynetworks,
permit_sasl_authenticated, reject_unauth_destination,
reject_unauth_pipelining
[Mailman-Users] one-click subscription
For a read-only announcement list, I'm looking for a way to set up one-click subscription where a user enters an email in a form on a web page and gets subscribed right away, with no confirmation needed. Thanks in advance for clues on setting this up with MM, Apache and postfix. Apologies in advance if this has been asked before. I didn't see anything specific in the FAQ or in a quick check of the archives. dn -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] one-click subscription
On 3/1/10 10:34 AM, Mark Sapiro wrote: David Newman wrote: For a read-only announcement list, I'm looking for a way to set up one-click subscription where a user enters an email in a form on a web page and gets subscribed right away, with no confirmation needed. This is not a good idea. It allows anyone to subscribe anyone else to your list without the subscribed person's knowledge or consent. Do you really want to do this? If you do, there are two ways. You can set ALLOW_OPEN_SUBSCRIBE = Yes in mm_cfg.py and then set the list's Privacy options... - Subscription rules - subscribe_policy to None, and create your subscribe form per the FAQ at http://wiki.list.org/x/hIA9. Or, you can create a web page that either invokes curl or wget or posts it's own data to the admin CGI as outlined in posts linked from the FAQ at http://wiki.list.org/x/uIA9. However, if what you want is for people to be able to subscribe without further interaction on their part, you might consider just setting subscribe_policy to Approve and having subscriptions approved by an admin or moderator. This isn't much better, but at least it allows the admin to detect a suspicious pattern. OK, thanks. Thinking about this some more, it does seem like an excellent way to subscribe users who never asked to hear from us. I'll recommend to our team that we at least get confirmation before proceeding. dn -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Really obscuring sender addresses
On 1/26/10 5:07 PM, Mark Sapiro wrote: David Newman wrote: I am looking to obscure any reference to the sender's address from list postings. Per the guidelines, this includes (all done via the Web UI): anonymous_list: Yes first_strip_reply_to: Yes reply_goes_to_list: Explicit address reply_to_address: i...@example.com include_rfc2369_headers: Yes include_list_post_header: No However, test messages I've sent to the list still include my address in the message headers: Received: from host.example.com (host.example.com [10.0.0.123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: dnew...@networktest.com) by mail.example.com (Postfix) with ESMTPSA id 8D354958A2 for announce-l...@lists.example.com; Tue, 26 Jan 2010 11:24:09 -0800 (PST) Is it possible to scrub that Authenticated sender line? This is fixed in Mailman 2.1.13 - Received: headers are removed from anonymized posts. If you can't upgrade, you can get the Cleanse.py module from http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/files/head%3A/Mailman/Handlers/ and replace your Mailman/Handlers/Cleanse.py with that one. It should work with any Mailman 2.1.x version. Thanks, Mark. The FreeBSD ports collection still uses 2.1.12 but dropping in that file works; now the posts are anonymous. dn -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Really obscuring sender addresses
I've set up a read-only announcement mailing list following these guidelines: http://wiki.list.org/pages/viewpage.action?pageId=4030685 I am looking to obscure any reference to the sender's address from list postings. Per the guidelines, this includes (all done via the Web UI): anonymous_list: Yes first_strip_reply_to: Yes reply_goes_to_list: Explicit address reply_to_address: i...@example.com include_rfc2369_headers: Yes include_list_post_header: No However, test messages I've sent to the list still include my address in the message headers: Received: from host.example.com (host.example.com [10.0.0.123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: dnew...@networktest.com) by mail.example.com (Postfix) with ESMTPSA id 8D354958A2 for announce-l...@lists.example.com; Tue, 26 Jan 2010 11:24:09 -0800 (PST) Is it possible to scrub that Authenticated sender line? thanks dn -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] host.domain.tld vs. domain.tld
On 1/16/10 7:55 AM, Mark Sapiro wrote: David Newman wrote: On 1/15/10 7:33 PM, Mark Sapiro wrote: My guess is that on the old server, domain.tld was in Postfix's mydestination so that addr...@domain.tld was a local address and only referred to alias_maps and not virtual_alias_maps, whereas on the new server domain.tld is a virtual_mailbox_domain, thus postfix is looking in virtual_mailbox_maps for addr...@domain.tld and not finding it.. Curiouser and curiouser. First, thanks, this provided a clue for a fix. Second, both old and new servers used the same postfix main.cf and master.cf files. Both main.cf files had this line: mydestination = $myhostname, localhost.$mydomain, localhost which shouldn't have worked since (1) $mydomain wasn't defined anywhere and (2) domain.tld wasn't invoked and (3) mail never was addressed to localhost.$mydomain. mydomain defaults to myhostname minus the first component. E.g., myhostname = mail.example.com = mydomain = example.com. myhostname has a default which is the value returned by gethostname() or `uname -n` OK, thanks. The 'myhostname' variable is not defined in main.cf, but per the above it sounds as though it doesn't have to be. On the new server I changed this to: mydomain = domain.tld mydestination = $myhostname, $mydomain, localhost You still probably want localh...@local_domain in mydestination however local_domain is determined because sooner or later some program somewhere on your server will mail to that domain. For clarification, which form do I want in mydestination? localh...@local_domain (as you wrote) or localhost.$mydomain (as formerly in main.cf) I think you mean the latter, but just checking. and now list mail goes to either listname@mail.domain.tld or listnamedomain.tld, as desired. Puzzling, but thanks again. Was myhostname different on the old server? No. Both old and new systems use the same hostname. dn -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] host.domain.tld vs. domain.tld
On 1/16/10 11:11 AM, Mark Sapiro wrote: David Newman wrote: For clarification, which form do I want in mydestination? localh...@local_domain (as you wrote) or localhost.$mydomain (as formerly in main.cf) I think you mean the latter, but just checking. What I actually suggest is reverting to your original main.cf (i.e. remove the mydomain = domain.tld that you added and restore mydestination = $myhostname, localhost.$mydomain, localhost except just add domain.tld to mydestination as in mydestination = $myhostname, localhost.$mydomain, localhost domain.tld OK, will do. I forget postfix syntax for lists, but if this all were on one line, there'd be a comma between localhost and domain.tld, yes? Was myhostname different on the old server? No. Both old and new systems use the same hostname. As reported by uname -n? Yes. I moved all Postfix and Mailman (and Dovecot and MySQL) configs from the old server to the new, and only changed a DNS A record to point to the new machine. dn -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] host.domain.tld vs. domain.tld
Mailman 2.1.13, postfix 2.5.6, MySQL 5.0.77, OpenBSD 4.5
After migrating to new hardware, Mailman lists are working OK using the
form listname@mail.domain.tld, but mail sent to listname@domain.tld
bounces with an User unknown in virtual mailbox table error.
This is a problem since some users expect listname@domain.tld to work.
So, I'm looking for help in getting either of these forms working:
listname@mail.domain.tld
listname@domain.tld
This error is odd in that the form listname@domain.tld worked on the
old server and I am using the exact same postfix and Mailman config
files as well as the same MySQL databases.
Odder still is that I don't see any reason why listname@domain.tld
should have worked on the old system. On both servers, the Mailman setup
is for mail.domain.tld.
There's nothing about these errors in the Mailman logs. As near as I can
tell, all Postfix and SQL setup is the same, as are file permissions.
I've played around with adding 'domain.tld' to add_virtualhost and
POSTFIX_STYLE_VIRTUAL_DOMAINS, and also followed this and other threads:
http://is.gd/6kB4Y
but no joy.
Thanks in advance for clues on getting both addresses working.
dn
from mm_cfg.py:
MTA = 'Postfix'
MAILMAN_SITE_LIST = 'mailman'
DEFAULT_EMAIL_HOST = 'mail.domain.tld'
DEFAULT_URL_HOST = 'mail.domain.tld'
# Clear the Defaults.py VIRTUAL_HOSTS entry
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('mail.domain.tld', 'mail.domain.tld')
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'
IMAGE_LOGOS = '/icons/'
POSTFIX_ALIAS_CMD = '/usr/local/sbin/postalias'
POSTFIX_MAP_CMD = '/usr/local/sbin/postmap'
POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'mail.domain.tld', 'mail.domain.tld' ]
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = Yes
VERP_CONFIRMATIONS = Yes
VERP_DELIVERY_INTERVAL = 1
OWNERS_CAN_ENABLE_PERSONALIZATION = Yes
from main.cf:
alias_maps = hash:/etc/mail/aliases, hash:/usr/local/mailman/data/aliases
# the above is all one line in the config file
alias_database = hash:/etc/mail/aliases
unknown_local_recipient_reject_code = 550
virtual_alias_domains =
virtual_alias_maps =
proxy:mysql:/etc/postfix/sql/forwardings.cf
proxy:mysql:/etc/postfix/sql/email2email.cf
hash:/usr/local/mailman/data/virtual-mailman
sample stanza from /usr/local/mailman/data/virtual-mailman:
# STANZA START: test
# CREATED: Wed Jan 13 15:48:46 2010
t...@mail.domain.tld test
test-ad...@mail.domain.tldtest-admin
test-boun...@mail.domain.tld test-bounces
test-conf...@mail.domain.tld test-confirm
test-j...@mail.domain.tld test-join
test-le...@mail.domain.tldtest-leave
test-ow...@mail.domain.tldtest-owner
test-requ...@mail.domain.tld test-request
test-subscr...@mail.domain.tldtest-subscribe
test-unsubscr...@mail.domain.tld test-unsubscribe
# STANZA END: test
--
Mailman-Users mailing list Mailman-Users@python.org
http://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:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] host.domain.tld vs. domain.tld
On 1/15/10 7:33 PM, Mark Sapiro wrote: David Newman wrote: After migrating to new hardware, Mailman lists are working OK using the form listname@mail.domain.tld, but mail sent to listname@domain.tld bounces with an User unknown in virtual mailbox table error. This is a problem since some users expect listname@domain.tld to work. So, I'm looking for help in getting either of these forms working: listname@mail.domain.tld listname@domain.tld This error is odd in that the form listname@domain.tld worked on the old server and I am using the exact same postfix and Mailman config files as well as the same MySQL databases. My guess is that on the old server, domain.tld was in Postfix's mydestination so that addr...@domain.tld was a local address and only referred to alias_maps and not virtual_alias_maps, whereas on the new server domain.tld is a virtual_mailbox_domain, thus postfix is looking in virtual_mailbox_maps for addr...@domain.tld and not finding it.. Curiouser and curiouser. First, thanks, this provided a clue for a fix. Second, both old and new servers used the same postfix main.cf and master.cf files. Both main.cf files had this line: mydestination = $myhostname, localhost.$mydomain, localhost which shouldn't have worked since (1) $mydomain wasn't defined anywhere and (2) domain.tld wasn't invoked and (3) mail never was addressed to localhost.$mydomain. On the new server I changed this to: mydomain = domain.tld mydestination = $myhostname, $mydomain, localhost and now list mail goes to either listname@mail.domain.tld or listnamedomain.tld, as desired. Puzzling, but thanks again. dn -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] password required for public archives?
I'm sure this is a standard problem, but I haven't found the answer in any of the FAQs or by searching the mailing list archives. A customer asked that we change archives of an existing list from private to public. That's done, but Mailman still requests a password, even from a new browser with no cookies installed. Apache uses the FollowSymLinks option for public lists, and I have restarted both Apache and Mailman. Here's the Mailman config for apache: # mailman stuff ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/ Alias /pipermail/ /usr/local/mailman/archives/public/ Directory /usr/local/mailman/archives/public/ Options Indexes FollowSymLinks MultiViews AllowOverride None Order allow,deny Allow from all AddDefaultCharset Off /Directory # end mailman stuff Thanks in advance for clues on making archives accessible without a password. dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] phantom subscription requests
Mailman 2.1.12 on OpenBSD 4.5 Don't know if this is a coincidence, but ever since rebuilding a Mailman server that crashed last week and restoring the lists from archives, the site admin address has received a few dozen bogus subscription requests to lists on that server. This is odd, in that I'm site admin and have not sent any such requests. From the little bit of spot checking I've done, the requests appear to come mostly from machines in RIPE space in Europe. Is anyone else seeing this? What measures, if any, can a site admin take to block bogus subscription requests? thanks dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] shunting after decoding Unicode is not supported
Mailman 2.1.12
Had a server crash. Built a new server, compiled MM 2.1.12 from source
and restored the lists, data, and archives from a backup.
Messages are going to the list but most aren't getting archived, with
errors like the one pasted below.
This has come up before:
http://mail.python.org/pipermail/mailman-users/2007-May/057100.html
I'm wary about screwing up the digests, so two questions:
1. Is there any way of clearing this error without renaming/moving the
digest?
2. If I do move the digest, will the messages that didn't get archived
then make it into the archive? Or will archiving work only for those
messages from that point forward?
Many thanks
dn
May 13 21:37:17 2009 (16245) Uncaught runner exception: decoding Unicode
is not
supported
May 13 21:37:17 2009 (16245) Traceback (most recent call last):
File /usr/local/mailman/Mailman/Queue/Runner.py, line 120, in _oneloop
self._onefile(msg, msgdata)
File /usr/local/mailman/Mailman/Queue/Runner.py, line 191, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/local/mailman/Mailman/Queue/ArchRunner.py, line 73, in
_dispose
mlist.ArchiveMail(msg)
File /usr/local/mailman/Mailman/Archiver/Archiver.py, line 216, in
ArchiveMa
il
h.processUnixMailbox(f)
File /usr/local/mailman/Mailman/Archiver/pipermail.py, line 578, in
processU
nixMailbox
a = self._makeArticle(m, self.sequence)
File /usr/local/mailman/Mailman/Archiver/HyperArch.py, line 684, in
_makeArt
icle
mlist=self.maillist)
File /usr/local/mailman/Mailman/Archiver/HyperArch.py, line 308, in
__init__
charset = message.get_content_charset(cset_out)
File /usr/local/lib/python2.4/email/Message.py, line 800, in
get_content_cha
rset
charset = unicode(charset, 'us-ascii').encode('us-ascii')
TypeError: decoding Unicode is not supported
May 13 21:37:17 2009 (16245) SHUNTING:
1242275836.745697+2fd3997d48268b501123514
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] shunting after decoding Unicode is not supported
On 5/13/09 10:06 PM, David Newman wrote:
Mailman 2.1.12
Had a server crash. Built a new server, compiled MM 2.1.12 from source
and restored the lists, data, and archives from a backup.
Messages are going to the list but most aren't getting archived, with
errors like the one pasted below.
This has come up before:
http://mail.python.org/pipermail/mailman-users/2007-May/057100.html
I'm wary about screwing up the digests, so two questions:
1. Is there any way of clearing this error without renaming/moving the
digest?
2. If I do move the digest, will the messages that didn't get archived
then make it into the archive? Or will archiving work only for those
messages from that point forward?
Many thanks
Sorry for replying to my own email, but I've noticed it's only HTML
email that produces this error, and doesn't go into the archives.
How to remedy (without clobbering the digest, that is)?
Thanks again
dn
dn
May 13 21:37:17 2009 (16245) Uncaught runner exception: decoding Unicode
is not
supported
May 13 21:37:17 2009 (16245) Traceback (most recent call last):
File /usr/local/mailman/Mailman/Queue/Runner.py, line 120, in _oneloop
self._onefile(msg, msgdata)
File /usr/local/mailman/Mailman/Queue/Runner.py, line 191, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/local/mailman/Mailman/Queue/ArchRunner.py, line 73, in
_dispose
mlist.ArchiveMail(msg)
File /usr/local/mailman/Mailman/Archiver/Archiver.py, line 216, in
ArchiveMa
il
h.processUnixMailbox(f)
File /usr/local/mailman/Mailman/Archiver/pipermail.py, line 578, in
processU
nixMailbox
a = self._makeArticle(m, self.sequence)
File /usr/local/mailman/Mailman/Archiver/HyperArch.py, line 684, in
_makeArt
icle
mlist=self.maillist)
File /usr/local/mailman/Mailman/Archiver/HyperArch.py, line 308, in
__init__
charset = message.get_content_charset(cset_out)
File /usr/local/lib/python2.4/email/Message.py, line 800, in
get_content_cha
rset
charset = unicode(charset, 'us-ascii').encode('us-ascii')
TypeError: decoding Unicode is not supported
May 13 21:37:17 2009 (16245) SHUNTING:
1242275836.745697+2fd3997d48268b501123514
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] shunting after decoding Unicode is notsupported
On 5/17/09 5:49 PM, Mark Sapiro wrote: David Newman wrote: On 5/13/09 10:06 PM, David Newman wrote: Mailman 2.1.12 Had a server crash. Built a new server, compiled MM 2.1.12 from source and restored the lists, data, and archives from a backup. Messages are going to the list but most aren't getting archived, with errors like the one pasted below. This has come up before: http://mail.python.org/pipermail/mailman-users/2007-May/057100.html I'm wary about screwing up the digests, so two questions: The above issue is the same exception, but it's a totally different cause. 1. Is there any way of clearing this error without renaming/moving the digest? 2. If I do move the digest, will the messages that didn't get archived then make it into the archive? Or will archiving work only for those messages from that point forward? This one has to be fixed in a different way. It has nothing to do with digests. Sorry for replying to my own email, but I've noticed it's only HTML email that produces this error, and doesn't go into the archives. How to remedy (without clobbering the digest, that is)? This is a known incompatibility between Mailman 2.1.12 and the Python email 3.0.2 package. email 3.0.2 is part of Python 2.4.4 through 2.4.6, and these are the only Python versions that have this problem with Mailman 2.1.12. There is a long thread about this in the bug report at https://bugs.launchpad.net/mailman/+bug/328353 which also contains a patch to (in your case) /usr/local/lib/python2.4/email/Charset.py. There is also an Update - March 2009: about this near the bottom of the FAQ at http://wiki.list.org/x/pYA9 which contains a direct link to the Charset.py patch. You could upgrade Python to 2.5.x or 2.6.x to fix this, but the easiest fix is to apply the patch to /usr/local/lib/python2.4/email/Charset.py and restart Mailman. Then you can run bin/unshunt to process the shunted messages to the archive. Thanks, Mark. Upgrading Python and running unshunt (which previously I didn't know about) appears to have made this archive whole. Thanks again. dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] some messages missing from archive
On 3/27/09 9:07 AM, Mark Sapiro wrote: David Newman wrote: On 3/26/09 2:49 PM, Mark Sapiro wrote: You can also see if this post in in archives/private/LISTNAME.mbox/LISTNAME.mbox which will tell you that Mailman tried to archive it. Note that two different messages should never have the same Message-ID, but ... And the message is the LISTNAME.mbox file. Another post from this same subscriber today also failed to make it into the archive. Any other places to check? You can look in the archives/private/LISTNAME/-.txt file and see if it is there. In fact you can do grep col113-w22fad79423ae3666eaae42cc...@phx.gbl archives/private/LISTNAME/*.txt And see if you can find it in any month's .txt file. The archiving code first appends the message to the LISTNAME.mbox file and then adds it to the pipermail archive which includes the periodic .txt file. If the message gets as far as being appended to LISTNAME.mbox, only a processing exception (which should be logged) or the message-id already existing in the archive should prevent it's being added. In fact, you could grep the LISTNAME.mbox for the message-id to see if there's a duplicate there. Pilot error. This poster's messages are in the archive, just not where I expected them to be in the threaded display. Possibly this is because the poster replied to some other message and just changed the subject, but in any event the messages are there. Thanks/sorry dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] some messages missing from archive
Mailman 2.1.10 on OpenBSD 4.4 with Postfix 2.5.3 Checked the FAQ and searched Google but didn't see anything that directly addressed this: Most messages make it into the archives but a few do not. I've pasted below a sample of a message that didn't make it to the archive. I suspect that it might be related to Postfix's message handling but am not sure what's missing from the offending messages. Thanks in advance for clues on debugging this. dn ((addresses, domains and IP addresses anonymized)) Return-Path: u...@example.com X-Original-To: myn...@mydomain.tld Delivered-To: myn...@mydomain.tld Received: from localhost (localhost [127.0.0.1]) by mail.mydomain.tld (Postfix) with ESMTP id 616F15B3159 for myn...@mydomain.tld; Sun, 11 Jan 2009 10:16:21 -0800 (PST) X-Virus-Scanned: amavisd-new at localdomain X-Spam-Flag: NO X-Spam-Score: -1.671 X-Spam-Level: X-Spam-Status: No, score=-1.671 tagged_above=-999 required=6.31 tests=[AWL=-0.929, BAYES_20=-0.74, SPF_PASS=-0.001] Received: from mail.mydomain.tld ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kkMkBnOO63bs for myn...@mydomain.tld; Sun, 11 Jan 2009 10:16:19 -0800 (PST) Received: from mx.otherdomain.net (blackhelicopters.otherdomain.net [666.1.2.3]) by mail.mydomain.tld (Postfix) with ESMTP id 6BDC15B3157 for myn...@mydomain.tld; Sun, 11 Jan 2009 10:16:19 -0800 (PST) Received: from elvis.example.net (dsl1-2-3.yetanotherdomain.net [1.2.3.666]) (Authenticated sender: someu...@example.com) by mx.otherdomain.net (Postfix) with ESMTP id 2A02D196841 for myn...@mydomain.tld; Sun, 11 Jan 2009 10:16:18 -0800 (PST) Message-Id: 23a25183-7f35-4d19-b528-53c0a6d4f...@example.com From: someuser example someu...@example.com To: myname myn...@mydomain.tld In-Reply-To: 4969a68c.8000...@mydomain.tld Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: [myname members] Message size limits (was: (no subject)) Date: Sun, 11 Jan 2009 10:16:17 -0800 References: 0089fc87e3644d289559007671785...@wizardry 52f0a1b1f834c54db1c0cf32182d6e9b03d7b...@sagan.aperio.int 4969a68c.8000...@mydomain.tld X-Mailer: Apple Mail (2.930.3) On Jan 10, 2009, at 11:58 AM, myname wrote: With due respect, I think it's a lousy idea +1 -someuser -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] some messages missing from archive
On 3/26/09 8:05 AM, Mark Sapiro wrote:
David Newman wrote:
Most messages make it into the archives but a few do not. I've pasted
below a sample of a message that didn't make it to the archive. I
suspect that it might be related to Postfix's message handling but am
not sure what's missing from the offending messages.
The message below wasn't posted to the list. It is an off-list reply to
you only.
Well, that will teach me not to post before finishing morning coffee. Sorry.
Here's another message that actually was cc:'d to a list but didn't make
it into the archives. This subscriber is a frequent poster and other
messages of his exist in the archives.
It's HTML mail but then so is all this subscriber's other mail.
Thanks again for any clues on what caused this not to get archived.
dn
((addresses, domains and IP addresses anonymized))
Return-Path: members-bounces+user=example@example.org
X-Original-To: u...@example.org
Delivered-To: u...@example.org
Received: from localhost (localhost [127.0.0.1])
by mail.example.org (Postfix) with ESMTP id 4F3335B31A7
for u...@example.org; Tue, 24 Mar 2009 21:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at mail.example.org
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=6.31
tests=[AWL=0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.example.org ([127.0.0.1])
by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id UqCM5fJ2cnnr for u...@example.org;
Tue, 24 Mar 2009 21:54:20 -0700 (PDT)
Received: from mail.example.org (localhost [127.0.0.1])
by mail.example.org (Postfix) with ESMTP id 99DB35B3221
for u...@example.org; Tue, 24 Mar 2009 21:53:02 -0700 (PDT)
X-Original-To: memb...@example.org
Delivered-To: memb...@mail.example.org
Received: from localhost (localhost [127.0.0.1])
by mail.example.org (Postfix) with ESMTP id CF2CE5B31A5
for memb...@example.org; Tue, 24 Mar 2009 21:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at mail.example.org
Received: from mail.example.org ([127.0.0.1])
by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id xitN3rRm3SCk for memb...@example.org;
Tue, 24 Mar 2009 21:52:33 -0700 (PDT)
Received: from obfuscatedhost.hotmail.com (obfuscatedhost.hotmail.com
[666.1.2.3])
by mail.example.org (Postfix) with ESMTP id C6F295B3161
for memb...@example.org; Tue, 24 Mar 2009 21:52:33 -0700 (PDT)
Received: from COL113-W22 ([65.55.34.200]) by obfuscatedhost.hotmail.com
with Microsoft SMTPSVC(6.0.3790.3959);
Tue, 24 Mar 2009 21:52:29 -0700
Message-ID: col113-w22fad79423ae3666eaae42cc...@phx.gbl
Content-Type: multipart/mixed;
boundary=_188a48b0-e5ed-4ad3-9ca7-309c67e769c9_
X-Originating-IP: [98.149.111.105]
From: George Washington g...@msn.com
Date: Tue, 24 Mar 2009 21:52:29 -0700
Importance: Normal
In-Reply-To: 2868dbc10e894fc7b7cf953d5bcaf...@wizardry
References: 2868dbc10e894fc7b7cf953d5bcaf...@wizardry
MIME-Version: 1.0
X-OriginalArrivalTime: 25 Mar 2009 04:52:29.0023 (UTC)
FILETIME=[7FF8E6F0:01C9AD05]
Subject: [members] the subject of my message '09
X-BeenThere: memb...@example.org
X-Mailman-Version: 2.1.10
Precedence: list
Cc: user member list memb...@example.org
List-Id: user member list members.example.org
List-Unsubscribe: https://mail.example.org/mailman/options/members,
mailto:members-requ...@example.org?subject=unsubscribe
List-Archive: https://mail.example.org/mailman/private/members
List-Post: mailto:memb...@example.org
List-Help: mailto:members-requ...@example.org?subject=help
List-Subscribe: https://mail.example.org/mailman/listinfo/members,
mailto:members-requ...@example.org?subject=subscribe
To: user webmaster u...@example.org
Sender: members-bounces+user=example@example.org
Errors-To: members-bounces+user=example@example.org
--_188a48b0-e5ed-4ad3-9ca7-309c67e769c9_
Content-Type: multipart/alternative;
boundary=_aa51c9db-94e9-48fd-aa05-1cba2e9cab37_
--_aa51c9db-94e9-48fd-aa05-1cba2e9cab37_
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
((message text omitted))
--_aa51c9db-94e9-48fd-aa05-1cba2e9cab37_
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
html
head
style
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Verdana
}
/style
/head
body class=3D'hmmessage'
((html version omitted))
/body
/html=
--_aa51c9db-94e9-48fd-aa05-1cba2e9cab37_--
--_188a48b0-e5ed-4ad3-9ca7-309c67e769c9_
Content-Type: text/plain
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename=ATT0
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1lbWJlcnMg
bWFpbGluZyBsaXN0DQptZW1iZXJzQGN2Y2Jpa2Uub3JnDQpodHRwczovL21haWwuY3ZjYmlrZS5v
cmcvbWFpbG1hbi9saXN0aW5mby9tZW1iZXJzDQo
Re: [Mailman-Users] some messages missing from archive
On 3/26/09 2:49 PM, Mark Sapiro wrote: There are only a few reasons why a particular post would not be archived, assuming archiving is working in general. Archiving is working in general. 1) There could be something in this particular post that throws an exception in ArchRunner. This is unlikely, but check Mailman's error log to be sure. 2) If a post contains an X-Archive: No or an X_No_Archive: header, it won't be archived. This doesn't seem to be the case here. 3) If the post's Message-ID is the same as that of an already archived post, it will be in the LISTNAME.mbox file, but it won't be in the pipermail archive. grep Mailman's post log for this post's Message-ID grep col113-w22fad79423ae3666eaae42cc...@phx.gbl /path/to/logs/post and see if there is more than one post with this Message-ID (don't forget to check rotated logs as well if any). Went 0 for 3 on these. You can also see if this post in in archives/private/LISTNAME.mbox/LISTNAME.mbox which will tell you that Mailman tried to archive it. Note that two different messages should never have the same Message-ID, but ... And the message is the LISTNAME.mbox file. Another post from this same subscriber today also failed to make it into the archive. Any other places to check? Many thanks dn ((addresses, domains and IP addresses anonymized)) Return-Path: members-bounces+user=example@example.org X-Original-To: u...@example.org Delivered-To: u...@example.org Received: from localhost (localhost [127.0.0.1]) by mail.example.org (Postfix) with ESMTP id 4F3335B31A7 for u...@example.org; Tue, 24 Mar 2009 21:54:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at mail.example.org X-Spam-Flag: NO X-Spam-Score: -2.597 X-Spam-Level: X-Spam-Status: No, score=-2.597 tagged_above=-999 required=6.31 tests=[AWL=0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.example.org ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UqCM5fJ2cnnr for u...@example.org; Tue, 24 Mar 2009 21:54:20 -0700 (PDT) Received: from mail.example.org (localhost [127.0.0.1]) by mail.example.org (Postfix) with ESMTP id 99DB35B3221 for u...@example.org; Tue, 24 Mar 2009 21:53:02 -0700 (PDT) X-Original-To: memb...@example.org Delivered-To: memb...@mail.example.org Received: from localhost (localhost [127.0.0.1]) by mail.example.org (Postfix) with ESMTP id CF2CE5B31A5 for memb...@example.org; Tue, 24 Mar 2009 21:52:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at mail.example.org Received: from mail.example.org ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xitN3rRm3SCk for memb...@example.org; Tue, 24 Mar 2009 21:52:33 -0700 (PDT) Received: from obfuscatedhost.hotmail.com (obfuscatedhost.hotmail.com [666.1.2.3]) by mail.example.org (Postfix) with ESMTP id C6F295B3161 for memb...@example.org; Tue, 24 Mar 2009 21:52:33 -0700 (PDT) Received: from COL113-W22 ([65.55.34.200]) by obfuscatedhost.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 24 Mar 2009 21:52:29 -0700 Message-ID: col113-w22fad79423ae3666eaae42cc...@phx.gbl Content-Type: multipart/mixed; boundary=_188a48b0-e5ed-4ad3-9ca7-309c67e769c9_ X-Originating-IP: [98.149.111.105] From: George Washington g...@msn.com Date: Tue, 24 Mar 2009 21:52:29 -0700 Importance: Normal In-Reply-To: 2868dbc10e894fc7b7cf953d5bcaf...@wizardry References: 2868dbc10e894fc7b7cf953d5bcaf...@wizardry MIME-Version: 1.0 X-OriginalArrivalTime: 25 Mar 2009 04:52:29.0023 (UTC) FILETIME=[7FF8E6F0:01C9AD05] Subject: [members] the subject of my message '09 X-BeenThere: memb...@example.org X-Mailman-Version: 2.1.10 Precedence: list Cc: user member list memb...@example.org List-Id: user member list members.example.org List-Unsubscribe: https://mail.example.org/mailman/options/members, mailto:members-requ...@example.org?subject=unsubscribe List-Archive: https://mail.example.org/mailman/private/members List-Post: mailto:memb...@example.org List-Help: mailto:members-requ...@example.org?subject=help List-Subscribe: https://mail.example.org/mailman/listinfo/members, mailto:members-requ...@example.org?subject=subscribe To: user webmaster u...@example.org Sender: members-bounces+user=example@example.org Errors-To: members-bounces+user=example@example.org body snipped -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] adding a list to a virtual domain
On 3/22/09 4:30 PM, Mark Sapiro wrote:
David Newman wrote:
This evening I tried creating a new list but posts from a subscriber to
the new list bounce with the message User unknown in virtual mailbox
table.
AFAICT Mailman is set up to work with Postfix virtual domains as
described in sections 6.1 and 6.2 of the Mailman docs. Mailman runs fine
for other lists in this domain on this host.
I did notice that the virtual-mailman file was not updated when I
created the list at 18:37:
That probably means that the host whose name is the host_name attribute
of the new list is not in the mm_cfg.py POSTFIX_STYLE_VIRTUAL_DOMAINS
list.
Nope, that wasn't it. host_name was set to mydomain.tld, as per the
mm_cfg.py below.
I've also pasted lines from the end of mm_cfg.py below.
Thanks in advance for clues as to what's missing here.
dn
from mm_cfg.py (with the domain name scrubbed out):
MTA = 'Postfix'
MAILMAN_SITE_LIST = 'mailman'
DEFAULT_EMAIL_HOST = 'mydomain.tld'
DEFAULT_URL_HOST = 'mydomain.tld'
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'
IMAGE_LOGOS = '/icons/'
POSTFIX_ALIAS_CMD = '/usr/local/sbin/postalias'
POSTFIX_MAP_CMD = '/usr/local/sbin/postmap'
POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'mydomain.tld' ]
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = Yes
VERP_CONFIRMATIONS = Yes
VERP_DELIVERY_INTERVAL = 1
OWNERS_CAN_ENABLE_PERSONALIZATION = Yes
add_virtualhost('mydomain.tld', 'mail.mydomain.tld')
I need more information to tell you exactly how to fix this, but let me
give you an example of how this should be set up with two virtual
hosts with host1's web host = web.example.com and email host =
mail.example.com and host2's web host = web.example.net and email host
= mail.example.net and both mail.example.com and mail.example.net
being Postfix virtual domains and host1 being the one with the
majority of lists.
DEFAULT_EMAIL_HOST = 'mail.example.com'
DEFAULT_URL_HOST = 'web.example.com'
# above could be the .net domains. It makes now difference other than
# these are the default domains for bin/newlist and some other things.
#
# Clear the Defaults.py VIRTUAL_HOSTS entry
VIRTUAL_HOSTS.clear()
#
# Add the defaults
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
# and the other(s)
add_virtualhost('web.example.net', 'mail.example.net')
#
# Update virtual-mailman for lists in both domains
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.example.com', 'mail.example.net']
I didn't have these two lines:
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
but adding them and restarting apache and mailman, deleting and
recreating the list didn't resolve the original error.
You mentioned you'd need more info -- what else do you need?
Many thanks.
dn
ps.
On 3/22/09 4:05 PM, Brad Knowles wrote:
I hope you mean that you're using 2.1.10 or
something like that, and not 2.1.0.
Yes, sorry I meant 2.1.10
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] adding a list to a virtual domain
On 3/23/09 7:44 AM, Mark Sapiro wrote:
David Newman wrote:
I didn't have these two lines:
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
but adding them and restarting apache and mailman, deleting and
recreating the list didn't resolve the original error.
That won't help if your representation of what you have is accurate.
You show
DEFAULT_EMAIL_HOST = 'mydomain.tld'
DEFAULT_URL_HOST = 'mydomain.tld'
add_virtualhost('mydomain.tld', 'mail.mydomain.tld')
make that
DEFAULT_EMAIL_HOST = 'mydomain.tld'
DEFAULT_URL_HOST = 'mydomain.tld'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
You now have a VIRTUAL_HOSTS dictionary with one entry with both key
and value = 'mydomain.tld'. Then
add_virtualhost('mydomain.tld', 'mail.mydomain.tld')
replaces that entry with one with key 'mydomain.tld' and value
'mail.mydomain.tld'. Every virtual host has to have a unique web host
because that's the key to look up the corresponding email host.
Ahhh, I see. I missed the part where one add_virtualhost directive's
key/value pair replaces another's. Thanks.
Also, if your list has email host 'mail.mydomain.tld', no
virtual-mailman entries will be created for it because
POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'mydomain.tld' ]
says only create virtual-mailman entries for lists with email host
'mydomain.tld'.
I've just set everything for simply 'mydomain.tld' (I'm only using one
virtual domain at the moment, though that will change in the future),
and all is good now. My mm_cfg.py additions are pasted below.
Thanks again for your help.
dn
MTA = 'Postfix'
MAILMAN_SITE_LIST = 'mailman'
DEFAULT_EMAIL_HOST = 'mydomain.tld'
DEFAULT_URL_HOST = 'mydomain.tld'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('mydomain.tld', 'mydomain.tld')
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'
IMAGE_LOGOS = '/icons/'
POSTFIX_ALIAS_CMD = '/usr/local/sbin/postalias'
POSTFIX_MAP_CMD = '/usr/local/sbin/postmap'
POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'mydomain.tld', 'mydomain.tld' ]
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = Yes
VERP_CONFIRMATIONS = Yes
VERP_DELIVERY_INTERVAL = 1
OWNERS_CAN_ENABLE_PERSONALIZATION = Yes
You mentioned you'd need more info -- what else do you need?
I need to know the web and email domains for all the domains that have
lists - not necessarily the real domain names, but some representation
of them. I need to know which of these are virtual domains to Postfix.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] adding a list to a virtual domain
Greetings. I have a mailserver running OpenBSD 4.4, Postfix 2.5.3 and
Mailman 2.1.0. The machine hosts multiple virtual domains and Mailman
already hosts several mailing lists in one of these domains.
This evening I tried creating a new list but posts from a subscriber to
the new list bounce with the message User unknown in virtual mailbox
table.
AFAICT Mailman is set up to work with Postfix virtual domains as
described in sections 6.1 and 6.2 of the Mailman docs. Mailman runs fine
for other lists in this domain on this host.
I did notice that the virtual-mailman file was not updated when I
created the list at 18:37:
r...@mail:data# pwd
/usr/local/mailman/data
r...@mail:data# ls -l
total 164
-rw-r- 1 root mailman 41 Apr 19 2008 adm.pw
-rw-rw 1 root mailman 7596 Mar 21 18:37 aliases
-rw-rw 1 mailman mailman 65536 Mar 21 18:37 aliases.db
-rw-r- 1 root mailman 41 Apr 19 2008 creator.pw
-rw-r--r-- 1 root mailman 10 Apr 22 2008 last_mailman_version
-rw-rw 1 mailman mailman 6 Feb 19 02:53 master-qrunner.pid
-rw-r--r-- 1 root mailman 14114 Jun 21 2008 sitelist.cfg
-rw-rw 1 root mailman 5077 Mar 21 18:33 virtual-mailman
-rw-rw 1 mailman mailman 65536 Mar 21 18:37 virtual-mailman.db
Not that aliases, aliases.db and virtual-mailman.db all got updated when
I created the new list but virtual-mailman did not. I've tried
restarting apache, postfix and Mailman, but no joy.
I've also pasted lines from the end of mm_cfg.py below.
Thanks in advance for clues as to what's missing here.
dn
from mm_cfg.py (with the domain name scrubbed out):
MTA = 'Postfix'
MAILMAN_SITE_LIST = 'mailman'
DEFAULT_EMAIL_HOST = 'mydomain.tld'
DEFAULT_URL_HOST = 'mydomain.tld'
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'
IMAGE_LOGOS = '/icons/'
POSTFIX_ALIAS_CMD = '/usr/local/sbin/postalias'
POSTFIX_MAP_CMD = '/usr/local/sbin/postmap'
POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'mydomain.tld' ]
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = Yes
VERP_CONFIRMATIONS = Yes
VERP_DELIVERY_INTERVAL = 1
OWNERS_CAN_ENABLE_PERSONALIZATION = Yes
add_virtualhost('mydomain.tld', 'mail.mydomain.tld')
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Disable monthly membership reminder
On 6/2/08 4:34 AM, Bill Honneus (honneus) wrote: Hi, Anyone know how I can disable the monthly membership reminder email that gets sent out to all members of a mailing list? It's send_reminders on the general options page, under notifications. dn Thanks, Bill -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/dnewman%40networktest.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
On 5/30/08 4:35 AM, Larry Stone wrote: On 5/29/08 11:37 PM, Jim Popovitch at [EMAIL PROTECTED] wrote: On Fri, May 30, 2008 at 12:18 AM, David Newman [EMAIL PROTECTED] wrote: Hmmm. I must be missing something, as the system is still associating each Message-ID with all 250 list subscribers. VERP has nothing to do with Message-ID, and everything to do with Return-Path and Sender: ;-) With VERP and personalization, the Return-Path, instead of being [EMAIL PROTECTED] becomes [EMAIL PROTECTED]. I think you said you're using Postfix in which case you need recipient_delimiter = + in your main.cf so it knows about the plus signs in the return paths. ACK. Yes, that's in main.cf. When you then get the AOL TOS e-mail, you can figure out who the list recipient was as while AOL redacts the AOL recipient, they don't touch the Return-Path. I wish this were true, but it appears AOL gets to the Return-Path too: Return-Path: [EMAIL PROTECTED] So neither Return-ID nor Message-ID identifies who's complaining. But...this might be something. The next message header contains an ESMTP ID that corresponds with exactly one AOL user in maillog: Received: from rly-mh07.mx.aol.com (rly-mh07.mail.aol.com [172.21.166.143]) by air-mh02.mail.aol.com (v121.4) with ESMTP id MAILINMH024-be4483f8d3acf; Fri, 30 May 2008 01:14:45 -0400 Received: from mail.somedomain.com (mail.somedomain.com [666.666.666.666]) by rly-mh07.mx.aol.com (v121.5) with ESMTP id MAILRELAYINMH074-be4483f8d3acf; Fri, 30 May 2008 01:14:35 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.somedomain.com (Postfix) with ESMTP id B55685B31C0 for redacted; Thu, 29 May 2008 22:14:34 - (UTC) [EMAIL PROTECTED]:log# grep -i B55685B31C0 /var/log/maillog May 29 22:14:34 mail postfix/smtpd[25785]: B55685B31C0: client=localhost[127.0.0.1] May 29 22:14:34 mail postfix/cleanup[21262]: B55685B31C0: message-id=[EMAIL PROTECTED] May 29 22:14:34 mail postfix/qmgr[23040]: B55685B31C0: from=[EMAIL PROTECTED], size=13344, nrcpt=1 (queue active) Given the above, is [EMAIL PROTECTED] the subscriber that's complaining? Or is it just a coincidence that that AOL user got listed first? many thanks dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
On 5/30/08 8:40 AM, Larry Stone wrote: On Fri, 30 May 2008, David Newman wrote: When you then get the AOL TOS e-mail, you can figure out who the list recipient was as while AOL redacts the AOL recipient, they don't touch the Return-Path. I wish this were true, but it appears AOL gets to the Return-Path too: Return-Path: [EMAIL PROTECTED] Hmmm. I had one as recently as 5/15 and Return-Path was not touched nor some of the other places the address appears. It is frustrating that AOL wants to stop the unwanted e-mail but tries to make it difficult to figure out who is complaining. Indeed. I got my case escalated, and at first the AOL postmaster was responsive, but I haven't heard back since pointing this out a few days ago. Given the above, is [EMAIL PROTECTED] the subscriber that's complaining? Or is it just a coincidence that that AOL user got listed first? I think so. With personalization on, Mailman is generating a separate e-mail for each user which passes through Postfix as separate messages with a unique ID in Postfix. Without personalization, Mailman could pass as few as one message to the MTA and let the MTA split it into all the destinations. With personalization, the message for each user comes to the MTA as a separate message. One of the tradeoffs of personalization is the increased workload for Mailman and the MTA. Initially I thought the changes I made to mailman would result in a unique Message-ID per recipient, but this does not appear to be the case. For future reference, are these the only mailman change needed to get unique ESMTP IDs? 1. in mm_cfg.py, add OWNERS_CAN_ENABLE_PERSONALIZATION = Yes 2. enable personalization for the list in the Web UI If so, that may be good enough to catch who's complaining. thanks much dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
On 5/30/08 3:28 PM, Brad Knowles wrote: Stephen J. Turnbull wrote: Yeah, somebody actually said that, but they really meant the Return-Path. Changing Message-ID on regular posts would violate RFC 2822. Message-ID ids the content, not the medium, and is an author header: intermediate senders like Mailman must not touch it. IIRC, when you enable Full Personalization, enough changes are made to the message that it ends up being considered a completely new message, and therefore a new message-id is created. Same for list anonymization. That didn't happen, at least with my setup. grep'ing on the Message-ID provided by AOL still returned the email addresses of all list subscribers. Certainly, when you turn on personalization, you can enable certain values to be used in the footer of each message being sent out that will tell you the original e-mail address that it was addressed to, and if the redacting covers only the headers and not the footer, then you might see that. But either way, even you turn on just regular personalization and don't make any modifications to the message, you will get unique queue-ids that you can work with and compare against data in your logs. Yes, that appears to have worked. At least so far after I unsubscribed the problem user, posts to this particular list have not resulted in spam reports from AOL. dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
On 5/28/08 8:43 PM, Larry Stone wrote: On 5/28/08 9:26 PM, David Newman at [EMAIL PROTECTED] wrote: Another is to enable VERP for your outgoing messages, this allows you to track the message ID to the individual user. That sounds very promising, thanks. Trying it now... I have all my lists VERPed for just that reason. Once I figure out who it is, they get unsubscribed with extreme prejudice (meaning they also get banned from the mail server). But you should be aware that will increase your outgoing mail load. Nothing I do is high enough frequency for that to be an issue but it can be for some people. Most of my lists are announcement lists. In fact, for some of them, the recipients aren't even aware it's a mailing list. I (as a side job) assign soccer referees for local leagues. Rather than sending out announcements to my referees with a long BCC: list, I add them to a private mailman list with VERP so they receive them with them as the To: recipient. That also lets me know who to remove when they decide that the easiest way to let me know that they're no longer interested in being notified of available games is to do a report as spam. :-( OK, I've enabled VERP but I'm no closer to isolating who's complaining in AOL-land. Possibly this is some VERP config error on my part. I added the following to mm_cfg.py and rebooted: VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = Yes VERP_CONFIRMATIONS = Yes VERP_DELIVERY_INTERVAL = 1 The next AOL feedback report contained a unique Message-ID, as always. grep'ing for that ID in /usr/local/mailman/logs tells me only that the message was delivered to 250 recipients in 65 seconds. grep'ing for that ID in /var/log/maillog produces a lot more output -- in fact, still one entry per mailing list subscriber. I've pasted one example below (addresses redacted); there are 250 of these in maillog. So, back to the original question: How to associate one message-ID with one subscriber? Many thanks dn May 29 10:01:22 mail amavis[24936]: (24936-17) Passed CLEAN, LOCAL [127.0.0.1] [ 207.178.164.26] [EMAIL PROTECTED] - [EMAIL PROTECTED], Message-ID: [EMAIL PROTECTED], mail_id : KdgO9YwQBfML, Hits: -2.403, size: 18328, queued_as: 482E25B31D5, 12089 ms May 29 10:01:22 mail postfix/cleanup[26083]: 913255B31D7: message-id=627766.373 [EMAIL PROTECTED] May 29 10:01:22 mail postfix/cleanup[31531]: BE4745B31D8: message-id=627766.373 [EMAIL PROTECTED] May 29 10:01:22 mail postfix/cleanup[26083]: D9C2E5B31D9: message-id=627766.373 [EMAIL PROTECTED] May 29 10:01:23 mail postfix/cleanup[31531]: 47F645B31DA: message-id=627766.373 [EMAIL PROTECTED] May 29 10:01:23 mail postfix/cleanup[26083]: 6E0D65B31DB: message-id=627766.373 [EMAIL PROTECTED] May 29 10:01:23 mail postfix/cleanup[31531]: 876B85B31DC: message-id=627766.373 [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
On 5/29/08 11:40 AM, Brad Knowles wrote: David Newman wrote: OK, I've enabled VERP but I'm no closer to isolating who's complaining in AOL-land. Possibly this is some VERP config error on my part. I added the following to mm_cfg.py and rebooted: VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = Yes VERP_CONFIRMATIONS = Yes VERP_DELIVERY_INTERVAL = 1 The next AOL feedback report contained a unique Message-ID, as always. Did you go back to the list configuration and turn on personalization? Er, no, I haven't. Where do I set that in the Web UI? thanks dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
On 5/29/08 12:09 PM, David Andrews wrote: Did you go back to the list configuration and turn on personalization? Er, no, I haven't. Where do I set that in the Web UI? thanks dn DA: It is under Nondigest Options. Sorry for being dense, but where? These are the only choices I see under nondigest options: nondigestable msg_header msg_footer scrub_nondigest and under sibling lists: regular_exclude_lists regular_include_lists dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
On 5/29/08 1:46 PM, Larry Stone wrote: On Thu, 29 May 2008, David Newman wrote: Possibly this is some VERP config error on my part. I added the following to mm_cfg.py and rebooted: VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = Yes VERP_CONFIRMATIONS = Yes VERP_DELIVERY_INTERVAL = 1 You also need OWNERS_CAN_ENABLE_PERSONALIZATION = Yes Once you do that, the personalization option will appear on the appropriate admin page. You will probably need to restart httpd for it to appear. I doubt restarting the qrunners will be needed. Hmmm. I must be missing something, as the system is still associating each Message-ID with all 250 list subscribers. This is in mm_cfg.py: VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = Yes VERP_CONFIRMATIONS = Yes VERP_DELIVERY_INTERVAL = 1 OWNERS_CAN_ENABLE_PERSONALIZATION = Yes and under Non-digest options, peronsalize is set to Full Personaliztion and I restarted mailman, apache, and postfix after all this. What else might be missing? many thanks dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] slightly OT: on not becoming a spam source
One or more AOL subscribers is reporting posts to one of our mailing lists as spam. Every time there's a post to this list, both we and our upstream provider get a feedback report from AOL. This report provides the message-ID for the offending email, but not the recipient's address. AOL claims I should be able to find the offended recipient(s) with just the message-ID, but I do not believe they are correct about that. grep'ing for the message-ID in maillog returns *all* of the ~250 recipients for each post. I would like to find which AOL user(s) are complaining and unsubscribe them. One method would be to write a script that sends an individual email containing a unique ID to each subscriber, and see if AOL sends feedback complaint(s) for those. Questions: 1. In putting together a script, do I need to include this header: Return-Path: [EMAIL PROTECTED] (mylist and example.org are fact-free examples) 2. Is there some better way of isolating a given recipient if all I have from a spam report is a single message-ID? This is on OpenBSD 4.2 running postfix 2.4.3 and mailman 2.1.10. Many thanks! dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
On 5/28/08 7:09 PM, Dave Dewey wrote: Quoting David Newman ([EMAIL PROTECTED]): One or more AOL subscribers is reporting posts to one of our mailing lists as spam. Every time there's a post to this list, both we and our upstream provider get a feedback report from AOL. This report provides the message-ID for the offending email, but not the recipient's address. AOL claims I should be able to find the offended recipient(s) with just the message-ID, but I do not believe they are correct about that. grep'ing for the message-ID in maillog returns *all* of the ~250 recipients for each post. Well, how many of those 250 use AOL email addresses? That'll narrow it down. Only around 15 percent are @aol.com addresses but unfortunately AOL has other domains such as @netscape.com, @bigfoot.com, and possibly others, all of which get handled by the AOL postmaster. I don't have an exhaustive list; while it's mostly likely some user in @aol.com-land, I can't say for sure. This is probably one way. Another is to enable VERP for your outgoing messages, this allows you to track the message ID to the individual user. That sounds very promising, thanks. Trying it now... dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman 2.1.10 has been released
Mark Sapiro wrote: I am happy to announce the release of Mailman 2.1.10. Congratulations! I presume the usual upgrade instructions apply? http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.014.htp dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] chroot, OpenBSD, Apache, and Mailman
Mark Sapiro wrote: I suspect a permissions problem. Mailman would not serve up pages when all files were owned by group mailman, so I did 'chgrp -R www /var/www/mailman'. But after trying to create a list, the aliases file is mode 660, owned by root:www. This is probably a mistake. Mailman relies on everything being group Mailman and the CGI and mail wrappers being group Mailman and SETGID so everything runs as group Mailman. If the chroot jail doesn't allow SETGID to work, then I'm not sure what you'ld need to do, but whatever user:group structure you have, both the web server and the MTA have to be able to write various Mailman files. Yes, that's the key issue. The OpenBSD chroot won't SETGID in part because it mounts the /var partition nosuid, which forbids SETGID. In theory it's possible to disable this, and get the python and other binaries and libraries into the chroot environment, but at that point there's really no benefit to running chroot'ed. The much easier (if somewhat less secure) solution is to run Apache without chroot. Just set 'httpd_flags=-u' in /etc/rc.conf. After restarting Apache, Mailman installed clean with the default configure options. thanks very much dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] chroot, OpenBSD, Apache, and Mailman
Greetings. Apologies if this has been answered before but I didn't find
a direct answer in the archives or FAQ.
Is there a howto for installing Mailman from source inside the Apache
chroot on OpenBSD?
I'm struggling with this, using Mailman 2.1.19, Postfix 2.4.3, and
OpenBSD 4.2. There's a list of installation steps pasted below.
I suspect a permissions problem. Mailman would not serve up pages when
all files were owned by group mailman, so I did 'chgrp -R www
/var/www/mailman'. But after trying to create a list, the
aliases file is mode 660, owned by root:www.
This is the error in /var/www/mailman/logs/error that results from
trying to create a new list:
Apr 18 11:21:00 2008 admin(1925):
admin(1925): [- Mailman Version: 2.1.9 -]
admin(1925): [- Traceback --]
admin(1925): Traceback (most recent call last):
admin(1925): File /var/www/mailman/scripts/driver, line 101, in run_main
admin(1925): main()
admin(1925): File /var/www/mailman/Mailman/Cgi/create.py, line 56,
in main
admin(1925): process_request(doc, cgidata)
admin(1925): File /var/www/mailman/Mailman/Cgi/create.py, line 238,
in proce
ss_request
admin(1925): sys.modules[modname].create(mlist, cgi=1)
admin(1925): File /var/www/mailman/Mailman/MTA/Postfix.py, line 232,
in crea
te
admin(1925): _update_maps()
admin(1925): File /var/www/mailman/Mailman/MTA/Postfix.py, line 53,
in _upda
te_maps
admin(1925): raise RuntimeError, msg % (acmd, status, errstr)
admin(1925): RuntimeError: command failed: /usr/local/sbin/postalias
/var/www/mailman/data/aliases (status: 1, Operation not permitted)
I've also tried putting postalias inside the chroot jail but the error
above persists.
Thanks in advance for clues on getting this working.
dn
PROCEDURE FOR INSTALLING MAILMAN IN OPENBSD 4.2 APACHE CHROOT
1. Read all of the installation manual, or at least up to chapter 6,
before proceeding:
http://mailman.sourceforge.net/mailman-install/index.html
2. Grab mailman source and unpack:
tar xzvf mailman-2.1.19.tgz
3. Add user mailman with UID/GID 91. Run adduser and follow the prompts.
Set the shell to nologin and set the password to blank, and then say yes
when asked if the user shouldn't be able to log in.
4. Create the /var/www/mailman directory where everything will go, and
set permissions and ownership:
mkdir /var/www/mailman
chgrp mailman /var/www/mailman
chmod a+rx,g+ws /var/www/mailman
5. If it's not there already, install python:
pkg_add python-2.4.4p4
and create the appropriate symlinks to make this the default:
ln -s /usr/local/bin/python2.4 /usr/local/bin/python
ln -s /usr/local/bin/pydoc2.4 /usr/local/bin/pydoc
Now we need to get python into the chroot. First let's find out what
dependencies python has:
#ldd /usr/local/bin/python
/usr/local/bin/python:
StartEnd Type Open Ref GrpRef Name
exe 10 0 /usr/local/bin/python
05054000 25096000 rlib 01 0
/usr/local/lib/libpython2.4.so.0.0
068bd000 268c1000 rlib 01 0 /usr/lib/libutil.so.11.0
05b7c000 25ba2000 rlib 01 0 /usr/lib/libstdc++.so.42.0
070f2000 270f9000 rlib 01 0 /usr/lib/libm.so.2.3
0b296000 2b29f000 rlib 01 0 /usr/lib/libpthread.so.8.0
05d9d000 25dd1000 rlib 01 0 /usr/lib/libc.so.41.0
0a739000 0a739000 rtld 01 0 /usr/libexec/ld.so
OK, so all of these files and directories need to go into the chroot jail:
mkdir -p /var/www/usr/lib
mkdir -p /var/www/usr/libexec
mkdir -p /var/www/usr/local/bin
mkdir -p /var/www/usr/local/lib
cp /usr/local/bin/python /var/www/usr/local/bin
cp /usr/local/lib/libpython2.4.so.0.0 /var/www/usr/local/lib
cp /usr/lib/libutil.so.11.0 /var/www/usr/lib
cp /usr/lib/libstdc++.so.42.0 /var/www/usr/lib
cp /usr/lib/libm.so.2.3 /var/www/usr/lib
cp /usr/lib/libpthread.so.8.0 /var/www/usr/lib
cp /usr/lib/libc.so.41.0 /var/www/usr/lib
cp /usr/libexec/ld.so /var/www/usr/libexec
And you'll also need some stuff from /etc in the chroot jail for UIDs
and GIDs to work:
mkdir -p /var/www/etc/
cp /etc/group /var/www/etc/
cp /etc/localtime /var/www/etc/
cp /etc/login.conf /var/www/etc/
cp /etc/passwd /var/www/etc/
cp /etc/pwd.db /var/www/etc/
mkdir -p /var/www/usr/share
cp -R /usr/share/nls /var/www/usr/share
6. If it's not there already (try cc from the command line), install
the compilers package:
tar -C / -xzphf ${RELEASEPATH}/comp42.tar.gz
7. From the directory where you unpacked Mailman, configure and install
the Mailman software:
./configure --prefix=/var/www/mailman --with-cgi-gid=67 \
--with-mail-gid=201
make
make install
Assuming this goes well:
make clean
8. Check file permissions
/var/www/mailman/bin/check_perms -f
Keep repeating this step until there are no errors.
9. (Optional) Make private archives private
cd /var/www/mailman/archives
chown www private
chmod o-x
Re: [Mailman-Users] virtual domain setup with postfix
On Monday, January 29, 2007, at 04:18PM, Mark Sapiro [EMAIL PROTECTED] wrote: Basically, postfix delivers message to [EMAIL PROTECTED] but nothing happens after that. Presumably, that's because Postfix is delivering the mail to a local mailbox 'pctest' instead of piping it to Mailman's mail wrapper via the command /usr/local/mailman/mail/mailman post pctest. Yup. That is exactly what's happening (except that it's a virtual mailbox and not a local user account). This is really a Postfix question, not a Mailman question Yes and no. I'd say it's more of a clueless-pilot question, esp. since Postfix is doing exactly what it's told -- in this instance, deliver messages to [EMAIL PROTECTED] The problem here is mailman-specific, though I'm unsure whether the solution is in mailman configuration or some combo of postfix and mailman configs. I've read and reread and reread the mailman docs, and I don't see where and how virtual addresses get piped to the command above. The file /usr/local/mailman/data/aliases has commands like the above; the file /usr/local/mailman/data/virtual-mailman does not. For example, aliases has: pctest: |/usr/local/mailman/mail/mailman post pctest but virtual-mailman has: [EMAIL PROTECTED] pctest I'm missing how to glue the two together, and this is NOT covered in the existing mailman docs. Once I get this running I'd be glad to write up documentation and submit it for possible inclusion. , but you might find the post at http://mail.python.org/pipermail/mailman-users/2007-January/055502.html to be helpful. Thanks. That post in turn links to an earlier howto which covers aliases but not virtual-mailman. On Monday, January 29, 2007, at 05:47PM, Paul Fox [EMAIL PROTECTED] wrote: However, MM never distributes the mail to list subscribers. /var/log/maillog says each message is sent to [EMAIL PROTECTED]; however, the only files in /usr/local/mailman/logs that change are smtp and subscribe (and then only when list members are added). so it sounds like you have postfix aliases set up for pctest-*, but not pctest itself? is that right? Actually, the opposite. I'd set up a virtual mailbox for pctest but none of the rest of the pctest-* hierarchy. It's not covered in the docs, but from Mark's email I gather that I shouldn't need this step -- instead mail should be piped to the command Mark gave above. Basically, postfix delivers message to [EMAIL PROTECTED] but nothing happens after that. i don't use mysql, but my epiphany was when i realized i needed two separate mappings to be in place to get postfix and mailman working together. you need the virtual domain map (which i believe you have) and you need the map that takes the result of the virtual domain map, and turns it into a real destination. Right. That's really my question -- how is that done? thanks! /wsbs -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] virtual domain setup with postfix
MM 2.1.9, Postfix 2.3.5, cyrus-imap 2.3.7, all on FreeBSD 6.1 installed from
ports
Postfix already handles mail for multiple virtual domains defined in a MySQL
database. I believe virtual domain setup is OK, as individual users have been
sending and receiving mail for some time.
Having problems with Mailman, though. I've read these instructions many times:
http://www.list.org/mailman-install/postfix-virtual.html
Besides doing what's listed there, I also defined a virtual mailbox for a new
pctest list (without that, mail sent to [EMAIL PROTECTED] bounces).
However, MM never distributes the mail to list subscribers. /var/log/maillog
says each message is sent to [EMAIL PROTECTED]; however, the only files in
/usr/local/mailman/logs that change are smtp and subscribe (and then only when
list members are added).
Basically, postfix delivers message to [EMAIL PROTECTED] but nothing happens
after that.
Thanks in advance for clues on fixing this.
/wsbs
from virtual-mailman (note that I have run postmap on this and restarted
mailman and postfix multiple times, but no joy):
# STANZA START: pctest
# CREATED: Mon Jan 29 15:05:35 2007
[EMAIL PROTECTED] pctest
[EMAIL PROTECTED]pctest-admin
[EMAIL PROTECTED] pctest-bounces
[EMAIL PROTECTED] pctest-confirm
[EMAIL PROTECTED] pctest-join
[EMAIL PROTECTED]pctest-leave
[EMAIL PROTECTED]pctest-owner
[EMAIL PROTECTED] pctest-request
[EMAIL PROTECTED]pctest-subscribe
[EMAIL PROTECTED] pctest-unsubscribe
# STANZA END: pctest
from mm_cfg.py:
# Put YOUR site-specific settings below this line.
$SMTPHOST = virt1.tld
DEFAULT_EMAIL_HOST = 'virt1.tld'
DEFAULT_URL_HOST = 'virt1.tld'
IMAGE_LOGOS = '/icons/'
MTA = 'Postfix'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virt1.tld']
VIRTUAL_HOSTS.clear()
add_virtualhost('mail.virt1.tld', 'virt1.tld')
from main.cf:
recipient_delimiter = +
unknown_local_recipient_reject_code = 550
virtual_alias_maps = mysql:/usr/local/etc/postfix/mysql_virtual_alias_maps.cf,
hash:/usr/local/mailman/data/virtual-mailman
from master.cf:
(nothing MM specific)
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
