I can't get to the pending request page for a mailing list.
(My web clients just say "waiting for response" and finally give up.)
I think it is because there are too many pending requests after some
problems. (config.db is almost 10MB.)
How can I do this some other way?
I have a list that I'd like to enforce a set of headers on. In other words, each message subject must start with a certain word in order be posted. Has anybody found a way to do this? I know I can block messages with certain headers, but I want to block all messages and only allow those with the approved headers. If anybody has a great idea how to accomplish this, please pass it on ...
-- Sarah
Hi all,
Quick question: I've looked through most of the options available
to a list admin, and I can't find one to disable the monthly password
reminders. I know this sounds like a bad idea, but we have a secretary
who maintains quite a few mailing lists for out department, and we'd like
to switch her over to mailman. However, we probably don't want students
to be able to unsubscribe themselves from certain of our announcement-type
mailing lists. Any ideas? Am I missing something simple?
Thanks much,
Josh Lothian
System Administrator
University of Tennessee, Department of Computer Science
I need some assistance if possible i get the following errors after reading your trouble shooting i still have no idea what im doing wrong.
# ./configure&
[1] 21167
[root mailman-2.0.6]# loading cache ./config.cache
checking for --with-python... no
checking for python... /usr/bin/python
checking Python interpreter... /usr/bin/python
checking Python version... 1.5.2
checking for a BSD compatible install... /usr/bin/install -c
checking whether make sets ${MAKE}... yes
checking for true... /bin/true
checking for --without-gcc... no
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking whether #! works in shell scripts... yes
checking for --with-var-prefix... no
checking for --with-username... mailman
checking for mailman UID... 500
checking for --with-groupname... mailman
checking for mailman GID... 500
checking permissions on /home/mailman... configure: error:
***** Installation directory /home/mailman is not configured properly!
***** Set-gid bit must be set for directory: /home/mailman
***** Permissions should be at least 02775: /home/mailman
drwxr-xr-x 4 mailman mailman 1024 Feb 21 23:34 mailman
[root mailman]# ls -al
total 7
drwxr-xr-x 4 mailman mailman 1024 Feb 21 23:34 .
drwxr-xr-x 15 root root 1024 Feb 21 23:20 ..
-rw------- 1 mailman mailman 176 Feb 21 23:37 .bash_history
-rwxr-xr-x 1 mailman mailman 434 Feb 21 23:20 .emacs
-rw-r--r-- 1 mailman mailman 778 Feb 21 23:20 .ftphelp
drwxr-xr-x 5 mailman mailman 1024 Feb 21 23:20 group
drwxr-xr-x 4 mailman mailman 1024 Feb 21 23:20 user
Anyone able to help?
> -----Original Message-----
> From: Moonlit Submit [mailto:moonlitsubmit@hotmail.com]
>
> Hello,
> I need to know if there's a command for when
> list's mail isn't being sent.
> I do have shell access, but I need step by step instructions for this.
The keyword is logfiles.
Check the mailman /log directory and check the MTA (mailer) logfiles which
are placed depending on your mailer and OS.
Most probably /var/log/maillog or something similar...
--
Enriko Groen, Hosting manager
--------------------------------------------------------
netivity bv www.netivity.nl enriko.groen(a)netivity.nl
038 - 850 1000 van nagellstraat 4 8011 eb zwolle
--------------------------------------------------------
Mailman CGI error!!!
The expected gid of the Mailman CGI wrapper did not match the gid as set by the Web server.
The most likely cause is that Mailman was configured and installed incorrectly. Please read the INSTALL instructions again, paying close attention to the --with-cgi-gid configure option. This entry is being stored in your syslog:
Failure to exec script. WANTED gid 99, GOT gid 48. (Reconfigure to take 48?)
OS: redhat7.2
maiman:mailman-2.0.5
question -----> how to fix it !!!!!
Please tell me!!!! thanks!!
Hot on the heels of Mailman 2.0.7, I'm now releasing 2.0.8 which fixes
several cross-site scripting security holes, and a few other minor bug
fixes. More information on cross-site scripting exploits in general
can be found at
http://www.cert.org/advisories/CA-2000-02.html
I recommend anybody running a version of Mailman up to, and including
2.0.7 to upgrade to version 2.0.8.
I've made both full source tarballs and patches available. Actually,
patches going all the way back to 2.0 are now available on
SourceForge. See
http://sourceforge.net/project/showfiles.php?group_id=103
for links to download all the patches and the source tarball. If you
decide to install the patches, please do read the release notes first:
http://sourceforge.net/project/shownotes.php?release_id=63042
Currently the SourceForge and www.list.org sites are up-to-date, and I
expect the gnu.org site to be updated soon.
See also:
http://www.gnu.org/software/mailmanhttp://www.list.orghttp://mailman.sf.net
I've also included links on the FAQ page to the Mailman FAQ wizard.
Thanks everybody for contributing good entries! (I may do some reorg
when I get a chance.) See the FAQ wizard at
http://www.python.org/cgi-bin/faqw-mm.py
Cheers,
-Barry
-------------------- snip snip --------------------
2.0.8 (27-Nov-2001)
Security fix release to prevent cross-site scripting exploits.
See http://www.cert.org/advisories/CA-2000-02.html for a
description of the general problem (not Mailman specific).
Hi all,
Just wanted to let you know that I've released Mailman 2.1 alpha 4.
Below is the big list of changes with this release. This will be the
last alpha release for 2.1, but this still leaves open the possibility
of a few new features in MM2.1. I've got everything in that I intend
to get in. If you've got a pet new feature -- and have code that
implements it -- please do remind me about it now and I'll work on
getting in what I can for the first beta. Apologies for falling so
far behind in the mailing list traffic.
This is admittedly a bit of a rushed release. I really wanted to get
this out before the end of the year (in my timezone at least ;).
Depending on my other real-job commitments, I'll be spending all my
spare time getting bugs fixed and moving toward the 2.1 final release.
I'm shooting for release by the Python conference in February, but I
don't know if I'll make it.
Cheers, and happy new year to you all.
I-swear-the-X-Oblique-Strategy-was-chosen-random-ly y'rs,
-Barry
-------------------- snip snip --------------------
2.1 alpha 4 (31-Dec-2001)
- The administrative requests database page (admindb) has been
redesigned for better usability when there are lots of held
postings. Changes include:
o A summary page which groups held messages by sender email
address. On this page you can dispose of all the sender's
messages in one action. You can also view the details of
all the sender's messages, or the details of a single
message. You can also add the sender to one of the list's
sender filters.
o A details page where you can view all messages, just those
for a particular sender, or just a single held message.
This details page is laid out the same as the old admindb
page.
o The instructions have been shorted on the summary and
details page, with links to more detailed explanations.
- Bounce processing
o Mailman now keeps track of the reason a member's delivery
has been disabled: explicitly by the administrator,
explicitly by the user, by the system due to excessive
bounces, or for (legacy) unknown reasons.
o A new bounce processing algorithm has been implemented (we
might actually understand this one ;). When an address
starts bouncing, the member gets a "bounce score". Hard
(fatal) bounces score 1.0, while soft (transient) bounces
score 0.5.
List administrators can specify a bounce threshold above
which a member gets disabled. They can also specify a time
interval after which, if no bounces are received from the
member, the member's bounce score is considered stale and is
thrown away.
o A new cron script, cron/disabled, periodically sends
notifications to members who are bounce disabled. After a
certain number of warnings the member is deleted from the
list. List administrators can control both the number of
notifications and the amount of time between notifications.
Notifications include a confirmation cookie that the member
can use to re-enable their subscription, via email or web.
o New configuration variables to support the bounce processing
are DEFAULT_BOUNCE_SCORE_THRESHOLD,
DEFAULT_BOUNCE_INFO_STALE_AFTER,
DEFAULT_BOUNCE_YOU_ARE_DISABLED_WARNINGS,
DEFAULT_BOUNCE_YOU_ARE_DISABLED_WARNINGS_INTERVAL.
- Privacy and security
o Sender filters can now be regular expressions. If a line
starts with ^ it is taken as a (raw string) regular
expression, otherwise it is a literal email address.
o Fixes in 2.0.8 ported forward: prevent cross-site scripting
exploits.
- Mail delivery
o Aliases have all been changed so that there's more
consistency between the alias a message gets delivered to,
and the script & queue runner that handles the message.
I've also renamed the mail wrapper script to `mailman' from
`wrapper' to avoid collisions with other MLM's. You /will/
need to regenerate your alias files with bin/genaliases, and
you may need to update your smrsh (Sendmail) configs.a
Bounces always go to listname-bounces now, since
administration has been separated from bounce processing.
listname-admin is obsolete.
o VERP support! This greatly improves the accuracy of bounce
detection. Configuration variables which control this feature
include VERP_DELIVERY_INTERVAL, VERP_PERSONALIZED_DELIVERIES,
VERP_PASSWORD_REMINDERS, VERP_REGEXP, and VERP_FORMAT. The
latter two must be tuned to your MTA.
o A new alias mailman-loop(a)dom.ain is added which directs all
output to the file $prefix/data/owner-bounces.mbox. This is
used when sending messages to the site list owners, as the
final fallback for bouncing messages.
o New configuration variable POSTFIX_STYLE_VIRTUAL_DOMAINS
which should be set if you are using the Postfix MTA and
want Mailman to play nice with Postfix-style virtual
domains.
- Miscellaneous
o Better interoperability with Python 2.2.
o MailList objects now record the date (in seconds since
epoch) that they were created. This is in a hidden
attribute `created_at'.
o bin/qrunner grows a -s/--subproc switch which is usually
used only when it's started from mailmanctl.
o bin/newlist grows a -l/--language option so that the list's
preferred language can be set from the command line.
o cron changes: admin reminders go out at 8am local time instead
of 10pm local time.
- Pipermail archiver
o MIME attachments are scrubbed out into separate files which
can be viewed by following a link in the original article.
Article contains an indication of the size of the
attachment, its type, and other useful information.
o New script bin/cleanarch which can be used to `clean' an
.mbox archive file by fixing unescaped embedded Unix From_
lines.
o New configuration variable ARCHIVE_SCRUBBER in
Defaults.py.in which names the module that Pipermail should
use to scrub articles of MIME attachments.
o New configuration variable ARCHIVE_HTML_SANITIZER which
describes how the scrubber should handle text/html
attachments.
o PUBLIC_ARCHIVE_URL has change its semantics. It is now an
absolute url, with the hostname and listname parts
interpolated into it on a per-list basis.
o Pipermail should now provide the proper character set in the
Content-Type: header for archived articles.
- Internationalization
o Czech translations by Dan Ohnesorg.
o The Hungarian charset has be fixed to be iso-8859-2.
o The member options login page now has a language selection
widget.
- Building, configuration
o email-0.96 package is required (see the misc directory).
o New recipes for integrating Mailman and Sendmail,
contributed by David Champion.
On Mon, 31 Dec 2001 13:24:04 -0800
Bill Moseley <moseleymm(a)hank.org> wrote:
> At 03:30 PM 12/31/01 -0500, Richard Idalski wrote:
> Does anyone know if it's possible to run Postfix on a high port
> while sendmail is still running? e.g. not install Postfix's
> sendmail binary over real sendmail?
Sure, its possible. You'll just need to exercise especial care with
the configure line and config files.
--
J C Lawrence
---------(*) Satan, oscillate my metallic sonatas.
claw(a)kanga.nu He lived as a devil, eh?
http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.
