[Mailman-Users] Password // URL in Notification Emails
Every month I get an email from MailMan list's I am currently subscribed to in this email there is a field that shows as follows: List Password // URL st...@mydomain.tld vipidimi https://mail.mydomain.tld/mailman/options/ctia/carlos%40mydomain.tld Can someone tell me if there is a way to disable the plain text email of passwords via the MailMan system? I don't think those passwords are for 'Administrative' login sessions of lists so I really don't understand their purpose. Can anyone tell me what they are used for and how can I disable them from the reminder email? Thanks for any help! -- 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] Unable To Create Mailman Lists
I just installed Mailman 2.1.9-4 on my Linux mail server and configured it according to the online guide straight from the Mailman site. It appears to be working fine and I get hit the main page via Apache and see the only pubic list available called 'Mailman'. Now I selected the 'Admin Overview Page' and it takes me straight to the 'Admin' page with out any credentials for password or anything. Is this normal Mailman behavior? Should anyone be able to simply hit my Mailman public page and walk right into the 'Admin' page with put any credentials? Secondly - since I am in the 'Admin' page, I then attempt to select the link that says create a new mailing list which takes me to a new page for adding all the criteria for the new list I would like to generate. At the very bottom, it has a blank field box for List creator's (authentication) password: and I simply have no idea what that is. If I leave it blank or type in the password for the only Mailman list I have called Mailman, I get an error when creating the new list that says: Error: You are not authorized to create new mailing lists Can someone please tell me what I did wrong? Thanks so much! -Carlos -- 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] Apache Configuration for Mailman
I am trying to install / configure MailMan on my mail server which is running Postfix 2.6 Apache 2 on CentOS 5 x64. I am following the guide on the MailMan page labeled 5 Set up your web server. I am confused here because it advises me to do the following: ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ When I add that line into my /etc/httpd/conf/httpd.conf file, I get this error when I restart Apache: [r...@mail conf]# service httpd restart Stopping httpd:[OK] Starting httpd: [Tue Oct 06 14:51:49 2009] [warn] The ScriptAlias directive in /etc/httpd/conf/httpd.conf at line 565 will probably never match because it overlaps an earlier ScriptAlias. [ OK ] So now I am wondering if this means I placed it in the wrong section of my httpd.conf file. I really don't know so I am asking you guys what I am doing wrong? In my httpd.conf file in CentOS, I placed it on line 565 in the section that looked appropriate: # ScriptAlias: This controls which directories contain server scripts. # ScriptAliases are essentially the same as Aliases, except that # documents in the realname directory are treated as applications and # run by the server when requested rather than as documents sent to the client. # The same rules about trailing / apply to ScriptAlias directives as to # Alias. # ScriptAlias /cgi-bin/ /var/www/cgi-bin/ ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ # # /var/www/cgi-bin should be changed to whatever your ScriptAliased # CGI directory exists, if you have that configured. # Directory /var/www/cgi-bin AllowOverride None Options None Order allow,deny Allow from all /Directory Can someone please tell me what I am doing wrong? -- 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] Apache Configuration for Mailman
I am trying to install / configure MailMan on my mail server which is running Postfix 2.6 Apache 2 on CentOS 5 x64. I am following the guide on the MailMan page labeled 5 Set up your web server. I am confused here because it advises me to do the following: ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ When I add that line into my /etc/httpd/conf/httpd.conf file, I get this error when I restart Apache: [r...@mail conf]# service httpd restart Stopping httpd:[OK] Starting httpd: [Tue Oct 06 14:51:49 2009] [warn] The ScriptAlias directive in /etc/httpd/conf/httpd.conf at line 565 will probably never match because it overlaps an earlier ScriptAlias. [ OK ] So now I am wondering if this means I placed it in the wrong section of my httpd.conf file. I really don't know so I am asking you guys what I am doing wrong? In my httpd.conf file in CentOS, I placed it on line 565 in the section that looked appropriate: # ScriptAlias: This controls which directories contain server scripts. # ScriptAliases are essentially the same as Aliases, except that # documents in the realname directory are treated as applications and # run by the server when requested rather than as documents sent to the client. # The same rules about trailing / apply to ScriptAlias directives as to # Alias. # ScriptAlias /cgi-bin/ /var/www/cgi-bin/ ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ # # /var/www/cgi-bin should be changed to whatever your ScriptAliased # CGI directory exists, if you have that configured. # Directory /var/www/cgi-bin AllowOverride None Options None Order allow,deny Allow from all /Directory Can someone please tell me what I am doing wrong? -- 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] Genaliases Command Help
When installing MailMan, the guide explains that I need to run the /usr/lib/mailman/bin/genaliases to to initialize your aliases file. I do so as instructed and get the following response: [r...@mail bin]# ./genaliases [r...@mail bin]# As you can see I am issued no errors or anything to that nature however nothing ever generates an aliases file unless it's somewhere I can't find. What am I doing wrong? I don't think this matters but the permissions are listed below: drwxrwsr-x 13 root mailman4096 Oct 9 12:15 mailman [r...@mail lib]# cd mailman/ [r...@mail mailman]# ls -l total 44 drwxrwsr-x 2 root mailman 4096 Oct 9 12:15 bin drwxrwsr-x 2 root mailman 4096 Oct 9 12:15 cgi-bin drwxrwsr-x 2 root mailman 4096 Oct 9 12:15 cron drwxrwsr-x 2 root mailman 4096 Oct 9 12:15 icons drwxrwsr-x 2 root mailman 4096 Oct 9 12:15 mail drwxrwsr-x 11 root mailman 4096 Oct 9 12:38 Mailman drwxrwsr-x 34 root mailman 4096 Oct 9 12:15 messages drwxrwsr-x 6 root mailman 4096 Oct 9 12:15 pythonlib drwxrwsr-x 2 root mailman 4096 Oct 9 12:15 scripts drwxrwsr-x 35 root mailman 4096 Oct 9 12:15 templates drwxrwsr-x 4 root mailman 4096 Oct 9 12:15 tests Please help me understand what is going wrong. Thanks! -- 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] MailMan For LAN Only
I am wanting to implement MailMan for my company LAN. I am currently running my email server on Postfix. I am wondering if someone can answer these questions for me. If I install MailMan / Apache on my mail server, will the MailMan list be visible by anyone on the web who can access my mail server via Apache? I am worried about spammers using MailMan to harvest valid email addresses. Even though it appears from the reading I have done that non-members can't send to the list w/o moderator approval, I still don't want the vulnerability of exposing my subscribed members email addresses. Can someone please tell me if this is possible and or how I should consider configuring MailMan for my LAN? Thanks for any assistance! -- Carlos -- 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] Install MailMan On Separate Server?
I asked this a week ago and did not hear anything back and I don't know if the message reached the list so I am re-sending this. Can someone please tell me if I am able to configure Mailman installation on a web server that is separate from my Postfix (mail) server? -- 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] Installation On Separate Server Plausible?
I am being told that my Postfix email server can no longer run Apache on the same physical server. The management has decided for specific reasons that Apache can only be installed and configured on the web server, not the mail server. The mail server will simply run Postfix / Dovecot. This will force me to move web mail (RoundCube) MailMan to my web server! My question is can I have MailMan function from scratch (no data needs to be migrated to the new install) from my web server and work? My mail and web server are on the same LAN and same network/subnet, just separate servers. They don't want IT to manage several instances of the same application on different servers, in this case Apache. Thanks for any input! - Carlos -- 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] Unable To Correct Errors (Debian)
I just installed Mailman on my Debian mail server and am following the guide however I used my package installer to install Mailman. I did not build from source. I am running v2.1.9-7 and it installed fine but when I run /usr/lib/mailman/bin/check_perms -f, I get the following: email:/usr/lib/mailman/bin# ./check_perms -f /var/lib/mailman/mail bad group (has: root, expected list) (fixing) /var/lib/mailman/scripts bad group (has: root, expected list) (fixing) /var/lib/mailman/templates bad group (has: root, expected list) (fixing) /var/lib/mailman/pythonlib bad group (has: root, expected list) (fixing) /var/lib/mailman/cron bad group (has: root, expected list) (fixing) /var/lib/mailman/locks bad group (has: root, expected list) (fixing) /var/lib/mailman/bin bad group (has: root, expected list) (fixing) /var/lib/mailman/icons bad group (has: root, expected list) (fixing) /var/lib/mailman/logs bad group (has: root, expected list) (fixing) /var/lib/mailman/Mailman bad group (has: root, expected list) (fixing) /var/lib/mailman/cgi-bin bad group (has: root, expected list) (fixing) Problems found: 11 Re-run as list (or root) with -f flag to fix I did create the mailman user and mailman group manually. $ groupadd mailman $ useradd -c GNU Mailman -s /bin/false -d /no/home -g mailman mailman No matter how many times I run the check_perms script with the -f flag, it will not fix the 11 issues. I have stopped and restarted Mailman several times. Anyone know what I am doing wrong? -- 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] Deleting Mailman Mbox
On Mon, Jul 14, 2008 at 11:33 AM, Mark Sapiro [EMAIL PROTECTED] wrote: Someone else reported a similar symptom a month or two ago. (I just tried to find this in the archive, and I see it was you, not someone else.) Yes - I reported this during my migration help email. It was me... I have no idea how this happened. I suspect somehow instead of mailman.mbox/mailman.mbox being a file, it somehow became a link back to its parent. If this is the case, even rm -rf /var/lib/mailman/archives/mailman.mbox may not succeed because it may loop indefinitely, but it's worth a try. At worst, you might be able to mv /var/lib/mailman/archives/mailman.mbox junk. Then you could create a new /var/lib/mailman/archives/mailman.mbox directory and empty /var/lib/mailman/archives/mailman.mbox/mailman.mbox file with the same ownership and permissions as the good ones. So I think I am simply going to just rm -rf /var/lib/mailman/archives/private/mailman.mbox/mailman.box This will retain the first mailman.box directory which is expected to be there and then remove everything beyond that. I will then assume at some point Mailman will attempt to re-generate a mailbox.mbox file in that directory. Do you think this is a bad idea? -- 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] Fresh Install Fails To Start
I just installed Mailman 2.1.9 on my new server and I cd /usr/lib/mailman/bin and ran the ./newlist script: [EMAIL PROTECTED] bin]# ./newlist Enter the name of the list: zoo Enter the email of the person running the list: [EMAIL PROTECTED] Initial zoo password: To finish creating your mailing list, you must edit your /etc/aliases (or equivalent) file by adding the following lines, and possibly running the `newaliases' program: ## zoo mailing list zoo: |/usr/lib/mailman/mail/mailman post zoo zoo-admin:|/usr/lib/mailman/mail/mailman admin zoo zoo-bounces: |/usr/lib/mailman/mail/mailman bounces zoo zoo-confirm: |/usr/lib/mailman/mail/mailman confirm zoo zoo-join: |/usr/lib/mailman/mail/mailman join zoo zoo-leave:|/usr/lib/mailman/mail/mailman leave zoo zoo-owner:|/usr/lib/mailman/mail/mailman owner zoo zoo-request: |/usr/lib/mailman/mail/mailman request zoo zoo-subscribe:|/usr/lib/mailman/mail/mailman subscribe zoo zoo-unsubscribe: |/usr/lib/mailman/mail/mailman unsubscribe zoo Hit enter to notify zoo owner... Now when I try and start Mailman, I get the following: [EMAIL PROTECTED] bin]# /etc/init.d/mailman start Starting mailman: Site list is missing: mailman [FAILED] When I check /var/log/mailman/error, I get the same message for every time I attempted to start the service. Anyone know what I am doing wrong? I can say that Postfix, Apache, or any other service on this server is not running so I don't know if Mailman does not like that...this was the 1st thing I decided to configure on the new email server. Thanks for any info / help! -- 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 Migration Trouble
On Mon, Jun 16, 2008 at 9:10 PM, Mark Sapiro [EMAIL PROTECTED] wrote: Since your domain names don't change, you shouldn't need to do step 6. For step 5, make sure that everything in lists/ and archives/ is your mailman group. I ran the following command: chown -R mailman:mailman /var/lib/mailman/lists/ I see that everything in /var/lib/mailman/lists is owned by mailman:mailman. So now I am looking at path in the error I received: OSError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman.mbox' [FAILED] When I look at the path in the error on my server_old and server_new, I notice the mailman.mbox path goes on and on and on and on... Is this normal? Look below - its identical on both servers however mailman works on server_old. You can see below that I start in private directory and I am able to cd in to the same directory over and over and then you can see the pwd command path... [EMAIL PROTECTED] private]# cd mailman.mbox/ [EMAIL PROTECTED] mailman.mbox]# ls -l total 4 drwxrwsr-x 3 mailman mailman 4096 Oct 25 2006 mailman.mbox [EMAIL PROTECTED] mailman.mbox]# cd mailman.mbox/ [EMAIL PROTECTED] mailman.mbox]# ls -l total 4 drwxrwsr-x 3 mailman mailman 4096 Oct 25 2006 mailman.mbox [EMAIL PROTECTED] mailman.mbox]# cd mailman.mbox/ [EMAIL PROTECTED] mailman.mbox]# cd mailman.mbox/ [EMAIL PROTECTED] mailman.mbox]# cd mailman.mbox/ [EMAIL PROTECTED] mailman.mbox]# cd mailman.mbox/ [EMAIL PROTECTED] mailman.mbox]# cd mailman.mbox/ [EMAIL PROTECTED] mailman.mbox]# ls -l total 4 drwxrwsr-x 3 mailman mailman 4096 Oct 25 2006 mailman.mbox [EMAIL PROTECTED] mailman.mbox]# pwd /var/lib/mailman/archives/private/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox/mailman.mbox -- 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 Migration Trouble
On Tue, Jun 17, 2008 at 11:15 AM, Mark Sapiro [EMAIL PROTECTED] wrote: This is very wrong. There should be one archives/private/list.mbox directory for each list and that directory should contain one list.mbox file which is a mailbox contianing all posts archived for the list. I.e., in the case of the 'mailman' list, an archives/private/mailman.mbox directory containing an archives/private/mailman.mbox/mailman.mbox file. What does 'ls -lR /var/lib/mailman/archives/private/mailman.mbox' show on the old and new servers? What about other lists? When I run ls -lR /var/lib/mailman/archives/private/mailman.mbox I get an output that is a mile long. The results from that command is huge. Every other list has one .mbox file with 775 permissions except mailman. I do see some other stuff I do not like so I am going to start from scratch. I think I will just re-create all the mailman lists from scratch and force everyone to re-subscribe. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Mailman Migration Trouble
I am migrating mailman from server_old (RHEL 4) to server_new (RHEL 5). Its basically in all sense the same machine / arch / domain / blah blah blah. I am using this archive as a guide: http://mail.python.org/pipermail/mailman-users/2007-January/055208.html I copies everything over from my old server to the new as below: /usr/bin/rsync -ave ssh --delete-after /var/lib/mailman/lists/ [EMAIL PROTECTED]:/var/lib/mailman/lists /usr/bin/rsync -ave ssh --delete-after /var/lib/mailman/archives/private/ [EMAIL PROTECTED]:/var/lib/mailman/archives/private I skipped step 3 in the guide since the domain is identical and has no reason to change... I then copied all /var/lib/mailman/archives/private/*mbox/*mbox to the new server as shown below: /usr/bin/rsync -ave ssh --delete-after /var/lib/mailman/archives/private/ [EMAIL PROTECTED]:/var/lib/mailman/archives/private Now I am trying to understand step # 5 and I don't understand since my system has no user or group called list so I can chown -R list:list. Am I missing something? Right now since I can't execute step 5, when I attempt to start mailman on my Linux server, I get the following error: [EMAIL PROTECTED] cwilliams]# /etc/init.d/mailman start Starting mailman: Traceback (most recent call last): File /usr/lib/mailman/bin/mailmanctl, line 607, in ? main() File /usr/lib/mailman/bin/mailmanctl, line 426, in main check_for_site_list() File /usr/lib/mailman/bin/mailmanctl, line 326, in check_for_site_list sitelist = MailList(sitelistname, lock=0) File /usr/lib/mailman/Mailman/MailList.py, line 130, in __init__ self.Load() File /usr/lib/mailman/Mailman/MailList.py, line 665, in Load self.CheckVersion(dict) File /usr/lib/mailman/Mailman/MailList.py, line 707, in CheckVersion self.InitVars() File /usr/lib/mailman/Mailman/MailList.py, line 404, in InitVars baseclass.InitVars(self) File /usr/lib/mailman/Mailman/Archiver/Archiver.py, line 96, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman.mbox' [FAILED] Anyone know what I am missing or doing wrong? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Mailman Permissions
I was looking today at /var/lib/mailman/lists and happened to notice the owner seems to vary. It appears that some older lists are owner by mailman:mailman and lists that I have recently created are owner by root:mailman. Here is what I see on my server: drwxrwsr-x 2 rootmailman 4096 Jun 13 13:02 lt2_support_thread drwxrwsr-x 2 rootmailman 4096 Jun 13 12:00 lvc_i2 drwxrwsr-x 2 mailman mailman 4096 Jun 13 12:00 mailman drwxrwsr-x 2 mailman mailman 4096 Jun 13 12:00 ngit drwxrwsr-x 2 rootmailman 4096 Jun 13 12:00 performancewg drwxrwsr-x 2 mailman mailman 4096 Jun 13 12:00 perf_results drwxrwsr-x 2 mailman mailman 4096 Jun 13 12:00 ptr_review_board drwxrwsr-x 2 mailman mailman 4096 Jun 13 12:00 risk_management_wg drwxrwsr-x 2 rootmailman 4096 Jun 13 12:00 scrum drwxrwsr-x 2 mailman mailman 4096 Jun 13 12:57 services_ipt drwxrwsr-x 2 mailman mailman 4096 Jun 13 12:00 stm_ipt drwxrwsr-x 2 mailman mailman 4096 Jun 13 12:00 syscon_thread drwxrwsr-x 2 rootmailman 4096 Jun 13 13:11 zoo Now I know all the lists I create are done in CLI mode using the /usr/lib/mailman/bin/.newlist script which walks me through the process easily. My question here is does it matter that some are owned by mailman and others by root and if so, how do I generate new lists properly as mailman:mailman? Thanks for any support and or info! I am using Linux RHEL 4.6 and mailman-2.1.5.1-34.rhel4.6. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Diff Two Mailman Paths?
I am moving mailman from one server to another server (not changing the domain) and noticed the instructions here: http://mail.python.org/pipermail/mailman-users/2007-January/055208.html The instructions show to make sure you copy both the contents of /var/lib/mailman/lists to the new server and also /var/lib/mailman/archives/private/. My question is when looking at /var/lib/mailman/archives/private/ I notice that there are several old and deleted or no longer functioning lists in this directory. Is there nothing that cleans up this path when you create a test list and then remove it using the script provided in /usr/lib/mailman/bin? I just don't like a lot of clutter and want this as clean as possible. Thanks for any info and help! -- Man your battle stations... -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Mailman Address Format
I was wondering why when something is sent to a mailman alias address is the actual email address manipulated to show a different non existing address. For example, I create a mailman group everyone so now people can email [EMAIL PROTECTED] and when the users get an email from that group, they see the following header info: Return Path = [EMAIL PROTECTED] X-Original-To = [EMAIL PROTECTED] Delivered-To = [EMAIL PROTECTED] So when people see this, they attempt to send back to [EMAIL PROTECTED] and of course the email is rejected because that address does not exist. I as an email administrator understand how to read the header but most common users don't and almost always send to the wrong address. They become frustrated and annoyed with Mailman and want this fixed. I explain to them to not copy and paste the email address but rather to simply reply to all or reply to sender. Why does mailman do this? I don't understand the bounce parameter and or why it does not show its from [EMAIL PROTECTED]. Thanks for any clarification or info on how to resolve this. -- Man your battle stations... -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Mailman Migration
Hello all! I have built a new email server on my LAN and would like to move over my Mailman content including archives over to my new email server and was wondering if this is a common procedure / task? I am moving from a RHEL4 to a RHEL5 server so not much is really too different in regards to location and files. Is there a guide or write up the Mailman community recommend I follow to perform this task? I am currently running mailman-2.1.5.1-34.rhel4.6 on my production server and my new server I plan to migrate to is running mailman-2.1.9-2. Thanks for any assistance and tips! Carlos -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Only One List Is Not Working
I have several mailman list on my Postfix server and all work as far as I know except for my most important one which is called everyone at example.com. This list goes out to everyone who has an email account on my Postfix server. I created some test lists today and just to make sure that mailman was not broken and they all worked. I tried sending email to some smaller lists and they all seem to work so I don't know exactly what to do to determine why my everyone list is no longer going out. I am the administrator for everyone and when anyone sends stuff to the list, I never get any emails that anything is pending and when I login via HTML interface, I don't see anything. Are there any tips you guys can suggest I do for troubleshooting or perhaps providing some information that could help me understand why simply one of my lists is not working? I checked /var/log/mailman/error and really don't know much about mailman except how to install it and mildly maintain it as far as list creation and deletion. Thanks for any assistance! mailman-2.1.5.1-34.rhel4.6 -- 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
