Re: [Mailman-Users] Start a new thread" button doesn't work - Mailman3.0.2 Panel

[Mark Sapiro]

On 03/21/2016 12:15 AM, scorpio 2005 via Mailman-Users wrote:
> My question is still not answered, can i do upgrade using gitlab individuals 
> component to fix this issue. that is, Example hyperkitty version installed 
> already using mailman bundler. but is it possible for me to do upgrade 
> hyperkitty using gitlab individual component latest version will fix this 
> issue? Please treat this urgent request and totally stagnant now.


There is no easy answer to this. I am in the process of setting up a
production Mailman 3 instance at lists.mailman3.org to support a
mailman-us...@mailman3.org list (not there yet). I'll outline what I did
which may help you, but it wasn't easy.

I created a system user 'mailman' and a /opt/mailman directory owned by
mailman.

I cloned mailman-bundler from gitlab into /opt/mailman/mailman-bundler.

I created no virtualenv. In the mailman-bundler directory as the
'mailman' user, I more or less followed
.

I set buildout.cfg for 'production' and ran buildout, not in a venv.
I did 'sudo apt-get install ruby-sass' (this is on Ubuntu)
I installed psycopg2 and set config stuff for both Django and Mailman to
use PostgreSQL
I installed gunicorn
I configured postfix and nginx and set up mailman and gunicorn services,
installed the Django crontab, ran ./bin/mailman-post-update, etc. (not
necessarily in that order) and made a more or less working installation
with most of the software in /opt/mailman/mailman-bundler/eggs and
/opt/mailman/mailman-bundler/venv-3.4 as created by bundler.

I assume this is where you are now.

My first step towards upgrading was to clone the mailman master branch
from gitlab, activate the venv-3.4 virtualenv, run 'python3 setup.py
install' in the cloned branch directory with the venv installed. Then in
the venv-3.4/lib/python3.4/site-packages I removed the 3.0.2 'mailman'
directory and created a symlink mailman -> mailman-3.1.0-py3.4.egg/mailman.

This then worked to use the core mailman from the gitlab master branch.

This was still not what I wanted, so I then cloned the gitlab master
branches of mailman,  mailman-hyperkitty, hyperkitty, mailmanclient and
postorius and cd to each branch directory in turn and 'sudo command
setup.py install' where 'command is python for mailmanclient, hyperkitty
and postorius, and python3 for mailman and mailman-hyperkitty. This got
almost everything installed system wide (I.e. in
/usr/local/lib/python2.7/dist-packages/ and
/usr/local/lib/python3.4/dist-packages/ instead of
/opt/mailman/mailman-bundler/eggs and
/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages.

The next step is the really tricky one. I verified that in the system
Python 3.4, I could import the top level module of every package in
/opt/mailman/mailman-bundler/venv-3.4/lib/python3.4/site-packages and
then removed them all.

I did the same with Python 2 and the /opt/mailman/mailman-bundler/eggs
directory, but here, there were a few things I couldn't find in
/usr/local/lib/python2.7/dist-packages/, so I left them in eggs/. One is
gunicorn-19.4.5-py2.7.egg, which I had originally installed with
buildout and decided to just leave. The others are
beautifulsoup4-4.4.1-py2.7.egg, mock-1.3.0-py2.7.egg,
collective.recipe.cmd-0.11-py2.7.egg, pbr-1.8.1-py2.7.egg,
djangorecipe-2.1.2-py2.7.egg, Whoosh-2.7.2-py2.7.egg,
funcsigs-0.4-py2.7.egg, z3c.recipe.filetemplate-2.2.0-py2.7.egg and
zc.recipe.egg-2.0.3-py2.7.egg. I think mock is just for testing and the
zc stuff is for buildout and others may be unneeded, but I left them all.

I also did 'sudo pip3 install psycopg2' because I think both Python 2
and Python 3 versions are required.

I then went through all the scripts in mailman-bundler/bin and removed
all the no longer present paths from the sys.path[0:0] = [ ... ] at the
beginning.

I may be forgetting something, but I think that was it.

I may have run into a missing import or two, but they were easy to fix.

The only other thing is you end up here with Django 1.9 only, and the
'mailman-web-django-admin runjobs daily' job runs into
"django.core.cache.get_cache was removed in Django 1.9 which breaks the
daily cache_cleanup job."  The fix is at
.

I do not recommend this as an install from scratch procedure at all. I'm
still figuring that one out, but if you already have a working install
with bundler and want to upgrade it without discarding all the
infrastructure already built, this may work for you.

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

Re: [Mailman-Users] Start a new thread" button doesn't work - Mailman3.0.2 Panel

[scorpio 2005 via Mailman-Users]

My question is still not answered, can i do upgrade using gitlab individuals 
component to fix this issue. that is, Example hyperkitty version installed 
already using mailman bundler. but is it possible for me to do upgrade 
hyperkitty using gitlab individual component latest version will fix this 
issue? Please treat this urgent request and totally stagnant now.
 

On Wednesday, March 16, 2016 5:06 PM, Barry Warsaw  wrote:
 

 On Mar 16, 2016, at 06:50 AM, scorpio 2005 via Mailman-Users wrote:

>Thanks for your reply. We are running mailman 3.0.2 using bundler and we are
>facing couple of issue with this version. We are stuck with this issues.  We
>are not sure which one is stable version in mailman to use it.

I suspect you will get better results running Mailman Core from the git master
branch.  While I am backporting fixes to the 3.0.x branch and releasing that
semi-regularly (e.g. 3.0.2) all new development, including the addition of new
features previously missing, happen only on master.  I expect that we'll
release 3.1 by Pycon 2016.

I know that bundler provides 3.0.2 right now, but it shouldn't be too
difficult to switch.  The few folks I know running Mailman 3 in production are
running Core off the git master branch.

Cheers,
-Barry


  
--
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] Start a new thread" button doesn't work - Mailman3.0.2 Panel

[Barry Warsaw]

On Mar 16, 2016, at 06:50 AM, scorpio 2005 via Mailman-Users wrote:

>Thanks for your reply. We are running mailman 3.0.2 using bundler and we are
>facing couple of issue with this version. We are stuck with this issues.  We
>are not sure which one is stable version in mailman to use it.

I suspect you will get better results running Mailman Core from the git master
branch.  While I am backporting fixes to the 3.0.x branch and releasing that
semi-regularly (e.g. 3.0.2) all new development, including the addition of new
features previously missing, happen only on master.  I expect that we'll
release 3.1 by Pycon 2016.

I know that bundler provides 3.0.2 right now, but it shouldn't be too
difficult to switch.  The few folks I know running Mailman 3 in production are
running Core off the git master branch.

Cheers,
-Barry
--
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] Start a new thread" button doesn't work - Mailman3.0.2 Panel

[scorpio 2005 via Mailman-Users]

Hi Mark,
Thanks for your reply. We are running mailman 3.0.2 using bundler and we are 
facing couple of issue with this version. We are stuck with this issues.
We are not sure which one is stable version in mailman to use it. Can you 
please tell me which mailman version is stable to setup it. If so, how can 
switch over or migrate my existing mailman 3.0.2 bundler to gitlab repository
Your valuable reply is highly appreciated.
Regards,Cool Pilot Scorpio

 

On Sunday, March 13, 2016 9:26 PM, Mark Sapiro  wrote:
 

 On 03/13/2016 08:19 AM, scorpio 2005 via Mailman-Users wrote:
> 
> 
> 
>  
> 
>  Hi Experts,  We setup mailman3 using bundler. Now, we are facingissue with 
>by clicking new thread button. That’s, after click create new thread and 
>clicksend button by typing some texts, it shows message sent successfully. 
>But, nothing is appearing inmailman admin panel. Please help and fix the issue.
>  Already posted in gitlab mailman forum. no response last 3 days till now.  
>Start and Reply button notworking from Mailman3 panel (#58) · Issues · mailman 
>/ HyperKitty


Your issue in the gitlab tracker is the appropriate place for this. The
mailman-users@python.org list is, of all the possibly appropriate
places, the place least likely to be seen by people actively working on
Postorius, Hyperkitty and Mailman 3.

There will very soon be a mailman-us...@mailman3.org list for general
questions. Until then, mailman-develop...@python.org is a better place
for those, and the gitlab issue trackers are probably the best place for
specific issues.


>  Refer attached screenshots for your reference.    Thanks and Regards,Cool 
>Pilot Scorpio  


Content filtering on these lists removes most non-text parts.

-- 
Mark Sapiro         The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/coolpilotscorpio%40yahoo.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] Start a new thread" button doesn't work - Mailman3.0.2 Panel

[Mark Sapiro]

On 03/13/2016 08:19 AM, scorpio 2005 via Mailman-Users wrote:
> 
> 
> 
>  
> 
>  Hi Experts,  We setup mailman3 using bundler. Now, we are facingissue with 
> by clicking new thread button. That’s, after click create new thread and 
> clicksend button by typing some texts, it shows message sent successfully. 
> But, nothing is appearing inmailman admin panel. Please help and fix the 
> issue.
>  Already posted in gitlab mailman forum. no response last 3 days till now.  
> Start and Reply button notworking from Mailman3 panel (#58) · Issues · 
> mailman / HyperKitty


Your issue in the gitlab tracker is the appropriate place for this. The
mailman-users@python.org list is, of all the possibly appropriate
places, the place least likely to be seen by people actively working on
Postorius, Hyperkitty and Mailman 3.

There will very soon be a mailman-us...@mailman3.org list for general
questions. Until then, mailman-develop...@python.org is a better place
for those, and the gitlab issue trackers are probably the best place for
specific issues.


>   Refer attached screenshots for your reference.Thanks and Regards,Cool 
> Pilot Scorpio  


Content filtering on these lists removes most non-text parts.

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

Re: [Mailman-Users] Announcing the new wiki.list.org

[Mark Sapiro]

The Mailman wiki (http://wiki.list.org/ has been getting some much
needed attention lately. In addition to the additions and cleaning up
http://wiki.list.org/RecentChanges that has been and is still going
on, there have been a couple of software changes since the initial move
to MoinMoin.

The wiki was initially running on the Ubuntu python-moinmoin
1.9.7-1ubuntu2 package. It is now running on the MoinMoin 1.9.8 source
distribution.

There is a change log at
http://hg.moinmo.in/moin/1.9/file/1.9.8/docs/CHANGES, but we don't
know which if any of the changes might have been backported in the
Ubuntu package, and we don't know what Ubuntu package specific things we
might have undone.

Noticeable changes at this point include a choice of the text or the GUI
editor where previously only the text editor was offered (you can change
this in your preferences) and a few bug fixes.

The wiki is also now being served through mod_wsgi which may result in
faster response, but probably won't be noticeable.

Otherwise, the wiki should be working the same as it has been since the
initial move to MoinMoin five weeks ago.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



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

Re: [Mailman-Users] Creating a new list - Bug in Mailman version 2.1.15

[Kevin Nowaczyk]

 Postconf Output
...
 alias_maps = hash:/etc/aliases
...
 mailman_destination_recipient_limit = 1
...
 relay_domains = lists.domain3.com
 relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman
...
 transport_maps = hash:/etc/postfix/transport
 virtual_alias_domains = list.domain3.com


I'm confused about list.domain3.com vs. lists.domain3.com in relay_domains.
 You are correct, this was a typo in main.cf, and has been changed. 


 virtual_alias_maps = hash:/etc/postfix/virtual, 
 hash:/var/www/domain3.com/domain3-virtual, 
 hash:/var/lib/mailman/data/virtual-mailman
...
 Feb 25 16:48:48 bunsen postfix/virtual[3850]: 65F271C37A: 
 to=mailingl...@domain3.com, relay=virtual, delay=0.22, 
 delays=0.2/0.02/0/0.01, dsn=5.1.1, status=bounced (unknown user: 
 mailingl...@domain3.com)

It appears your mail is being mapped to mailingl...@domain3.com via the
mapping in /var/lib/mailman/data/virtual-mailman, and there is probably
an alias for this address in /var/lib/mailman/data/aliases, but there is
no hash:/var/lib/mailman/data/aliases in alias_maps.

/var/lib/mailman/data/virtual-mailman has the line:
mailingl...@lists.domain3.com  MailingList

and /var/lib/mailman/data/aliases contains the line
MailingList: |/var/lib/mailman/mail/mailman post MailingList

You are correct, the alias_maps line in /etc/postfix/main.cf does not reference 
hash:/var/lib/mailman/data/aliases I changed it to be:
alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases

and now it appears to work.

It is not completely clear to me what's going on, but it looks like you
have a Debian/Ubuntu package and are using postfix_to_mailman.py as a
transport. I'd know more if I saw /etc/postfix/transport and
/etc/postfix/master.cf.

If my thought above is correct, the issue is all lists should be in the
same domain. See the FAQ at http://wiki.list.org/x/15564817 for more.
I AM using Debian, but in setting up mailman, the FAQ makes 
postfix_to_mailman.py out to be a bad idea, so I abandoned it and tried to do 
things The Right Way™. The alias_map was probably the core problem.  Thanks 
for the help!
Kevin Nowaczyk
--
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] Creating a new list - Bug in Mailman version 2.1.15

[Mark Sapiro]

On 02/25/2015 08:53 AM, Kevin Nowaczyk wrote:
 Postconf Output
...
 alias_maps = hash:/etc/aliases
...
 mailman_destination_recipient_limit = 1
...
 relay_domains = lists.domain3.com
 relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman
...
 transport_maps = hash:/etc/postfix/transport
 virtual_alias_domains = list.domain3.com


I'm confused about list.domain3.com vs. lists.domain3.com in relay_domains.


 virtual_alias_maps = hash:/etc/postfix/virtual, 
 hash:/var/www/domain3.com/domain3-virtual, 
 hash:/var/lib/mailman/data/virtual-mailman
...
 Feb 25 16:48:48 bunsen postfix/virtual[3850]: 65F271C37A: 
 to=mailingl...@domain3.com, relay=virtual, delay=0.22, 
 delays=0.2/0.02/0/0.01, dsn=5.1.1, status=bounced (unknown user: 
 mailingl...@domain3.com)

It appears your mail is being mapped to mailingl...@domain3.com via the
mapping in /var/lib/mailman/data/virtual-mailman, and there is probably
an alias for this address in /var/lib/mailman/data/aliases, but there is
no hash:/var/lib/mailman/data/aliases in alias_maps.

It is not completely clear to me what's going on, but it looks like you
have a Debian/Ubuntu package and are using postfix_to_mailman.py as a
transport. I'd know more if I saw /etc/postfix/transport and
/etc/postfix/master.cf.

If my thought above is correct, the issue is all lists should be in the
same domain. See the FAQ at http://wiki.list.org/x/15564817 for more.

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

Re: [Mailman-Users] Creating a new list - Bug in Mailman version 2.1.15

[Kevin Nowaczyk]

Postconf Output

alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
inet_interfaces = all
mailbox_size_limit = 0
mailman_destination_recipient_limit = 1
mydestination = domain2.com, bunsen.domain1.com, localhost.domain1.com, 
localhost, lists.domain3.com
myhostname = bunsen.domain1.com
mynetworks = 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
myorigin = /etc/mailname
readme_directory = no
recipient_delimiter = +
relay_domains = lists.domain3.com
relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman
relayhost =
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtpd_use_tls = yes
transport_maps = hash:/etc/postfix/transport
virtual_alias_domains = list.domain3.com
virtual_alias_maps = hash:/etc/postfix/virtual, 
hash:/var/www/domain3.com/domain3-virtual, 
hash:/var/lib/mailman/data/virtual-mailman
virtual_mailbox_base = /var/spool/mail
virtual_mailbox_domains = domain3.com

--
From /var/log/mail.info

Feb 25 16:48:47 bunsen postfix/smtpd[3845]: connect from 
mail-wg0-f54.google.com[74.125.82.54]
Feb 25 16:48:48 bunsen postfix/smtpd[3845]: 65F271C37A: 
client=mail-wg0-f54.google.com[74.125.82.54]
Feb 25 16:48:48 bunsen postfix/cleanup[3849]: 65F271C37A: 
message-id=canfwnp5dtwnrzhca6sem2jpae5+j2hzgjdc9w+we3z5kz+s...@mail.gmail.com
Feb 25 16:48:48 bunsen postfix/qmgr[19544]: 65F271C37A: from=m...@gmail.com, 
size=6385, nrcpt=1 (queue active)
Feb 25 16:48:48 bunsen postfix/virtual[3850]: 65F271C37A: 
to=mailingl...@domain3.com, relay=virtual, delay=0.22, 
delays=0.2/0.02/0/0.01, dsn=5.1.1, status=bounced (unknown user: 
mailingl...@domain3.com)
Feb 25 16:48:48 bunsen postfix/cleanup[3849]: 977381C382: 
message-id=20150225164848.977381c...@bunsen.domain3.com
Feb 25 16:48:48 bunsen postfix/qmgr[19544]: 977381C382: from=, size=8296, 
nrcpt=1 (queue active)
Feb 25 16:48:48 bunsen postfix/bounce[3851]: 65F271C37A: sender non-delivery 
notification: 977381C382
Feb 25 16:48:48 bunsen postfix/qmgr[19544]: 65F271C37A: removed
Feb 25 16:48:48 bunsen postfix/smtpd[3845]: disconnect from 
mail-wg0-f54.google.com[74.125.82.54]
Feb 25 16:48:48 bunsen postfix/smtp[3852]: connect to 
gmail-smtp-in.l.google.com[2607:f8b0:400d:c07::1a]:25: Network is unreachable
Feb 25 16:48:50 bunsen postfix/smtp[3852]: 977381C382: to=m...@gmail.com, 
relay=gmail-smtp-in.l.google.com[173.194.204.26]:25, delay=2, 
delays=0/0.02/0.26/1.7, dsn=2.0.0, status=sent (250 2.0.0 OK 1424882930 
u39si15292123qge.27 - gsmtp)
Feb 25 16:48:50 bunsen postfix/qmgr[19544]: 977381C382: removed
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Creating a new list - Bug in Mailman version 2.1.15

[Kevin Nowaczyk]

Your aliases and virtual-mailman were never updated for newlist because
of the permissions error. Run Mailman's bin/genaliases to rebuild these.

Or, possibly newlist was never created because of the error. Does
bin/list_lists show it?

I ran genaliases and there was no output (hopefully a good thing). The list 
does show up on list_lists and the addresses are in the virtual-aliases table.

Mail to the list still was not being accepted by the mail server. I deleted the 
list and recreated it an did not receive the bug in Mailman screen. Mailman 
did send me an email telling me that the list was created, and when I added 
another email address of mine to the list, it sent an email to that address as 
well. However, it is still not accepting emails from the subscribed email 
address.

Kevin
--
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] Creating a new list - Bug in Mailman version 2.1.15

[Mark Sapiro]

On 02/22/2015 05:42 AM, Kevin Nowaczyk wrote:
 Feb 22 12:45:54 2015 (19172) command failed: /usr/sbin/postalias 
 /var/lib/mailman/data/aliases (status: 1, Operation not permitted)
 
 I'm assuming it's a permission problem. If so, what should permissions be, 
 and what files do I need to modify? Do I just need to add the www-data user 
 to the lists group?


The files in question are /var/lib/mailman/data/aliases and
/var/lib/mailman/data/aliases.db. Also check
/var/lib/mailman/data/virtual-mailman and
/var/lib/mailman/data/virtual-mailman.db if they exist.

Adding www-data to the list group should not be needed and in fact won't
help unless something else is wrong as the create CGI wrapper should be
in mailman's group (list or whatever) and SETGID so the process is
already running with effective group list.

All four (if they exist) of the above files should be group writable and
Mailman's group (list or whatever).

The owner is not significant except in the case of aliases.db because
Postfix invokes the mail wrapper as the group of the owner of the
aliases.db file, so if mail delivery is working, don't change this.

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

Re: [Mailman-Users] This is new

[Mark Sapiro]

On 08/16/2014 08:34 PM, Mark J Bradakis wrote:


Indeed. I can go to the listinfo page, click on the archives for the bad
lists, browse the archives, no problem.



And after doing this is the list's data_version still 98? If so, I 
suspect some permissions issue or something like that?


What's in Mailman's 'error' log?



Go to get a password reminder mailed to me, it claims to work but
nothing is actually sent out.



This can happen if the email address you entered is not a list member. 
What's in Mailman's 'mischief' log?


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

Re: [Mailman-Users] This is new

[Mark Sapiro]

On 08/17/2014 06:45 AM, Mark Sapiro wrote:

On 08/16/2014 08:34 PM, Mark J Bradakis wrote:


Indeed. I can go to the listinfo page, click on the archives for the bad
lists, browse the archives, no problem.



And after doing this is the list's data_version still 98? If so, I
suspect some permissions issue or something like that?



Can you go to the admin page for the list? If so, does the from_is_list 
setting appear there?


Have you run bin/check_perms?

Does your Mailman web UI go to the right installation?

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

Re: [Mailman-Users] This is new

[Mark J Bradakis]

Mark Sapiro wrote:

On 08/16/2014 08:34 PM, Mark J Bradakis wrote:


Indeed. I can go to the listinfo page, click on the archives for the bad
lists, browse the archives, no problem.



And after doing this is the list's data_version still 98? If so, I suspect some 
permissions issue or something like that?


Yes, the data_version remains unchanged. The first thing I did was run 
check_perms, nothing showed up there.


What's in Mailman's 'error' log?


Actually something did change. Instead of 'from_is_list' the error now is 
'dmarc_moderation_action'




Go to get a password reminder mailed to me, it claims to work but
nothing is actually sent out.



This can happen if the email address you entered is not a list member. What's 
in Mailman's 'mischief' log?


I used an address I know is a list member, nothing related to it in mischief 
log.

The last time I had a really weird problem like this it turned out to be some 
bad disk blocks in the mailman tree.
I may take the machine to single user and do some disk checks.

mjb.

 


--
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] This is new

[Mark J Bradakis]

Mark Sapiro wrote:
 


Can you go to the admin page for the list? If so, does the from_is_list setting 
appear there?


Sort of. I get the login page for the list just fine, type in the password then 
get the 'hit a bug' page.

Error log shows:

admin(2802):   File /local/mailman/teamnet/Mailman/MailList.py, line 146, in 
__getattr__
admin(2802): raise AttributeError, name
admin(2802): AttributeError: from_is_list


mjb.


--
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] This is new

[Mark Sapiro]

On August 17, 2014 11:32:52 AM PDT, Mark J Bradakis m...@bradakis.com wrote:
Mark Sapiro wrote:
 On 08/16/2014 08:34 PM, Mark J Bradakis wrote:

 Indeed. I can go to the listinfo page, click on the archives for the
bad
 lists, browse the archives, no problem.


 And after doing this is the list's data_version still 98? If so, I
suspect some permissions issue or something like that?

Yes, the data_version remains unchanged. The first thing I did was run
check_perms, nothing showed up there.

 What's in Mailman's 'error' log?

Actually something did change. Instead of 'from_is_list' the error now
is 'dmarc_moderation_action'


 Go to get a password reminder mailed to me, it claims to work but
 nothing is actually sent out.


 This can happen if the email address you entered is not a list
member. What's in Mailman's 'mischief' log?

I used an address I know is a list member, nothing related to it in
mischief log.

The last time I had a really weird problem like this it turned out to
be some bad disk blocks in the mailman tree.
I may take the machine to single user and do some disk checks.


This is really weird. A few things come to mind. Perhaps data_version in the 
file is not a integer but Is a string or something with some white space that 
compares greater than 10 4.

Maybe there is some hardware or system disk caching problem.

If you installed from a package you might contact the packager.

Otherwise you might compare your Mailman/MailList.py and Mailman/versions.py 
with the ones in the source tarball.

I am now going off line for 2 weeks.

-- 
Mark Sapiro m...@msapiro.net
Sent from my Android phone with K-9 Mail. [Unpaid endorsement]
--
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] This is new

[Mark J Bradakis]

As an added bit of info, the first 7 of 67 lists, in alphabetical order all 
have this
problem. Maybe I just need to reinstall  2.1.18-1

mjb.


--
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] This is new

[Mark Sapiro]

On 08/16/2014 03:43 PM, Mark J Bradakis wrote:

S I finally decide to sit down and try to figure out why
http://www.team.net/mailman/admin
and http://autox.team.net/mailman/admin return different results, even
though it is the same machine.



See the FAQ at http://wiki.list.org/x/lYA9.



Checking on some list configs, I do  bin/config_list -o - listname and
get this from one list,
but not others:

[...]
# href=?VARHELP=privacy/sender/dmarc_moderation_action
# dmarc_moderation_action applies to this message with an action other
# than Accept, that action rather than this is applied
Traceback (most recent call last):
   File ./config_list, line 364, in module
 main()
   File ./config_list, line 357, in main
 do_output(listname, outfile)
   File ./config_list, line 128, in do_output
 do_list_categories(mlist, k, None, outfp)
   File ./config_list, line 180, in do_list_categories
 value = getattr(mlist, varname)
   File /local/mailman/teamnet/Mailman/MailList.py, line 146, in
__getattr__
 raise AttributeError, name
AttributeError: from_is_list



So I go to the admin page for that list and get the We've hit a bug page.

Fun. Any quick fixes to the config.pck file?



There is an issue with the list's data_version attribute vs. 
Mailman.Version.DATA_FILE_VERSION. When the from_is_list and other new 
attributes were added, Mailman.Version.DATA_FILE_VERSION was incremented 
to make it greater than the list's data_version attribute which in turn 
will cause the lists to be updated the first time they are instantiated.


Perhaps you had some other patches that incremented 
Mailman.Version.DATA_FILE_VERSION, so that the list's data_version 
attribute was not  Mailman.Version.DATA_FILE_VERSION causing the update 
to be skipped.


The way to fix this is to set Mailman.Version.DATA_FILE_VERSION to a 
value greater than the data_version attribute of the lists.


First run this bash script

for l in `/path/to/mailman/bin/list_lists --bare`
  do /path/to/mailman/bin/dumpdb /path/to/mailman/lists/$l/config.pck \
| grep data_version
  done

This will print the data_version for each list. If N is the largest such 
value, edit Mailman/Version.py to change the line


DATA_FILE_VERSION = 104

to set a value  N. Then visit the listinfo overview page which should 
update all the lists.


Then so this doesn't happen again, set DATA_FILE_VERSION back to 104 in 
Mailman/Version.py and create a file containing the single line


mlist.data_version = 104

and run this bash script

cd /path/to/mailman/bin/
for l in `./list_lists --bare`
 do ./config_list -i /path/to/above/file $l
 done

That should fix things.

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

Re: [Mailman-Users] This is new

[Mark J Bradakis]

There is an issue with the list's data_version attribute vs. 
Mailman.Version.DATA_FILE_VERSION. When the from_is_list and other new 
attributes were added, Mailman.Version.DATA_FILE_VERSION was incremented to 
make it greater than the list's data_version attribute which in turn will cause 
the lists to be updated the first time they are instantiated.

Perhaps you had some other patches that incremented 
Mailman.Version.DATA_FILE_VERSION, so that the list's data_version attribute was 
not  Mailman.Version.DATA_FILE_VERSION causing the update to be skipped.

The way to fix this is to set Mailman.Version.DATA_FILE_VERSION to a value 
greater than the data_version attribute of the lists.

First run this bash script

for l in `/path/to/mailman/bin/list_lists --bare`
   do /path/to/mailman/bin/dumpdb /path/to/mailman/lists/$l/config.pck \
 | grep data_version
   done

This will print the data_version for each list. If N is the largest such value, 
edit Mailman/Version.py to change the line

DATA_FILE_VERSION = 104

to set a value  N. Then visit the listinfo overview page which should update 
all the lists.

Then so this doesn't happen again, set DATA_FILE_VERSION back to 104 in 
Mailman/Version.py and create a file containing the single line

mlist.data_version = 104

and run this bash script

cd /path/to/mailman/bin/
for l in `./list_lists --bare`
  do ./config_list -i /path/to/above/file $l
  done

That should fix things.



The problem lists all have 98 as the data_version.  Config_list does not work, 
for input or output.

mjb.

--
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] This is new

[Mark Sapiro]

On 08/16/2014 07:20 PM, Mark J Bradakis wrote:


The problem lists all have 98 as the data_version.  Config_list does not
work, for input or output.



I understood that config_list wouldn't work. That's why I suggested that 
you need first to fix the lists by changing DATA_FILE_VERSION in 
Mailman/Version.py and then instantiating the lists to fix them.


However, There would seem to be other issues.

You say the problem lists all have data_version = 98 (Mailman 2.1.14). 
What do the other lists have? What is DATA_FILE_VERSION in 
Mailman/Version.py? If it is  98 an Mailman/versions.py is at least as 
new as 2.1.16, the lists should get a from_is_list attribute and have 
data_version updated when they are instantiated.


Perhaps reinstalling 2.1.18-1 would help, as something seems amiss.

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

Re: [Mailman-Users] This is new

[Mark J Bradakis]

Mark Sapiro wrote:



I understood that config_list wouldn't work. That's why I suggested that you 
need first to fix the lists by changing DATA_FILE_VERSION in Mailman/Version.py 
and then instantiating the lists to fix them.


I guess I am not understanding what you mean by instantiating existing lists.  
All the others have version 104, as does the Version.py file.

mjb.


--
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] This is new

[Mark Sapiro]

On 08/16/2014 08:04 PM, Mark J Bradakis wrote:


I guess I am not understanding what you mean by instantiating existing
lists.  All the others have version 104, as does the Version.py file.



Anything you do which accesses a list's config.pck via 
Mailman/MailList.py (which is pretty much any Mailman process other than 
bin/dumpdb) will test if Mailman.Version.DATA_FILE_VERSION is greater 
than the list's data_version and if so, will run 
Mailman.versions.Update() to update the list configuration, add new 
attributes, etc.


Clearly this is not happening in your case because the from_is_list 
attribute is not being added.


Does your Mailman/versions.py contain

PreferStored('author_is_list', 'from_is_list',
 mm_cfg.DEFAULT_FROM_IS_LIST)

at lines 317,318?

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

Re: [Mailman-Users] This is new

[Mark J Bradakis]

Mark Sapiro wrote:
 


Anything you do which accesses a list's config.pck via Mailman/MailList.py 
(which is pretty much any Mailman process other than bin/dumpdb) will test if 
Mailman.Version.DATA_FILE_VERSION is greater than the list's data_version and 
if so, will run Mailman.versions.Update() to update the list configuration, add 
new attributes, etc.

Clearly this is not happening in your case because the from_is_list attribute 
is not being added.


Indeed. I can go to the listinfo page, click on the archives for the bad lists, 
browse the archives, no problem.
Go to get a password reminder mailed to me, it claims to work but nothing is 
actually sent out.


Does your Mailman/versions.py contain

 PreferStored('author_is_list', 'from_is_list',
  mm_cfg.DEFAULT_FROM_IS_LIST)

at lines 317,318?




Yes.

mjb.


--
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] building a new mailman server

[Stephen J. Turnbull]

Sajan Parikh writes:

  sendmail is still widely used, and if I were you, I'd just stick with 
  what works unless you have you a particular need that sendmail wasn't 
  filling.

+1 with caveat:

Exim and Postfix both have recipes for working with Mailman 3.  It
seems likely to me that it won't be hard to get Mailman 3 and
Sendmail to work and play well together -- but nobody has done it yet.

--
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] building a new mailman server

[Adam McGreggor]

On Wed, Mar 26, 2014 at 09:32:50PM -0700, Carl Zwanzig wrote:
 On 3/26/2014 3:33 PM, Mark Sapiro wrote:
 I'd be inclined to chose Postfix over Exim simply because Postfix is
 more popular, and new things (e.g. Mailman 3) tend to be implemented
 first for Postfix.
 
 FWIW, I found postfix to be generally easier to deal with than the
 others. And the config files don't look like line noise with
 comments :).

grep -v ^\# exim.conf is too much?

I don't know if it's down to popularity or not, but I notice far more
questions on this list concerning Postfix than I do exim.

(Exim user/admin for 10 years here)

-- 
Suburbia: where they cut down the trees then name streets after them
--
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] building a new mailman server

[Barry Warsaw]

On Mar 27, 2014, at 05:26 PM, Stephen J. Turnbull wrote:

Exim and Postfix both have recipes for working with Mailman 3.  It
seems likely to me that it won't be hard to get Mailman 3 and
Sendmail to work and play well together -- but nobody has done it yet.

It's certainly the intent of the project to interoperate with any FLOSS MTA.

It should be rather trivial to integrate MM3 with any MTA that supports LMTP
delivery (currently the only supported method) which includes Postfix and
Exim, and should include Sendmail afaik.  For the most part, not much needs to
be done on the Mailman side, so it's mostly getting your MTA configured
correctly.  Contributions welcome of course!

-Barry
--
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] building a new mailman server

[Sebastian Hagedorn]

--On 27. März 2014 09:22:02 -0400 Barry Warsaw ba...@list.org wrote:


On Mar 27, 2014, at 05:26 PM, Stephen J. Turnbull wrote:


Exim and Postfix both have recipes for working with Mailman 3.  It
seems likely to me that it won't be hard to get Mailman 3 and
Sendmail to work and play well together -- but nobody has done it yet.


It's certainly the intent of the project to interoperate with any FLOSS
MTA.

It should be rather trivial to integrate MM3 with any MTA that supports
LMTP delivery (currently the only supported method) which includes
Postfix and Exim, and should include Sendmail afaik.  For the most part,
not much needs to be done on the Mailman side, so it's mostly getting
your MTA configured correctly.  Contributions welcome of course!


We are a Sendmail shop, so perhaps I can find the time to help with that. 
It does support LMTP delivery, so that's not an issue.


Cheers
Sebastian
--
   .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:.
.:.Regionales Rechenzentrum (RRZK).:.
  .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.
--
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] building a new mailman server

[Gary Algier]

On 03/27/14 04:26, Stephen J. Turnbull wrote:

Sajan Parikh writes:

   sendmail is still widely used, and if I were you, I'd just stick with
   what works unless you have you a particular need that sendmail wasn't
   filling.

+1 with caveat:

Exim and Postfix both have recipes for working with Mailman 3.  It
seems likely to me that it won't be hard to get Mailman 3 and
Sendmail to work and play well together -- but nobody has done it yet.



I have it working fine.  I recently replaced a very old implementation
of sendmail and Mailman on Solaris with a new one on CentOS 6.  When I
did so, I used the POSTFIX_ALIAS_CMD mechanism to automatically process
the aliases.  See: 
https://mail.python.org/pipermail/mailman-users/2004-June/037518.html


In mm_cfg.py:
MTA='Postfix'
POSTFIX_ALIAS_CMD = '/usr/bin/sudo /etc/mail/import-mailman-aliases'
/etc/mail/import-mailman-aliases contains:
#! /bin/sh
/bin/cp /etc/mailman/aliases /etc/mail/mailman.aliases
/usr/bin/newaliases
In /etc/sudoers.d/mailman:
Cmnd_Alias IMPORT_MAILMAN_ALIASES = /etc/mail/import-mailman-aliases
apache ALL= NOPASSWD: IMPORT_MAILMAN_ALIASES
mailman ALL= NOPASSWD: IMPORT_MAILMAN_ALIASES
Defaults!IMPORT_MAILMAN_ALIASES !requiretty
In the sendmail.mc file I changed:
define(`ALIAS_FILE', `/etc/aliases')dnl
to:
define(`ALIAS_FILE', `/etc/aliases,/etc/mail/mailman.aliases')dnl
so that the Mailman aliases would be in a separate file.

Warning: You need to have Mailman 2.1.15 or better (or patch it).
See this bug: https://bugs.launchpad.net/mailman/+bug/266408.
A fix is here: 
http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1291

(Thanks to Mark Sapiro)

I stayed with sendmail because I am using LDAP for aliases and routing and I 
did not want to figure out how to do it with Postfix.  My one exposure to 
Postfix was a disaster trying to fix the email services on our marketing 
department's web server at a hosting provider that did not support sendmail. 
Perhaps with time, I could have made it work for our mail server, but the 
duckling syndrome may have set in (yes, I still use vi and sometimes ed).


--
Gary Algier, WB2FWZg...@ulticom.com +1 856 787 2758
Ulticom Inc., 1020 Briggs Rd, Mt. Laurel, NJ 08054 Fax:+1 856 866 2033

Nielsen's First Law of Computer Manuals:
People don't read documentation voluntarily.
--
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] building a new mailman server

[Carl Zwanzig]

On 3/27/2014 2:48 AM, Adam McGreggor wrote:

I don't know if it's down to popularity or not, but I notice far more
questions on this list concerning Postfix than I do exim.


I suspect it's due to installed base- my very unscientific survey says that 
there are far more sendmail and postfix sites than exim sites. (In the end, 
I also suspect this is rather like the perl/tcl/python/ruby arguments; take 
whatever works for you and run with it.)


z!

--
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] building a new mailman server

[Hank van Cleef]

The esteemed Mark Sapiro has said:
 
 On 03/26/2014 02:19 PM, Bruce Harrison wrote:
  
  We are currently running an old mailman instance and am planning to bring 
  up the newest version of mailman and migrate to it.  Current system uses 
  sendmail.  Since I now have a chance to change things, what is the best 
  mail server to run on my mailman box?  It will be talking to an exchange 
  2010 frontend server (current mailman system is doing that now).  I can 
  install sendmail or go with postfix or ???
  This is running on a debian box.
 
 
 Disclaimer: I am not an MTA expert. This is all personal opinion based
 on possibly limited experience.
 
 I would go with either Postfix or Exim. Both integrate well with
 Mailman; http://www.exim.org/howto/mailman21.html and
 http://www.list.org/mailman-install/node12.html.
 
 I have used both in Mailman environments, but Exim only in a Mailman
 development environment, Postfix both in development and on a production
 server handling both Mailman and other mail.
 
 I have little experience with sendmail, and while it is possible to
 hijack Mailman's Postfix integration to use with sendmail, on the whole
 it seems 'clunkier' to configure, and I see no reason to chose sendmail
 over Postfix.
 
I'm not an MTA expert, either.  However, I've used sendmail ever
since there was a sendmail.  My systems are Solaris, which comes with
a good implementation of sendmail, and my installations are all
configured to do what I want them to do with regular e-mail.  

I found adding Mailman to my existing setups to be quite simple.
You'll need to manually add the Mailman pipes to the aliases, using
the Mailman utility that gives you the list, but with the vi editor,
it's a simply copy-and-paste.  The only issue I had with integrating
Mailman with sendmail was getting the Masquerades set up properly to
host a different domain on my systems.  however, that is covered in 
the O'Reilly Bat Book, which you should have.  It is not a Mailman
issue, and proper configuration is done through the M4 macro files.  
I haven't had to tamper with the sendmail.cf file separately.

I think that if you're familiar with sendmail, and have a satisfactory
setup, do your upgrade, and integrate it with your current sendmail.
I'm aware that most of the people posting to this list are using other
MTA's on Linux systems, so there's little support here for a sendmail
setup.  

For reference, my links between Mailman and sendmail are through
localhost to a local sendmail, and I also have a caching DNS server,
all on the same box.  

For me, switching to another MTA would mean a lot of work learning how
to integrate all of the spam filtering and other things I already have
integrated and working in sendmail.  

Hank
--
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] building a new mailman server

[Bruce Harrison]

Thanks to all who replied.  Since I've used sendmail and have limited 
experience with it, I decided to go with that.  Less variables in the mix!  :)

Anyway, proceeded with the install and got to make install, which failed with 
Permission denied for the mkdir commands.
I'm running from a non-root userid who has a membership in the mailman group.  
The directory /usr/local/mailman has rws privs for the mailman group (but is 
owned by root).  Do I need to do a sudo make install or am I missing some type 
of privilege setting?  

Bruce
UTM


--
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] building a new mailman server

[Mark Sapiro]

On 03/27/2014 02:40 PM, Bruce Harrison wrote:
 
 Anyway, proceeded with the install and got to make install, which failed with 
 Permission denied for the mkdir commands.
 I'm running from a non-root userid who has a membership in the mailman group. 
  The directory /usr/local/mailman has rws privs for the mailman group (but is 
 owned by root).  Do I need to do a sudo make install or am I missing some 
 type of privilege setting?  


Yes, I think you may need to 'sudo make install'. Either that or chown
the /usr/local/mailman directory to the user you're running as.

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

Re: [Mailman-Users] building a new mailman server

[Stephen J. Turnbull]

Gary Algier writes:
  On 03/27/14 04:26, Stephen J. Turnbull wrote:

   Exim and Postfix both have recipes for working with Mailman 3.  It
   seems likely to me that it won't be hard to get Mailman 3 and
   Sendmail to work and play well together -- but nobody has done it yet.
  
  
  I have it working fine.

Did you notice I specified Mailman **3**?

  Warning: You need to have Mailman 2.1.15 or better (or patch it).

Mailman 3 is not a trivial upgrade from Mailman 2.x.

--
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] building a new mailman server

[Sajan Parikh]

It seems the 3 most popular MTAs are sendmail, Exim, and Postfix.  All 
do the job well if you're running just a standard install of mailman 
without much fuss.


sendmail is still widely used, and if I were you, I'd just stick with 
what works unless you have you a particular need that sendmail wasn't 
filling.


Sajan Parikh
On 03/26/2014 04:19 PM, Bruce Harrison wrote:

We are currently running an old mailman instance and am planning to bring up 
the newest version of mailman and migrate to it.  Current system uses sendmail. 
 Since I now have a chance to change things, what is the best mail server to 
run on my mailman box?  It will be talking to an exchange 2010 frontend server 
(current mailman system is doing that now).  I can install sendmail or go with 
postfix or ???
This is running on a debian box.

Bruce Harrison
UT Martin
--
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/sajan%40parikh.io



--
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] building a new mailman server

[Mark Sapiro]

On 03/26/2014 02:19 PM, Bruce Harrison wrote:
 
 We are currently running an old mailman instance and am planning to bring up 
 the newest version of mailman and migrate to it.  Current system uses 
 sendmail.  Since I now have a chance to change things, what is the best mail 
 server to run on my mailman box?  It will be talking to an exchange 2010 
 frontend server (current mailman system is doing that now).  I can install 
 sendmail or go with postfix or ???
 This is running on a debian box.


Disclaimer: I am not an MTA expert. This is all personal opinion based
on possibly limited experience.

I would go with either Postfix or Exim. Both integrate well with
Mailman; http://www.exim.org/howto/mailman21.html and
http://www.list.org/mailman-install/node12.html.

I have used both in Mailman environments, but Exim only in a Mailman
development environment, Postfix both in development and on a production
server handling both Mailman and other mail.

My impression is that if you want to do esoteric things, it's easier (at
least for a coder like me) with Exim's routers and transports than with
Postfix, but I've always been able to accomplish whatever I've wanted
with Postfix.

I have little experience with sendmail, and while it is possible to
hijack Mailman's Postfix integration to use with sendmail, on the whole
it seems 'clunkier' to configure, and I see no reason to chose sendmail
over Postfix.

I'd be inclined to chose Postfix over Exim simply because Postfix is
more popular, and new things (e.g. Mailman 3) tend to be implemented
first for Postfix.

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

Re: [Mailman-Users] building a new mailman server

[Carl Zwanzig]

On 3/26/2014 3:33 PM, Mark Sapiro wrote:

I'd be inclined to chose Postfix over Exim simply because Postfix is
more popular, and new things (e.g. Mailman 3) tend to be implemented
first for Postfix.


FWIW, I found postfix to be generally easier to deal with than the others. 
And the config files don't look like line noise with comments :).


z!

--
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] Configuration of New Mailman Instance

[Mark Sapiro]

On 03/14/2014 03:12 PM, Paul Crown wrote:
 
 My scenerio:
 
 Server W is running Apache2, and my initial config has
 http://lists.mydomain.com letting me login as admin and create new lists.
 Server P is running Postfix
 Server R is my mail-relay for outbound SMTP traffic unique to this domain
 
 No messages are being sent out through R or any other server for that
 matter.
 No messages are being received by P.  (5.1.1 list-email address
 rejected: user unknown in relay recipient table.


Which server has Mailman installed?

It looks like W.

This can work, but I might install Mailman on P and configure Postfix on
P per http://www.list.org/mailman-install/node12.html.

If Mailman is on W, you have to configure Postfix on P to relay list
mail to W and have some kind of MTA/MDA on W to deliver that mail to
Mailman.

If Mailman is on P you need to share Mailman's file system or at least
$var-prefix via NFS or whatever between W and P.

Either way, you need to set SMTPHOST in Mailman/mm_cfg.py to point to R.

If your only issue is P's user unknown in relay recipient table see
user unknown in relay recipient table for how to get Mailman to write
it's virtual-mailman file which can be used as relay_recipient_maps on P.

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

Re: [Mailman-Users] Configuration of New Mailman Instance

[Mark Sapiro]

On 03/15/2014 10:45 AM, Mark Sapiro wrote:
 
 If your only issue is P's user unknown in relay recipient table see
 user unknown in relay recipient table for how to get Mailman to write
 it's virtual-mailman file which can be used as relay_recipient_maps on P.


Ooops... copy/paste error. That should be

... see http://www.list.org/mailman-install/node12.html for how to get
Mailman to write it's virtual-mailman file ...

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

Re: [Mailman-Users] adding a new (second) domain to an existing mailman server?

[Mark Sapiro]

On 12/06/2013 09:34 AM, David wrote:
 
 We have a mailman server that was dedicated to a single domain and set up
 with the intention that this would never change. Now, I would like to add a
 second independent domain and create a new mailman list.
 
 In addition to the basic mailman how-to steps, I suspect I'll have
 questions that probably relate to apache and postfix. Is there a guide that
 covers all of this?


If your Mailman is installed from source, see
http://www.list.org/mailman-install/index.html, in particular
http://www.list.org/mailman-install/postfix-integration.html and
http://www.list.org/mailman-install/postfix-virtual.html.

If your Mailman is installed from a package or uses some third party
delivery module like postfix_to_mailman.py, see
http://wiki.list.org/x/OIDD.

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

Re: [Mailman-Users] Mailman / Postfix new list issue

[Mark Sapiro]

Dan Offord wrote:

I'm having an issue with any new lists created in Mailman, it appears
to be forcing each mailing lists host_name to: multiplay.co.uk

So any welcome emails specifically states:

To post to this list, send your message to:

 newl...@multiplay.co.uk

Where the host/domain for Mailman is set to lists.multiplay.co.uk

My mm_cfg.py is at http://pastie.org/4178388


The relevant lines of which are:

DEFAULT_URL_HOST = 'lists.multiplay.co.uk'
add_virtualhost('lists.multiplay.co.uk')
DEFAULT_EMAIL_HOST = 'lists.multiplay.co.uk'
host_name = 'lists.multiplay.co.uk'

The assignment to host_name in mm_cfg.py does nothing useful. remove it.

add_virtualhost() takes one or two arguments and creates a mapping from
a url host (web host) to an email host. If the email host argument is
ommitted, it is determined by stripping everything up to the first dot
'.' from the url host argument. This is documented in Defaults.py

# ...  If optional emailhost is
# omitted it defaults to urlhost with the first name stripped off, e.g.
#
# add_virtualhost('www.dom.ain')
# VIRTUAL_HOST['www.dom.ain']
# == 'dom.ain'

Thus,

add_virtualhost('lists.multiplay.co.uk')

is the same as

add_virtualhost('lists.multiplay.co.uk', 'multiplay.co.uk')

What you want in mm_cfg.py are these 3 lines in this order

DEFAULT_URL_HOST = 'lists.multiplay.co.uk'
DEFAULT_EMAIL_HOST = 'lists.multiplay.co.uk'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

Then, you can fix the host_name of the already created list either from
the web UI General Options page or by running fix_url {see
http://wiki.list.org/x/mIA9).

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] Mailman / Postfix new list issue

[Dan Offord]

On 1 July 2012 15:27, Mark Sapiro m...@msapiro.net wrote:

 The relevant lines of which are:

 DEFAULT_URL_HOST = 'lists.multiplay.co.uk'
 add_virtualhost('lists.multiplay.co.uk')
 DEFAULT_EMAIL_HOST = 'lists.multiplay.co.uk'
 host_name = 'lists.multiplay.co.uk'

 The assignment to host_name in mm_cfg.py does nothing useful. remove it.

 add_virtualhost() takes one or two arguments and creates a mapping from
 a url host (web host) to an email host. If the email host argument is
 ommitted, it is determined by stripping everything up to the first dot
 '.' from the url host argument. This is documented in Defaults.py

 # ...  If optional emailhost is
 # omitted it defaults to urlhost with the first name stripped off, e.g.
 #
 # add_virtualhost('www.dom.ain')
 # VIRTUAL_HOST['www.dom.ain']
 # == 'dom.ain'

 Thus,

 add_virtualhost('lists.multiplay.co.uk')

 is the same as

 add_virtualhost('lists.multiplay.co.uk', 'multiplay.co.uk')

 What you want in mm_cfg.py are these 3 lines in this order

 DEFAULT_URL_HOST = 'lists.multiplay.co.uk'
 DEFAULT_EMAIL_HOST = 'lists.multiplay.co.uk'
 add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

 Then, you can fix the host_name of the already created list either from
 the web UI General Options page or by running fix_url {see
 http://wiki.list.org/x/mIA9).

 --
 Mark Sapiro m...@msapiro.netThe highway is for gamblers,
 San Francisco Bay Area, Californiabetter use your sense - B. Dylan


Thank you Mark,

That fixed the issue I was seeing :)

Kind Regards,

Dan Offord

Technical Systems Administrator

Multiplay (UK) Ltd, Unit 7 Whitefield, Lepe Road, Blackfield
Southampton, Hampshire, SO45 1XR

Registered in England  Wales No. 3370594

Phone: +44 (0) 845 868 1337 | Direct: +44 (0) 56 000 36985
Twitter: @liv3d | Skype: mpukliv3d
This e.mail is private and confidential between Multiplay (UK) Ltd. and the 
person or entity to whom it is addressed. In the event of misdirection, the 
recipient is prohibited from using, copying, printing or otherwise 
disseminating it or any information contained in it.

In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk.

--
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] Migration to new server

[Mark Sapiro]

On 6/16/2011 8:35 AM, William Ashworth wrote:

 Currently, a client of mine has a mailman list running since 2006 on
 a server with a company they no longer do business with. We're
 wanting to consolidate resources for their organization and migrate
 them to a cPanel web host that supports mailman.


cPanel will be a complication if the old server is not also cPanel.


 Is there any concern about mailman versions between servers or
 anything else I might not be thinking of? What's the best way to go
 about moving them to another server supporting mailman?


As long as both Mailman versions are 2.1.x and the target version is as
new or newer than the source version and the source version uses the
standard MemberAdaptor (i.e. no custom member database), this is
normally completely straightforward. It may be complicated if going from
non-cPanel to cPanel.


 I can say with fair certainty that we don't have root access to the
 old server, so I'm not sure what needs to be planned for during a
 migration between service providers. Thanks.


You need to stop Mailman on the old server or at least be sure that your
lists are 'quiet'. You need to get all the lists/*/config.pck files and
all the archives/private/*.mbox/*.mbox files from the old server and
move them to the new server.

The cPanel complication is that the *'s above are listnames and in a
non-cPanel installation, the listname of the li...@example.com list is
'listx', but in cPanel it is 'listx_example.com', so those directories
and files will need to be placed on the cPanel machine with their cPanel
names. I think this is the only complication.

After moving the files, you should run Mailman's bin/check_perms to fix
any permission issues, run fix_url and run 'bin/arch --wipe LISTNAME'
using the cPanel listnames for each list to rebuild the pipermail
archive on the new host.

I'm not sure exactly how to run fix_url in a cPanel installation or if
it will even work, and I'm not sure it's necessary if the domain names
aren't changing. I'm guessing for li...@example.com, you could run

  bin/withlist -l -r fix_url listx_example.com -u example.com

but this may leave the list with an incorrect host_name. Maybe it's best
to not run it, do one list as a test and if things are OK, just proceed.

There is other information in the FAQ at http://wiki.list.org/x/2oA9
and there are other FAQs about fix_url and cPanel

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] Migration to new server

[Brian Carpenter]

On 6/16/2011 11:35 AM, William Ashworth wrote:

Currently, a client of mine has a mailman list running since 2006 on a server 
with a company they no longer do business with. We're wanting to consolidate 
resources for their organization and migrate them to a cPanel web host that 
supports mailman.

Is there any concern about mailman versions between servers or anything else I 
might not be thinking of? What's the best way to go about moving them to 
another server supporting mailman?

I can say with fair certainty that we don't have root access to the old server, 
so I'm not sure what needs to be planned for during a migration between service 
providers. Thanks.

Regards,
Will Ashworth



Hi Will:

We are a cpanel host that specializes in Mailman hosting. We have 
clients all the time migrating to our services from various different 
servers and versions and to date we have had no problems in moving them. 
All we ask for is the mbox file that governs their archives and the list 
configuration files that make up their list.


In case you haven't made a firm decision, I recommend checking us out at 
http://www.mailmanhost.com. When choosing any cpanel host that supports 
mailman, make sure that they are actually willing to support mailman AND 
that they are not throttling their smtp servers. A lot of cpanel hosts 
will limit how much email an account can send out per hour and that can 
cripple an active mailman list. Just some thoughts.


--
Brian Carpenter
Owner | EMWD  dotList
br...@emwd.com | http://www.emwd.com | http://www.mailmanhost.com


--
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] Advice on new install of Mailman to CentOS 5

[Mark Sapiro]

Richard Damon wrote:

The question comes in that the CentOS 5 distribution only has a RPM
for Mailman 2.1.9, instead of the recently released 2.1.14, so the
question comes do I use the RPM from the distribution and run a
version several years old, or is it better to install from a direct
download.


Quoting from the FAQ at http://wiki.list.org/x/tIA9

  It is possible to trick Plesk into recognizing newer versions
  installed manually but it's not for the faint of heart.


I am working of a fresh install so I don't need to worry
about migrating existing list on the server, but I definitely want to
be able to import the existing lists from the old server. (And will
probably do at least one dry run of the migration to a different
domain name just to make sure I know how to do this and that things
work before moving the live site).


The actual migration of list data from the old to the new installation
should be straightforward as long as the new installation is the same
or a newer version. See the initial section of the FAQ at
http://wiki.list.org/x/2oA9, and note that you may need to run
fix_url to update list domains and this should be done prior to
regenerating archives.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] mailman 2.1.14 new features

[Barry Warsaw]

On Oct 20, 2010, at 01:53 PM, Adam McGreggor wrote:

It appears that 'official' Mailman packages for lenny are a wee bit
behind upstream. 

I believe others on this list use the Umbungo packages on lenny
(Debian 5), without too many difficulties. YMMV.

(I don't really have the time to take on debian package maint, at the
moment.)

Sadly, I do not either, but I am willing to help anyone who steps forward to
do so.

-Barry


signature.asc
Description: PGP signature
--
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] mailman 2.1.14 new features

[Barry Finkel]

On Oct 20, 2010, at 01:53 PM, Adam McGreggor wrote:

It appears that 'official' Mailman packages for lenny are a wee bit
behind upstream.

I believe others on this list use the Umbungo packages on lenny
(Debian 5), without too many difficulties. YMMV.

(I don't really have the time to take on debian package maint, at the
moment.)

Barry Warsaw ba...@list.org replied:
Sadly, I do not either, but I am willing to help anyone who steps
forward to do so.

-Barry

As I have posted before, I looked at the Debian packaging for
Mailman, and I found there are lots of patches (most undocumented
as to what they do).  There was one patch that removed a library
that may be needed.  And one security of three I researched had
different code in Debian/Ubuntu than in SourceForge.  I assume that
the Debian/Ubuntu patch that differed fixed the security problem,
but I can not be sure.  After following the discussions on
mailman-users where users were running non-SourceForge code, I decided
that I had to take the SourceForge code and build a Mailman package.
It took me a while to discover exactly what to do, but once I did it
(IIRC for 2.1.9), I have had no trouble building packages for 10
through 14.  I can send my steps to anyone who wants them.  My Mailman
machines are still Ubuntu/dapper, but I assume that my steps would work
unchanged on any later release of Debian/Ubuntu.
--
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory  Phone:+1 (630) 252-7277
9700 South Cass Avenue   Facsimile:+1 (630) 252-4601
Building 240, Room 5.B.8 Internet: bsfin...@anl.gov
Argonne, IL   60439-4828 IBMMAIL:  I1004994

--
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] mailman 2.1.14 new features

[Adam McGreggor]

On Fri, Oct 15, 2010 at 03:46:31PM +0200, Alessandro Bruchi wrote:
 Do you know when mailman 2.1.14 will be included as package in some debian 
 distribution?

The XSS patch, per 2010-September's announcement, seems to now be in
Debian's repositories:


http://lists.alioth.debian.org/pipermail/pkg-mailman-hackers/2010-October/003355.html


http://lists.alioth.debian.org/pipermail/pkg-mailman-hackers/2010-October/003360.html
(et. seq.)

and


http://lists.alioth.debian.org/pipermail/pkg-mailman-hackers/2010-October/003369.html

It appears that 'official' Mailman packages for lenny are a wee bit
behind upstream. 

I believe others on this list use the Umbungo packages on lenny
(Debian 5), without too many difficulties. YMMV.

(I don't really have the time to take on debian package maint, at the
moment.)

-- 
Life was simple before World War II. After that, we had systems.
-- Grace Hopper
--
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] mailman 2.1.14 new features

[Mark Sapiro]

Alessandro Bruchi alessandro.bru...@iit.it wrote:

Does mailman 2.1.14 solve the virtual domain problem? 
In particular the ability to create:

l...@domain1
l...@domain2


No.


I read that the new version support virtual domains.


That support is in MM 3. It is not yet ready for production use.



Do you know when mailman 2.1.14 will be included as package in some debian 
distribution?


No.


-- 
Mark Sapiro - m...@msapiro.net
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
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] {RW-Spam?} New install problems

[Mark Sapiro]

Dave Filchak wrote:

I can find no instances of a 
alias/forward to the old server and our aliases in 
/usr/local/mailman/data/aliases is correct. There is not such reference 
in /etc/aliases as well.


Do you have a reference in Postfix to
/usr/local/mailman/data/virtual-mailman?

Have you checked things in Postfix such as transport_maps?

What does the postfix log message say for mail to a list?

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] [Mailman-Announce] New Logo Contest for 2010

[Barry Warsaw]

On Jan 15, 2010, at 10:07 AM, Barry Warsaw wrote:

Our current GNU Mailman logos were designed by the Dragon De Monsyne many
years ago.  They have served us exceedingly well, but with the coming of
Mailman 3, we've decided it's time our logos got a face lift.  So we're
opening up a new logo contest to the Mailman and GNU communities.  We invite
your creative and inspiring designs!

Details of the contest and submission guidelines are available here:

http://wiki.list.org/display/DEV/NewLogo

Submissions will be open until February 28, 2010, and is open to everyone, so
feel free to forward this announcement.  Please contact the Mailman Steering
Committee at mailman-ca...@python.org with any questions.

Due to some confusion about posting permissions, we've decided to keep the
logo contest open for two more weeks.  We've got a number of really good ones,
but your chance at fame is not yet past.

We'll close the contest on Monday March 15 at 2200 UTC (don't forget DST in
the US starts on March 14).

Just to clarify: if you still want to submit a logo, you need to create an
account on wiki.list.org and send us (mailman-ca...@python.org) your wiki user
id so that we can enable your write access.  Sorry for the convolution but
that's the price of spam reduction.

Cheers,
-Barry



signature.asc
Description: PGP signature
--
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] Can't Create New Lists for RonaldKnox.org

[Mark Sapiro]

Anita McGing wrote:

Hi - when we click on the link to create a new list 
http://ronaldknox.org/mailman/create, we get an error that this page cannot be 
displayed - no sign-in page is shown.

http://ronaldknox.org/mailman/listinfo does work so this appears to be
an issue with Mailman's create CGI. I note that your Mailman version
is 2.1.11.cp3 (i.e. cPanel) so see the FAQ at
http://wiki.list.org/x/sYA9

If this is a hosted Mailman, you will have to pursue this with the
hosting service.

If this is your own server, you may be able to look at the
/usr/local/cpanel/3rdparty/mailman/cgi-bin/ directory and see if the
'create' wrapper has the same ownership and permissions as the others.
You may also be able to gett additional information from the web
server logs.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] Migration to new server, new domain name

[Zhengquan Zhang]

On Tue, Jun 09, 2009 at 11:33:11AM -0400, Duane Winner wrote:
 Hello,
 
 Can anybody point me to a document or explain to me what is necessary to
 complete these steps?

I am in the same position and hope somebody can point to a link to a
step by step tutorial or something like that.

-- 
Zhengquan

--
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] Migration to new server, new domain name

[Mark Sapiro]

Duane Winner wrote:

Can anybody point me to a document or explain to me what is necessary to
complete these steps?

We have a mailman server hosted on a FreeBSD box and need to migrate it an
Ubuntu box and change domain names on all the lists.

We have several dozen lists, all under the foo.org domain. We need to
change foo.org to bar.org

The current mail.foo.org server on FreeBSD is getting long in the tooth,
and we need to move anyway to Ubuntu. So I need to set up a new Ubuntu
server w/ Postfix, Mailman and Apache and call this server mail.bar.org
and this will be the MX server for bar.org.

For each *...@foo.org list, I need to move it to the new server, and it's
archives to mail.bar.org and that list will be called *...@bar.org


This is covered in the FAQ at http://wiki.list.org/x/gIA9.


But I also want to be able to protect users with forwarding.if they
still send mail to their old respective *...@foo.org list, how do I configure
to foward and process to the new *...@bar.org list?


You need to congigure the MX MTA for foo.org with aliases or whatever
to forward l...@foo.org mail to l...@bar.org for each list.

In mailman, you probably want to set l...@foo.org in Privacy options...
- Recipient filters - acceptable_aliases for each l...@bar.org list,
although this isn't strictly necessary because current code will
accept l...@foo.org as an explicit destination for l...@bar.org for
backwards compatibility reasons.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] Creating a new list fails

[LuKreme]

On 30-May-2009, at 15:42, Mark Sapiro wrote:

See the FAQ at http://wiki.list.org/x/fIA9 for why you should make
this change in mm_cfg.py, not Defaults.py.



OK, but the settings in Defaults.py were from 2007, when the machine  
was named 'akane' and it had an alias as 'mail'. Now the machine is  
named mail and 'akane' is just a DNS alias. I went ahead and added the  
lines to mm_cfg.py so they won't get blow away, but don't see any  
reason to restore the lines in Defaults.py as it will be overwritten  
when I finally get around to updating.



--
Love seekest only self to please, To bind another to its delight
Joys in another's loss of ease And builds a hell in Heaven's
despite!

--
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] Creating a new list fails

[Mark Sapiro]

LuKreme wrote:

On 30-May-2009, at 15:42, Mark Sapiro wrote:
 See the FAQ at http://wiki.list.org/x/fIA9 for why you should make
 this change in mm_cfg.py, not Defaults.py.


OK, but the settings in Defaults.py were from 2007, when the machine  
was named 'akane' and it had an alias as 'mail'. Now the machine is  
named mail and 'akane' is just a DNS alias. I went ahead and added the  
lines to mm_cfg.py so they won't get blow away, but don't see any  
reason to restore the lines in Defaults.py as it will be overwritten  
when I finally get around to updating.


That's fine. You now have the correct settings in mm_cfg.py so it
doesn't matter what's in Defaults.py for these. What will be in
Defaults.py after an upgrade depends on how you upgrade. If you
upgrade from our source, you set these things in Defaults.py with the
--with-urlhost= and --with-mailhost= options to configure.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] Creating a new list fails

[Mark Sapiro]

LuKreme wrote:

$ bin/newlist -l en --urlhost=mailman.covisp.net --emailhost=kreme.com 
hgt-sch...@kreme.com 
  kr...@kreme.com
Initial hgt-school password:
Create a new, unpopulated mailing list.

Usage: bin/newlist [options] [listname [listadmin-addr [admin- 
password]]]

[ bunch of stuff]

Illegal list name: hgt-sch...@akane


The short answer is DEFAULT_EMAIL_HOST must be a fully qualified doman
name.

The underlying issue is the MailList.Create() method as called by
bin/newlist validates the list name by checking that
listn...@default_email_host is a valid email address. This check in
turn requires at least one dot '.' in the domain part.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] Creating a new list fails

[LuKreme]

On 30-May-2009, at 12:53, Mark Sapiro wrote:

LuKreme wrote:


$ bin/newlist -l en --urlhost=mailman.covisp.net -- 
emailhost=kreme.com hgt-sch...@kreme.com

kr...@kreme.com
Initial hgt-school password:
Create a new, unpopulated mailing list.

Usage: bin/newlist [options] [listname [listadmin-addr [admin-
password]]]

[ bunch of stuff]

Illegal list name: hgt-sch...@akane


The short answer is DEFAULT_EMAIL_HOST must be a fully qualified doman
name.


kreme.com _IS_ a fqdn.  Or are we talking about a setting somwhere  
else?  I do have several lists up and running, but they were all  
created years ago and have been pretty much left alone. If I trey to  
create a list via the web interface I get a different error:


Error: Unknown virtual host: mailman.covisp.net


The underlying issue is the MailList.Create() method as called by
bin/newlist validates the list name by checking that
listn...@default_email_host is a valid email address.


So I need to create the listname aliases before the list is created?


This check in
turn requires at least one dot '.' in the domain part.


I which domain part?  My mm_cfg.py is very simple:

###
# Here's where we get the distributed defaults.

from Defaults import *

##
# Put YOUR site-specific settings below this line.

VERP_CONFIRMATIONS = Yes
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = 1
ADMIN_MEMBER_CHUNKSIZE = 100
OWNERS_CAN_ENABLE_PERSONALIZATION = Yes
ADMINDB_PAGE_TEXT_LIMIT = 4096
OWNERS_CAN_DELETE_THEIR_OWN_LISTS = Yes
HOLD_MESSAGES_AS_PICKLES = No

--
The person on the other side was a young woman. Very obviously a
young woman. There was no possible way that she could have been
mistaken for a young man in any language, especially Braille.

--
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] Creating a new list fails

[Mark Sapiro]

LuKreme krem...@kreme.com
   Date: Sat, 30 May 2009 14:55:44 -0600
 To: mailman-users@python.org

On 30-May-2009, at 12:53, Mark Sapiro wrote:
 LuKreme wrote:

 $ bin/newlist -l en --urlhost=mailman.covisp.net -- 
 emailhost=kreme.com hgt-sch...@kreme.com
 kr...@kreme.com
 Initial hgt-school password:
 Create a new, unpopulated mailing list.

 Usage: bin/newlist [options] [listname [listadmin-addr [admin-
 password]]]

 [ bunch of stuff]

 Illegal list name: hgt-sch...@akane

 The short answer is DEFAULT_EMAIL_HOST must be a fully qualified doman
 name.

kreme.com _IS_ a fqdn.  Or are we talking about a setting somwhere  
else?  


Yes, and this is really a bug in newlist in that you supplied an email
host, but it didn't put it in the initial Create() method call, so
create uses DEFAULT_EMAIL_HOST (from Defaults.py or mm_cfg.py) as the
domain to validate the list posting address. This setting is

DEFAULT_EMAIL_HOST = 'akane'.


I do have several lists up and running, but they were all  
created years ago and have been pretty much left alone. If I trey to  
create a list via the web interface I get a different error:

Error: Unknown virtual host: mailman.covisp.net


This is because you went to the create page via a URL with hostname
mailman.covisp.net, and that name is not in your VIRTUAL_HOSTS
dictionary. See below.


 The underlying issue is the MailList.Create() method as called by
 bin/newlist validates the list name by checking that
 listn...@default_email_host is a valid email address.

So I need to create the listname aliases before the list is created?


No. the check is for 'syntactically valid', not 'deliverable'


 This check in
 turn requires at least one dot '.' in the domain part.

I which domain part?  My mm_cfg.py is very simple:

###
# Here's where we get the distributed defaults.

from Defaults import *

##
# Put YOUR site-specific settings below this line.

VERP_CONFIRMATIONS = Yes
VERP_PASSWORD_REMINDERS = Yes
VERP_PERSONALIZED_DELIVERIES = Yes
VERP_DELIVERY_INTERVAL = 1
ADMIN_MEMBER_CHUNKSIZE = 100
OWNERS_CAN_ENABLE_PERSONALIZATION = Yes
ADMINDB_PAGE_TEXT_LIMIT = 4096
OWNERS_CAN_DELETE_THEIR_OWN_LISTS = Yes
HOLD_MESSAGES_AS_PICKLES = No


You also want (guessing based on above)

DEFAULT_URL_HOST = 'mailman.covisp.net'
DEFAULT_EMAIL_HOST = 'kreme.com'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

because the Defaults.py entries for these are not correct, and possibly
more add_virtualhost('www.example.com', 'example.com') entries if you
have other domains.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] Creating a new list fails

[LuKreme]

On 30-May-2009, at 14:55, LuKreme wrote:

I which domain part?  My mm_cfg.py is very simple:



OK, I fixed this by editing Defaults.py

--
The most perfidious way of harming a cause consists of defending
it deliberately with faulty arguments.

--
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] Creating a new list fails

[LuKreme]

On 30-May-2009, at 14:55, LuKreme wrote:

I which domain part?  My mm_cfg.py is very simple:



I managed to fix this by editing Defaults.py

DEFAULT_EMAIL_HOST = 'mail.covisp.net'
DEFAULT_URL_HOST = 'mailman.covisp.net'

Everything seems to work as it did before. Yay!

(both values were set to 'akane' before, which is an alias for the  
machine)


--
MEGAHAL: within my penguin lies a torrid story of hate and love.

--
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] Creating a new list fails

[Mark Sapiro]

LuKreme wrote:

I managed to fix this by editing Defaults.py

DEFAULT_EMAIL_HOST = 'mail.covisp.net'
DEFAULT_URL_HOST = 'mailman.covisp.net'


See the FAQ at http://wiki.list.org/x/fIA9 for why you should make
this change in mm_cfg.py, not Defaults.py.

It's a bit more complicated in this case than just adding the above two
lines to mm_cfg.py (although that would suffice for the newlist issue)
because those settings are used in an additional definition in
Defaults.py so you also need

VIRTUAL_HOSTS.clear()

to undo what was done in Defaults.py, and

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

to redo it with the correct values.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] migrating to new server

[Brendon Lloyd]

Here's a good one:

http://www.debian-administration.org/articles/567

However, I found that in addition to the steps described above, the 
make install script updates old data, archives, and lists directories, 
so it's best to install from source if you plan to migrate/upgrade.


Also you will need to run the /usr/local/mailman/bin/check_perms script 
to straighten out your permissions.


Pieter Donche wrote:

An old server is to be replaced with a new one. The old server
(solaris mailman-2.1.7) runs a couple of mailing lists. We will keep 
the same web address and the same e-mail address on the new server 
(FreeBSD7 mailman-2.1.11).


In the old server the mailman software ran under a normal user with 
everything in the home-dir of that user. In the new server it needs to 
be in /usr/local/mailman (where FreeBSD installs it)


What steps need to be executed to migrate all the mailings lists 
(archives

memberslists etc...) from the old to the new server?
I have unix root access to both machines.

Is there a step by step document ?

The B.Warsaw GNU Mailman - Installation Manual lacks a section on
migration ...
--
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/brendonl%40isi.edu


Security Policy: http://wiki.list.org/x/QIA9


--
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] migrating to new server

[Mark Sapiro]

- Original Message ---

Subject: [Mailman-Users] migrating to new server
   From: Pieter Donche pieter.don...@ua.ac.be
   Date: Tue, 7 Apr 2009 15:55:51 +0200 (CEST)
 To: mailman-users@python.org

An old server is to be replaced with a new one. The old server
(solaris mailman-2.1.7) runs a couple of mailing lists. 
We will keep the same web address and the same e-mail address on 
the new server (FreeBSD7 mailman-2.1.11).

In the old server the mailman software ran under a normal user 
with everything in the home-dir of that user. 
In the new server it needs to be in /usr/local/mailman 
(where FreeBSD installs it)

What steps need to be executed to migrate all the mailings lists (archives
memberslists etc...) from the old to the new server?
I have unix root access to both machines.

Is there a step by step document ?


There's information in the FAQ. In your case, all you really need to do
is move the contents of Mailman's lists/* and archives/private/*
directories from the old installation to the new. You may not want to
move the 'mailman' list.

See the posts linked at the very beginning of the FAQ at
http://wiki.list.org/x/2oA9.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] create a new list web interface

[jewel . brueggeman-makda]

When I add: MTA='Postfix' to my mm_cfg.py file mail stops getting
delivered.  I don't see anything suspicous in my logs to help.  I
checked to confirm that the OutgoingRunner hasn't died.  Postfix appears
to still be livering based on it's logs saying 'sent'.  Anyone else had
this issue?


Jewel
- Original Message -
From: Mark Sapiro [EMAIL PROTECTED]
Date: Thursday, November 13, 2008 2:22 pm
Subject: Re: [Mailman-Users] create a new list web interface
To: Jewel [EMAIL PROTECTED], Mail List - Mailman
mailman-users@python.org

 Jewel wrote:
 
 When I create a new list from the web interface I get an email 
 confirmation just fine.  My question is I know that this didn't 
 update 
 the aliases file and didn't know if there was any configuring I 
 could do 
 so that the aliases file is updated and creating a list is 
 automatic.  I 
 did look in the archives and online but I could find anything, 
 maybe I 
 am not searching correctly.
 
 
 If your outgoing MTA is Postfix, see
 http://www.list.org/mailman-install/node13.html. If Sendmail, see
 step 6. in the FAQ at http://wiki.list.org/x/B4Au and/or the last
 paragraph of the FAQ at http://wiki.list.org/x/joA9 and the list
 post to which it links.
 
 If you are using aliases with come other MTA, you can probably adapt
 the Sendmail methods.
 
 -- 
 Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
 San Francisco Bay Area, Californiabetter use your sense - B. Dylan
 
 
--
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] create a new list web interface

[Mark Sapiro]

[EMAIL PROTECTED] wrote:

When I add: MTA='Postfix' to my mm_cfg.py file mail stops getting
delivered.  I don't see anything suspicous in my logs to help.  I
checked to confirm that the OutgoingRunner hasn't died.  Postfix appears
to still be livering based on it's logs saying 'sent'.  Anyone else had
this issue?


What does the postfix log actually say? Does it say status=sent
(delivered to command: /usr/local/mailman/mail/mailman post LISTNAME)
or does it say status=sent (delivered to mailbox) or something else?

After adding MTA = 'Postfix' to mm_cfg.py, you have to run Mailman's
bin/genaliases to build the data/aliases and data/aliases.db files.

You also need to add hash:/usr/local/mailman/data/aliases to the
alias_maps list in Postfix's main.cf.

Then you need to remove any mailman aliases from /etc/aliases or
whereever they were before if not /usr/local/mailman/data/aliases, and
run 'postalias /etc/aliases' (or wherever to update the corresponding
.db file.

The above assumes that Mailman's email domain is not a Postfix virtual
domain. If it is, there's more that needs to be done.

Then depending on how you configured mailman, you might run into group
mismatch errors on mail delivery. See the FAQ at
http://wiki.list.org/x/tYA9.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] create a new list web interface

[jewel . brueggeman-makda]

My maillog shows:

Nov 14 16:43:27 lists postfix/smtp[18085]: 60CE58C0013:
to=[EMAIL PROTECTED],
relay=relay.washburnlaw.edu[198.252.9.211]:25, delay=0.18,
delays=0.1/0.02/0.05/0.02, dsn=2.0.0, status=sent (250 Message accepted
for delivery)
Nov 14 16:43:27 lists postfix/qmgr[1858]: 60CE58C0013: removed

When I run genaliases I recieve the following error:

postalias: fatal: open /usr/local/mailman/data/aliases.db: Permission denied
Traceback (most recent call last):
  File ./genaliases, line 116, in ?
main()
  File ./genaliases, line 106, in main
MTA.create(mlist, nolock=True, quiet=quiet)
  File /usr/local/mailman/Mailman/MTA/Postfix.py, line 232, in create
_update_maps()
  File /usr/local/mailman/Mailman/MTA/Postfix.py, line 53, in _update_maps
raise RuntimeError, msg % (acmd, status, errstr)
RuntimeError: command failed: /usr/sbin/postalias
/usr/local/mailman/data/aliases (status: 1, Operation not permitted)

When I disable my SELinux security I am able to run the genaliases
command successfully but only as root. I only create a few lists a year
so getting this feature is not a high priority but would be nice.  I
also must admit I don't know what you mean by Postfix virtual domain

Thanks,


- Original Message -
From: Mark Sapiro [EMAIL PROTECTED]
Date: Friday, November 14, 2008 4:34 pm
Subject: Re: [Mailman-Users] create a new list web interface
To: [EMAIL PROTECTED]
Cc: Mail List - Mailman mailman-users@python.org

 [EMAIL PROTECTED] wrote:
 
 When I add: MTA='Postfix' to my mm_cfg.py file mail stops getting
 delivered.  I don't see anything suspicous in my logs to help.  I
 checked to confirm that the OutgoingRunner hasn't died.  Postfix 
 appearsto still be livering based on it's logs saying 'sent'.  
 Anyone else had
 this issue?
 
 
 What does the postfix log actually say? Does it say status=sent
 (delivered to command: /usr/local/mailman/mail/mailman post LISTNAME)
 or does it say status=sent (delivered to mailbox) or something else?
 
 After adding MTA = 'Postfix' to mm_cfg.py, you have to run Mailman's
 bin/genaliases to build the data/aliases and data/aliases.db files.
 
 You also need to add hash:/usr/local/mailman/data/aliases to the
 alias_maps list in Postfix's main.cf.
 
 Then you need to remove any mailman aliases from /etc/aliases or
 whereever they were before if not /usr/local/mailman/data/aliases, and
 run 'postalias /etc/aliases' (or wherever to update the corresponding
 .db file.
 
 The above assumes that Mailman's email domain is not a Postfix virtual
 domain. If it is, there's more that needs to be done.
 
 Then depending on how you configured mailman, you might run into group
 mismatch errors on mail delivery. See the FAQ at
 http://wiki.list.org/x/tYA9.
 
 -- 
 Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
 San Francisco Bay Area, Californiabetter use your sense - B. Dylan
 
 
--
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] create a new list web interface

[jewel . brueggeman-makda]

Ok, I stand corrected.  Mail is working fine!  

My problem is issuing the genaliases command.  If it only works for root
when SELinux is off it should work for the user mailman.  I have also
added  the hash:/usr/local/mailman/data/aliases to my alias_maps in
/etc/postfix/main.cf

Jewel 

- Original Message -
From: [EMAIL PROTECTED]
Date: Friday, November 14, 2008 4:48 pm
Subject: Re: [Mailman-Users] create a new list web interface
To: Mark Sapiro [EMAIL PROTECTED]
Cc: Mail List - Mailman mailman-users@python.org

 My maillog shows:
 
 Nov 14 16:43:27 lists postfix/smtp[18085]: 60CE58C0013:
 to=[EMAIL PROTECTED],
 relay=relay.washburnlaw.edu[198.252.9.211]:25, delay=0.18,
 delays=0.1/0.02/0.05/0.02, dsn=2.0.0, status=sent (250 Message 
 acceptedfor delivery)
 Nov 14 16:43:27 lists postfix/qmgr[1858]: 60CE58C0013: removed
 
 When I run genaliases I recieve the following error:
 
 postalias: fatal: open /usr/local/mailman/data/aliases.db: 
 Permission denied
 Traceback (most recent call last):
  File ./genaliases, line 116, in ?
main()
  File ./genaliases, line 106, in main
MTA.create(mlist, nolock=True, quiet=quiet)
  File /usr/local/mailman/Mailman/MTA/Postfix.py, line 232, in 
 create_update_maps()
  File /usr/local/mailman/Mailman/MTA/Postfix.py, line 53, in 
 _update_mapsraise RuntimeError, msg % (acmd, status, errstr)
 RuntimeError: command failed: /usr/sbin/postalias
 /usr/local/mailman/data/aliases (status: 1, Operation not permitted)
 
 When I disable my SELinux security I am able to run the genaliases
 command successfully but only as root. I only create a few lists a 
 yearso getting this feature is not a high priority but would be 
 nice.  I
 also must admit I don't know what you mean by Postfix virtual domain
 
 Thanks,
 
 
 - Original Message -
 From: Mark Sapiro [EMAIL PROTECTED]
 Date: Friday, November 14, 2008 4:34 pm
 Subject: Re: [Mailman-Users] create a new list web interface
 To: [EMAIL PROTECTED]
 Cc: Mail List - Mailman mailman-users@python.org
 
  [EMAIL PROTECTED] wrote:
  
  When I add: MTA='Postfix' to my mm_cfg.py file mail stops getting
  delivered.  I don't see anything suspicous in my logs to help.  I
  checked to confirm that the OutgoingRunner hasn't died.  Postfix 
  appearsto still be livering based on it's logs saying 'sent'.  
  Anyone else had
  this issue?
  
  
  What does the postfix log actually say? Does it say status=sent
  (delivered to command: /usr/local/mailman/mail/mailman post 
 LISTNAME) or does it say status=sent (delivered to mailbox) or 
 something else?
  
  After adding MTA = 'Postfix' to mm_cfg.py, you have to run Mailman's
  bin/genaliases to build the data/aliases and data/aliases.db files.
  
  You also need to add hash:/usr/local/mailman/data/aliases to the
  alias_maps list in Postfix's main.cf.
  
  Then you need to remove any mailman aliases from /etc/aliases or
  whereever they were before if not 
 /usr/local/mailman/data/aliases, and
  run 'postalias /etc/aliases' (or wherever to update the 
 corresponding .db file.
  
  The above assumes that Mailman's email domain is not a Postfix 
 virtual domain. If it is, there's more that needs to be done.
  
  Then depending on how you configured mailman, you might run into 
 group mismatch errors on mail delivery. See the FAQ at
  http://wiki.list.org/x/tYA9.
  
  -- 
  Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
  San Francisco Bay Area, Californiabetter use your sense - B. 
 Dylan 
  
 --
 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/jewel.brueggeman-makda%40washburn.edu
 
 Security Policy: http://wiki.list.org/x/QIA9
 
--
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] create a new list web interface

[Mark Sapiro]

[EMAIL PROTECTED] wrote:

My maillog shows:

Nov 14 16:43:27 lists postfix/smtp[18085]: 60CE58C0013:
to=[EMAIL PROTECTED],
relay=relay.washburnlaw.edu[198.252.9.211]:25, delay=0.18,
delays=0.1/0.02/0.05/0.02, dsn=2.0.0, status=sent (250 Message accepted
for delivery)
Nov 14 16:43:27 lists postfix/qmgr[1858]: 60CE58C0013: removed


That is some message to you. What does the log show for a message to a
list?

When I run genaliases I recieve the following error:

postalias: fatal: open /usr/local/mailman/data/aliases.db: Permission denied
Traceback (most recent call last):
  File ./genaliases, line 116, in ?
main()
  File ./genaliases, line 106, in main
MTA.create(mlist, nolock=True, quiet=quiet)
  File /usr/local/mailman/Mailman/MTA/Postfix.py, line 232, in create
_update_maps()
  File /usr/local/mailman/Mailman/MTA/Postfix.py, line 53, in _update_maps
raise RuntimeError, msg % (acmd, status, errstr)
RuntimeError: command failed: /usr/sbin/postalias
/usr/local/mailman/data/aliases (status: 1, Operation not permitted)

When I disable my SELinux security I am able to run the genaliases
command successfully but only as root. I only create a few lists a year
so getting this feature is not a high priority but would be nice.  I
also must admit I don't know what you mean by Postfix virtual domain


Then you probably don't need to worry about Postfix virtual domain.

The permissions on Mailman's aliases should look like

-rw-rw 1 markmailman  7193 Sep  7 07:54 aliases
-rw-rw 1 mailman mailman 12288 Sep  7 07:54 aliases.db

The owner of 'aliases' (mark in this case, maybe root in yours) doesn't
matter, but both files need to be group mailman and aliases.db needs
to be owned by whatever user has a primary group equal to what the
mail wrapper expects.

I don't know SELinux so I can't help with how you might augment the
security policy to allow this to work.

(since I already wrote the above, here it is)

Jewel wrote:

Ok, I stand corrected.  Mail is working fine!  

My problem is issuing the genaliases command.  If it only works for root
when SELinux is off it should work for the user mailman.  I have also
added  the hash:/usr/local/mailman/data/aliases to my alias_maps in
/etc/postfix/main.cf

If you want web create to work, the apache user running with effective
GID of Mailman's group has to be able to write these files.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] create a new list web interface

[jewel . brueggeman-makda]

By diabling SELinux altogether it worked.  My only question is regarding
what you said earlier, the working was a bit confusing for me:

  Then you need to remove any mailman aliases from /etc/aliases or
  whereever they were before if not
 /usr/local/mailman/data/aliases, and
  run 'postalias /etc/aliases' (or wherever to update the
 corresponding .db file.

I have alias_maps pointing to both /etc/aliases ad
/usr/local/mailman/data/aliases.  Currently both alias files contain all
of my lists.
So do I need to remove the mailman instance from the /etc/aliases file
or all lists?  If I create a new list using the web interface it will
should update both aliases or just the data/aliases? I apologize I am
not understanding.

Jewel 


- Original Message -
From: Mark Sapiro [EMAIL PROTECTED]
Date: Friday, November 14, 2008 5:04 pm
Subject: Re: [Mailman-Users] create a new list web interface
To: [EMAIL PROTECTED]
Cc: Mail List - Mailman mailman-users@python.org

 [EMAIL PROTECTED] wrote:
 
 My maillog shows:
 
 Nov 14 16:43:27 lists postfix/smtp[18085]: 60CE58C0013:
 to=[EMAIL PROTECTED],
 relay=relay.washburnlaw.edu[198.252.9.211]:25, delay=0.18,
 delays=0.1/0.02/0.05/0.02, dsn=2.0.0, status=sent (250 Message 
 acceptedfor delivery)
 Nov 14 16:43:27 lists postfix/qmgr[1858]: 60CE58C0013: removed
 
 
 That is some message to you. What does the log show for a message 
 to a
 list?
 
 When I run genaliases I recieve the following error:
 
 postalias: fatal: open /usr/local/mailman/data/aliases.db: 
 Permission denied
 Traceback (most recent call last):
   File ./genaliases, line 116, in ?
 main()
   File ./genaliases, line 106, in main
 MTA.create(mlist, nolock=True, quiet=quiet)
   File /usr/local/mailman/Mailman/MTA/Postfix.py, line 232, in 
 create_update_maps()
   File /usr/local/mailman/Mailman/MTA/Postfix.py, line 53, in 
 _update_mapsraise RuntimeError, msg % (acmd, status, errstr)
 RuntimeError: command failed: /usr/sbin/postalias
 /usr/local/mailman/data/aliases (status: 1, Operation not permitted)
 
 When I disable my SELinux security I am able to run the genaliases
 command successfully but only as root. I only create a few lists a 
 yearso getting this feature is not a high priority but would be 
 nice.  I
 also must admit I don't know what you mean by Postfix virtual 
 domain
 
 Then you probably don't need to worry about Postfix virtual domain.
 
 The permissions on Mailman's aliases should look like
 
 -rw-rw 1 markmailman  7193 Sep  7 07:54 aliases
 -rw-rw 1 mailman mailman 12288 Sep  7 07:54 aliases.db
 
 The owner of 'aliases' (mark in this case, maybe root in yours) 
 doesn'tmatter, but both files need to be group mailman and 
 aliases.db needs
 to be owned by whatever user has a primary group equal to what the
 mail wrapper expects.
 
 I don't know SELinux so I can't help with how you might augment the
 security policy to allow this to work.
 
 (since I already wrote the above, here it is)
 
 Jewel wrote:
 
 Ok, I stand corrected.  Mail is working fine!  
 
 My problem is issuing the genaliases command.  If it only works 
 for root
 when SELinux is off it should work for the user mailman.  I have also
 added  the hash:/usr/local/mailman/data/aliases to my alias_maps in
 /etc/postfix/main.cf
 
 If you want web create to work, the apache user running with effective
 GID of Mailman's group has to be able to write these files.
 
 -- 
 Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
 San Francisco Bay Area, Californiabetter use your sense - B. Dylan
 
 
--
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] create a new list web interface

[Jewel]

Everything is working now! I am able to create a list via the 
interface.  I read a thread where someone disabled SELinux, then 
re-enabled it, and then rebooted and it worked for them. Sure enough it 
worked for me too.  Not sure why.  I am still wanting to know about the 
aliases though.


Thanks!

[EMAIL PROTECTED] wrote:

By diabling SELinux altogether it worked.  My only question is regarding
what you said earlier, the working was a bit confusing for me:

  

Then you need to remove any mailman aliases from /etc/aliases or
whereever they were before if not
  

/usr/local/mailman/data/aliases, and


run 'postalias /etc/aliases' (or wherever to update the
  

corresponding .db file.



I have alias_maps pointing to both /etc/aliases ad
/usr/local/mailman/data/aliases.  Currently both alias files contain all
of my lists.
So do I need to remove the mailman instance from the /etc/aliases file
or all lists?  If I create a new list using the web interface it will
should update both aliases or just the data/aliases? I apologize I am
not understanding.

Jewel 



- Original Message -
From: Mark Sapiro [EMAIL PROTECTED]
Date: Friday, November 14, 2008 5:04 pm
Subject: Re: [Mailman-Users] create a new list web interface
To: [EMAIL PROTECTED]
Cc: Mail List - Mailman mailman-users@python.org

  

[EMAIL PROTECTED] wrote:



My maillog shows:

Nov 14 16:43:27 lists postfix/smtp[18085]: 60CE58C0013:
to=[EMAIL PROTECTED],
relay=relay.washburnlaw.edu[198.252.9.211]:25, delay=0.18,
delays=0.1/0.02/0.05/0.02, dsn=2.0.0, status=sent (250 Message 
  

acceptedfor delivery)


Nov 14 16:43:27 lists postfix/qmgr[1858]: 60CE58C0013: removed
  
That is some message to you. What does the log show for a message 
to a

list?



When I run genaliases I recieve the following error:

postalias: fatal: open /usr/local/mailman/data/aliases.db: 
  

Permission denied


Traceback (most recent call last):
 File ./genaliases, line 116, in ?
   main()
 File ./genaliases, line 106, in main
   MTA.create(mlist, nolock=True, quiet=quiet)
 File /usr/local/mailman/Mailman/MTA/Postfix.py, line 232, in 
  

create_update_maps()

 File /usr/local/mailman/Mailman/MTA/Postfix.py, line 53, in 
  

_update_mapsraise RuntimeError, msg % (acmd, status, errstr)


RuntimeError: command failed: /usr/sbin/postalias
/usr/local/mailman/data/aliases (status: 1, Operation not permitted)

When I disable my SELinux security I am able to run the genaliases
command successfully but only as root. I only create a few lists a 
  
yearso getting this feature is not a high priority but would be 
nice.  I

also must admit I don't know what you mean by Postfix virtual 
  

domain

Then you probably don't need to worry about Postfix virtual domain.

The permissions on Mailman's aliases should look like

-rw-rw 1 markmailman  7193 Sep  7 07:54 aliases
-rw-rw 1 mailman mailman 12288 Sep  7 07:54 aliases.db

The owner of 'aliases' (mark in this case, maybe root in yours) 
doesn'tmatter, but both files need to be group mailman and 
aliases.db needs

to be owned by whatever user has a primary group equal to what the
mail wrapper expects.

I don't know SELinux so I can't help with how you might augment the
security policy to allow this to work.

(since I already wrote the above, here it is)

Jewel wrote:


Ok, I stand corrected.  Mail is working fine!  

My problem is issuing the genaliases command.  If it only works 
  

for root


when SELinux is off it should work for the user mailman.  I have also
added  the hash:/usr/local/mailman/data/aliases to my alias_maps in
/etc/postfix/main.cf
  

If you want web create to work, the apache user running with effective
GID of Mailman's group has to be able to write these files.

--
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan




--
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/jewel.brueggeman-makda%40washburn.edu

Security Policy: http://wiki.list.org/x/QIA9
  


--
Jewel Makda
Student Computer Services Coordinator

--
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] create a new list web interface

[Mark Sapiro]

[EMAIL PROTECTED] wrote:

By diabling SELinux altogether it worked.  My only question is regarding
what you said earlier, the working was a bit confusing for me:

  Then you need to remove any mailman aliases from /etc/aliases or
  whereever they were before if not
 /usr/local/mailman/data/aliases, and
  run 'postalias /etc/aliases' (or wherever to update the
 corresponding .db file.

I have alias_maps pointing to both /etc/aliases ad
/usr/local/mailman/data/aliases.


This part is correct.
-

Currently both alias files contain all
of my lists.


This is not correct, but it get's complicated. The only list aliases
which are actually being used by Postfix are the ones in the file
which is mentioned first in the main.cf alias_maps directive.

Normally, you would remove all of Mailman's aliases for the mailman
list and all the other lists from /etc/aliases, but if the owner of
/etc/aliases.db is not the same (mailman?) as the owner of
/usr/local/mailman/data/aliases.db, this will break mail delivery to
Mailman, at least until you reconfigure Mailman with
--with-mail-gid=mailman and reinstall.


So do I need to remove the mailman instance from the /etc/aliases file
or all lists?  If I create a new list using the web interface it will
should update both aliases or just the data/aliases? I apologize I am
not understanding.


For Postfix/Mailman integration to work as intended, Mailman's aliases
(for all lists) should only be in data/aliases*. Then list creation
and deletion maintains these aliases. But, as I note above, this has
an effect on mail delivery to Mailman, because when Postfix finds an
alias which is a pipe to a command, Postfix runs that command (the
mailman/mail/mailman wrapper) as the user who owns the aliases.db file
in which it found that aliases and as the group which is that user's
primary group.

Now, if the aliases are coming from /etc/aliases.db which I suspect is
owned by root, Postfix is invoking the wrapper as root:root, and if
this is working and not giving a group mismatch error, the wrapper was
compiled with --with-mail-gid=root. If you then remove the aliases
from /etc/aliases, postfix will get them from data/aliases.db and will
run the pipe as the owner of that file and that owner's group (not the
group of the file).

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] create a new list web interface

[Todd Zullinger]

[EMAIL PROTECTED] wrote:
 By diabling SELinux altogether it worked.

If you don't want to keep SELinux disabled, it should be possible to
make mailman work without too much trouble.  I do know that the Red
Hat packages install mailman in locations that are more FHS compliant
to help ease the writing of the SELinux policy.  If you're installing
mailman from source, it might be a little messier.

FWIW, I installed mailman from the packages provided as part of CentOS
5 and did a little light testing.  I had to create a small SELinux
policy module to allow mailman to be able to play nicely with postfix
and have the web interface be able to create lists.  The audit2allow
tool made this fairly trivial (easier than the manual steps I'll
list below to recreate the SELinux module, in fact :).

So, the policy that was generated via audit2allow is:

module mailmanpostfix 1.0;

require {
type mailman_mail_t;
type mailman_archive_t;
type postfix_etc_t;
type mailman_cgi_t;
class file { read getattr };
class dir search;
}

#= mailman_cgi_t ==
allow mailman_cgi_t postfix_etc_t:dir search;
allow mailman_cgi_t postfix_etc_t:file { read getattr };

#= mailman_mail_t ==
allow mailman_mail_t mailman_archive_t:dir search;

If you put that in to a file, say mailmanpostfix.te, you can compile
it into a module and load it with just a few commands (all taken from
the audit2allow manpage):

# Compile the module
$ checkmodule -M -m -o mailmanpostfix.mod mailmanpostfix.te
# Create the package
$ semodule_package -o mailmanpostfix.pp -m mailmanpostfix.mod
# Load the module into the kernel
$ semodule -i mailmanpostfix.pp

Now, I don't claim to be enough of an SELinux guru to know whether
some of the generated policy could be tightened up, but I don't think
any of it looks egregiously incorrect.  It's also quite likely to be
more secure than disabling SELinux entirely. ;)

On another note, you also said that you needed to be root to make
genaliases work.  Is that perhaps because the permissions and
ownership on the aliases* files are not correct? The mailman install
manual details the proper permission and ownership commands you should
run:

http://www.gnu.org/software/mailman/mailman-install/node13.html

-- 
ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~
The best leaders inspire by example. When that's not an option, brute
intimidation works pretty well, too.
-- Demotivators (www.despair.com)



pgpPO0ZfwoJYd.pgp
Description: PGP signature
--
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] create a new list web interface

[Mark Sapiro]

Jewel wrote:

When I create a new list from the web interface I get an email 
confirmation just fine.  My question is I know that this didn't update 
the aliases file and didn't know if there was any configuring I could do 
so that the aliases file is updated and creating a list is automatic.  I 
did look in the archives and online but I could find anything, maybe I 
am not searching correctly.


If your outgoing MTA is Postfix, see
http://www.list.org/mailman-install/node13.html. If Sendmail, see
step 6. in the FAQ at http://wiki.list.org/x/B4Au and/or the last
paragraph of the FAQ at http://wiki.list.org/x/joA9 and the list
post to which it links.

If you are using aliases with come other MTA, you can probably adapt
the Sendmail methods.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] Can't create new mail list

[Mark Sapiro]

HSU NORML wrote:

Running latest version of mailman with the mailman/joomla bridge on a joomla
server.
at /mailman/admin/ i click on the link to create a new mail list and i
receive a page:
Internal Server Error

The server encountered an internal error or misconfiguration and was unable
to complete your request.

Please contact the server administrator, [EMAIL PROTECTED] and inform
them of the time the error occurred, and anything you might have done that
may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 404 Not Found error was encountered while trying to use an
ErrorDocument to handle the request.
How do I get beyond this?


This error comes from your web server (apache ?). Look in the web
server's error log (/var/log/httpd/error_log ?) for more detail about
the specific problem.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] Upgrading to new mailman version

[Mark Sapiro]

wolf97 wrote:

I
would like to upgrade to a completely new box.  Linux
Redhat Enterprise and the latest version of mailman
and postfix.  Is there a way to export/import all my
existing list from the original server to the new one?


See
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.004.htp

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] Problem with new subscribers

[Mark Sapiro]

Carlos Corredor wrote:
 
I have two lists. In one of them, I can add new members by mass subscription
only - adding a member using the general list information page does not
work: nothing happens - no response email of any kind, and of course, the
user does not get subscribed. In the other list, everything works as it's
supposed to.


Did you edit the listinfo page template for the non-working list?

If so, you probably lost or misplaced the MM-Subscribe-Form-Start tag.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] Trouble adding new users

[Mark Sapiro]

Pete Bronder wrote:

I am having problems adding new members.  It is something that I've done 
successfully many times in the past.  The new addresses show up on the 
list through the administrative interface however the new people that 
are added do not receive any messages.  I compared the profiles of 
members who are working correctly against those members who are not 
receiving messages and could not find any problems.  I also checked the 
FAQs and did not see where this problem might have been addressed.


Look at the new members in the admin Membership List. Are the 'nomail'
and 'digest' columns both unchecked?

If 'nomail' is checked, it was set either by [A]dmin, [B]ounce, or the
[U]ser. You can uncheck it and Submit Your Changes. Normally, it would
not be initially checked for a new user, but might by set by bounce
after some time if the user is bouncing.

Even if nomail is unchecked, you can click the user's address to go to
the user's options page where there will be a not near the top if the
user has a non zero bounce score.

Also, you should make sure that bounce_processing and all the
notifications on the Bounce processing admin page are set to Yes.

If digest is checked, the member is receiving digest's and perhaps none
have been sent. If this is the case, and you don't want members to be
digested by default, make sure that digest_is_default on Digest
options is set to Regular. If you want all members to be non-digest,
set digestable to No.

If it's OK for a member to receive digests, but they aren't being sent,
make sure that digest_size_threshhold is not too large and/or
digest_send_periodic is set to Yes.


Do you have any explanation or pointers for what else to try?  Could 
this be a problem with the server?  If so, what can I ask the service 
who runs the server to look at?


If the above suggestions don't lead to a solution, The problem is in
mail delivery outside of Mailman. The server admin's will need to look
at Mailman's 'post', 'smtp', 'smtp-failure' and 'bounce' logs and the
logs of the outgoing MTA to get more information, but even that may
not reveal anything if the recipient's ISP(s) are just discarding the
messages. BTW, have the new members checked their 'bulk' or 'spam'
folders for the messages?

-- 
Mark Sapiro [EMAIL PROTECTED]   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] problems with new web host and too many complaints

[Jonathan Dill]

Brad Knowles wrote:
 Well, you haven't really given us any real details as to the nature of 
 the problem or the nature of the complaints.  So, I'm not sure that 
 anyone can give you any advice that will be useful.

 I can say that I'd expect to see more support from your new ISP, and 
 if they're willing to treat you this way this soon after you switched, 
 I have to wonder how they're going to treat you in the future.
First, I want to say thanks to Kyle Banerjee who responded off list with 
a lot of great advice.  To summarize the problem again, the complaints 
are really in response to the newsletter.  The web host in question has 
had some bad press lately, mainly with respect to being a major source 
of blog comment spam, so possibly they are overreacting to compensate.

In a nutshell, it is way too easy for people to sign up for the list, 
which is what I have been telling them all along, but unfortunately, 
they had to learn this the hard way.  They should include their phone 
number in the newsletter to give people another way to respond, since 
some people are paranoid about clicking on links in messages.  For 
CAN-SPAM compliance, they should also include their postal address, 
which they have not been doing.

Trying to find a technical solution to the problem, such as using a 
different domain name in the messages, is pretty much begging to have 
their account terminated altogether per AUP, especially since the host's 
AUP is incredibly vague with respect to spam--they pretty much get to 
dictate whether they think it's spam or not, including requiring to ask 
all of the subscribers to opt-in again or be removed from the list.

Jonathan
--
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] problems with new web host and too many complaints

[Jeffrey Goldberg]

On Aug 30, 2007, at 9:24 PM, Jonathan Dill wrote:

 I have a customer who has a fairly large opt-in only mailman mailing
 list (~40,000 subscribers) that they use to send out a weekly
 newsletter,

How was the opt-in done?  Was it done with Mailman's confirmation  
process, or  would it have been possible for person A to accidently  
or maliciously get person B on the list?  If the latter, I would  
consider the list mailing unacceptable.

 people seem to primarily subscribe for the weekly contest
 for free tickets to events.  Unsubscribe links are conspicuous, and
 people who otherwise complain are unsubscribed from the list.

A great deal of spam contains fake unsubscribe information.  Indeed  
following the unsubscribe information in spam often gets you opted  
in to more lists because you have proved (1) that a human actually  
reads the mail sent to that address, and (2) that the human who does  
read that mail is gullible.

 Recently, they moved their web hosting to a new service, and the new
 service shut down their website because they had received too many
 complaints about the newsletter, which mentions the website address.

Obviously there are too many members of the list who do not believe  
that they opted in to it.  Why might that be?

 I
 would have thought it would be easier to follow the unsubscribe link
 than track down the hosting company for the website, which makes me
 wonder if these complaints are being generated by some kind of
 antispam software.

You sound like someone defending opt-out mass mailing.  I've  
described above why people (correctly) avoid the opt-out instructions  
in what the think might be spam.

 The host forwarded a sample but stripped out some
 of the message headers, so all I can tell is that it really was in
 response to the newsletter.

This is normal practice to prevent the list managers from merely  
engaging in list washing (removing the complainers while continuing  
to send the spam to many people who never really wanted it but don't  
bother to complain.

 Now the web host is talking about requiring that all of the  
 subscribers
 be required to opt in again or be unsubscribed from the list--to be
 honest, that might not be a bad idea, but the customer wants to  
 avoid this.

That is a good idea.  This is really the only way your customer can  
continue with the mass mailing.  There may have been things that your  
customer might have done earlier to prevent this state of affairs,  
but at this point, what the hosting providers are suggesting is the  
only way forward, unless your customer can document how each address  
came to be added to the list with some evidence that the  person who  
reads mail at that addresses confirmed the process.

 Has anyone else run into a situation like this and have some practical
 advice?

I certainly have experience from the other end.  A few years ago some  
unknown person signed me up to scores of lists that didn't do proper  
confirmation.  Apparently, this bit of abuse is known as list bombing.

 They have been asking me about technical ways to circumvent the
 problem, but that sounds like a really bad idea to me for several
 reasons,

Your customer will either have to

   (1) do what the hosting company says (and that can be done with  
mailman) or
   (2) prove that each address was added by the person behind that  
address or
   (3) close up shop or
   (4) find a spammer friendly hosting service.

-j



-- 
Jeffrey Goldberghttp://www.goldmark.org/jeff/

--
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] problems with new web host and too many complaints

[Jonathan Dill]

Jeffrey Goldberg wrote:

 How was the opt-in done?  Was it done with Mailman's confirmation 
 process, or  would it have been possible for person A to accidently or 
 maliciously get person B on the list?  If the latter, I would consider 
 the list mailing unacceptable.
If the list was hosted on one of our servers, we definitely would have 
refused to host the list under these conditions.  However, in this case 
they own the server, which is located at their own office, and they have 
asked me for advice as a consultant.  I have told them before that they 
should require confirmation and explained why they should do that.  
Sometimes, people have to learn things the hard way, nothing I can do 
about that.  However, sometimes it is helpful to have comments from 
other people and other sources that I can point to that corroborate what 
I have been telling them all along, best practices and all that.

My position at this point is this is a policy issue, not a technical 
issue.  I have warned them that trying to sneak around the problem by 
technical means is just begging to have their account terminated as a 
violation of the TOS, and that moving to another hosting service is no 
guarantee that they won't run into the same objections again.
 That is a good idea.  This is really the only way your customer can 
 continue with the mass mailing.  There may have been things that your 
 customer might have done earlier to prevent this state of affairs, but 
 at this point, what the hosting providers are suggesting is the only 
 way forward, unless your customer can document how each address came 
 to be added to the list with some evidence that the  person who reads 
 mail at that addresses confirmed the process.
They do have a paper trail for some of the subscriptions from paper 
forms that people filled out at certain events, but I don't think the 
documentation has been maintained with the thought in mind that someday 
this could be audited, but again, this is really a policy and clerical 
issue and not a technical issue.  Possibly, I could help them to find a 
solution to better manage the documentation, beyond that, it is really 
outside my scope of work.  I have managed several other lists for other 
customers on other servers (albeit much smaller than this uber list) all 
of those have required confirmation, have never run into to this type of 
problem with the other lists.

Jonathan
--
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] problems with new web host and too manycomplaints

[[EMAIL PROTECTED]]

I think all of you will find below quite interesting!!!

http://www.mattheaton.com/

I did.

Ed
--
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] problems with new web host and too many complaints

[Brad Knowles]

On 8/30/07, Jonathan Dill wrote:

  Has anyone else run into a situation like this and have some practical
  advice?  They have been asking me about technical ways to circumvent the
  problem, but that sounds like a really bad idea to me for several
  reasons, I don't want to be a party to that.  I'm wondering if they
  should just say to heck with this hosting company, but the customer is
  concerned that moving to yet another ISP is going to be just as painful
  a process as it was moving to this one, and I am not entirely sure that
  they wouldn't run into the same complaint problem with another host.

Well, you haven't really given us any real details as to the nature 
of the problem or the nature of the complaints.  So, I'm not sure 
that anyone can give you any advice that will be useful.

I can say that I'd expect to see more support from your new ISP, and 
if they're willing to treat you this way this soon after you 
switched, I have to wonder how they're going to treat you in the 
future.

-- 
Brad Knowles [EMAIL PROTECTED]
LinkedIn Profile: http://tinyurl.com/y8kpxu
--
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] problem creating new list on the web - Unkown Virtual Host

[Brad Knowles]

On 6/19/07, Christopher Adams wrote:

  When I create a list via the web, I get the dreaded 'Unknown Virtual
  Host mailinglists.state.or.us' message.

That name does not exist in the DNS:

% dig mailinglists.state.or.us. any

;  DiG 9.3.4  mailinglists.state.or.us. any
;; global options:  printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 49283
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;mailinglists.state.or.us.  IN  ANY

;; Query time: 3 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Tue Jun 19 18:30:48 2007
;; MSG SIZE  rcvd: 42


% dig @lynx.state.or.us. mailinglists.state.or.us. any

;  DiG 9.3.4  @lynx.state.or.us. mailinglists.state.or.us. any
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 12659
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;mailinglists.state.or.us.  IN  ANY

;; AUTHORITY SECTION:
state.or.us.3600IN  SOA lynx.state.or.us. 
dns-admin.state.or.us. 2007061500 10800 1800 604800 3600

;; Query time: 72 msec
;; SERVER: 159.121.107.82#53(159.121.107.82)
;; WHEN: Tue Jun 19 18:31:44 2007
;; MSG SIZE  rcvd: 93


You might want to get that fixed.

While you're at it, you should have your nameserver administrators 
look into fixing the other things wrong with the domain -- see 
http://www.dnsstuff.com/tools/dnsreport.ch?%26domain%3Dstate.or.us.

-- 
Brad Knowles [EMAIL PROTECTED], Consultant  Author
LinkedIn Profile: http://tinyurl.com/y8kpxu
Slides from Invited Talks: http://tinyurl.com/tj6q4

09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
--
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] problem creating new list on the web - UnkownVirtual Host

[Mark Sapiro]

Christopher Adams wrote:

When I create a list via the web, I get the dreaded 'Unknown Virtual
Host mailinglists.state.or.us' message.

I consulted the FAQ, but I couldn't see what was wrong:

http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.036.htp


Also see
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.062.htp
(now referenced from 4.36).


I didn't configure the DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST during
the configuration of Mailman, so I added them to mm_cfg.py and
restarted mailman. My entry looks like this:

#Virtual Host and Email Host
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
DEFAULT_EMAIL_HOST = 'mailinglists.state.or.us'
DEFAULT_URL_HOST = 'mailinglists.state.or.us'


Presumably the definitions of DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST
in  Defaults.py are wrong since you didn't configure them and your
host is 'Unknown'. Therefore, there are two problems with the above.

The first problem is you want to remove the erroneous VIRTUAL_HOSTS
entry created in Defaults.py. This is not critical, but it is good
practice.

The main problem is you need to move the

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

directive to a point AFTER you have redefined DEFAULT_EMAIL_HOST and
DEFAULT_URL_HOST. Otherwise, you are just re-adding the erroneous
entry from Defaults.py.

So what you want is

VIRTUAL_HOSTS.clear()
DEFAULT_EMAIL_HOST = 'mailinglists.state.or.us'
DEFAULT_URL_HOST = 'mailinglists.state.or.us'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

(the first 3 can be in any order, but the add_virtualhost() must be the
last of the 4.


Other list admin functions from the web work and I can create lists
from the command line.


You may need to run fix_url on the lists you created from the command
line. See the above referenced FAQ 4.62 and also 4.69.

-- 
Mark Sapiro [EMAIL PROTECTED]   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] problem creating new list on the web - Unkown Virtual Host

[Christopher Adams]

Brad,

Sorry for putting you through that. 'mailinglists.state.or.us' is not
the actual domain name. I used it as an example. The actual name is
'listsmart.osl.state.or.us' and does exist in DNS.

I have a server with 2 NICs. One of the NICs has the
'listsmart.osl.state.or.us' IP attached to it along with another IP. I
don't know if that makes any difference.


On 6/19/07, Brad Knowles [EMAIL PROTECTED] wrote:
 On 6/19/07, Christopher Adams wrote:

   When I create a list via the web, I get the dreaded 'Unknown Virtual
   Host mailinglists.state.or.us' message.

 That name does not exist in the DNS:

 % dig mailinglists.state.or.us. any

 ;  DiG 9.3.4  mailinglists.state.or.us. any
 ;; global options:  printcmd
 ;; Got answer:
 ;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 49283
 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

 ;; QUESTION SECTION:
 ;mailinglists.state.or.us.  IN  ANY

 ;; Query time: 3 msec
 ;; SERVER: 192.168.1.1#53(192.168.1.1)
 ;; WHEN: Tue Jun 19 18:30:48 2007
 ;; MSG SIZE  rcvd: 42


 % dig @lynx.state.or.us. mailinglists.state.or.us. any

 ;  DiG 9.3.4  @lynx.state.or.us. mailinglists.state.or.us. any
 ; (1 server found)
 ;; global options:  printcmd
 ;; Got answer:
 ;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 12659
 ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

 ;; QUESTION SECTION:
 ;mailinglists.state.or.us.  IN  ANY

 ;; AUTHORITY SECTION:
 state.or.us.3600IN  SOA lynx.state.or.us.
 dns-admin.state.or.us. 2007061500 10800 1800 604800 3600

 ;; Query time: 72 msec
 ;; SERVER: 159.121.107.82#53(159.121.107.82)
 ;; WHEN: Tue Jun 19 18:31:44 2007
 ;; MSG SIZE  rcvd: 93


 You might want to get that fixed.

 While you're at it, you should have your nameserver administrators
 look into fixing the other things wrong with the domain -- see
 http://www.dnsstuff.com/tools/dnsreport.ch?%26domain%3Dstate.or.us.

 --
 Brad Knowles [EMAIL PROTECTED], Consultant  Author
 LinkedIn Profile: http://tinyurl.com/y8kpxu
 Slides from Invited Talks: http://tinyurl.com/tj6q4

 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0



-- 
Christopher Adams
[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] Migrating to new server...

[Mark Sapiro]

Will Nordmeyer wrote:

I'm preparing to migrate my mailman V2.1.9 (just upgraded from 2.1.8 last
night) lists, etc. to a new server.  I found this article
http://www.mail-archive.com/mailman-users@python.org/msg11052.html directing
me how to back up/restore, etc.


Also see
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.004.htp
and perhaps other FAQs including 4.6 and 4.18 and 4.29.


It tells me to back up config.db for each list.  I don't have/can't find any
config.db files within the mailman system.  How bad is that?


config.db went away in Mailman 2.1. It is now config.pck. The
instructions in the article you point to contain unnecessary steps. It
isn't necessary to create the list with newlist on the new server.
Also, the config.db files they refer to (now config.pck files) are in
the lists/listname/ directories, so following the steps literally will
move them twice.

-- 
Mark Sapiro [EMAIL PROTECTED]   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] help with new server.

[Brad Knowles]

At 3:55 PM -0400 2006-08-07, Lopez, Carlos Andres wrote:

  Does anyone know a good site where I can find some good how-to's setup
  postfix and mailman?

We've worked pretty hard on the documentation and the FAQ.  Is there 
something specific you're looking for that is not covered there?

-- 
Brad Knowles, [EMAIL PROTECTED]

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.

 -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
 Assembly to the Governor, November 11, 1755

  Founding Individual Sponsor of LOPSA.  See http://www.lopsa.org/.
--
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] help with new server.

[Patrick Bogen]

On 8/7/06, Lopez, Carlos Andres [EMAIL PROTECTED] wrote:
 Does anyone know a good site where I can find some good how-to's setup
 postfix and mailman?

This looks promising:
http://homex.subnet.at/~max/mail/mailman.php

I don't know if it's totally up-to-date, though.

-- 
- Patrick Bogen
--
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] help request: new 1300 member list results inmostly bounces

[Mark Sapiro]

Nathan wrote:

Any advice as to why this is happening? I'm assuming the problem is NOT 
with mailman itself, but possibly with her webhost (maybe flagged as a 
spammer by other hosts?).


That's one possibility.


For what it's worth, one other address to 
which the email did get through was my mac.com address. I noticed in my 
mac.com web interface that the message showed that it had an 
attachment, but there was no evidence of that attachment once I clicked 
through to read the mail. She's sending from AOL, and it does appear 
that html was included, so maybe the attached file is the html 
document?


Or maybe it's the list footer. See
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.039.htp.


I am not her usual web person, so don't have a lot of other info, or a 
way to take it up directly with the host, however I'm sure I could 
speak with him and get whatever info is necessary, but at the moment, I 
don't even know what to ask. Since mailman handles the bounces 
automatically, I don't even know how to go about figuring out what 
caused them.


One possibility is the host has a limit on how many recipients can be
addressed in one email or sent to within some time frame.

In a hosted situation, it's difficult to deal with bounce info. If
bounce_notify_owner_on_disable is on, the owner will get a copy of any
disabling bounce, but bounces that only increment the score are not
saved or reported. You can set bounce_score_threshold to 1.0 so the
member is disabled and the owner notified on the first bounce, but
then you have the problem of re-enabling everyone which is tedious via
the web. Since you are just setting this up, you could set the
threshold low, send a message, see the bounces and then mass remove
everyone and mass subscribe them back.


Also, is there a way to send out a test message to only a few members 
of the group? If this were the case, I could try to troubleshoot by 
sending a message from my account rather than hers, using plain text, 
etc.


Set up a separate test list with only those few addresses. There's no
convenient way to disable delivery for all but a few members and then
re-enable it. As above, you could mass remove all but a few and then
mass subscribe them when you're done.

-- 
Mark Sapiro [EMAIL PROTECTED]   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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-i18n] New Mailman wiki, Subversion (and other stuff)

[Barry Warsaw]

On Sun, 2006-04-16 at 11:17 +0930, Clytie Siddall wrote:
 Barry, thanks for such an encouraging look into the near future. :)

I'm trying to get re-energized! :)

 OK, I've already submitted an i18n howto to the SF tracker, which I  
 don't think Tokoi has had time to implement. I would be happy to do a  
 full Mailman i18n howto in the wiki. I think we need an  
 Internationalization space: can I create that, or does an admin  
 have to do that? (We should use the full word because we are likely  
 to attract first-time translators who don't know the jargon yet: we  
 have done so recently.)

Only wiki admins can create spaces.  I thought about creating an
Internationalization space but because spaces are fairly distinct, I
opted instead to create a subpage under the Development space.  Let's
see if that works before adding another space.  (And BTW, although I
haven't read your HOWTO, I think that's /exactly/ the kind of thing I'd
like to see in the wiki!  So go for it. :)

 I'm really pleased that we have a central information space like  
 this, which is relatively easily-accessed. It should make updating  
 and contribution in general, much easier.

Exactly!

 I think you'd end up spending a lot of time bridging between  
 trackers, trying to keep track of items that affect more than one  
 version. I'd recommend getting the lot across, if possible.

Yep.

 
  Now that Mailman 2.1.8 is out, I've gone ahead and converted the SF  
  CVS
  repository to Subversion.
 
 Yay! :)

Indeed!  Subversion is /so/ much better than CVS. :)
 
 I might even get my translation (completed some time ago)  
 implemented. ;)

Yes, let's try to make that happen now.
-Barry



signature.asc
Description: This is a digitally signed message part
--
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] cant create new lists ?

[Mark Sapiro]

Mehmet Fatih AKBULUT wrote:

i cannot create new lists.
getting the errors below :
*You are not authorized to create new mailing lists*
snip

what is missing ? i did everything as supposed to be ? i am the mailowner
and administrator ?
what should i do to create new mailing lists ?


To create a list from the web, you need to supply either the site
password or the special list creation password - both set by
bin/mmsitepass - in the List creator's (authentication) password:
field at the bottom of the form. The message is telling you that the
password you provided is not one of those two.


and the second question i want to ask is about images.
i installed mailman using apt-get install. but images not shown on pages.
where exactly i move images directory to be able to see icons on pages ?


See http://www.list.org/mailman-install/node10.html. If that doesn't
help you, you'll need to talk to whoever built the package you
installed or someone who knows the details of that package.

You can always put IMAGE_LOGOS = 0 in mm_cfg.py to 'turn off' the
images all together.

-- 
Mark Sapiro [EMAIL PROTECTED]   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] Creatng a new list

[Ronnie Napster Tash]

Hi am geting this error when am creating a   new mailing lists.

Bug in Mailman version 2.1.7 We're sorry, we hit a bug!

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



--
   Ronnie Tash says,
there's a method to my madness, its called being insane
Everything can be achieved as long you can do what it takes to achieve it!
--
--
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] Creatng a new list

[Mark Sapiro]

Ronnie Napster Tash wrote:

Hi am geting this error when am creating a   new mailing lists.

Bug in Mailman version 2.1.7 We're sorry, we hit a bug!

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

Look in mailman's 'error' log and find the full description and
traceback for this error, and if that doesn't tell you what the
problem is, post it here for advice.

-- 
Mark Sapiro [EMAIL PROTECTED]   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] Creatng a new list

[Andrew Partan]

On Thu, Feb 02, 2006 at 01:21:44PM -0700, Ronnie Napster Tash wrote:
 Hi am geting this error when am creating a   new mailing lists.
 
 Bug in Mailman version 2.1.7 We're sorry, we hit a bug!

I ran into this too; run check_perms  see if there is a new directory
that was created with the wrong permissions.  Fix the permissions
(check_perms -f) and try to create the list again.
--asp
--
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] User unknown new error

[John Fleming]

- Original Message - 
From: John Fleming [EMAIL PROTECTED]
To: mailman-users@python.org
Sent: Saturday, July 23, 2005 4:19 PM
Subject: [Mailman-Users] User unknown new error


 This list used to work, and now it has a problem that I have found some
 threads about, but I still can't fix it - Not to mention, I don't know why
 it used to work and now it doesn't!  Here's the msg received back after
 trying to post to the list:

 The original message was received at Sat, 23 Jul 2005 17:09:59 -0400
 from vsat-148-64-5-87.c050.t7.mrt.starband.net [148.64.5.87]

   - The following addresses had permanent fatal errors -
 [EMAIL PROTECTED]
(reason: 550 [EMAIL PROTECTED]: Recipient address
 rejected: User unknown in local recipient table)

   - Transcript of session follows -
 ... while talking to wa9als.com.:
 DATA
  550 [EMAIL PROTECTED]: Recipient address rejected: User
 unknown in local recipient table
 550 5.1.1 [EMAIL PROTECTED]... User unknown
  554 Error: no valid recipients

 Is this an alias issue, and if so, how to fix?  Or permissions?  And 
 why/how
 could it change without my input???  Many thanks!  - John

More info - List was quiet yeterday, and I took the newbie approach and 
simply recreated the list and now that list is OK.  BUT, now another list, 
that was working yesterday, has developed the same problem, yet others are 
still fine!  How could this problem crop up in an unpredictable way?  And 
how to fix?

Tnx agn - John

--
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] User unknown new error

[Mark Sapiro]

John Fleming wrote:

- Original Message - 
From: John Fleming [EMAIL PROTECTED]
To: mailman-users@python.org
Sent: Saturday, July 23, 2005 4:19 PM
Subject: [Mailman-Users] User unknown new error


 This list used to work, and now it has a problem that I have found some
 threads about, but I still can't fix it - Not to mention, I don't know why
 it used to work and now it doesn't!  Here's the msg received back after
 trying to post to the list:

 The original message was received at Sat, 23 Jul 2005 17:09:59 -0400
 from vsat-148-64-5-87.c050.t7.mrt.starband.net [148.64.5.87]

   - The following addresses had permanent fatal errors -
 [EMAIL PROTECTED]
(reason: 550 [EMAIL PROTECTED]: Recipient address
 rejected: User unknown in local recipient table)

   - Transcript of session follows -
 ... while talking to wa9als.com.:
 DATA
  550 [EMAIL PROTECTED]: Recipient address rejected: User
 unknown in local recipient table
 550 5.1.1 [EMAIL PROTECTED]... User unknown
  554 Error: no valid recipients

 Is this an alias issue, and if so, how to fix?  Or permissions?  And 
 why/how
 could it change without my input???  Many thanks!  - John

More info - List was quiet yeterday, and I took the newbie approach and 
simply recreated the list and now that list is OK.  BUT, now another list, 
that was working yesterday, has developed the same problem, yet others are 
still fine!  How could this problem crop up in an unpredictable way?  And 
how to fix?


This is almost certainly an MTA alias problem. Since you don't mention
specifically updating aliases, I'm guessing your MTA is Postfix and
that somehow your $prefix/data/aliases has gotten out of synch with
your lists or something like that.

See http://www.list.org/mailman-install/node13.html

--
Mark Sapiro [EMAIL PROTECTED]   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
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] User unknown new error

[John Fleming]

- Original Message - 
From: Mark Sapiro [EMAIL PROTECTED]
To: John Fleming [EMAIL PROTECTED]; mailman-users@python.org
Sent: Sunday, July 24, 2005 9:33 AM
Subject: Re: [Mailman-Users] User unknown new error


 John Fleming wrote:

- Original Message - 
From: John Fleming [EMAIL PROTECTED]
To: mailman-users@python.org
Sent: Saturday, July 23, 2005 4:19 PM
Subject: [Mailman-Users] User unknown new error


 This list used to work, and now it has a problem that I have found some
 threads about, but I still can't fix it - Not to mention, I don't know 
 why
 it used to work and now it doesn't!  Here's the msg received back after
 trying to post to the list:

 The original message was received at Sat, 23 Jul 2005 17:09:59 -0400
 from vsat-148-64-5-87.c050.t7.mrt.starband.net [148.64.5.87]

   - The following addresses had permanent fatal errors -
 [EMAIL PROTECTED]
(reason: 550 [EMAIL PROTECTED]: Recipient address
 rejected: User unknown in local recipient table)

   - Transcript of session follows -
 ... while talking to wa9als.com.:
 DATA
  550 [EMAIL PROTECTED]: Recipient address rejected: 
 User
 unknown in local recipient table
 550 5.1.1 [EMAIL PROTECTED]... User unknown
  554 Error: no valid recipients

 Is this an alias issue, and if so, how to fix?  Or permissions?  And
 why/how
 could it change without my input???  Many thanks!  - John

More info - List was quiet yeterday, and I took the newbie approach and
simply recreated the list and now that list is OK.  BUT, now another list,
that was working yesterday, has developed the same problem, yet others are
still fine!  How could this problem crop up in an unpredictable way?  And
how to fix?


 This is almost certainly an MTA alias problem. Since you don't mention
 specifically updating aliases, I'm guessing your MTA is Postfix and
 that somehow your $prefix/data/aliases has gotten out of synch with
 your lists or something like that.

 See http://www.list.org/mailman-install/node13.html

Any idea how they get out of synch?  I hadn't created a new list for awhile 
when it started screwing up.  Here are some observations after reading the 
info at the link above:

1.  Regarding the ownership of aliases and aliases.db, mine are reversed -

aliases - Owner = www-data, Group = list
aliases.db - Owner = list, Group - www-data

I don't know if that's how they used to be or not.

Permissions for both files is 0660.

Would you suggest that I change both to owner = list and group = www-data 
and then run bin/genaliases?

The aliases file only has information for 2 of my lists - The 2 that work 
BTW!

I tried running genaliases yesterday, but I think it didn't work correctly 
due to permissions mismatch.
- John

--
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] create a new list (web interface) + qmailaliases

[Rodrigo Lagos]

Thats a good idea, the other bit here is that i need to create the .qmail 
aliases based on domain, looking at the directory listing will not get me 
the information of what domain this list belongs to.
any other ideas?
--rodrigo



How about using a small script that is kicked off every 5 minutes via a
cron job?

Something like this (that looks at the last time the ~mailman/lists
directory was modified)...

  LDT1=`ls -ld /usr/local/mailman/lists`
  LDT2=`cat /usr/local/mailman/checklist LDT 2/dev/null`
  if [ $LDT1 = $LDT2 ]; then exit 0 ; fi
  # if the listing for the ~mailman/lists directory
  # hasn't changed then no lists have been created or deleted
insert your script commands here...
...

Good Luck - Jon Carnes


On Mon, 2003-01-27 at 20:23, Rodrigo Lagos wrote:
 Hi all,
 I have Mailman 2.1 installed running with qmail, i have been using the
 Mailman+qmail configuration for a while, but just now making the upgrade 
to
 MM 2.1.
 I was very happy to see the create a new mailing list in the admin 
page. I
 have it all working with virtual domains, and its great.
 I do have one question. Is there a way to use the create cgi to also 
kick
 off creation of .qmail aliases for that list, maybe from create.py?  i 
have
 a small shell script that creates the aliases, but don't know how to 
kick
 off the script after the list has been created from the same process.
 Anyone done this ??
 ideas?
 thanks
 --rodrigo


 _
 Help STOP SPAM with the new MSN 8 and get 2 months FREE*
 http://join.msn.com/?page=features/junkmail


 --
 Mailman-Users mailing list
 [EMAIL PROTECTED]
 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/

 This message was sent to: [EMAIL PROTECTED]
 Unsubscribe or change your options at
 http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com


_
The new MSN 8: smart spam protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] create a new list (web interface) + qmailaliases

[Jon Carnes]

After sensing a change in the lists you could use the
~mailman/bin/list_lists command to look at each mailing list in each
domain (the command has a switch that lets you list lists by virtual
domains).

Jon Carnes

On Tue, 2003-01-28 at 18:43, Rodrigo Lagos wrote:
 Thats a good idea, the other bit here is that i need to create the .qmail 
 aliases based on domain, looking at the directory listing will not get me 
 the information of what domain this list belongs to.
 any other ideas?
 --rodrigo
 
 
 
 How about using a small script that is kicked off every 5 minutes via a
 cron job?
 
 Something like this (that looks at the last time the ~mailman/lists
 directory was modified)...
 
LDT1=`ls -ld /usr/local/mailman/lists`
LDT2=`cat /usr/local/mailman/checklist LDT 2/dev/null`
if [ $LDT1 = $LDT2 ]; then exit 0 ; fi
# if the listing for the ~mailman/lists directory
# hasn't changed then no lists have been created or deleted
  insert your script commands here...
  ...
 
 Good Luck - Jon Carnes
 
 
 On Mon, 2003-01-27 at 20:23, Rodrigo Lagos wrote:
   Hi all,
   I have Mailman 2.1 installed running with qmail, i have been using the
   Mailman+qmail configuration for a while, but just now making the upgrade 
 to
   MM 2.1.
   I was very happy to see the create a new mailing list in the admin 
 page. I
   have it all working with virtual domains, and its great.
   I do have one question. Is there a way to use the create cgi to also 
 kick
   off creation of .qmail aliases for that list, maybe from create.py?  i 
 have
   a small shell script that creates the aliases, but don't know how to 
 kick
   off the script after the list has been created from the same process.
   Anyone done this ??
   ideas?
   thanks
   --rodrigo
  
  
   _
   Help STOP SPAM with the new MSN 8 and get 2 months FREE*
   http://join.msn.com/?page=features/junkmail
  
  
   --
   Mailman-Users mailing list
   [EMAIL PROTECTED]
   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/
  
   This message was sent to: [EMAIL PROTECTED]
   Unsubscribe or change your options at
   http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com
 
 
 _
 The new MSN 8: smart spam protection and 2 months FREE*  
 http://join.msn.com/?page=features/junkmail
 
 
 --
 Mailman-Users mailing list
 [EMAIL PROTECTED]
 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/
 
 This message was sent to: [EMAIL PROTECTED]
 Unsubscribe or change your options at
 http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] create a new list (web interface) + qmailaliases

[Jon Carnes]

How about using a small script that is kicked off every 5 minutes via a
cron job?

Something like this (that looks at the last time the ~mailman/lists
directory was modified)...

  LDT1=`ls -ld /usr/local/mailman/lists`
  LDT2=`cat /usr/local/mailman/checklist LDT 2/dev/null`
  if [ $LDT1 = $LDT2 ]; then exit 0 ; fi
  # if the listing for the ~mailman/lists directory
  # hasn't changed then no lists have been created or deleted
insert your script commands here...
...

Good Luck - Jon Carnes


On Mon, 2003-01-27 at 20:23, Rodrigo Lagos wrote:
 Hi all,
 I have Mailman 2.1 installed running with qmail, i have been using the 
 Mailman+qmail configuration for a while, but just now making the upgrade to 
 MM 2.1.
 I was very happy to see the create a new mailing list in the admin page. I 
 have it all working with virtual domains, and its great.
 I do have one question. Is there a way to use the create cgi to also kick 
 off creation of .qmail aliases for that list, maybe from create.py?  i have 
 a small shell script that creates the aliases, but don't know how to kick 
 off the script after the list has been created from the same process.
 Anyone done this ??
 ideas?
 thanks
 --rodrigo
 
 
 _
 Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
 http://join.msn.com/?page=features/junkmail
 
 
 --
 Mailman-Users mailing list
 [EMAIL PROTECTED]
 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/
 
 This message was sent to: [EMAIL PROTECTED]
 Unsubscribe or change your options at
 http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org