Re: [Mailman-Users] problem with mailman not working...
Thanks again. Observations: Somehow the stale lock was stopping all emails from going out and secondly, /var/lock/mailman is where the lock was. I'm not sure how I happened to figure that lock location out as it isn't ~mailman/locks. Perhaps my config is non-standard. Troy This email was created using 100% recycled organic free range electrons. On 1/13/2012 4:11 PM, Mark Sapiro wrote: Troy Campbell wrote: It appears there was a list that created locks in /var/lock/mailman so I deleted this list and recreated it and life seems to be good again...thanks again man for the excellent support! I'm glad things are again working well for you, but deleting and recreating the list was probably overkill. The FAQ at http://wiki.list.org/x/noA9 gives information about clearing stale/orphaned locks. I have now added a pointer to this FAQ from section 7 of the FAQ athttp://wiki.list.org/x/A4E9. -- 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] problem with mailman not working...
It appears there was a list that created locks in /var/lock/mailman so I deleted this list and recreated it and life seems to be good again...thanks again man for the excellent support! Troy This email was created using 100% recycled organic free range electrons. On 1/12/2012 8:05 PM, Mark Sapiro wrote: On 1/12/2012 6:09 PM, Troy Campbell wrote: It seems to be recognizing the email as local now: Jan 12 18:57:27 request1 sendmail[3015]: q0D1vRSU003015: to=troyt...@mailman.rmtc.fedex.com, ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30076, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (Ok: queued as C7FE237878) Jan 12 18:57:28 request1 postfix/local[1069]: C7FE237878: to=troyt...@mailman2.rmtc.fedex.com, relay=local, delay=0.23, delays=0.07/0/0/0.16, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post troytest) No email is coming out though? It should be expanding to my email address? OK. The mail was piped to the wrapper to be posted to the list, so now it's getting to Mailman. See the FAQ athttp://wiki.list.org/x/A4E9, particularly sections 2b, 6b, 7, 8, 9 and 13. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] problem with mailman not working...
For some reason Mailman just stopped working and I must confess that I have forgot how to debug since it has run so well for the last couple of years...it appears that when a Mailman email is sent to the Mailman server it that it doesn't recognize it as local but instead tries to relay out and then the relay sends it back and this happens multilple times if I'm reading the logs right so I assume that the aliases file for the Mailman lists isn't being recognized properly by Postfix? Here is some info (yes, I know it's ancient): rpm -qa | grep -i mailman mailman-2.1.9-4.el5 /etc/postfix/main.cf: alias_maps =hash:/etc/aliases hash:/etc/mailman/aliases and in /etc/mailman/aliases it has the list troytest with this: # STANZA START: troytest # CREATED: Sun Mar 14 19:20:17 2010 troytest: |/usr/lib/mailman/mail/mailman post troytest troytest-admin: |/usr/lib/mailman/mail/mailman admin troytest troytest-bounces: |/usr/lib/mailman/mail/mailman bounces troytest troytest-confirm: |/usr/lib/mailman/mail/mailman confirm troytest troytest-join:|/usr/lib/mailman/mail/mailman join troytest troytest-leave: |/usr/lib/mailman/mail/mailman leave troytest troytest-owner: |/usr/lib/mailman/mail/mailman owner troytest troytest-request: |/usr/lib/mailman/mail/mailman request troytest troytest-subscribe: |/usr/lib/mailman/mail/mailman subscribe troytest troytest-unsubscribe: |/usr/lib/mailman/mail/mailman unsubscribe troytest # STANZA END: troytest There is also a python process owned by mailman that is varying between 75-100% of the CPU. I realize that Postfix per se is out of the scope of this list but any suggestions/tips are sincerely appreciated. My current thinking is I need to run a postmap command to update the aliases config perhaps? Regards, -- Troy 719-484-2300 This email was created using 100% recycled organic free range electrons. -- 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] problem with mailman not working...
Thanks so much Mark...see inline replies below Troy This email was created using 100% recycled organic free range electrons. On 1/12/2012 5:48 PM, Mark Sapiro wrote: Troy Campbell wrote: For some reason Mailman just stopped working and I must confess that I have forgot how to debug since it has run so well for the last couple of years...it appears that when a Mailman email is sent to the Mailman server it that it doesn't recognize it as local but instead tries to relay out and then the relay sends it back and this happens multilple times if I'm reading the logs right so I assume that the aliases file for the Mailman lists isn't being recognized properly by Postfix? Yes, it sounds like a Postfix issue, but in order to say anything, we'd need to see postconf -n and some relevant Postfix log messages. # postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliaseshash:/etc/mailman/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2 html_directory = no inet_interfaces = all local_recipient_maps = mail_owner = postfix mailbox_size_limit = 0 mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = $myhostname localhost.$mydomainlocalhost localhost.localdomainrequest1.localdomain request2.localdomain request1.rmtc.fedex.com request2.rmtc.fedex.com mailman.rmtc.fedex.commailman2.rmtc.fedex.com mynetworks = 127.0.0.1/32146.18.0.0/16 155.161.0.0/16161.135.0.0/16 165.150.0.0/16170.5.0.0/16 170.86.0.0/16172.18.64.0/18 192.189.184.0/22198.140.0.0/22 199.81.0.0/16199.82.0.0/16 204.135.100.0/23204.135.106.0/23 204.135.108.0/23204.135.92.0/23 204.135.94.0/23204.135.96.0/23 204.135.97.0/23172.31.248.0/23 172.31.252.0/23 newaliases_path = /usr/bin/newaliases.postfix owner_request_special = no permit_mx_backup_networks = $mynetworks queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES recipient_delimiter = + relay_domains = cosd.fedex.comrmtc.fedex.com relayhost = mapper.mail.fedex.com sample_directory = /usr/share/doc/postfix-2.3.3/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtpd_authorized_verp_clients = localhost smtpd_recipient_restrictions = check_recipient_access hash:/etc/postfix/accesspermit_mynetworks reject_unauth_destination transport_maps = hash:/etc/postfix/transport unknown_local_recipient_reject_code = 550 Here is some info (yes, I know it's ancient): rpm -qa | grep -i mailman mailman-2.1.9-4.el5 /etc/postfix/main.cf: alias_maps =hash:/etc/aliases hash:/etc/mailman/aliases and in /etc/mailman/aliases it has the list troytest with this: # STANZA START: troytest # CREATED: Sun Mar 14 19:20:17 2010 troytest: |/usr/lib/mailman/mail/mailman post troytest troytest-admin: |/usr/lib/mailman/mail/mailman admin troytest troytest-bounces: |/usr/lib/mailman/mail/mailman bounces troytest troytest-confirm: |/usr/lib/mailman/mail/mailman confirm troytest troytest-join:|/usr/lib/mailman/mail/mailman join troytest troytest-leave: |/usr/lib/mailman/mail/mailman leave troytest troytest-owner: |/usr/lib/mailman/mail/mailman owner troytest troytest-request: |/usr/lib/mailman/mail/mailman request troytest troytest-subscribe: |/usr/lib/mailman/mail/mailman subscribe troytest troytest-unsubscribe: |/usr/lib/mailman/mail/mailman unsubscribe troytest # STANZA END: troytest There is also a python process owned by mailman that is varying between 75-100% of the CPU. Which one? (ps -fw) mailman 21869 21862 92 16:16 ?02:24:52 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s I realize that Postfix per se is out of the scope of this list but any suggestions/tips are sincerely appreciated. My current thinking is I need to run a postmap command to update the aliases config perhaps? The command is postalias, not postmap, and it's unlikely to help unless perhaps you previously ran 'postmap /etc/mailman/aliases', but it couldn't hurt to run 'postalias /etc/mailman/aliases'. It seems to be recognizing the email as local now: Jan 12 18:57:27 request1 sendmail[3015]: q0D1vRSU003015: to=troyt...@mailman.rmtc.fedex.com, ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30076, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (Ok: queued as C7FE237878) Jan 12 18:57:28 request1 postfix
Re: [Mailman-Users] Mailman-Users Digest, Vol 80, Issue 2
Thanks again Mark. I've decided to manage it with separate postfix config files (one for when there is no service group on a server, one for when there is just the Mailman service group, one for when there is just the IMAP service group and one when there is both) and just restart postfix and monitor it as part of VCS as it doesn't make sense to merge config files for other reasons anyway. Regards, Troy -Original Message- Troy Campbell wrote: For some reason when I moved the mailman configuration a few months ago I had to add /etc/mailman/aliases to the alias_maps e.g.,: alias_maps =hash:/etc/aliases hash:/etc/mailman/aliases whereas on the old installation I didn't. Since this is on a server that can fail over to another server that has the IMAP configuration which doesn't need /etc/mailman/aliases I would like to see if there is a workaround so that they both have the same postfix configuration. Sorry if this is more of a postfix question but I didn't get an answer on their list yet. Postfix doesn't do IMAP, nor do other MTAs, so I'm not sure if the IMAP reference is relevant. Is the Mailman package on the other server the same as the one on this server which is clearly a downstream package if aliases are in /etc/mailman. Basically trying to get the /etc/postfix/main.cf files identical so I don't have to manage the differences and bounce postfix on failover. If Mailman is installed the same way from the same package on both servers, and there are no non-mailman differences in the Postfix configuration, there should be no reason why they couldn't use the same main.cf. On the other hand if the two servers have different Mailman packages, then their Postfix requirements could be different. On the third hand, this could be simply that on the other server, Mailman's aliases were copied to /etc/aliases so /etc/mailman/aliases wasn't needed. -- 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
[Mailman-Users] /etc/mailman/aliases.db
For some reason when I moved the mailman configuration a few months ago I had to add /etc/mailman/aliases to the alias_maps e.g.,: alias_maps =hash:/etc/aliases hash:/etc/mailman/aliases whereas on the old installation I didn't. Since this is on a server that can fail over to another server that has the IMAP configuration which doesn't need /etc/mailman/aliases I would like to see if there is a workaround so that they both have the same postfix configuration. Sorry if this is more of a postfix question but I didn't get an answer on their list yet. Basically trying to get the /etc/postfix/main.cf files identical so I don't have to manage the differences and bounce postfix on failover. Regards, Troy -- 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] Problem sending emails out
Things magically started working after about an hour and a half so it must have been something else this time. Anyway, much appreciate your timely reponse! Regards, Troy -Original Message- From: Mark Sapiro [mailto:m...@msapiro.net] Sent: Thursday, July 01, 2010 6:09 PM To: Troy Campbell; mailman-users@python.org Subject: Re: [Mailman-Users] Problem sending emails out Troy Campbell wrote: The issue I'm having is that my mailman server is no longer sending email out. There was an issue with it earlier in the day where VCS shut it down because of the disk set monitor script was not completing. I'm running: mailman-2.1.9-4.el5 This was working up till today. I did some googling and there are qrunner processes running: [r...@request1 mailman]# ps -ef | grep qrunner mailman 13235 13231 0 16:26 ?00:00:01 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s mailman 13236 13231 0 16:26 ?00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 13237 13231 0 16:26 ?00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 13238 13231 0 16:26 ?00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 13239 13231 0 16:26 ?00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 13240 13231 0 16:26 ?00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 13241 13231 0 16:26 ?00:00:01 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s mailman 13242 13231 0 16:26 ?00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s Good. check_perms says everything is ok Good crond is running Irrelevant for non-digest mail delivery with Mailman 2.1.x mailmanctl is running Good. I'm running postfix 2.3.3 Any help is much appreciated! See the FAQ at http://wiki.list.org/x/A4E9. What's in Mailman's queues (/var/spool/mailman/* in RHEL)? What's in Mailman's logs, particularly smtp, smtp-failure and error? -- 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
[Mailman-Users] Problem sending emails out
The issue I'm having is that my mailman server is no longer sending email out. There was an issue with it earlier in the day where VCS shut it down because of the disk set monitor script was not completing. I'm running: mailman-2.1.9-4.el5 This was working up till today. I did some googling and there are qrunner processes running: [r...@request1 mailman]# ps -ef | grep qrunner mailman 13235 13231 0 16:26 ?00:00:01 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s mailman 13236 13231 0 16:26 ?00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 13237 13231 0 16:26 ?00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 13238 13231 0 16:26 ?00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 13239 13231 0 16:26 ?00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 13240 13231 0 16:26 ?00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 13241 13231 0 16:26 ?00:00:01 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s mailman 13242 13231 0 16:26 ?00:00:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s check_perms says everything is ok crond is running mailmanctl is running I'm running postfix 2.3.3 Any help is much appreciated! Troy -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] migrated lists getting firefox error, and new name not original list name
Hello,
I just migrated some lists from a server called
mailman.rmtc.fedex.com to a new server called
mailman2.rmtc.fedex.com (both running
2.1.9) and configuring things to try to keep the
lists the original @mailman.rmtc.fedex.com name
and I'm running into two issues.
First I've started getting the following error in firefox
on Mailman pages where I try to add a user or create
a list using the web pages:
Although this page is encrypted, the information you have entered is to be
sent over an unencrypted connection and could easily be read by a third party.
Are you sure you want to continue sending this information?
Then when I hit Continue nothing happens, it's
like I hit Cancel. The workaround is to use the
command line to do the function (such as add a member).
I modified this in mm_cfg.py on mailman2 (after
migrating) to:
fqdn = 'mailman.rmtc.fedex.com'
so as to have everything stay
@mailman.rmtc.fedex.com in the name.
Also I'm rewriting http to https URLs however I was
doing that on the original server and not getting this
error.
After creating a newlist I see this:
# withlist -l troytest
Loading list troytest (locked)
The variable `m' is the troytest MailList instance
m.getListAddress('admin')
'troytest-ad...@mailman.rmtc.fedex.com'
m.getListAddress()
'troyt...@mailman.rmtc.fedex.com'
which seems to be what I want (not mailman2...).
I was going to try running the withlist...fix_url command
on all the lists I brought over but thought I should wait/see
as the issue seems to be related more to the fqdn
not taking effect?
Secondly when I send an email using a test list I also get
@mailman2.rmtc.fedex.com as the email address rather
than @mailman.rmtc.fedex.com?
Any help with either issue appreciated!
Troy
--
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] migrated lists getting firefox error, and new name not original list name
Secondly when I send an email using a test list I also get @mailman2.rmtc.fedex.com as the email address rather than @mailman.rmtc.fedex.com? Get it where? If you mean in things like the List-* headers and the Sender:, fix_url will fix that too if DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST are properly set or you can just change a list's host_name on General Options. Sorry I was unclear Mark. When I email to the lists that I moved over I'm getting this in the sender address: listn...@mailman2.rmtc.fedex.com rather than listn...@mailman.rmtc.fedex.com. I tried doing the withlist -l -r fix_url listname but that didn't seem to have an effect? I also tried withlist -l -a -r fix_url which seemed to run pretty quick considering all the lists and the time it took to do just one so I don't know if I ran it right? Regards, Troy -- 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] buildup of attachment files...
Thanks Mark, The list's Non-digest options - scrub-nondigest is No. In the Content Filtering -Details for pass_mime_types field I show the following: multipart/mixed multipart/alternative text/plain Would that be sufficient to do what you are suggesting if I turn Edit filter_content on? Could I then remove the attachments subdirectories? Regards, Troy on 11/16/2009 07:23 PM Mark Sapiro said the following: Troy Campbell wrote: On one mailing list I'm seeing alot of attachment files building up in the archive directory: [...] Basically there are many directories in the attachments directory that go from 20070808 to 20091116. I'm running 2.1.9. I just need to know how to cleanup and turnoff if possible. It is Scrubber.py that saves these. Depending on settings, you may get one or two copies of each attachment which is either not text/plain or text/plain with an unknown character set. If the list's Non-digest options - scrub-nondigest is Yes, you will get one saved attachment when the attachment is removed from the message and replaced by a link to the saved attachment. Otherwise, you get two. One when the attachment is scrubbed for the archive and one when the attachment is scrubbed from the plain format digest. You can avoid almost all of this by removing all non-plain text with content filtering. If you don't remove them with content filtering, you can avoid the 'digest copies' by setting Digest options - digestable to No. You can avoid the 'archive copies' by turning off archiving for the list. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] buildup of attachment files...
On one mailing list I'm seeing alot of attachment files building up in the archive directory: # pwd /var/lib/mailman/archives/private # ls listname* listname: attachments index.html listname.mbox: Looking down a couple directory levels in attachements: # pwd /var/lib/mailman/archives/private/listname/attachments/20091116/4763b4e9 # file * attachment.obj: gzip compressed data, was ErrorReport.21234.txt, from Unix, last modified: Mon Nov 16 11:03:59 2009 [r...@albers 4763b4e9]# ls attachment.obj Basically there are many directories in the attachments directory that go from 20070808 to 20091116. I'm running 2.1.9. I just need to know how to cleanup and turnoff if possible. Thanks! Troy -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] upgrading from 2.1.9 to 2.1.12
I'm considering upgrading from a current installation running 2.1.9 to a new server running 2.1.12. Do I need to upgrade the 2.1.9 version on the existing server first? I saw this note about 2.1.9 which I think I can safely ignore but wondering if there are any other upgrade issues: http://wiki.list.org/pages/viewpage.action?pageId=4030623 My preference is to make a copy of everything on the new server and try a cutover so I would have the old server to fall back to in case there are any issues since it's a relatively important mail server (production like qualities). Secondly, how do I move the lists to the second server? Is there a way to export the lists and re-import to another server such that all the password information is retained or do I have to move or copy the var-prefix directory over and other parts? I'm looking for a tool that's a bit more robust than just list_members. I looked at this link but step 1 did not seem to apply to my installation..my current configuration is alot more like step 3: http://wiki.list.org/display/DOC/How+do+I+move+a+list+to+a+different+server-Mailman+installation. Appreciate your answering my preliminary and I'm sure basic questions while I do some googling to hopefully get some better questions. Regards, Troy -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] mailmanctl status question...
Hello, I'm starting an install of mailman but have not created the newlist or started mailman but decided to test the status script and getting the following: [r...@request1 ~]# /etc/init.d/mailman status Warning! You may encounter permission problems. [r...@request1 ~]# echo $? 0 My question is should the status below be non-zero? Regards, Troy -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] mmdsr question
I'm trying to figure out how to find out the location of my queue directory e.g., for the mmdsr script: QUEUEDIR=/var/lib/mailman/qfiles Thanks Troy -- 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
