Hullo,
I'm struggling to get mailman up and running again after changing a virtual server to a new platform, upgrading to debian jessie in the process.
I've made the permissions on the new platform for /usr/lib/cgi-bin/mailman identical: (e.g.):-rwxr-sr-x 1 root list 10K Apr 6 16:45 admin
I've altered /etc/group to match the old server like this: list:x:38:lurker lurker:x:109:list,www-data
/etc/mailman/apache.conf contains these lines:
ScriptAlias /cgi-bin/mailman/ /usr/lib/cgi-bin/mailman/ Alias /pipermail/ /var/lib/mailman/archives/public/ Alias /images/mailman/ /usr/share/images/mailman/
<Directory /usr/lib/cgi-bin/mailman/> AllowOverride None Options ExecCGI AddHandler cgi-script .cgi Require all granted </Directory> <Directory /var/lib/mailman/archives/public/> Options FollowSymlinks AllowOverride None Require all granted </Directory> <Directory /usr/share/images/mailman/> AllowOverride None Require all granted </Directory>
My first issue is that all site links point to {server}/cgi-bin/mailman/{file}, which gives a "You don't have permission to access /cgi-bin/mailman/create on this server." warning, but if I manually change that to {server}/mailman/{file}, it works.
The second issue is that although the link to the archives displays the messages fine, the overview mailman doesn't seem to think I have any existing lists, although /var/lib/mailman is fully synced from the old server. I can't seem to find any file that holds this information.
(There is a third that in when I click on one of the mailing list titles, the actual message can't be found, but that's probably moving on to lurker issues).
Any ideas welcome!
Thanks,
Jenny
** Jenny Hopkins hopkins.jenny@gmail.com [2015-09-08 09:00]:
Hullo,
I'm struggling to get mailman up and running again after changing a virtual server to a new platform, upgrading to debian jessie in the process.
I've made the permissions on the new platform for /usr/lib/cgi-bin/mailman identical: (e.g.):-rwxr-sr-x 1 root list 10K Apr 6 16:45 admin
I've altered /etc/group to match the old server like this: list:x:38:lurker lurker:x:109:list,www-data
/etc/mailman/apache.conf contains these lines:
ScriptAlias /cgi-bin/mailman/ /usr/lib/cgi-bin/mailman/ Alias /pipermail/ /var/lib/mailman/archives/public/ Alias /images/mailman/ /usr/share/images/mailman/
<Directory /usr/lib/cgi-bin/mailman/> AllowOverride None Options ExecCGI AddHandler cgi-script .cgi Require all granted
</Directory> <Directory /var/lib/mailman/archives/public/> Options FollowSymlinks AllowOverride None Require all granted </Directory> <Directory /usr/share/images/mailman/> AllowOverride None Require all granted </Directory>
My first issue is that all site links point to {server}/cgi-bin/mailman/{file}, which gives a "You don't have permission to access /cgi-bin/mailman/create on this server." warning, but if I manually change that to {server}/mailman/{file}, it works.
If you look in /etc/mailman/mm_cfg.py you will find a line:
DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/'
and change it to:
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
that should fix issue one. I don't even have the mailman/ bit in there, but that's down to my own server setup where I have a dedicated sub domain for the lists.
The second issue is that although the link to the archives displays the messages fine, the overview mailman doesn't seem to think I have any existing lists, although /var/lib/mailman is fully synced from the old server. I can't seem to find any file that holds this information.
How long since you set this up? It may be that the cron job hasn't run to populate/update the web page. I know when I first set mine up it wasn't until the next day that I saw my test messages in the archive.
(There is a third that in when I click on one of the mailing list titles, the actual message can't be found, but that's probably moving on to lurker issues).
** end quote [Jenny Hopkins]
On 8 September 2015 at 11:07, Paul Tansom paul@aptanet.com wrote:
** Jenny Hopkins hopkins.jenny@gmail.com [2015-09-08 09:00]:
Hullo,
I'm struggling to get mailman up and running again after changing a virtual server to a new platform, upgrading to debian jessie in the process.
I've made the permissions on the new platform for /usr/lib/cgi-bin/mailman identical: (e.g.):-rwxr-sr-x 1 root list 10K Apr 6 16:45 admin
I've altered /etc/group to match the old server like this: list:x:38:lurker lurker:x:109:list,www-data
/etc/mailman/apache.conf contains these lines:
ScriptAlias /cgi-bin/mailman/ /usr/lib/cgi-bin/mailman/ Alias /pipermail/ /var/lib/mailman/archives/public/ Alias /images/mailman/ /usr/share/images/mailman/
<Directory /usr/lib/cgi-bin/mailman/> AllowOverride None Options ExecCGI AddHandler cgi-script .cgi Require all granted
</Directory> <Directory /var/lib/mailman/archives/public/> Options FollowSymlinks AllowOverride None Require all granted </Directory> <Directory /usr/share/images/mailman/> AllowOverride None Require all granted </Directory>
My first issue is that all site links point to {server}/cgi-bin/mailman/{file}, which gives a "You don't have permission to access /cgi-bin/mailman/create on this server." warning, but if I manually change that to {server}/mailman/{file}, it works.
If you look in /etc/mailman/mm_cfg.py you will find a line:
DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/'
and change it to:
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
that should fix issue one. I don't even have the mailman/ bit in there, but that's down to my own server setup where I have a dedicated sub domain for the lists.
Thanks Paul.
I tried that, with no luck. I finally found that moving the apache conf file into the apache directory worked.
The second issue is that although the link to the archives displays the messages fine, the overview mailman doesn't seem to think I have any existing lists, although /var/lib/mailman is fully synced from the old server. I can't seem to find any file that holds this information.
How long since you set this up? It may be that the cron job hasn't run to populate/update the web page. I know when I first set mine up it wasn't until the next day that I saw my test messages in the archive.
It was set up yesterday. I think I'm misunderstanding how lurker works. I've copied the db from the original server into /var/lib/lurker, but it keeps disappearing. Tried running lurker-regenerate, but that also removes the copied db then grumbles it isn't there.
Thanks,
Jenny
** Jenny Hopkins hopkins.jenny@gmail.com [2015-09-08 15:48]:
On 8 September 2015 at 11:07, Paul Tansom paul@aptanet.com wrote:
** Jenny Hopkins hopkins.jenny@gmail.com [2015-09-08 09:00]:
Hullo,
I'm struggling to get mailman up and running again after changing a virtual server to a new platform, upgrading to debian jessie in the process.
I've made the permissions on the new platform for /usr/lib/cgi-bin/mailman identical: (e.g.):-rwxr-sr-x 1 root list 10K Apr 6 16:45 admin
I've altered /etc/group to match the old server like this: list:x:38:lurker lurker:x:109:list,www-data
/etc/mailman/apache.conf contains these lines:
ScriptAlias /cgi-bin/mailman/ /usr/lib/cgi-bin/mailman/ Alias /pipermail/ /var/lib/mailman/archives/public/ Alias /images/mailman/ /usr/share/images/mailman/
<Directory /usr/lib/cgi-bin/mailman/> AllowOverride None Options ExecCGI AddHandler cgi-script .cgi Require all granted
</Directory> <Directory /var/lib/mailman/archives/public/> Options FollowSymlinks AllowOverride None Require all granted </Directory> <Directory /usr/share/images/mailman/> AllowOverride None Require all granted </Directory>
My first issue is that all site links point to {server}/cgi-bin/mailman/{file}, which gives a "You don't have permission to access /cgi-bin/mailman/create on this server." warning, but if I manually change that to {server}/mailman/{file}, it works.
If you look in /etc/mailman/mm_cfg.py you will find a line:
DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/'
and change it to:
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
that should fix issue one. I don't even have the mailman/ bit in there, but that's down to my own server setup where I have a dedicated sub domain for the lists.
Thanks Paul.
I tried that, with no luck. I finally found that moving the apache conf file into the apache directory worked.
That would work, I was a stage on from thinking about that, rashly assuming it was there and diving in with more complex suggestions!
The second issue is that although the link to the archives displays the messages fine, the overview mailman doesn't seem to think I have any existing lists, although /var/lib/mailman is fully synced from the old server. I can't seem to find any file that holds this information.
How long since you set this up? It may be that the cron job hasn't run to populate/update the web page. I know when I first set mine up it wasn't until the next day that I saw my test messages in the archive.
It was set up yesterday. I think I'm misunderstanding how lurker works. I've copied the db from the original server into /var/lib/lurker, but it keeps disappearing. Tried running lurker-regenerate, but that also removes the copied db then grumbles it isn't there.
I played with Lurker a bit a while back but didn't really get on with it, so I don't think I can help much. I'm afraid I assumed you meant the built in Mailman archives - I didn't do very well with my suggestions did I!
** end quote [Jenny Hopkins]
On 8 September 2015 at 22:42, Paul Tansom paul@aptanet.com wrote:
** Jenny Hopkins hopkins.jenny@gmail.com [2015-09-08 15:48]:
On 8 September 2015 at 11:07, Paul Tansom paul@aptanet.com wrote:
** Jenny Hopkins hopkins.jenny@gmail.com [2015-09-08 09:00]:
Hullo,
I'm struggling to get mailman up and running again after changing a virtual server to a new platform, upgrading to debian jessie in the process.
I've made the permissions on the new platform for /usr/lib/cgi-bin/mailman identical: (e.g.):-rwxr-sr-x 1 root list 10K Apr 6 16:45 admin
I've altered /etc/group to match the old server like this: list:x:38:lurker lurker:x:109:list,www-data
/etc/mailman/apache.conf contains these lines:
ScriptAlias /cgi-bin/mailman/ /usr/lib/cgi-bin/mailman/ Alias /pipermail/ /var/lib/mailman/archives/public/ Alias /images/mailman/ /usr/share/images/mailman/
<Directory /usr/lib/cgi-bin/mailman/> AllowOverride None Options ExecCGI AddHandler cgi-script .cgi Require all granted
</Directory> <Directory /var/lib/mailman/archives/public/> Options FollowSymlinks AllowOverride None Require all granted </Directory> <Directory /usr/share/images/mailman/> AllowOverride None Require all granted </Directory>
My first issue is that all site links point to {server}/cgi-bin/mailman/{file}, which gives a "You don't have permission to access /cgi-bin/mailman/create on this server." warning, but if I manually change that to {server}/mailman/{file}, it works.
If you look in /etc/mailman/mm_cfg.py you will find a line:
DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/'
and change it to:
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
that should fix issue one. I don't even have the mailman/ bit in there, but that's down to my own server setup where I have a dedicated sub domain for the lists.
Thanks Paul.
I tried that, with no luck. I finally found that moving the apache conf file into the apache directory worked.
That would work, I was a stage on from thinking about that, rashly assuming it was there and diving in with more complex suggestions!
The second issue is that although the link to the archives displays the messages fine, the overview mailman doesn't seem to think I have any existing lists, although /var/lib/mailman is fully synced from the old server. I can't seem to find any file that holds this information.
How long since you set this up? It may be that the cron job hasn't run to populate/update the web page. I know when I first set mine up it wasn't until the next day that I saw my test messages in the archive.
It was set up yesterday. I think I'm misunderstanding how lurker works. I've copied the db from the original server into /var/lib/lurker, but it keeps disappearing. Tried running lurker-regenerate, but that also removes the copied db then grumbles it isn't there.
I played with Lurker a bit a while back but didn't really get on with it, so I don't think I can help much. I'm afraid I assumed you meant the built in Mailman archives - I didn't do very well with my suggestions did I!
I got there in the end - lurker simply has to be pointed at a mailbox with the correct runes, and it builds the database.
And on the contrary - your suggestions stopped me being a lonely panicky sysadmin thinking things will never work again, and turned me back into a logical human being that can do the job! Thanks!
Jenny
-
Jenny Hopkins -
Paul Tansom