At 03:18 p.m. 16/12/03 -0500, you wrote:
Send Mailman-Users mailing list submissions to [EMAIL PROTECTED]
To subscribe or unsubscribe via the World Wide Web, visit http://mail.python.org/mailman/listinfo/mailman-users or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED]
You can reach the person managing the list at [EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific than "Re: Contents of Mailman-Users digest..." Today's Topics:
1. Re: Not receiving mail (Somik Raha) 2. Re: Not receiving mail (Simon White) 3. Re: Not receiving mail (Somik Raha) 4. Re: re-creating list archive - old List-Archive problem (Todd) 5. Re: SetGID (Jon Carnes) 6. Re: re-creating list archive - old List-Archive problem (Gour) 7. Re: re-creating list archive - old List-Archive problem (Todd) 8. Re: re-creating list archive - old List-Archive problem (Gour) 9. Re: re-creating list archive - old List-Archive problem (Todd) 10. Re: re-creating list archive - old List-Archive problem (Gour) Content-Transfer-Encoding: 7bit From: "Somik Raha" <[EMAIL PROTECTED]> Precedence: list MIME-Version: 1.0 Cc: To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Date: Tue, 16 Dec 2003 09:01:48 -0800 Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1" Subject: Re: [Mailman-Users] Not receiving mail Message: 1
Simon White wrote: >From this log entry, it looks to me as if the account 'internal' on the > local machine is indeed receiving the email. > The aliases are not being included. Did you copy them to /etc/aliases > before you did newaliases? Have you checked to see if the message turns > up in /var/spool/mail/internal ?
I did copy them to aliases. Here's what /etc/aliases shows:
## internal mailing list ## created: 15-Dec-2003 somik internal: "|/home/mailman/mail/wrapper post internal" internal-admin: "|/home/mailman/mail/wrapper mailowner internal" internal-request: "|/home/mailman/mail/wrapper mailcmd internal" internal-owner: internal-admin
Also looked in the /var/spool/mail directory and did not find any file called internal.
Regards, Somik
From: Simon White <[EMAIL PROTECTED]> Precedence: list MIME-Version: 1.0 Cc: [EMAIL PROTECTED] To: Somik Raha <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> In-Reply-To: <[EMAIL PROTECTED]> Date: Tue, 16 Dec 2003 18:02:13 +0100 Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii Subject: Re: [Mailman-Users] Not receiving mail Message: 2
Reply to the list!
16-Dec-03 at 09:00, Somik Raha ([EMAIL PROTECTED]) wrote :
> Simon White wrote:
> >From this log entry, it looks to me as if the account 'internal' on the
> > local machine is indeed receiving the email.
> > The aliases are not being included. Did you copy them to /etc/aliases
> > before you did newaliases? Have you checked to see if the message turns
> > up in /var/spool/mail/internal ?
>
> I did copy them to aliases. Here's what /etc/aliases shows:
>
> ## internal mailing list
> ## created: 15-Dec-2003 somik
> internal: "|/home/mailman/mail/wrapper post internal"
> internal-admin: "|/home/mailman/mail/wrapper mailowner internal"
> internal-request: "|/home/mailman/mail/wrapper mailcmd internal"
> internal-owner: internal-admin
>
> Also looked in the /var/spool/mail directory and did not find any file
> called internal.
So maybe you need to look in the Mailman logs then, although the log entry you showed, if I remember correctly, looked like local delivery to me.
-- Simon White. Internet Consultant, Linux/Windows Server Administration. email, dns and web servers; php javascript perl asp; MySQL MSSQL Access Bridging the gap between management, HR and the tech team.
Content-Transfer-Encoding: 7bit From: "Somik Raha" <[EMAIL PROTECTED]> Precedence: list MIME-Version: 1.0 To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Date: Tue, 16 Dec 2003 09:09:39 -0800 Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1" Subject: Re: [Mailman-Users] Not receiving mail Message: 3
> Reply to the list!
Apologies! Didn't check the reply-to address..
> So maybe you need to look in the Mailman logs then, although the log > entry you showed, if I remember correctly, looked like local delivery to > me.
Looking at /home/mailman/logs does not reveal much. I can see three log files, error, subscribe and smtp, and error does not have any entries for my test mail. smtp shows these lines, but they were from an earlier test. Dec 15 14:54:44 2003 (21615) smtp for 1 recips, completed in 20.138 seconds Dec 15 15:13:02 2003 (21807) smtp for 1 recips, completed in 0.093 seconds
Is there any other log file that I should be looking at?
Thank you very much.
Regards, Somik ----- Original Message ----- From: "Simon White" <[EMAIL PROTECTED]> To: "Somik Raha" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, December 16, 2003 9:02 AM Subject: Re: [Mailman-Users] Not receiving mail
> Reply to the list! > > 16-Dec-03 at 09:00, Somik Raha ([EMAIL PROTECTED]) wrote : > > Simon White wrote: > > >From this log entry, it looks to me as if the account 'internal' on the > > > local machine is indeed receiving the email. > > > The aliases are not being included. Did you copy them to /etc/aliases > > > before you did newaliases? Have you checked to see if the message turns > > > up in /var/spool/mail/internal ? > > > > I did copy them to aliases. Here's what /etc/aliases shows: > > > > ## internal mailing list > > ## created: 15-Dec-2003 somik > > internal: "|/home/mailman/mail/wrapper post internal" > > internal-admin: "|/home/mailman/mail/wrapper mailowner internal" > > internal-request: "|/home/mailman/mail/wrapper mailcmd internal" > > internal-owner: internal-admin > > > > Also looked in the /var/spool/mail directory and did not find any file > > called internal. > > So maybe you need to look in the Mailman logs then, although the log > entry you showed, if I remember correctly, looked like local delivery to > me. > > -- > Simon White. Internet Consultant, Linux/Windows Server Administration. > email, dns and web servers; php javascript perl asp; MySQL MSSQL Access > Bridging the gap between management, HR and the tech team. >
From: Todd <[EMAIL PROTECTED]> Precedence: list MIME-Version: 1.0 Cc: To: mailman <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> In-Reply-To: <[EMAIL PROTECTED]> Date: Tue, 16 Dec 2003 12:17:58 -0500 Reply-To: Todd <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Subject: Re: [Mailman-Users] re-creating list archive - old List-Archive problem Message: 4
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Gour wrote: > If the listinfo is on http://lists.domain.com/mailman/listinfo/listname and > admin on http://lists.domain.com/mailman/admin/listname why is the > lists' archive on http://www.virtualdomain.com/mailman/pipermail/.. ?
Check what you have PUBLIC_ARCHIVE_URL and DEFAULT_URL_HOST set to in either Defaults.py or mm_cfg.py. Here's some text from Defaults.py regarding PUBLIC_ARCHIVE_URL:
# The url template for the public archives. This will be used in # several places, including the List-Archive: header, links to the # archive on the list's listinfo page, and on the list's admin # page. # # This should be a string with "%(listname)s" somewhere in it. # Mailman will interpolate the name of the list into this. You # can also include a "%(hostname)s" in the string, into which # Mailman will interpolate the host name (usually # DEFAULT_URL_HOST). PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/pipermail/%(listname)s'
- -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp ====================================================================== Freedom can be preserved only if it is treated as a supreme principle which must not be sacrificed for any particular advantage. -- F. A. Hayek
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.
iD8DBQE/3z5Fuv+09NZUB1oRApRqAKCAO4fS1DxTR/JvUF5UyyAyWHCSTQCgwehl urit/9DyQ952LIgnDnn0ztU= =H9A+ -----END PGP SIGNATURE-----
Content-Transfer-Encoding: 7bit From: Jon Carnes <[EMAIL PROTECTED]> Precedence: list MIME-Version: 1.0 Cc: [EMAIL PROTECTED] To: Melanie Dymond Harper <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> In-Reply-To: <[EMAIL PROTECTED]> Date: 16 Dec 2003 12:59:10 -0500 Reply-To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain Subject: Re: [Mailman-Users] SetGID Message: 5
You should be able to work around this particular problem by having them add the apache user (whatever "user" the server runs as) into the mailman group. That will allow Apache to run any of the apps and still have access to all the data.
Good luck - Jon Carnes
On Tue, 2003-12-16 at 11:31, Melanie Dymond Harper wrote:
> Hi folks,
>
> I'm in the process of trying to transfer some Mailman list across from one
> server to another; the current server is local, the new server is some
> space on a remotely-hosted server.
>
> I have everything working in terms of accepting mail and sending it out, but
> I'm having some trouble with the Web interface. Specifically, the web host
> concerned don't allow setuid/setgid scripts within cgi-bin directories.
>
> As far as I can tell, it is possible for the wrapper scripts (e.g. /mailman/
> listinfo/) to work without being setgid, but they don't seem to be picking
> up the right set of information -- such as the list of lists available on
> the machine.
>
> Is it likely that I will be able to work around this, or should I just give
> up and try to put the lists somewhere else?
>
> Thanks
>
> Mel
>
>
> ------------------------------------------------------
> Mailman-Users mailing list
> [EMAIL PROTECTED]
> 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/
>
> This message was sent to: [EMAIL PROTECTED]
> Unsubscribe or change your options at
> http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com
From: Gour <[EMAIL PROTECTED]> Precedence: list MIME-Version: 1.0 Cc: To: mailman <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> In-Reply-To: <[EMAIL PROTECTED]> Date: Tue, 16 Dec 2003 19:41:39 +0100 Reply-To: Gour <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=utf-8 Subject: Re: [Mailman-Users] re-creating list archive - old List-Archive problem Message: 6
Todd ([EMAIL PROTECTED]) wrote:
> Check what you have PUBLIC_ARCHIVE_URL and DEFAULT_URL_HOST set to in > either Defaults.py or mm_cfg.py. Here's some text from Defaults.py > regarding PUBLIC_ARCHIVE_URL:
They're set (in mm_cfg.py) and the mystery is that for some lists everything is
OK, while others have wrong url.
Any other idea?
Sincerely, Gour
-- Gour [EMAIL PROTECTED] Registered Linux User #278493
From: Todd <[EMAIL PROTECTED]> Precedence: list MIME-Version: 1.0 Cc: To: mailman <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> In-Reply-To: <[EMAIL PROTECTED]> Date: Tue, 16 Dec 2003 13:52:01 -0500 Reply-To: Todd <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Subject: Re: [Mailman-Users] re-creating list archive - old List-Archive problem Message: 7
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Gour wrote:
> Todd ([EMAIL PROTECTED]) wrote:
>
>> Check what you have PUBLIC_ARCHIVE_URL and DEFAULT_URL_HOST set to in
>> either Defaults.py or mm_cfg.py. Here's some text from Defaults.py
>> regarding PUBLIC_ARCHIVE_URL:
>
> They're set (in mm_cfg.py) and the mystery is that for some lists everything is
> OK, while others have wrong url.
Well, just so we'll all know, what are they set to? Was mailman restarted after they were last changed, before you ran the fix_url.py script? Are the lists that work ones which were created after you moved servers? Any other clues that might help differentiate the working lists from the nonworking lists?
- -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp ====================================================================== Learn from the mistakes of others--you can never live long enough to make them all yourself. -- John Luther
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.
iD8DBQE/31RRuv+09NZUB1oRAt0nAJwPmpdhyBcfN/5IWW1Q3eprIJeIWACg/BFh 4FK+K0yu8QlX3fZd8tecdWA= =ipeB -----END PGP SIGNATURE-----
From: Gour <[EMAIL PROTECTED]> Precedence: list MIME-Version: 1.0 Cc: To: mailman <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> In-Reply-To: <[EMAIL PROTECTED]> Date: Tue, 16 Dec 2003 20:10:32 +0100 Reply-To: Gour <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=utf-8 Subject: Re: [Mailman-Users] re-creating list archive - old List-Archive problem Message: 8
Todd ([EMAIL PROTECTED]) wrote:
> Well, just so we'll all know, what are they set to?
PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s' DEFAULT_URL_HOST = 'lists.vediclists.net' DEFAULT_URL_PATTERN = 'https://%s/mailman/'
> Was mailman restarted after they were last changed, before you ran the > fix_url.py script?
Yes, it was restarted severla times.
> Are the lists that work ones which were created after you > moved servers? Any other clues that might help differentiate the > working lists from the nonworking lists? >
Some of the old lists works and the new ones also, while some of the old does not work and I do not have clue why is it so.
One possible clue: it looks like that only those lists that were under
www.virtuladomain.com and now they are moved to lists.domain.com does not
work, while those that stayed under same domain (whether www.virtualdomain.com
or lists.domain.com) are OK.
-- Gour [EMAIL PROTECTED] Registered Linux User #278493
From: Todd <[EMAIL PROTECTED]> Precedence: list MIME-Version: 1.0 Cc: To: mailman <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> In-Reply-To: <[EMAIL PROTECTED]> Date: Tue, 16 Dec 2003 14:41:07 -0500 Reply-To: Todd <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Subject: Re: [Mailman-Users] re-creating list archive - old List-Archive problem Message: 9
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Gour wrote: > PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s' > DEFAULT_URL_HOST = 'lists.vediclists.net' > DEFAULT_URL_PATTERN = 'https://%s/mailman/'
Here's a WAG, does it matter that PUBLIC_ARCHIVE_URL is set before DEFAULT_URL_HOST? I don't know how Python handles that. If order counts, then PUBLIC_ARCHIVE_URL would be picking up the hostname from what's defined in Defaults.py. If order is irrelevant, then so is this whole paragraph.
> Some of the old lists works and the new ones also, while some of the > old does not work and I do not have clue why is it so. > > One possible clue: it looks like that only those lists that were > under www.virtuladomain.com and now they are moved to > lists.domain.com does not work, while those that stayed under same > domain (whether www.virtualdomain.com or lists.domain.com) are OK.
You might try using dumpdb on a working list and a nonworking list to see what differences there are. I would assume that the nonworking lists will have the old virtual domain in them somewhere.
- -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp ====================================================================== An idea is not responsible for the people who believe in it. -- Anonymous
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.
iD8DBQE/31/Suv+09NZUB1oRAiEQAKCWaXUnG8O26rcahT+RS5679H3r6gCgy8nR f8FMXTyGUTim9NYmPnTPjq8= =J7CG -----END PGP SIGNATURE-----
From: Gour <[EMAIL PROTECTED]> Precedence: list MIME-Version: 1.0 Cc: To: mailman <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> In-Reply-To: <[EMAIL PROTECTED]> Date: Tue, 16 Dec 2003 21:12:09 +0100 Reply-To: Gour <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=utf-8 Subject: Re: [Mailman-Users] re-creating list archive - old List-Archive problem Message: 10
Todd ([EMAIL PROTECTED]) wrote:
> Here's a WAG, does it matter that PUBLIC_ARCHIVE_URL is set before > DEFAULT_URL_HOST? I don't know how Python handles that. If order > counts, then PUBLIC_ARCHIVE_URL would be picking up the hostname from > what's defined in Defaults.py. If order is irrelevant, then so is > this whole paragraph.
Actually, I wrote in such an order, actually it's:
DEFAULT_EMAIL_HOST = 'lists.vediclists.net' DEFAULT_URL_HOST = 'lists.vediclists.net'
# Using secure http (SSL)
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
# Public archive URL
PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'
so it does not apply :-(
> You might try using dumpdb on a working list and a nonworking list to > see what differences there are. I would assume that the nonworking > lists will have the old virtual domain in them somewhere.
I'll do it, and I'm sure that nonworking lists have the old values, but I'm just wondering how to change them :-)
Sincerely, Gour
-- Gour [EMAIL PROTECTED] Registered Linux User #278493
------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] 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/
------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] 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/
This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
