Hi. I work at a small company with an externally hosted Exhange server
for an MTA. DNS is also externally managed. We'd like to set up mailing
lists and I'd like to use Mailman to do it. We have a linux machine
internally on which I've installed Mailman & Postfix. I can configure
this machine t
Morgan Fletcher <[EMAIL PROTECTED]> writes:
> I have a netbsd 1.6 machine running Mailman 2.1.5 serving about twenty
> lists. One of my lists has a problem where it's pending moderator requests
> page can't be viewed, it just times out. I'm speaking about the URL
iles.
I can load the pending administrative requests pages for all my other
lists, including those with bigger admin queues.
I appreciate your help,
Morgan
--
Morgan Fletcher, [EMAIL PROTECTED] Oakland, CA
--
Mailman-Users mailing list
M
-r-- 1 mailman mailman 2975275 Dec 28 01:11 request.pck
-rw-rw-r-- 1 morgan mailman 1169 Apr 13 2002 roster.html
-rw-rw-r-- 1 morgan mailman 198 Apr 13 2002 subscribe.html
I've run 'check_perms' and 'check_db' and everything checks out OK.
Got anything f
Morgan Fletcher <[EMAIL PROTECTED]> writes:
> I recently made the upgrade* from 2.0.8 to 2.1.5. It went well. Thank you,
> mailman maintainers, for a great piece of software.
>
> Mail to our mailing lists has had empty Cc headers since the upgrade. Why
> is that? It'
I recently made the upgrade* from 2.0.8 to 2.1.5. It went well. Thank you,
mailman maintainers, for a great piece of software.
Mail to our mailing lists has had empty Cc headers since the upgrade. Why
is that? It's causing some mail to be rejected by our subscribers' MTAs,
like so:
Aug 4 07
Morgan Fletcher <[EMAIL PROTECTED]> writes:
> Do I need to update the data under $prefix/lists/ when upgrading from 2.0.X
> to 2.1.X? If so, how? I don't see any mention of it in the 2.1.3 INSTALL or
> UPGRADING document, but when I try the upgrade with 2.0.8-era lists/ data,
Do I need to update the data under $prefix/lists/ when upgrading from 2.0.X
to 2.1.X? If so, how? I don't see any mention of it in the 2.1.3 INSTALL or
UPGRADING document, but when I try the upgrade with 2.0.8-era lists/ data,
I get errors about missing properties. (fields?)
Morgan Fle
Is 'bin/update -f' required, for an upgrade from 2.0.8 -> 2.1.3? It's not
mentioned as needed in the INSTALL or UPGRADING docs, except for 1.0 or 1.1
-> 2.0.
Morgan
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/l
Morgan Fletcher <[EMAIL PROTECTED]> writes:
> I've got a netbsd server which has a working 2.0.8 installation in
> /home/mailman. Python is 2.3. MTA is postfix. I've installed mailman
> 2.1.3 in /usr/local/mailman. The /usr/local/mailman is basically owned by
> root.ma
I've got a netbsd server which has a working 2.0.8 installation in
/home/mailman. Python is 2.3. MTA is postfix. I've installed mailman 2.1.3
in /usr/local/mailman. The /usr/local/mailman is basically owned by
root.mailman. I've copied the lists and archives files over to the new
tree, but I've hit
Richard Barrett <[EMAIL PROTECTED]> writes:
>> I am using mharc for our mailing list archives, and other mailing lists
>> which we don't host:
>>
>> http://birfield.com/archives/
>>
>> I'd recommend it, although if mailman had an integrated solution as nice
>> I'd use that instead.
>
> MHonArc is n
John Poltorak <[EMAIL PROTECTED]> writes:
> Are there any recommendations for providing a search facility for
> archives?
I am using mharc for our mailing list archives, and other mailing lists
which we don't host:
http://birfield.com/archives/
I'd recommend it, although if mailman had an integr
Morgan Fletcher <[EMAIL PROTECTED]> writes:
> We're running mailman 2.0.8 & python 2.0.1 on a netbsd 1.6 box. Digests are
> getting truncated "early" when a message containing a single period ('^.$')
> is encountered.
>
> Is this bug fixed in a lat
We're running mailman 2.0.8 & python 2.0.1 on a netbsd 1.6 box. Digests are
getting truncated "early" when a message containing a single period ('^.$')
is encountered.
Is this bug fixed in a later mailman release?
Please let me know if I've left any necessary information out of this
message, and
Our spam filter seems to have sprung a leak, and one of our lists (mailman
2.0.8) now has over 1000 messages in the admin queue. We'd like to just
clear it out without using the web interface. I searched for the solution
but could not find it. How can we clear that queue en masse?
We'll upgrade to
"Marci O'Daffer" <[EMAIL PROTECTED]> writes:
> I have seen a lot of questions posted here in the past few days since
> I joined, but no answers. I've personally posted two questions, and
> have received no answers. Are there any list moderators? Anyone to
> answer questions for us newbies?
What ar
Mick Prescott <[EMAIL PROTECTED]> writes:
> Please forgive a new mail list user what could be some very basic
> questions. One of my users reported the link to the Subscribe page for my
> mail list takes them to an error page "'page not found' error
> -http://nkemmaus.com/pipermail/nkemmaus_nkemma
Paul Croft <[EMAIL PROTECTED]> writes:
> Is it possible to download my membership into my computer so that I can
> search for members instead of having to go on site for it? Reason I ask is
> that sometime people don't necessarily know their email address when they
> complain to you...but by read
Thomas Hillson <[EMAIL PROTECTED]> writes:
> The first involves qrunner, what happens is that a list gets locked and no
> mail will go through it.
Tom, when I first moved my 1800-member list to mailman, it had upwards of
200 dead addresses. Those 200 dead addresses caused a lot of bounces, and
f
Ted M Harapat <[EMAIL PROTECTED]> writes:
> > > It all installed fine as always, and I made lists and sent some mails
> > > to them. So it appeared to work. So I went to the web interface to
> > > start to configure them and add the users to the lists. Here's where
> > > the problem started. I p
"Bodnyk, Bruce W" <[EMAIL PROTECTED]> writes:
> I'm running mailman on a Compaq 450Mz Pentium II with 512Mb of memory. I
> started adding users by sending an email to the list-request and the
> email has about 50 names on it. I'm finding that Mailman is adding at max
> two people per minute.
>
>
27;s
admin cookie(s) when I've made network changes.
Morgan
--
VVVVV
>> Morgan Fletcher 63 FJ40, 76 FJ55, 94 FJ80 TLCA #5973, Oakland, CA <<
>> Illegitimi non carborundum http://www.birfield.com/~morgan <<
very minute, and it's been
humming along for about 10 hours with no problem.
This would probably be a good test case for mailman: add some percentage of
known dead addresses to a list and see what mailman does.
Thanks for your help, it seems to be working now.
Morgan
--
VV
Charlie Watts <[EMAIL PROTECTED]> writes:
>> > I think our list is hitting some sort of postfix limitation, but I'm not
>> > sure what it is.
>
> Why do you think it's postfix? That doesn't make sense, based on what
> you've said.
Yeah, it's python/qrunner that's wedged, postfix seems OK.
> Anyw
Morgan Fletcher <[EMAIL PROTECTED]> writes:
> I just used bin/add_members to build out the ~1800 members of our mailing
> list.
>
> Now, python (2.0) is wedging itself everytime it's launched:
>
> PID USERNAME PRI NICE SIZE RES STATE TIME WCPUCPU COMM
I just used bin/add_members to build out the ~1800 members of our mailing
list.
Now, python (2.0) is wedging itself everytime it's launched:
PID USERNAME PRI NICE SIZE RES STATE TIME WCPUCPU COMMAND
4246 mailman 57024M 23M run 8:22 98.44% 98.44% python
I'm run
Is there a way to build out pipermail's archives incrementally, with older
archives?
Could I sequentially add month-long chunks of majordomo archives to
listname.mbox, updating pipermail as I go?
I'm trying to get around bin/arch, and I can't edit a 360MB file...
Morgan
--
"Michael Bray" <[EMAIL PROTECTED]> writes:
> I am having a problem with different results being returned for different
> host names that I want to use the same list configuration. For example,
> I want 'http://www.xyz.com/mailman/listinfo' and
> 'http://xyz.com/mailman/listinfo' to both go to the
I have a 360MB listname.mbox file, which is concatenated from six years of
majordomo archives. I tried archiving the mbox using bin/arch (via the
built-in pipermail), and got this:
Traceback (most recent call last):
File "bin/arch", line 129, in ?
main()
File "bin/arch", line 118, in main
I've got 360MB of ASCII majordomo archives, all files in the form
listname.MM. I'd like to grandfather them into the pipermail archives
our list will be creating, once it's run by mailman.
How do the monthly text archives from majordomo correspond to the files
down in archives/private?
I tri
I asked this yesterday, got no reply, so again: Is there any way to filter
for message body content with Mailman?
Morgan
--
Mailman-Users maillist - [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
The list admin I'm working with filters for expletives with majordomo, and
redirects matching posts to his admin queue. Is there a way to filter the
message body with Mailman?
Morgan
--
Mailman-Users maillist - [EMAIL PROTECTED]
http://mail.p
Heiko Rommel <[EMAIL PROTECTED]> writes:
> What about using MHonArc
>
> http://www.oac.uci.edu/indiv/ehood/mhonarc.html#whatis
MHonArc just archives. Wilma wraps MHonArc and Glimpse to get you
search-able archives:
http://www.hpc.uh.edu/majordomo/#wilma
I have set up a large archive that is i
alex wetmore <[EMAIL PROTECTED]> writes:
>> Is there a way with Mailman 2.0.8 to filter out HTML and attachments,
>> per-list?
>
> Look at the privacy page (under list admin) for "Hold posts with..."
A lot of the mail encoded with HTML doesn't have anything in the header
warning you the contents
I'm switching a 1700-person mailing list from majordomo to mailman. I like
mailman a lot, so far, so does the list admin. But there's one thing
missing: The ability to differentiate between and filter out HTML/RTF
messages and MIME attachments. Our list's policy is: no HTML, no
attachments. With m
Morgan Fletcher <[EMAIL PROTECTED]> writes:
> I'm trying to run mailman 2.0.8 on NetBSD 1.5.1 with postfix. When I create
> a list and it tries to send mail to a valid external address (for the list
> owner), postfix doesn't send the message and I see this in maillog
I'm trying to run mailman 2.0.8 on NetBSD 1.5.1 with postfix. When I create
a list and it tries to send mail to a valid external address (for the list
owner), postfix doesn't send the message and I see this in maillog:
Recipient address rejected: Relay access denied
I've created user and group
38 matches
Mail list logo
