Todd,
That update took case of it. Thanks.
-- Rob
On 02/05/2008 05:56 PM, Todd Zullinger wrote:
> Rob Tanner wrote:
>
>> I think the bug URL you gave me is a wrong URL. Bug 132495 is a
>> Japanese encoding bug and its status is closed (which I presume
>> means fixed). That doesn't sound li
Rob Tanner writes:
> File "bin/check_perms", line 216, in checkarchives
> print _("""\
> NameError: global name '_' is not defined
This is the conventional equivalent to GNU gettext used by most Python
programs. Find the definition of '_' which will either look like
def _(x):
# cod
Robert Everson wrote:
>I'm running a mail list that is used for emergency notification, and
>many people subscribe using their cellphones. Because of this,
>sending a confirmation email isn't really the easiest way for the
>users to subscribe. Also, I don't really think that approving
>e
I'm running a mail list that is used for emergency notification, and
many people subscribe using their cellphones. Because of this,
sending a confirmation email isn't really the easiest way for the
users to subscribe. Also, I don't really think that approving
everyone would be feasible fo
Rob Tanner wrote:
> I think the bug URL you gave me is a wrong URL. Bug 132495 is a
> Japanese encoding bug and its status is closed (which I presume
> means fixed). That doesn't sound like the problem I'm seeing.
The bug summary may not sound like what you're seeing, but the patch
that was appl
On 2/5/08, Thomas J Casey wrote:
> In an email from Brad Knowles, he stated: If they are not subscribers, "then
> they need to be on the whitelist." But I cannot find a whitelist anywhere.
Go to the web mail admin interface for your list. Go to the "Privacy
options..." sub-page, then to "Sen
On 2/5/08, ippaso wrote:
> Here is the log from the smtp server for that time, in case it can help:
> (qmail is patched to check the 'rcpt to' against a valid addresses list
> before accepting a message and to reject during the smtp conversation
> the mails which achieve a very high spamassass
Rob Tanner wrote:
>
>I think the bug URL you gave me is a wrong URL. Bug 132495 is a
>Japanese encoding bug and its status is closed (which I presume means
>fixed). That doesn't sound like the problem I'm seeing.
Read further down in the comment thread. It talks about the _() i18n
function be
Todd,
I think the bug URL you gave me is a wrong URL. Bug 132495 is a
Japanese encoding bug and its status is closed (which I presume means
fixed). That doesn't sound like the problem I'm seeing.
In answer to your questions, the Fedora release is Fedora release 7
(Moonshine) and the mailman
Rob Tanner wrote:
> Running this as root so that it can fix any perm problems, but I'm
> getting what I assume to be python errors:
>
> [EMAIL PROTECTED] mailman]# bin/check_perms -f
> Traceback (most recent call last):
> File "bin/check_perms", line 382, in
> checkarchives()
> File "bin/check
Hi,
Running this as root so that it can fix any perm problems, but I'm
getting what I assume to be python errors:
[EMAIL PROTECTED] mailman]# bin/check_perms -f
Traceback (most recent call last):
File "bin/check_perms", line 382, in
checkarchives()
File "bin/check_perms", line 216, in c
That was very very helpful. Thanks!
-- Rob
Mark Sapiro said the following on 02/05/2008 01:22 PM:
> Rob Tanner wrote:
>
>> I am retiring a server running Mailman 2.1.5 and need to port
>> everything to a server running 2.1.7 (Fedora Core distribution). Can I
>> take the lists directory a
Victor M.J. Ryden wrote:
>Is there a way to turn off the monthly Memberships Reminder EMail. I have an
>announcements list and don't want any additional EMail. I have searched on
>Google and the Archives, for this but all I see is how to turn off the
>Password Reminder, which is already off.
Is there a way to turn off the monthly Memberships Reminder EMail. I have an
announcements list and don't want any additional EMail. I have searched on
Google and the Archives, for this but all I see is how to turn off the Password
Reminder, which is already off.
Thanks for your help.
Rob Tanner wrote:
>
>I am retiring a server running Mailman 2.1.5 and need to port
>everything to a server running 2.1.7 (Fedora Core distribution). Can I
>take the lists directory and simply copy it from one server to another
>(i.e., is the format of the various files the same)? Is there any
ippaso wrote:
>SP ha scritto:
>
>> Ok, thanks: I will patch mailman immediately and post here the 'error'
>> log as soon as the error appears again.
>
>Here the relevant part of mailman 'error' log (the time of the last sent
>message is 22.29 and the time of the first message which gets stuck in
>
ippaso wrote:
>
>After a look at the log of the smtp server (see below), I can guess that
>the reason might be an high load on the system due to intense
>spamassassin activity: at the time of the error there were 20
>connections (the maximum number of allowable concurrent connections) to
>the serve
As some of the mailing lists I administer experience a steady flow of
spam, I was looking for a way to add REL="nofollow" attribute to
Mailman's messages.
As I didn't find a way to do it in Mailman, and I don't know enough of
Python, I decided to write a simple Perl script which does it.
This
Hi,
I am retiring a server running Mailman 2.1.5 and need to port
everything to a server running 2.1.7 (Fedora Core distribution). Can I
take the lists directory and simply copy it from one server to another
(i.e., is the format of the various files the same)? Is there anything
else that ne
I updated the /etc/logrotate.d/mailman file as you suggested.
Thanks! Greg
-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 05, 2008 9:33 AM
To: Greg Sims; mailman-users@python.org
Subject: Re: [Mailman-Users] Scripts Associated with Log File Rota
Greg Sims wrote:
>
>I have a couple of question about doing what I need to without breaking
>anything:
>
>
>
>(1) The time stamps of the log files on my system are not all the same.
>The time stamp of /var/log/mailman/subscribe.1 and /var/log/mailman/bounce.1
>are not even on the same day. This
Hi There,
I have been studying the mailman code this morning to find a way to do some
processing when the mailman logs are rotated. My goal is to process the
data in /var/log/mailman/subscribe.1 and /var/log/mailman/bounce.1 just
after they are rotated. I reviewed the file /etc/logrotate.d/ma
Thomas J Casey wrote:
>
>For each of my lists, I need for certain individuals to be able to be able
>to submit to the mailing list but only those that I define. In the Privacy
>Section/Sender Filters/All mailing list administration do I set the By
>default, should new list member postings be moder
I'm not very technical so I need some more help please. Step me through in
terms that are for dummies like me. I'll try to explain:
I have 20+ Mailing Lists setup with each containing a unique set of
individuals who are to receive email sent to the list. Some indididuals
need the ability to
Marvin Raab wrote:
>Thanks for the response.
>
>
>Yup, it does.
>
>So, I should simply comment out all lines in the crontab.in file?
>
>
>
>
>
>I said:
>>To resolve the problem, I had root use: crontab -u mailman -e and
>>manually edited the file; removing the mailman field
>>
>>In Fedora 8 us
SP ha scritto:
> Ok, thanks: I will patch mailman immediately and post here the 'error'
> log as soon as the error appears again.
Here the relevant part of mailman 'error' log (the time of the last sent
message is 22.29 and the time of the first message which gets stuck in
qfiles/out is 22.30):
For some reason my previous posts never reached the mailing list, so I
repost it here, sorry for the delay:
Mark Sapiro ha scritto:
>> Jan 27 13:34:57 2008 (2154) <[EMAIL PROTECTED]> smtp
>> to test for 1 recips, completed in 55.860 seconds
>> Jan 27 13:37:21 2008 (2154) <[EMAIL PROTECTED]> smtp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 5, 2008, at 6:23 AM, Lachlan Michael wrote:
> Now to just work out the root cause of the memory errors ...
It's important to remember that Python's email parsing code sucks the
entire message text into memory and keeps large attachments in m
>> Prior to Mailman 2.1.9, the error would have occurred once and the
>> message would have been lost. Beginning in 2.1.9, a queue file
>> backup/recovery mechanism was implemented which allowed messages that
>> were in process when a crash occurred to be recovered, but the problem
>> here is that
29 matches
Mail list logo
