[Copy sent separately to both exim and mailman lists]
I updated and cleaned up my HOWTO information for using exim & mailman
together and put it up on the exim web site. The exim list is now
using *exactly* that configuration (copied and pasted from the howto)
for its list settings, so I am reasonably confident that I didn't break
something stupidly when copying :-)
Any comments, corrections or additions on this can be sent directly to
me.
The URL for the HOWTO is
http://www.exim.org/howto/mailman.html
For completeness, Mailman info is at
http://www.list.org/
and exim information is at
http://www.exim.org/
The mailing lists and archives for each are linked off their main pages.
Nigel.
--
[ Nigel Metheringham Nigel.Metheringham(a)VData.co.uk ]
[ Phone: +44 1423 850000 Fax +44 1423 858866 ]
At the beginning of each year, we do a massive creation of new accounts
for students. (Well, not THAT massive but a few hundred anyway)
Currently with PMDF listserv our addstudent script on the unix host that
holds the student accounts fires off a "subscribe class-of-2001" message
to the list server and the student is added.
Mailman has that feature but requires a confirmation of the student
before the subscription is added. While most would argue that this is
acceptable, Im going to say most students as well as the administrators
of those lists will complain to me they want one step adding. Anyway to
do this? Perhaps a "subscribe [password] [digest option] [no confirm]
address=blah(a)blah.com"? If im sending the list password (admittedly
though unsecure email) this should work the same as if I added them via
the web interface.
-Nick
--
----------------------------------------------------------------------
Nicholas Brenckle Yale University School of Medicine
nicholas.brenckle(a)yale.edu ITS Med - PO Box 208089
203-737-2377 New Haven, CT 06520-8089
I installed the patch as posted by Tor Houghton (mailman-users : 30
March 1999 -
http://www.python.org/pipermail/mailman-users/1999-March/000941.html )
This didnt work for me. I still receive the error on newlist creation
(see below) This is on an OpenBSD 2.5 system and Python 1.5b2.
A little more poking and I found the solution was to set the list to
'openbsd2' instead of 'openbsd' in the posixfile.py lib file.
Is now: if sys.platform in ('netbsd1', 'freebsd2', 'freebsd3'):
Change to: if sys.platform in ('netbsd1', 'freebsd2', 'freebsd3',
'openbsd2'):
There are two lines that contain the same thing (checking for netbsd and
freebsd) add the 'openbsd2' to each of them.
-Nick
--
----------------------------------------------------------------------
Nicholas Brenckle Yale University School of Medicine
nicholas.brenckle(a)yale.edu ITS Med - PO Box 208089
203-737-2377 New Haven, CT 06520-8089
Error Message I was getting before the fix to the posixfile.py:
Traceback (innermost last):
File "bin/newlist", line 146, in ?
raise SystemExit(main(sys.argv))
File "bin/newlist", line 93, in main
newlist.Create(list_name, owner_mail, pw)
File "/home/mailman/Mailman/MailList.py", line 724, in Create
self.Lock()
File "/home/mailman/Mailman/MailList.py", line 1379, in Lock
self._lock_file.lock('w|', 1)
File "/usr/local/lib/python1.5/posixfile.py", line 190, in lock
flock = fcntl.fcntl(self._file_.fileno(), cmd, flock)
IOError: [Errno 22] Invalid argument
How can I set up a search engine like htdig that uses the regular
mailman (email+password) security?
If I point it at http://hostname/pipermail/listname/ it's going to only
index the enter-your-information pages and not the content, correct?
How can I get around this? And how can I -then- require actual users to
enter their email+password to access the info?
bekj
--
: --Hacker-Neophile-Eclectic-Geek-Grrl-Queer-Disabled-Boychick--
: gossamer(a)tertius.net.au http://www.tertius.net.au/~gossamer/
: It may be irrational of me, but human beings are quite my
: favorite species. -- The Doctor, 'Doctor Who'
will(a)connectcorp.net said:
> Some of our subscribers are reporting receiving 2, 3, or even 4 copies
> of each post.
I've seen very occasional examples of this on our list running mailman
1.0. The headers show that the duplication is occurring at the point
where mailman injects the message into the MTA for delivery to the list
subscribers.
I've just checked yesterdays logs and found one message that did this.
In this case the final mail injection was duplicated - ie mailman
injected the message 5 times to a different set of subscribers, and
then injected it twice with the same recipient list each time.
There is no indication of problems in the mailman logs.
The injects were spread over a 5 or so minute period, with the last 2
(duplicated) injects done 2.5 minutes apart. The machine would have
been quite heavily loaded around that time - there was a message still
in the process of injection by mailman when the second arrived and a
few messages in the mailq.
Nigel.
--
[ Nigel Metheringham Nigel.Metheringham(a)VData.co.uk ]
[ Phone: +44 1423 850000 Fax +44 1423 858866 ]
I have a closed list but for some *subscribed* users, all posts
must be approved by me (error Only subscribed users may post to
the list). (See Bug 126 in the jitterbug DB). Can you please have
a look ASAP because many valid users get these mails back ?
This seems to be related to having several aliases for
a machine.
--
Aaron "Optimizer" Digulla Team AMIGA AROS Head of Development
Author of XDME, ResTrackLib, CInt. <http://www.aros.org/>
"(to) optimize: Make a program faster by improving the algorithms rather than
by buying a faster machine." <digulla(a)hepe.com>
Hi,
After installing mailman at the bottom of my mailing list pages it says it
is version 1.0.
However, it seems as this list runs on v 1.0.2 .
Look at the bottom of:
http://www.python.org/mailman/listinfo/mailman-users
Can someone explain what the difference is if any?
Is 1.0.2 the latest release?
later,
Mentor
Dear Mailman Makers,
GREAT PROGRAM! Running mailing lists was the reason I got into linux oh so
long ago. Mailman is the tool that we all needed all those years.
Congradulations! (kudos to majordomo required at this point... :)
Dear Mailman Users,
I have a simple problem. But I just can't find the switch to fix it.
I get this warning in pink at the top of an admin page.
>>
Warning: you have lst members, but non-digestified mail is turned off.
They will receive mail until you fix this problem.
>>
I copied and pasted that, so it's shown as-is. I don't quite understand
the message actually. Should 'lst' be list? I have many members all set to
receive non-digest (that is normal mail). Why would it be a problem if
they got mail? The list seems to be functioning normally.
The real questions are these:
Where are the switches to enable and disable mail types?
What do I have to do to get this warning to go away?
THANKS ALL...
Christian Nally
Hi.
I'm using the mailman release supplied with the current stable
debian distribution. The package version is:
ii mailman 1.0rc2-5 Powerful, web based list processor
The problem I'm having is that I've partially but not
completely got mailman working. I can create a newlist with 'newlist',
subscribe to it, post stuff, all that. I can subscribe via the
web. But if I try to go to the web admin page, going to the url
supplied in the mail sent when the list was created, I get a
'premature end of script headers' message. I've read the FAQ about
possible uid/gid problems, but reading the logs doesn't produce any of
the syslog messages I'm warned to be looking for. All I can find in
syslog or the apache logs is the 'premature end of script headers'
message that I already know about (in the apache error log).
