[Mailman-Users] mailman/gentoo/apache2, but going to web interface gives me 404 not found
Hi, I'm almost ashamed to ask this since it's probably the single most common error when setting up mailman. I have searched the archives but I haven't seen a case quite like mine; namely, with gentoo. The reason I wonder if this plays a role is that the gentoo install probably tried to do something, and perhaps got it wrong. Anyway, installation went smoothly following the gentoo+mailman howto (http://gentoo-wiki.com/HOWTO_install_Gnu_Mailman) and I received the mail saying my default list mailman had been created and how to access it. However, visiting any of the pages mentioned there gave me a 404 - not found error. Searching the archives did turn up a suggestion, that I add to my apache2 config file a line: ScriptAlias /mailman /usr/local/mailman/cgi-bin now accessing any of my mailman URLs give: 403 Forbidden: You don't have permission to access /mailman/admin/mailman on this server. but bin/check_perms -f says everything is ok. Any ideas? Thanks in advance, Michael -- 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 not sending
Well, I *thought* I had it fixed, but not. It worked for the domain
that actually matches the machine name, but not for the virtual domain
I just tested. The list address is something like [EMAIL PROTECTED],
and my mm-cfg.py is as follows:
##
# Put YOUR site-specific settings below this line.
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
DEFAULT_NNTP_HOST = 'amd64.csd-bes.net'
DEFAULT_EMAIL_HOST = 'amd64.csd-bes.net'
DEFAULT_URL_HOST = 'amd64.csd-bes.net'
MTA = 'Postfix'
POSTFIX_ALIAS_CMD = '/usr/sbin/postalias'
POSTFIX_MAP_CMD = '/usr/sbin/postmap'
POSTFIX_STYLE_VIRTUAL_DOMAINS =
['amd64.csd-bes.net','mail.csd-bes.net','lists.csd-bes.net','sbypc.org','eagles81.org','ez-realty.net','maccounting.net','re-techtalk.com','hoopscout.com']
DELIVERY_MODULE = 'SMTPDirect'
SMTPHOST = 'localhost'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('amd64.csd-bes.net', 'amd64.csd-bes.net')
add_virtualhost('mail.csd-bes.net', 'amd64.csd-bes.net')
add_virtualhost('lists.csd-bes.net', 'amd64.csd-bes.net')
add_virtualhost('sbypc.org', 'amd64.csd-bes.net')
add_virtualhost('eagles81.org', 'amd64.csd-bes.net')
add_virtualhost('ez-realty.net', 'amd64.csd-bes.net')
add_virtualhost('maccounting.net', 'amd64.csd-bes.net')
add_virtualhost('re-techtalk.com', 'amd64.csd-bes.net')
add_virtualhost('hoopscout.com', 'amd64.csd-bes.net')
IMAGE_LOGOS = '/mailmanicons/'
The error message is the same as below. Since the add virtualhost item
above sets that to amd64.csd-bes.net, and amd64.csd-bes.net is the name
of the machine in the dns settings, that should take care of it, right?
But it doesn't.
Rob Quoting [EMAIL PROTECTED]:
Thanks, this put me on the right track. My machine id did not match
the settings in my config file after the server swap.
Rob
Quoting Mark Sapiro [EMAIL PROTECTED]:
[EMAIL PROTECTED] wrote:
There is no maillog activity indicating delivery attempts, and in
viewing the mailman smtp-failure log I see lots of messages like this:
Jul 21 15:46:54 2005 (1361) delivery to [EMAIL PROTECTED]
failed with code -1: (-2, 'Name or service not known')
See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.014.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/bronto%40csd-bes.net
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
This message was sent using IMP, the Internet Messaging Program.
--
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/bronto%40csd-bes.net
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
This message was sent using IMP, the Internet Messaging Program.
--
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] (no subject)
-- 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] 2 different lists
Mark Sapiro wrote: Alexander Baldauf wrote: We have the problem that under our server mail/mailman/listinfo and under mail.dfki.de/mailman/listinfo, there are 2 different list of the mailinglists but it is the same server. If I understand you correctly, Mailman thinks you are using virtual hosts and lists are only shown on the page for the host that created them. If you set VIRTUAL_HOST_OVERVIEW = Off in mm_cfg.py, all public lists will appear on the overview listinfo and admin pages regardless of host. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan Hi yes that was the problem, the line VIRTUAL_HOST_OVERVIEW was deleted by someone, after adding it again, it works. Thanks a lot Alexander Baldauf ISG-SB DFKI -- 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/gentoo/apache2, but going to web interface gives me 404 not found
[EMAIL PROTECTED] wrote: now accessing any of my mailman URLs give: 403 Forbidden: You don't have permission to access /mailman/admin/mailman on this server. but bin/check_perms -f says everything is ok. Check both your Mailman and Apache error logs. It doesn't seem that you're even getting to the wrappers (/usr/local/mailman/cgi-bin/*), but if you are, it could be a group mismatch error - see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.016.htp Check the permissions on /usr/local/mailman/cgi-bin/. On my system, the directory and all its files are owner:group = root:mailman and the directory is rwxrwsr-x and the files are rwxr-sr-x. the setgid bits and mailman group are critical. Granted, check_perms should check this, but ?? It could also be a SELinux issue if that is applicable in your environment. -- 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 not sending
[EMAIL PROTECTED] wrote:
Well, I *thought* I had it fixed, but not. It worked for the domain
that actually matches the machine name, but not for the virtual domain
I just tested. The list address is something like [EMAIL PROTECTED],
and my mm-cfg.py is as follows:
See comments below, although virtual hosts shouldn't have anything to
do with this issue.
##
# Put YOUR site-specific settings below this line.
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
DEFAULT_NNTP_HOST = 'amd64.csd-bes.net'
DEFAULT_EMAIL_HOST = 'amd64.csd-bes.net'
DEFAULT_URL_HOST = 'amd64.csd-bes.net'
MTA = 'Postfix'
POSTFIX_ALIAS_CMD = '/usr/sbin/postalias'
POSTFIX_MAP_CMD = '/usr/sbin/postmap'
POSTFIX_STYLE_VIRTUAL_DOMAINS =
['amd64.csd-bes.net','mail.csd-bes.net','lists.csd-bes.net','sbypc.org','eagles81.org','ez-realty.net','maccounting.net','re-techtalk.com','hoopscout.com']
DELIVERY_MODULE = 'SMTPDirect'
SMTPHOST = 'localhost'
It is best to add
VIRTUAL_HOSTS.clear()
here to remove the entry from Defaults.py although this usually isn't
strictly necessary.
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('amd64.csd-bes.net', 'amd64.csd-bes.net')
The line above essentially duplicates the one above it and is redundant.
add_virtualhost('mail.csd-bes.net', 'amd64.csd-bes.net')
add_virtualhost('lists.csd-bes.net', 'amd64.csd-bes.net')
add_virtualhost('sbypc.org', 'amd64.csd-bes.net')
It seems from your reference to [EMAIL PROTECTED] that this should
probably be
add_virtualhost('sbypc.org', 'sbypc.org')
and maybe similarly for all the others.
add_virtualhost('eagles81.org', 'amd64.csd-bes.net')
add_virtualhost('ez-realty.net', 'amd64.csd-bes.net')
add_virtualhost('maccounting.net', 'amd64.csd-bes.net')
add_virtualhost('re-techtalk.com', 'amd64.csd-bes.net')
add_virtualhost('hoopscout.com', 'amd64.csd-bes.net')
Also, the Mailman.Archiver.Archiver.GetBaseArchiveURL() method inverts
the VIRTUAL_HOSTS dictionary to get the URL host name corresponding to
a particular email host. This doesn't work well if there are entries
with duplicate email host values.
IMAGE_LOGOS = '/mailmanicons/'
The error message is the same as below. Since the add virtualhost item
above sets that to amd64.csd-bes.net, and amd64.csd-bes.net is the name
of the machine in the dns settings, that should take care of it, right?
But it doesn't.
The VIRTUAL_HOSTS dictionary is not involved in this at all.
See http://mail.python.org/pipermail/mailman-users/2005-May/044742.html
for a Python script that does exactly what SMTPDirect does to send
mail.
Also see thread starting at
http://mail.python.org/pipermail/mailman-users/2005-June/045157.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
[Mailman-Users] new list announcements coming from mailman-admin
On our system (Mac OS X Server, using the bundled Postfix and bundled Mailman 2.1.4), when we create a new list with the newlist command, the new list announcement that is sent to the list owner comes from [EMAIL PROTECTED]. This address is also cited as the address to which questions should be sent. However, when a user sends mail to mailman-admin, the system thinks it's a bounce. Unrecognized bounces get forwarded to the list owners, so we do see them, but this is obviously sub-optimal. So, it seems that we have two options: 1. We could edit the aliases file. It currently reads as follows. mailman: |/usr/share/mailman/mail/mailman post mailman mailman-admin: |/usr/share/mailman/mail/mailman admin mailman mailman-bounces: |/usr/share/mailman/mail/mailman bounces mailman mailman-confirm: |/usr/share/mailman/mail/mailman confirm mailman mailman-join:|/usr/share/mailman/mail/mailman join mailman mailman-leave: |/usr/share/mailman/mail/mailman leave mailman mailman-owner: |/usr/share/mailman/mail/mailman owner mailman mailman-request: |/usr/share/mailman/mail/mailman request mailman mailman-subscribe: |/usr/share/mailman/mail/mailman subscribe mailman mailman-unsubscribe: |/usr/share/mailman/mail/mailman unsubscribe mailman If we made mailman-admin just be an alias for mailman, this could possibly work, although I worry that this alteration would be undone if someone ever ran genaliases. (I also note that the admin and bounces scripts in /usr/share/mailman/scripts are identical.) 2. We could edit the newlist command, and where it says siteadmin = Utils.get_site_email(mlist.host_name, 'admin') we could make it read siteadmin = Utils.get_site_email(mlist.host_name) This is not very appealing---I'd rather not have to remember to make this change when we update the Mailman software. Is there something else that we are doing wrong? Perhaps our site list is somehow set up incorrectly? I did read the FAQ and search the archives a bit, but I'm sure it's possible that I missed a solution. Any pointers or help would be appreciated. -- Matt Emerson [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] new list announcements coming from mailman-admin
Matt Emerson wrote: On our system (Mac OS X Server, using the bundled Postfix and bundled Mailman 2.1.4), when we create a new list with the newlist command, the new list announcement that is sent to the list owner comes from [EMAIL PROTECTED]. This address is also cited as the address to which questions should be sent. This is a bug in that bin/newlist was not updated to use listname-owner instead of the deprecated listname-admin address. The 2.1.6 version of bin/newlist fixes this. However, when a user sends mail to mailman-admin, the system thinks it's a bounce. Unrecognized bounces get forwarded to the list owners, so we do see them, but this is obviously sub-optimal. So, it seems that we have two options: 1. We could edit the aliases file. It currently reads as follows. mailman: |/usr/share/mailman/mail/mailman post mailman mailman-admin: |/usr/share/mailman/mail/mailman admin mailman mailman-bounces: |/usr/share/mailman/mail/mailman bounces mailman mailman-confirm: |/usr/share/mailman/mail/mailman confirm mailman mailman-join:|/usr/share/mailman/mail/mailman join mailman mailman-leave: |/usr/share/mailman/mail/mailman leave mailman mailman-owner: |/usr/share/mailman/mail/mailman owner mailman mailman-request: |/usr/share/mailman/mail/mailman request mailman mailman-subscribe: |/usr/share/mailman/mail/mailman subscribe mailman mailman-unsubscribe: |/usr/share/mailman/mail/mailman unsubscribe mailman If we made mailman-admin just be an alias for mailman, this could possibly work, although I worry that this alteration would be undone if someone ever ran genaliases. (I also note that the admin and bounces scripts in /usr/share/mailman/scripts are identical.) The -admin address is deprecated and should be a synonym for -bounces. This shouldn't be changed in aliases. 2. We could edit the newlist command, and where it says siteadmin = Utils.get_site_email(mlist.host_name, 'admin') we could make it read siteadmin = Utils.get_site_email(mlist.host_name) This is not very appealing---I'd rather not have to remember to make this change when we update the Mailman software. This is effectively what is done in 2.1.6 newlist except -owner is used. Is there something else that we are doing wrong? Perhaps our site list is somehow set up incorrectly? I did read the FAQ and search the archives a bit, but I'm sure it's possible that I missed a solution. No, It's not you - it's newlist. Any pointers or help would be appreciated. Download the current newlist from http://cvs.sourceforge.net/viewcvs.py/*checkout*/mailman/mailman/bin/newlist?rev=2.16.2.4 This fixes your issue and also adds a couple of options for better specifying list domains. It should work with 2.1.4 and if you upgrade to 2.1.6 in the future, nothing will change. -- 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] extract emails from a list
Hi Trevor, This scripts works wonderfuly! Thank you so much. On 7/15/05, Trevor Cullingsworth [EMAIL PROTECTED] wrote: Hi James, This script should do the trick. It is what I use. -- 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 not sending - Solved(?)
Thanks for your corrections and tips.
I made the changes, and it still didn't work. I read the thread you
referenced, and verified that my permissions and users were correct.
I then went back to look at my dns and machine settings, and found that
my host name had reverted back to the machine name, not the full name I
changed to it to previously that fixed the problem. So it wasn't
that it was working for just one list and not others, it was that the
fix that I previously made reverted before I tested other mailing
lists. When I changed it back again, all the files in the retry queue
flushed and I got a bunch of messages delivered on serveral lists.
I'm running SuSE 9.2; maybe there's a process running somewhere that is
doing this. I know there are processes that keep permissions and other
settings in sync. If this reverts again, I think the logical solution
would be to find where SuSE is deciding what hostname to use and change
it, or to change mm-cfg to match the hostname that SuSE wants to use.
Rob
Quoting Mark Sapiro [EMAIL PROTECTED]:
[EMAIL PROTECTED] wrote:
Well, I *thought* I had it fixed, but not. It worked for the domain
that actually matches the machine name, but not for the virtual domain
I just tested. The list address is something like [EMAIL PROTECTED],
and my mm-cfg.py is as follows:
See comments below, although virtual hosts shouldn't have anything to
do with this issue.
##
# Put YOUR site-specific settings below this line.
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
DEFAULT_NNTP_HOST = 'amd64.csd-bes.net'
DEFAULT_EMAIL_HOST = 'amd64.csd-bes.net'
DEFAULT_URL_HOST = 'amd64.csd-bes.net'
MTA = 'Postfix'
POSTFIX_ALIAS_CMD = '/usr/sbin/postalias'
POSTFIX_MAP_CMD = '/usr/sbin/postmap'
POSTFIX_STYLE_VIRTUAL_DOMAINS =
['amd64.csd-bes.net','mail.csd-bes.net','lists.csd-bes.net','sbypc.org','eagles81.org','ez-realty.net','maccounting.net','re-techtalk.com','hoopscout.com']
DELIVERY_MODULE = 'SMTPDirect'
SMTPHOST = 'localhost'
It is best to add
VIRTUAL_HOSTS.clear()
here to remove the entry from Defaults.py although this usually isn't
strictly necessary.
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('amd64.csd-bes.net', 'amd64.csd-bes.net')
The line above essentially duplicates the one above it and is redundant.
add_virtualhost('mail.csd-bes.net', 'amd64.csd-bes.net')
add_virtualhost('lists.csd-bes.net', 'amd64.csd-bes.net')
add_virtualhost('sbypc.org', 'amd64.csd-bes.net')
It seems from your reference to [EMAIL PROTECTED] that this should
probably be
add_virtualhost('sbypc.org', 'sbypc.org')
and maybe similarly for all the others.
add_virtualhost('eagles81.org', 'amd64.csd-bes.net')
add_virtualhost('ez-realty.net', 'amd64.csd-bes.net')
add_virtualhost('maccounting.net', 'amd64.csd-bes.net')
add_virtualhost('re-techtalk.com', 'amd64.csd-bes.net')
add_virtualhost('hoopscout.com', 'amd64.csd-bes.net')
Also, the Mailman.Archiver.Archiver.GetBaseArchiveURL() method inverts
the VIRTUAL_HOSTS dictionary to get the URL host name corresponding to
a particular email host. This doesn't work well if there are entries
with duplicate email host values.
IMAGE_LOGOS = '/mailmanicons/'
The error message is the same as below. Since the add virtualhost item
above sets that to amd64.csd-bes.net, and amd64.csd-bes.net is the name
of the machine in the dns settings, that should take care of it, right?
But it doesn't.
The VIRTUAL_HOSTS dictionary is not involved in this at all.
See http://mail.python.org/pipermail/mailman-users/2005-May/044742.html
for a Python script that does exactly what SMTPDirect does to send
mail.
Also see thread starting at
http://mail.python.org/pipermail/mailman-users/2005-June/045157.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/bronto%40csd-bes.net
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
This message was sent using IMP, the Internet Messaging Program.
--
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:
Re: [Mailman-Users] Mailman not sending - Solved(?)
On Fri, 2005-07-22 at 11:27 -0700, [EMAIL PROTECTED] wrote: Thanks for your corrections and tips. I made the changes, and it still didn't work. I read the thread you referenced, and verified that my permissions and users were correct. I then went back to look at my dns and machine settings, and found that my host name had reverted back to the machine name, not the full name I changed to it to previously that fixed the problem. So it wasn't that it was working for just one list and not others, it was that the fix that I previously made reverted before I tested other mailing lists. When I changed it back again, all the files in the retry queue flushed and I got a bunch of messages delivered on serveral lists. I'm running SuSE 9.2; maybe there's a process running somewhere that is doing this. I know there are processes that keep permissions and other settings in sync. If this reverts again, I think the logical solution would be to find where SuSE is deciding what hostname to use and change it, or to change mm-cfg to match the hostname that SuSE wants to use. I can't speak for SuSE nor do I know how you changed your hostname, but I can tell you this, if you used the plain hostname command that change will not persist across reboots. See the hostname man page on your system for how to make a permanent change. Also, if your machine is being assigned a permanent IP address via a local DHCP server you will likely have to make that change in the DHCP configuration. HTH, -- John Dennis [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
[Mailman-Users] Footer Personalization
Hi All - In the Mailman FAQ it mentions being able to personalize the footers if some settings for VERP are made in mm_cfg.py, but does not go into much detail about how to do the required changes. -- Q. Can I put the user's address in the footer that Mailman adds to each message? A. Yes, in Mailman 2.1. The site admin needs to enable personalization by setting the following variables in the mm_cfg.py file: VERP_PASSWORD_REMINDERS = 1 VERP_PERSONALIZED_DELIVERIES = 1 VERP_DELIVERY_INTERVAL = 1 VERP_CONFIRMATIONS = 1 Once this is done, list admins can enable personalization for regular delivery members (digest deliveries can't be personalized currently). A personalized list can include the user's address in the footer. -- I would like to add the original sender's email address to the footer section, copying that section from Defaults.py to mm_cfg.py, and then adding some string (conceptually). What string do I need to add to get the sender? Any advice warmly welcomed! Thanks Rick Cogley Tokyo, Japan -- 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 not sending - Solved(?)
Quoting John Dennis [EMAIL PROTECTED]: On Fri, 2005-07-22 at 11:27 -0700, [EMAIL PROTECTED] wrote: Thanks for your corrections and tips. I made the changes, and it still didn't work. I read the thread you referenced, and verified that my permissions and users were correct. I then went back to look at my dns and machine settings, and found that my host name had reverted back to the machine name, not the full name I changed to it to previously that fixed the problem. So it wasn't that it was working for just one list and not others, it was that the fix that I previously made reverted before I tested other mailing lists. When I changed it back again, all the files in the retry queue flushed and I got a bunch of messages delivered on serveral lists. I'm running SuSE 9.2; maybe there's a process running somewhere that is doing this. I know there are processes that keep permissions and other settings in sync. If this reverts again, I think the logical solution would be to find where SuSE is deciding what hostname to use and change it, or to change mm-cfg to match the hostname that SuSE wants to use. I can't speak for SuSE nor do I know how you changed your hostname, but I can tell you this, if you used the plain hostname command that change will not persist across reboots. See the hostname man page on your system for how to make a permanent change. Also, if your machine is being assigned a permanent IP address via a local DHCP server you will likely have to make that change in the DHCP configuration. Thanks, the server has not rebooted, and the IP address is fixed. Rob This message was sent using IMP, the Internet Messaging Program. -- 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 / Postfix Question on Tiger Server
I am in the process of changing over my mailing list from LetterRip Pro to Mailman , which is running on my Tiger Server (10.4.2). All of the list addresses are actually received by my EIMS server which then forwards mail for that list to the correct server - either LRP or Mailman. All of that works just fine. I have the Letter Rip Pro server to only accept mail on the SMTP Submit Port of 587. By doing that i have stopped any spam getting to that server directly as all mail for that server goes through the EIMS box which has filtering on it. My questions is how do I set Postfix on the OSX box to only receive on the SMTP Submit Port of 587? And then if I do that how do I set Mailman to send to that port rather than the default SMTP port? Thanks David Scribner BI Consulting -- 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] Footer Personalization
Cogley, Rick wrote: In the Mailman FAQ it mentions being able to personalize the footers if some settings for VERP are made in mm_cfg.py, but does not go into much detail about how to do the required changes. -- Q. Can I put the user's address in the footer that Mailman adds to each message? A. Yes, in Mailman 2.1. The site admin needs to enable personalization by setting the following variables in the mm_cfg.py file: VERP_PASSWORD_REMINDERS = 1 VERP_PERSONALIZED_DELIVERIES = 1 VERP_DELIVERY_INTERVAL = 1 VERP_CONFIRMATIONS = 1 Once this is done, list admins can enable personalization for regular delivery members (digest deliveries can't be personalized currently). A personalized list can include the user's address in the footer. -- Where in the FAQ did you find the above? I don't see it, and more importantly, it is not correct. The relevant FAQ article is 3.15 at http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.015.htp I would like to add the original sender's email address to the footer section, copying that section from Defaults.py to mm_cfg.py, and then adding some string (conceptually). What string do I need to add to get the sender? Once you have set OWNERS_CAN_ENABLE_PERSONALIZATION per the above FAQ 3.15, the personalize help on the Non-digest options page will tell you what additional substitutions are available in list headers and footers. -- 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 / Postfix Question on Tiger Server
David Scribner wrote: My questions is how do I set Postfix on the OSX box to only receive on the SMTP Submit Port of 587? And then if I do that how do I set Mailman to send to that port rather than the default SMTP port? I don't offhand know the Postfix incantations to tell it on which port(s) to listen, but on the Mailman sending side the relevant mm_cfg.py variables are SMTPHOST and SMTPPORT - read the descriptions in Defaults.py. -- 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 / Postfix Question on Tiger Server
On Fri, 2005-07-22 at 16:56 -0700, Mark Sapiro wrote: David Scribner wrote: My questions is how do I set Postfix on the OSX box to only receive on the SMTP Submit Port of 587? And then if I do that how do I set Mailman to send to that port rather than the default SMTP port? I don't offhand know the Postfix incantations to tell it on which port(s) to listen, but on the Mailman sending side the relevant mm_cfg.py variables are SMTPHOST and SMTPPORT - read the descriptions in Defaults.py. Perhaps this will be of help: http://www.macosxhints.com/article.php?story=2004122809382235 -- John Dennis [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
[Mailman-Users] Help
I would like to know how to get started ... I searched FAQ and tried to get a grasp at list.org but here I am ... I don't get the Python thing ... I understand it is a programming language but certainly I don't have to learn Python to install Mailman, right? And then when I go to download SNU Mailman version 2.1.6 there are three downloads: Mailman 2.1.6 (show only this release) Download mailman 2.1.6.tgz and Download mailman 2.1.6.tgz.asc !! So, what should I download ... and then what do I do? You're help will be greatly appreciated and as you see, I need a good deal of getting started help ... I am able to follow directions but I don't see anything that really spells it out clearly for me. Do I upload this to my cgi bin ... am I hopeless :) Thanks, Linda Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs -- 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
LinK wrote: I would like to know how to get started ... I searched FAQ and tried to get a grasp at list.org but here I am ... I don't get the Python thing ... I understand it is a programming language but certainly I don't have to learn Python to install Mailman, right? And then when I go to download SNU Mailman version 2.1.6 there are three downloads: Mailman 2.1.6 (show only this release) This is the release notes. Download mailman 2.1.6.tgz This is the actual source distribution. and Download mailman 2.1.6.tgz.asc !! This is checksums to verify the integrity of mailman-2.1.6.tgz So, what should I download ... and then what do I do? Download mailman-2.1.6.tgz and use gunzip to unzip it and tar to unpack the result. See http://www.list.org/mailman-install/index.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
