This with 2.2.23 on some Linux server: the subject says it all. I know y'all
will
find it odd but when I get an unsubscribe request I sometimes [often? :o)] deal
with it directly and don't bother dealing with the moderator request. I had
hoped they would go away by themselves. I realize
Hello,
I've been working on migrating an old Mailman 2.1 server over to a new server.
I'm currently using Mailman 2.1.29 for the new server. The new server is a
CentOS 8 server. The Mailman package that is being used is
mailman-3:2.1.29-4.module_el8.0.0+34+0459d3d0.x86_64.
When I try to visit
On 10/5/20 1:15 PM, Thomas Gramstad wrote:
> This is the error message I get when I try to update a picture URL with
> its current URL, in the file
> https://mailman.gramstad.no/mailman/edithtml/enag-mausoleum/listinfo.html :
>
> Bug in Mailman version 2.1.29
>
> We're sorry, we hit a bug!
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Argh! This was intended for just Mark, not the whole list. Sigh.
- -Jim P.
On Thu, 2018-05-24 at 11:40 -0400, Jim Popovitch via Mailman-Users
wrote:
> Hello!
>
> Given a bounce msg with a subpart of:
>
>
> message/delivery-status:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello!
Given a bounce msg with a subpart of:
message/delivery-status:
Final-Recipient: rfc822;u...@domain.tld
Action: failed
Status: 5.1.10
Diagnostic-Code: smtp;550 5.1.10 RESOLVER.ADR.RecipientNotFound;
and the code
Laura Creighton wrote:
Recently Tin Tvrtković tried to subscribe to the pypy-dev mailing list.
He got the Bug in Mailman version 2.1.15 We're sorry, we hit a bug! message.
When he tried to reply to the confirmation message, he got it again.
It looks like it could possibly be this 10 year
Recently Tin TvrtkoviÄ tried to subscribe to the pypy-dev mailing list.
He got the Bug in Mailman version 2.1.15 We're sorry, we hit a bug! message.
When he tried to reply to the confirmation message, he got it again.
It looks like it could possibly be this 10 year old bug that Mark was
unable
On 02/06/2015 09:34 AM, Laura Creighton wrote:
Recently Tin Tvrtković tried to subscribe to the pypy-dev mailing list.
He got the Bug in Mailman version 2.1.15 We're sorry, we hit a bug! message.
When he tried to reply to the confirmation message, he got it again.
It looks like it could
Ok we are running version 2.1.5 on an old White Box server and are
encountering this bug which is preventing us from accessing the
membership management pages for some (but not all) of our mailing
lists.
if bucket not in digits + '_' + lowercase:
TypeError: 'in string' requires character as
On 02/04/2015 09:10 AM, James Sceets wrote:
Ok we are running version 2.1.5 on an old White Box server and are
encountering this bug which is preventing us from accessing the
membership management pages for some (but not all) of our mailing
lists.
if bucket not in digits + '_' + lowercase:
Hi,
Reserecting an old thread.
On Sat, 6 Mar 2010, Mark Sapiro wrote:
Geoff Shang wrote:
I've noticed that if I go to pending Moderator requests and approve a
message from a particular user, if I leave the resulting page open which
says Click here to reload this page and another message
Geoff Shang wrote:
On Sat, 6 Mar 2010, Mark Sapiro wrote:
Geoff Shang wrote:
I've noticed that if I go to pending Moderator requests and approve a
message from a particular user, if I leave the resulting page open which
says Click here to reload this page and another message from that user
Hi,
I've noticed an odd thing but am not sure if it's Mailman (2.1.11) or my
browser (Lynx 2.8.7dev.9) which is at fault.
I've noticed that if I go to pending Moderator requests and approve a
message from a particular user, if I leave the resulting page open which
says Click here to reload
Geoff Shang wrote:
I've noticed that if I go to pending Moderator requests and approve a
message from a particular user, if I leave the resulting page open which
says Click here to reload this page and another message from that user
comes through which requires approval, if I click to reload
Mark Sapiro wrote:
The underlying problem is that the data posted from the summary page
says apply the selected action to all messages from this user rather
than apply the selected action to all messages from this user that
were displayed on the page.
I have reported this at
Barry Finkel wrote:
I ran a test with a test list on my test virtual machine, and this is
what is happening. The line in the -f file for sync_members
bsf-cr...@example.com (New 1 (zzz))
is causing all of the succeeding lines in that file to be treated as
part of the parenthesized
I wrote:
I think I may have uncovered a bug in Mailman 2.1.13. I have not
completed my research. I have a script that refreshes the subscriber
list via:
/usr/lib/mailman/bin/sync_members -w=no -g=no -d=no -a=no \
-f /e tc/mailman/generated_lists/LISTNAME LISTNAME
where
Barry Finkel wrote:
I ran a test with a test list on my test virtual machine, and this is
what is happening. The line in the -f file for sync_members
bsf-cr...@example.com (New 1 (zzz))
is causing all of the succeeding lines in that file to be treated as
part of the parenthesized
Barry Finkel wrote:
I ran a test with a test list on my test virtual machine, and this is
what is happening. The line in the -f file for sync_members
bsf-cr...@example.com (New 1 (zzz))
is causing all of the succeeding lines in that file to be treated as
part of the parenthesized
I think I may have uncovered a bug in Mailman 2.1.13. I have not
completed my research. I have a script that refreshes the subscriber
list via:
/usr/lib/mailman/bin/sync_members -w=no -g=no -d=no -a=no \
-f /etc/mailman/generated_lists/LISTNAME LISTNAME
where
Barry Finkel wrote:
I think I may have uncovered a bug in Mailman 2.1.13. I have not
completed my research. I have a script that refreshes the subscriber
list via:
/usr/lib/mailman/bin/sync_members -w=no -g=no -d=no -a=no \
-f /etc/mailman/generated_lists/LISTNAME LISTNAME
where
Mark Sapiro wrote:
Tomasz Chmielewski wrote:
It exited with Bug in Mailman version 2.1.12.
Webserver nor Mailman logs didn't give me a clue.
Mailman's 'error' log should have a a complete traceback and other
information about the error.
Here is a sample log - it doesn't give me any
Tomasz Chmielewski wrote:
Mark Sapiro wrote:
Tomasz Chmielewski wrote:
It exited with Bug in Mailman version 2.1.12.
Webserver nor Mailman logs didn't give me a clue.
Mailman's 'error' log should have a a complete traceback and other
information about the error.
Here is a sample log -
Today, I had an interesting bug or a feature in Mailman, which took me
some time to fix.
I have a Mailman 2.1.12 which was running fine for months on a virtual host.
I did some low level kernel experiments, and the virtual guest started
to malfunction.
So, back to the original state -
Tomasz Chmielewski wrote:
It exited with Bug in Mailman version 2.1.12.
Webserver nor Mailman logs didn't give me a clue.
Mailman's 'error' log should have a a complete traceback and other
information about the error.
I browsed Mailman installation files; lists/*/config.pck suspiciously
Hello there list,
I am a new person using mailman and it looks like a bug is prevalent in
2.1.9. Here is what I got off the web page:
Bug in Mailman version 2.1.9
Bug in Mailman version 2.1.9
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing
* Scott Berry [EMAIL PROTECTED]:
Hello there list,
I am a new person using mailman and it looks like a bug is prevalent in
2.1.9. Here is what I got off the web page:
Bug in Mailman version 2.1.9
Bug in Mailman version 2.1.9
We're sorry, we hit a bug!
Please inform the
Scott Berry wrote:
Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited, but
the webmaster
can find this information in the Mailman error logs.
I am using Fedora and could not find any erros.
Try
Bob Tschannen-Moran wrote:
When I create a header_filter_rule, of any sort, I no longer receive the
automatic coded confirmation email from the Mailman list. The post is held
by the list, I am notified of the post (as the sender), I can Accept the
post by Tending to Pending Moderator Requests and
I use my list as a distribution-only list, holding all posts from me, the
Administrator. My posts are released only after I Accept them, either by
Tending to Pending Moderator Requests or by returning the coded
confirmation email (with Approved: password in the first line). I use the
latter system
Please copy replies to the list.
Bob Tschannen-Moran Wrote:
Well, now that you put it THAT way, I have done more experimenting. When I
put in either of the following two header_filter_rules (from Spammers):
Received: from [83.93.206.242]
helo=karin
I do receive the admin notices, as one would
-users@python.org
Subject: Re: [Mailman-Users] header_filter_rules bug?
Bob Tschannen-Moran wrote:
When I create a header_filter_rule, of any sort, I no longer receive
the automatic coded confirmation email from the Mailman list. The post
is held by the list, I am notified of the post
]
Sent: Sunday, October 22, 2006 9:39 PM
To: Bob Tschannen-Moran
Cc: Mailman Users
Subject: RE: [Mailman-Users] header_filter_rules bug?
Please copy replies to the list.
Bob Tschannen-Moran Wrote:
Well, now that you put it THAT way, I have done more experimenting.
When I put in either
Bob Tschannen-Moran wrote:
1. The action for that rule is Discard.
2. The post from me is held by the list until I Accept it, then it is sent
on.
3. As the poster, I immediately receive the Your message to LIST awaits
moderator approval notice.
4. The post from me has the following header line:
apache conf. file which
concern the mailman integration.
Regards,
Leon Kolchinsky
От: [EMAIL PROTECTED] от имени plaza c
Отправлено: Вт, 8/23/2005 2:43
Кому: mailman-users@python.org
Тема: [Mailman-Users] Bug in Mailman
Hi,
Im new to mailman.I've
Elissa wrote:
I'm hoping someone can help me fix this. I installed mailman, and
couldn't figure out why the web interface didn't work. It seems I CAN
access any of the pages, but the admin ones. I get a lovely message in
the browser:
Bug in Mailman version 2.1.6rc3
We're sorry, we hit a
-
--
Message: 3
Date: Tue, 17 May 2005 14:46:36 +0900
From: Jim Tittsler [EMAIL PROTECTED]
Subject: Re: [Mailman-Users] Mailman Bug?/no Admin level web access
To: [EMAIL PROTECTED]
Cc: Mailman-users list mailman-users@python.org
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain
On Tue, 2005-05-17 at 13:02 -0400, [EMAIL PROTECTED] wrote:
May 10th was the day I put in the new hard drive after the old one
died. So basically I did a clean install. I had set up the domain/host
stuff on the old drive so all I did was reinstall. I only have one
domain/host name, and
invites, etc using mailman so I know it's
working as expected.
Elissa
-Original Message-
From: John Dennis [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: mailman-users@python.org; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tue, 17 May 2005 13:23:47 -0400
Subject: Re: [Mailman-Users] Mailman Bug
Elissa wrote:
I trashed the old mailman error log. I now have a new 0k
file called error. I can send invites, etc using mailman so I know it's
working as expected.
How did this file get created? Did Mailman create it? If so, then the
question is why can Mailman create this file but not be
On Tue, 2005-05-17 at 21:33 -0400, [EMAIL PROTECTED] wrote:
Mailman created a new file, but the others show as plain text and the
new one as octet stream.
I'm afraid I don't understand. What others and what do you mean the
new log file is octet stream?
Right now I'm at accept all on
I'm hoping someone can help me fix this. I installed mailman, and
couldn't figure out why the web interface didn't work. It seems I CAN
access any of the pages, but the admin ones. I get a lovely message in
the browser:
Bug in Mailman version 2.1.6rc3
We're sorry, we hit a bug!
Please inform
On Mon, May 16, 2005 at 02:14:02PM -0400, [EMAIL PROTECTED] wrote:
I'm hoping someone can help me fix this. I installed mailman, and
couldn't figure out why the web interface didn't work. It seems I CAN
access any of the pages, but the admin ones. I get a lovely message in
the browser:
Bug
Elissa wrote:
I'm hoping someone can help me fix this. I installed mailman, and
couldn't figure out why the web interface didn't work. It seems I CAN
access any of the pages, but the admin ones. I get a lovely message in
the browser:
Bug in Mailman version 2.1.6rc3
We're sorry, we hit a bug!
Elissa wrote:
snip
I'm using my aol address to make sure I get my mail.
Well, that doesn't work. My reply to you was bounced by AOL because
* 554 HVU:B1
http://postmaster.info.aol.com/errors/554hvub1.html
EXPLANATION:
There is at least one URL in your email that is
In a message dated 5/16/2005 6:37:20 PM Eastern Daylight Time,
[EMAIL PROTECTED] writes:
Well, that doesn't work. My reply to you was bounced by AOL because
* 554 HVU:B1
http://postmaster.info.aol.com/errors/554hvub1.html
This may be true, but the server mail doesn't get checked
Thanks Mark,
That fixed it, at least temporarily. I did have to change the name with
mv before I removed it.
Mark Ballard
Site Technology Specialist
El Molino High School
http://www.elmolino.org
On Feb 27, 2005, at 10:28 AM, Mark Sapiro wrote:
Mark Ballard wrote:
Mailman has been working fine
Mailman has been working fine for a couple of week now and it just
stopped with a bug.
Below is what it tells me when I go to admindb on any list.
any ideas???
Bug in Mailman version 2.1.2
We're sorry, we hit a bug!
If you would like to help us identify the problem, please email a copy
of this
Mark Ballard wrote:
Mailman has been working fine for a couple of week now and it just
stopped with a bug.
Below is what it tells me when I go to admindb on any list.
any ideas???
Bug in Mailman version 2.1.2
snip
File /usr/share/mailman/Mailman/MailList.py, line 487, in __save
Mark Ballard wrote:
Mailman has been working fine for a couple of week now and it just
stopped with a bug.
Below is what it tells me when I go to admindb on any list.
any ideas???
Bug in Mailman version 2.1.2
snip
File /usr/share/mailman/Mailman/MailList.py, line 487, in __save
Upon receiving a message like bellow (and similar messages) that are
virus social engineering without the viral payload, mailman,
specifically qrunner, chokes for good, and does not deliver any message
that follows, on any list. There's the relevant excerpt from error log
bellow. I still have
Hi,
Heiko Gerstung wrote:
b) why the owner-address is used no matter if there is an umbrella list
or not? Either the online description for the owner-suffix is wrong or
the usage of this field is wrong in that message.
-owner address is meant to the person who owns and manages the list.
--
At 11:37 AM +0200 2004-06-17, Heiko Gerstung wrote:
A last question: Is there a bug tracking system available for mailman?
Something where I can submit my bugs or feature requests?
See the Mailman SourceForge page at
http://sourceforge.net/tracker/?group_id=103atid=100103.
--
Brad Knowles,
Hello List!
In the LC_MESSAGES for mailman there is one for the reject message that
is sent when a non-member tries to post to a list and the posting is
rejected automatically. In this error message the mail address of the
list-owner (xxx-owner) is mentioned. But, regarding this owner-address,
Hi all,
We recently moved a machine (physically) and for some reason the mailman
installation quit working.
I get the following error when viewing the main mailman page. Any help
would be greatly appreciated.
Thanks,
Ethan
--
Traceback (most recent call last):
File
ii mailman2.1.4-1Powerful, web-based mailing list manager
ii python2.3 2.3.3-5An interactive high-level object-oriented la
Hi there,
I would like to report a bug in mailman 2.1.4, which only surfaces,
when config_list is used to import a configuration file that
In many parts of the web interface I am getting the same mailman bug:
It started when confirming a subscription through the online interface:
File /usr/local/mailman/Mailman/OldStyleMemberships.py, line 312, in
setMemberOption
self.__mlist.user_options[memberkey] |= flag
TypeError:
We recently upgraded to Mailman 2.1.3.
On one list (an unmoderated list), I get the following message:
Your membership in the mailing list Delphi-Talk has been disabled due
to excessive bounces The last bounce received from you was dated
25-Dec-2003. You will not get any more messages from this
We recently upgraded to Mailman 2.1.3.
On one list (an unmoderated list), I get the following message:
Your membership in the mailing list Delphi-Talk has been disabled due
to excessive bounces The last bounce received from you was dated
25-Dec-2003. You will not get any more messages from this
Hi,
Trying to figure this one out.
Twice now in the past month, a mailing list has
died here. You cannot login to the administrative
interface and posts go into into a logjam.
From the logs I see:
[EMAIL PROTECTED] mailman]# tail error
NotLockedError:
Aug 02 16:38:52 2003 qrunner(28147):
Hi,
Althought, the problem is regarding a page that generating on Russian - you can see it
youself, that bottom part is not translated.
My users found a problem - they could not get to options page if they view listinfo
page on Russian. I investigated that russian template starts wrong form. I
I wrote earlier about some suggested improvements with the confirmation
by mail function.
Here's another thing - if you insert an 'Approved: ' string that's
incorrect, the message is deleted (in a way that's unrecoverable,
AFAICT). My suggestion is that you get an error message back instead,
Folks,
Everytime I try to create a list I get the following error.
However, the list is actually created? I'm running mailman 2.1,
postfix 1.11 and Apache. Any help appreciated.
Mike
Bug in Mailman version 2.1.1
We're sorry, we hit a bug!
If you would like to help us identify the problem,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
mcobb wrote:
Everytime I try to create a list I get the following error.
However, the list is actually created? I'm running mailman 2.1,
postfix 1.11 and Apache. Any help appreciated.
[...]
RuntimeError: command failed: /usr/sbin/postalias
On 14 January 2003, I received the following message:
Your membership in the mailing list Mailman-Users has been disabled due to
excessive bounces The last bounce received from you was dated 14-Jan-2003.
On 13 February 2003, I received the following message: Your membership in
the mailing list
On Tue, 4 Feb 2003, Tokio Kikuchi wrote:
I think this bug is fixed. Please get a patch from
http://sourceforge.net/tracker/index.php?func=detailaid=670167group_id=103atid=300103
The patch seems to work. Thanks!
-David
+--+
David Eisner
Hy,
I'm using mailman 2.0.13 on a RedHat 8.0 linux box. Today I've discovered a
bug in authentification on administrative interface. For instance, suppose that
I have for a list, the password 1234, and when mailman is asking me for a
password, I give him 123456789 he shouldn't let me go
I checked out the latest sources from CVS this afternoon and
discovered the following bug in Scrubber.py ( I think ).
I. PROBLEM
If I send a message with an attachment to a list from Outlook (XP),
the pipermail archived version of the message is missing the
content of the message, although the
Hi,
I think this bug is fixed. Please get a patch from
http://sourceforge.net/tracker/index.php?func=detailaid=670167group_id=103atid=300103
Cheers,
David Eisner wrote:
I checked out the latest sources from CVS this afternoon and
discovered the following bug in Scrubber.py ( I think ).
I.
30-Jan-03 at 18:23, Will Yardley ([EMAIL PROTECTED]) wrote :
On Thu, Jan 30, 2003 at 09:14:05AM +, Simon White wrote:
29-Jan-03 at 13:37, Will Yardley ([EMAIL PROTECTED]) wrote :
Is there any way to fix this in the future? With some browsers, it's not
simple to remove an individual
On Thu, Jan 30, 2003 at 09:14:05AM +, Simon White wrote:
29-Jan-03 at 13:37, Will Yardley ([EMAIL PROTECTED]) wrote :
If you have an old cookie from Mailman 2.0.x, you'll have to re-login
for every page until you manually clear the cookie from your browser
(after upgrading to 2.1).
JAE == Jeff A Earickson [EMAIL PROTECTED] writes:
JAE In my study of my mailing lists today (both new in MM 2.1,
JAE and upgraded from 2.0.13), I made the sad discovery that
JAE generic_nonmember_action = 0
JAE for **all** of my lists. The bend over and take spam
JAE
On Sat, 18 Jan 2003 15:43:06 -0500
Barry A Warsaw [EMAIL PROTECTED] wrote:
I got working a prototype integration of Mailman and spambayes, and
I'll probably be checking this into cvs when I get back wink. I'd
label it as an interesting experiment, but whether it'll be useful
remains to be
Y'all,
In my study of my mailing lists today (both new in MM 2.1,
and upgraded from 2.0.13), I made the sad discovery that
generic_nonmember_action = 0
for **all** of my lists. The bend over and take spam
setting. I noticed that DEFAULT_GENERIC_NONMEMBER_ACTION is
set to one in
Why should the list administrator be bothered with having to
tend admin requests from spammers and other idiots?
Jeff,
I assume this is because people are generally more concerned about false
positives in spam-checking than they are with having to glance at a few
admin requests. I suppose
Is it linked to my problem with installing email-2.0.4? In any case the
iso-encoding/decoding of subjects seems to be failing, as this header shows:
Subject: [Spip] des sources =?iso-8859-1?Q?=E0_syndiquer?=^M
=?iso-8859-1?B?Li4u?=
-- Fil
My hosting company is running version 2.0.8. I've encountered a problem
where email sent to the administrator for the list (i.e., me) goes into a
loop that finally gets detected and killed but not before I get flooded with
copies. This only happens with the admin account, not to email sent to the
Hi,
The webpage at http://www.gnu.org/software/mailman/MM21/todo.html
is buggy; it repeats the wishlist items over and over again under each
topic = the list gets very long towards the end...
P.S. Thanks for the Mailman, it's great!
Juha 'Mox' Huuhtanen -- [email protected]
Hi all,
When I try to access my list info page, or any other list page or admin
page, I get the following error:
Bug in Mailman version 2.0
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been
Stephen McKeown wrote:
This just started. I buy my hosting from a company, and they have great
support, but I haven't heard back yet on this one so I thought it might help
if I could give them some pointers on what to do. Or if you could suggest a
solution I could do myself.
There's
Pipermail 0.05 (Mailman edition) does not seem to decode
non-ascii MIME subject correctly under some conditions, even the
Prefix for subject line of list postings has been emptied.
Attached ma1 files are captured before ma2 files. The messages
sent by Reed Lai are subjected with iso-8859-1
David Moruzzi wrote:
admin(5625): IOError: [Errno 2] No such file or directory:
'/var/lib/mailman/templates/admlogin.txt'
This is the actual error. It's not finding the templates. How, or where
did you install MM?
--
W | I haven't lost my mind; it's backed up on tape somewhere.
I use the apt-get install---command in Debian to install the mailman.
That is the correct path /var/lib/mailman/templates
These is no admlogin.txtIs Mailman meant to create this file or am I?
-Original Message-
From: Ashley M. Kirchner [mailto:[EMAIL PROTECTED]]
Sent: Tuesday,
David Moruzzi wrote:
I use the apt-get install---command in Debian to install the mailman.
That is the correct path /var/lib/mailman/templates
These is no admlogin.txtIs Mailman meant to create this file or am I?
Mailman installs several files in the templates directory, including
Hello,
I have two problems: I am newbie in mailman anf my english is very bad
(sorry).
I'd installed python-1.5.2-13 and mailman 2.0.5. I have zmailer and
apache 1.3.14. I'd installed mailman while I read INSTALL.
My problem is: how I begin it?
I'd created entries in aliases with
Quoting Rocio Alfonso Pita, [EMAIL PROTECTED]:
I'd installed python-1.5.2-13 and mailman 2.0.5. I have zmailer and
apache 1.3.14. I'd installed mailman while I read INSTALL.
My problem is: how I begin it?
I'd created entries in aliases with newlist and I write in netscape:
Try:
chmod o+rw $prefix/mailman/logs/error
Message from Tu 10 Jul 2001 13:21:
Quoting Rocio Alfonso Pita, [EMAIL PROTECTED]:
I'd installed python-1.5.2-13 and mailman 2.0.5. I have zmailer and
apache 1.3.14. I'd installed mailman while I read INSTALL.
My problem is: how I begin it?
Hello again,
Geert Altena wrote:
Quoting Rocio Alfonso Pita, [EMAIL PROTECTED]:
I'd installed python-1.5.2-13 and mailman 2.0.5. I have zmailer and
apache 1.3.14. I'd installed mailman while I read INSTALL.
My problem is: how I begin it?
I'd created entries in aliases with
I'd found my problem. I had user mailman and group mailman in my
directories, so apache has not permissions. I change it by user nobody
and group nobody and it works fine.
Thanks.
rozio
Geert Altena wrote:
Quoting Rocio Alfonso Pita, [EMAIL PROTECTED]:
I'd installed python-1.5.2-13
D == David [EMAIL PROTECTED] writes:
D The problem is that I had 24 messages in this digest, but the
D subject tells me it's
D 30. If you take a closer look, you will find 30 lines under
D 'Today's Topics:' Is it possible to fix this bug in the 2.1
D version?
Known bug in
Dear gurus,
Take a look at this DIGEST snipped from my list.
I'm running a swedish list and get problems with 8-bit chars in the
subject. No big deal, I can live with that. The problem is that I had 24
messages in this digest, but the subject tells me it's 30. If you take a
closer look, you
Hi:
Upgrading mailman ver 2.0beta6 to mailman 2.0.1 did the trick. Thanks for
your prompt help.
- Francis
PS
--
We are running mailman on a Linux system. Some members send MS Word files
as postings. How do I ensure that the attachment file is virus free?
Bye,
- Francis
Dear Member:
we have been using mailman ver. 2.0beta6 for about six months now on a
pentium II with RedHat Linux 6.0 this morning I had approved a message.
After a while I realised that multiple copies of this message (in fact
more than 50 copies) ware being broadcasted to the members of the
On 2/7/01 11:41 PM, "Francis Jayakanth" [EMAIL PROTECTED] wrote:
we have been using mailman ver. 2.0beta6 for about six months now
I would like to know as to why this could have happened and how do I
prevent recurrence of such incidents.
Easy -- if you're using beta releases, upgrade when
94 matches
Mail list logo
