I have a couple of Mailman lists on a server happily running 2.1.9 but I
am also a moderator on a very active list that's running on 2.1.12. I do
not host this list, just volunteer because I have some experience with
Mailman.
That list has started to get some significant bounces due to the DMA
Greetings:
I'm having problem with administratively changing addresses. When I get
a request to change addresses on this list I normally just go ahead and
change it figuring that it's easier than explaining the process to those
who didn't just go and change it themselves to start with. Several
Paul Tomblin wrote:
>Quoting G. Armour Van Horn ([EMAIL PROTECTED]):
>
>
>>After moving the list to it's new home and running the script to update
>>the archive, I ended up with a raft of messages in the January 2007
>>archive that are probably ancient. They
Paul Tomblin wrote:
>Quoting G. Armour Van Horn ([EMAIL PROTECTED]):
>
>
>>After moving the list to it's new home and running the script to update
>>the archive, I ended up with a raft of messages in the January 2007
>>archive that are probably ancient. They
After moving the list to it's new home and running the script to update
the archive, I ended up with a raft of messages in the January 2007
archive that are probably ancient. They show no subject, and all of them
are dated this afternoon, probably at the time that I ran the script. Is
there any
Mark,
Thanks.
../../bin/withlist -l -r fix_url
worked like a charm. I'm sure there's some cleanup to do, but I'll bet
that took care of most of it.
Van
Mark Sapiro wrote:
>G. Armour Van Horn wrote:
>
>
>>The problem with the old server is that it wo
thing back easily from this data?
Van
Patrick Bogen wrote:
> On 1/29/07, G. Armour Van Horn <[EMAIL PROTECTED]> wrote:
>
>> So, where do I dig up the membership list, and how do I deal with all
>> the old URLs?
>
>
> FAQ 3.4
> <http://www.python.org/cg
n wrote:
> On 1/29/07, G. Armour Van Horn <[EMAIL PROTECTED]> wrote:
>
>> So, where do I dig up the membership list, and how do I deal with all
>> the old URLs?
>
>
> FAQ 3.4
> <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.00
My old Mailman host died a while back, and I'm finally getting around to
getting the new one running again. Before I shut off the old host I
tarred up the old files and have them on the new server.
I just moved the components from the old archives and lists directories
into the new locations, a
Mark Sapiro wrote:
>G. Armour Van Horn wrote:
>
>
>>The heart of the bounce is as follows:
>>
>><"|/home/mailman/mail/mailman post freehand"@domainvanhorn.com> (expanded from
>> <[EMAIL PROTECTED]>): unknown user:
>> "|/
I did something, although I can't for the life of me figure out what,
that broke my mailman server. The web presence hasn't changed any, user
administration works fine, as does access to the archive, and monthly
password reminders are being sent. But mail to any of the lists bounces.
I'm runnin
I've just noticed that one of the lists I'm moderating shows messages
from next Monday in the private archive. The last message is timestamped
for 8:08 (Pacific, +0700) on 14 Aug, but was actually distributed by
Mailman at 08:51 on 11 Aug.
Unfortunately, the archive seems to be ordered by times
One of the lists I moderate is fairly high volume, dedicated to art
quilting. A subscriber noted this morning that we had 269 digests
released in June, and wondered what the record was. Made me curious,
does anyone track such things?
Van
--
--
Greetings,
It has come to my attention that messages with signatures from Mozilla
or Netscape mail clients cause digests to be displayed in grey from the
beginning of one such message to the end of the digest when received by
Gecko-powered mail clients when the MIME version of the digests is sel
Silly me, I searched the FAQs at www.list.org instead. But hey, you nailed
it and the lists appear to be up and running again. Thanks.
Van
Tom Eastep wrote:
> On Sun, 01 Jun 2003 11:30:57 -0700, G. Armour Van Horn
> <[EMAIL PROTECTED]> wrote:
>
> > When I resta
Well, that was reassuring, so I ran "ps aux | grep mail" to dig out the syntax
for mailmanctl, and stopped it with
/usr/bin/python2 /home/mailman/bin/mailmanctl -s -q stop
I went to /usr/scr/mailman.2.1.2 and ran the exact same commands I used last
October to install 2.1b3. (Yes, I keep these thi
Greetings,
I've been through a ton of messages, the README-POSTFIX, alternate regexp
approach mentioned in there, and the alternate (by Dax Kelson) mentioned in
that. It's left me confused.
I have had Mailman running with Postfix for a couple of years, it currently is
at 2.0b3. (I will be install
On my lists I probably have a two to one ratio of spam or virus postings to
legitimate messages. The legitimate postings come entirely from users who either
have multiple addresses or slight variations of their address, and I really don't
feel like throwing them away. Mailman 2.1 handles this a lit
setup "postfix virtual domains",
please
post here and possibly send it to [EMAIL PROTECTED] - the address
I'll be
checking for the next week while I'm out of town.
Van
Larry Rosenman wrote:
> On Wed, 2002-10-09 at 04:33, G. Armour Van Horn wrote:
>
> > I discovere
Well, at the time I had a permissions issue. So I chowned the whole tree
to mailman:mailman, and went back and did "config.status" and "make install"
to ratify it. Then I did a couple of other little things I had overlooked
in the INSTALL file. Nothing is being logged in the mailman/logs to spea
Barry hit the nail on the head regarding python2-devel being needed for RedHat
users. I installed that package and 2.1b3 compiled in just a few minutes, and
ran the first time. (Well, at least I can get to the admin interface.)
I went to setup a new list, ran newlist from the mailman/bin collecti
I sent this early this morning when I gave up on the upgrade for the day, I'd really
like to have someone look at this so I can try again tonight.
Van
"G. Armour Van Horn" wrote:
> I've been running Mailman for most of two years, going from 2.0.5 to 2.0.12+ on a
>
I've been running Mailman for most of two years, going from 2.0.5 to 2.0.12+
on a very lightly loaded K6-233. I've finally been convinced to move up.
Last night I reved RedHat from 6.2 to 7.2, installed Python2 2.2.1, and
generally brought things up to date.
I also added virtual host support to
Larry Rosenman wrote:
> On Mon, 2002-09-30 at 14:46, G. Armour Van Horn wrote:
> > I've decided that it's time to make the jump to the beta, and I'm wondering if
>anyone is maintaining
> > any guides for the process. I have a new list to setup, which will be
I've decided that it's time to make the jump to the beta, and I'm wondering if anyone
is maintaining
any guides for the process. I have a new list to setup, which will be my first with a
virtual domain,
but I also have a dozen current lists to preserve.
I assume that this is touched on in the d
I simply put a 40,000 character limit on message size. It eliminates every virus
I'm aware of, and also blocks someone from accidentally replying to a message
and helpfully including some monster file with the answer. (I used to see that
on one list, discussing an illustration program, where one h
I have a small group of lists for one client (one company wide, one each for four
offices, one for the managers, etc.) that are all set to "Reply to sender" as the
default. For most users it works just fine. However, some of the Outlook 2000
users seem to end up with their replies directed to the
.88.61)
by 172.16.44.130 with SMTP; 18 Feb 2001 21:05:13 -
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 18 Feb 2001 13:08:09 -0800
From: "G. Armour Van Horn" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
---etc---
Now, here is one that a recipient of the proposed list has (with a
s (which where simply test messages). Copied the
old
> lists mbox file over the Mailman one, then ran the Mailman arch
> command, and told it to re-create the archives. Worked a charm!
>
> On Mon, 2002-09-23 at 04:35, G. Armour Van Horn wrote:
> > Greetings,
> >
> &g
Greetings,
I have been asked to possibly host a list previously kept in another system.
They would like to include archives from their existing list, and have the
messages in mbox format. The format appears to be compatible, but when I
appended a sample to one of my test lists the other messages
When I first was investigating Mailman I read enough of the site to see that
Postfix was probably the best bet. It sounded like Barry was running it, which
meant that Mailman would always work with Postfix! So I installed RedHat and
Postfix, and then setup Mailman.
I still run Sendmail for my mai
Richard,
Perhaps you could take a minute to sketch the advantages of the options
mentioned, the FAQ tells me that there are three but gives no clue as to
establishing a preference among MnoGoSearch, HT:Dig, and Pipermail
itself.
I have never tried to set any of these up, and the only one I reca
Mailman needs to run as user mailman, presumably 514 is the gid of whoever
you were logged in as when you got that error.
If mailman has run in the past and nobody has changed anything on you,
that's probably all it is.
The configuration files refer to compiling the source, and I have no
idea wh
So far, I've dealt with this entirely by getting my server whitelisted
with the ISPs that are doing that. I believe that there is a setting for
the number sent in a batch, but to go from 500 (default, I think) to 1
would be an excruciating hit to your performance. I believe all of the
discussion
Au contraire! Every version of Mailman I've used (back to 2.0.4, now on
2.0.12+) has handled bounced message with aplomb. Check out:
http:///mailman/admin//bounce
for the options.
Van
Will Yardley wrote:
Angel Gabriel wrote:
> I'd like to know how bouncing mail is treated, is it removed from
On the Privacy Options page, set "Must posts be approved by an administrator?"
to yes so the occasional post will not pass. On General Options, set "Where are
replies to list messages directed?" to Explicit address and make sure that
address ends up in one of your inboxes.
There is no way to auto
e site)
was saying not to, and felt that the issue should be addressed.
If nothing else, it pushed Barry to endorse the current beta more strongly
than he had before!
Van
J C Lawrence wrote:
> On Wed, 28 Aug 2002 15:08:00 -0700
> G Armour Van Horn <[EMAIL PROTECTED]> wrote:
>
> &
Barry,
According to the website, 2.1 is a beta program not to be installed for
production use. Half my listss (and my most active list) are things I
volunteered to do for various reasons. But I do have a number of lists that I am
paid to host, which, by my lights, means that this is a production
Heaven knows I tried to make them break. My MUA in this case is Netscape Messenger
4.78. At least it demonstrates that it
isn't Mailman messing them up! (Not to mention that Netscape is immune to Klez.H.)
Van
Greg Westin wrote:
> All four of those links work, and none break into two lines.
>
>
What happens when you send a really long link through the system? In this
case, I suspect that the line is broken before Mailman ever sees it - it
would be broken if you sent it to a standard mail client just the same.
But what you are sending is a text URL, not a link. The link the reipient
see
I'm using Mailman 2.0.12 with the almost-2.0.13 patch. I have a new list that I
created a couple of days ago, and the messages from the list do not have the footer
on them. The information in the last part of the "Regular-member (non-digest)
Options" page matches at least two other lists that are
Yeah, I have my Mailman machine, along with three webservers and my private home
network, on a DSL line, and I don't think the proposed mail volume would be any
problem on his DSL line, which is faster than my 768K/768K line here.
In two years I've had two outages. One was resolved by updating th
Tom Whiting wrote:
> > (2) A feature that allows a user to register someone else (a friend) with
> > an Introduction ADDED to the subscription email that is sent. So I could
> > subscribe a friend and add a personal messge so they know I sent this to
> > them ...
> VERY VERY not good idea (though
I believe I was the first to report the problem last week, and I felt a certain
relief as other reported it since - I had already been through the fire. Alas, it
bit me again yesterday and one client was fuming this morning because a
time-sensitive message didn't get delivered.
I started pulling
I'm certainly not brave enough to attempt to change it, but I have often been bothered
by the terminology. Subscriber is the exact right word in this case, member or
employee might be a good fit, but then again, they might not. I have lists in which
member, employee, and stockholder would be ap
Locate the two oldest files in /qfiles and move them out of the directory
(or delete them if the .msg file appears to be unimportant). At least in my
case the problem was that the oldest message was damaged and there was no
body. I'm working on the assumption that the lack of a message body is wha
Greetings:
I was on something of a maintenance tear this week, so when I got
Barry's announcement of 2.0.12 I decided it was time to catch up. I've
been running Mailman since 2.0.1, and had been running 2.0.8 from the
week it was released until this morning. I fetched the four patch files,
all of
I left out a little information in the last message that might be useful
with that last message:
This server does almost nothing other than Mailman, I think there is one
very quiet website other than the mailman pages.
The OS is RedHat Linux, probably 6.1.
Python is at 1.5.2
Mailserver is Post
your inbound MTA before you did the
> upgrade to 2.0.12?
>
> -Jim P.
>
> > -----Original Message-
> > From: G. Armour Van Horn
> > Sent: Saturday, July 13, 2002 4:35 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [Mailman-Users] Everything stopped yeste
Andy,
For me it turned out not to be the case at all. After hours of
hair-pulling
I found that the oldest message in
/home/mailman/qfiles/
was truncated. Deleting that one message opened the floodgates.
I've left the error entry in the original message below. It was the
"'string' object has
Greetings:
I was on something of a maintenance tear this week, so when I got
Barry's announcement of 2.0.12 I decided it was time to catch up. I've
been running Mailman since 2.0.1, and had been running 2.0.8 from the
week it was released until this morning. I fetched the four patch files,
all o
I haven't tried this myself yet, but I'm assuming that as long as every
tag continues to be present on the page it doesn't have to be actually
visible to visitors. You should be able to surround some of that info
with comment tags:
for example, should prevent that data from appearing.
Changing
That would be too easy! I would assume that we at least have to create a
DNS entry (probably both A and MX along with a reverse) for the host
name and setup an alias for it in Apache. Anything else, from those that
have done this?
Van
Dave Sherohman wrote:
>
> On Tue, Jan 23, 2001 at 11:12:30PM
One of my Majordomo lists recently went nuts because of a subscriber who
left town with an autoreply in place, one that responded to every
incoming message. Obviously, such a feedback loop had quite an impact -
luckily I caught it in less than two hours when "only" 114 of these
messages had been s
When I setup one of the lists here I had quite a sequence of "this is a
test after at hh:mm" sorts of messages, and they are hanging out in
the archive.
It looks like I can probably edit the file
/home/mailman/archives/public/.mbox/.mbx
and delete the offending messages, but I really
It's a piece of cake, and one that I am very appreciative of since my
first client had me set up five new lists all at once. The key is
config_list in the script directory (/home/mailman/bin by default).
Get the right syntax from the help page, of course, but basically you
setup all of your lists
56 matches
Mail list logo
