Re: [Mailman-Users] Server migration problems
![](https://secure.gravatar.com/avatar/7a816c9b5e71bd5aa351660bb51d86b6.jpg?s=120&d=mm&r=g)
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.062.htp>.
Thanks, you were right on about the domain problem. I looked right passed it, since the server will end up at the same domain, but currently I'm accessing by IP address (I hosts file update on my local machine solved that problem).
The archives problem persists. You gave me the right place to look here
as well. The archives are all owned by list (group list), but the
private archives have restricted access that blocks other users from
getting in:
ls of /var/lib/mailman/archives:
drwxrws--- 200 list list 8.0K 2007-04-25 14:26 private
drwxrwsr-x 2 list list 4.0K 2007-04-25 14:23 public
A sample from the private directory is: drwxrwsr-x 4 list list 4.0K 2007-04-25 14:18 itd_test
Apache's error log: [Fri Apr 27 11:42:14 2007] [error] [client 172.17.201.205] Symbolic link not allowed or link target not accessible: /var/lib/mailman/archives/public/itd_test, referer: http://server.org/mailman/listinfo/itd_test
I can't browse the file system (in bash) to those directories. I did double check the links in public as root, and they do work just fine, so I'm at a permissions problem. What should the perms here be? Or am I missing something else?
Aaron
![](https://secure.gravatar.com/avatar/a400697dc7cda649ce9311544c83fdda.jpg?s=120&d=mm&r=g)
Hi All--
On 4/27/07, Aaron Crosman <acrosman@afsc.org> wrote:
Unless I'm missing something, this is an Apache configuration problem. It both has to know about the mailman directories and be allowed to follow symbolic links. Permissions have to be correct yes, but if Apache can't follow links then the permissions are moot. Include this directive in your httpd.conf file:
Options FollowSymLinks
You must provide it for any directory you need to put symlinks in. For example:
Alias /icons/ "/usr/share/apache2/icons/" <Directory "/usr/share/apache2/icons"> Options FollowSymLinks blah blah blah ... </Directory>
Of course, the directories listed in httpd.conf are dependent on your *nix, as is the location (and name) of the httpd.conf file.
Metta, Ivan
Ivan Van Laningham God N Locomotive Works http://www.pauahtun.org/ http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningh... Army Signal Corps: Cu Chi, Class of '70 Author: Teach Yourself Python in 24 Hours
![](https://secure.gravatar.com/avatar/b10038a93090eba2cd27338ca2e1f6ff.jpg?s=120&d=mm&r=g)
I've started to get an error message back from the monthly reminders. The gateway is reporting that:
"Your message could not be delivered to:
dawn norris,University of Maine (The name was not found at the remote site. Check that the name has been entered correctly.)"
Fair enough. It's not an e-mail address, there's no reason why the server SHOULD be able to deliver it. But I can't find the bad entry. Find_member for 'dawn,' 'dawn Norris,' and 'University of Maine' are all coming back with nothing found. How do I locate this incorrect entry?
Bill
![](https://secure.gravatar.com/avatar/746f7519ba02fb0d815e59f305c53fa2.jpg?s=120&d=mm&r=g)
McNutt Jr, William R wrote:
Presumably the address on the list is OK, but a .forward or other aliasing mechanism downstream of Mailman is converting it.
Also, it seems you are not getting the message body returned since it contains the address to which the reminder was sent.
If you are getting Received: headers back, you might be able to narrow it down from the domain of the first server it is sent to.
If you set
VERP_PASSWORD_REMINDERS = Yes
in mm_cfg.py, the reminders will be sent with envelope from mailman-bounces+user=example.net@example.com where user=example.net comes from the recipients user@example.net member address and example.com is your domain. The 'bounce' should come back to the envelope address and enable you to see the user's address.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/7bdecdef03708b218939094eb05e8b35.jpg?s=120&d=mm&r=g)
On 5/1/07, McNutt Jr, William R wrote:
Good question. If find_member isn't finding it, that tells me that there's some other illegal characters in the address that aren't visible, or that maybe the address is something totally different inside your system and that the broken aliasing is happening somewhere else.
Other than doing a "dumpdb" of all the lists and doing some visual searching, I'm not sure that I've got an easy answer for you.
-- Brad Knowles <brad@shub-internet.org>, Consultant & Author LinkedIn Profile: <http://tinyurl.com/y8kpxu> Slides from Invited Talks: <http://tinyurl.com/tj6q4>
![](https://secure.gravatar.com/avatar/a400697dc7cda649ce9311544c83fdda.jpg?s=120&d=mm&r=g)
Hi All--
On 4/27/07, Aaron Crosman <acrosman@afsc.org> wrote:
Unless I'm missing something, this is an Apache configuration problem. It both has to know about the mailman directories and be allowed to follow symbolic links. Permissions have to be correct yes, but if Apache can't follow links then the permissions are moot. Include this directive in your httpd.conf file:
Options FollowSymLinks
You must provide it for any directory you need to put symlinks in. For example:
Alias /icons/ "/usr/share/apache2/icons/" <Directory "/usr/share/apache2/icons"> Options FollowSymLinks blah blah blah ... </Directory>
Of course, the directories listed in httpd.conf are dependent on your *nix, as is the location (and name) of the httpd.conf file.
Metta, Ivan
Ivan Van Laningham God N Locomotive Works http://www.pauahtun.org/ http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningh... Army Signal Corps: Cu Chi, Class of '70 Author: Teach Yourself Python in 24 Hours
![](https://secure.gravatar.com/avatar/b10038a93090eba2cd27338ca2e1f6ff.jpg?s=120&d=mm&r=g)
I've started to get an error message back from the monthly reminders. The gateway is reporting that:
"Your message could not be delivered to:
dawn norris,University of Maine (The name was not found at the remote site. Check that the name has been entered correctly.)"
Fair enough. It's not an e-mail address, there's no reason why the server SHOULD be able to deliver it. But I can't find the bad entry. Find_member for 'dawn,' 'dawn Norris,' and 'University of Maine' are all coming back with nothing found. How do I locate this incorrect entry?
Bill
![](https://secure.gravatar.com/avatar/746f7519ba02fb0d815e59f305c53fa2.jpg?s=120&d=mm&r=g)
McNutt Jr, William R wrote:
Presumably the address on the list is OK, but a .forward or other aliasing mechanism downstream of Mailman is converting it.
Also, it seems you are not getting the message body returned since it contains the address to which the reminder was sent.
If you are getting Received: headers back, you might be able to narrow it down from the domain of the first server it is sent to.
If you set
VERP_PASSWORD_REMINDERS = Yes
in mm_cfg.py, the reminders will be sent with envelope from mailman-bounces+user=example.net@example.com where user=example.net comes from the recipients user@example.net member address and example.com is your domain. The 'bounce' should come back to the envelope address and enable you to see the user's address.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/7bdecdef03708b218939094eb05e8b35.jpg?s=120&d=mm&r=g)
On 5/1/07, McNutt Jr, William R wrote:
Good question. If find_member isn't finding it, that tells me that there's some other illegal characters in the address that aren't visible, or that maybe the address is something totally different inside your system and that the broken aliasing is happening somewhere else.
Other than doing a "dumpdb" of all the lists and doing some visual searching, I'm not sure that I've got an easy answer for you.
-- Brad Knowles <brad@shub-internet.org>, Consultant & Author LinkedIn Profile: <http://tinyurl.com/y8kpxu> Slides from Invited Talks: <http://tinyurl.com/tj6q4>
participants (5)
-
Aaron Crosman
-
Brad Knowles
-
Ivan Van Laningham
-
Mark Sapiro
-
McNutt Jr, William R