We've just recently noticed that on messages that come through the
mailing list that the message footer is appended to the end of the
message and also as an attachment in the message. I want the footer to
appear at the bottom of the message but not as an attachment. Is there
anyway to prevent this from happening?
Thanks
--
Robert Haack
Programmer Analyst
North Clackamas School District
haack(a)nclack.k12.or.us
503-353-6100
Greetings... I'm installing a new virtual mail server using Debian
Sarge, PostgreSQL, Postfix, Dovecot, Mailman, and PostfixAdmin. I'm
trying to automate/tie as much of the administrative configuration
into the PostfixAdmin web interface & PostgreSQL database as
possible. The only thing in the entire setup that doesn't have
direct query access to the SQL database is Mailman. What I want to
do is create an hourly cron job to run a script which pulls the names
of the virtual domains from the database and creates the necessary
addvirtualhost('lists.%s', 'lists.%s') configuration items in
mm_cfg.py. If I end up needing to use a new domain for mailing lists
more quickly than an hour, I can just run the script manually.
I figure that the easiest way to do that would be to have the script
put those configuration items in a separate file and just use
something like Apache's "Include" directive to read it into the
configuration.
I'm not terribly familiar with Python programming, and the only thing
I can find that's similar to what I want to do is the "import"
command. It's not working like I'd hoped because when I add a "from
vhosts_cfg import *" to mm_cfg.py, the Mailman web scripts just come
back with "We've found a bug!" errors and nothing shows up in
/var/log/mailman/error. I did remember to create an
/etc/mailman/vhosts_cfg.py test file with correct addvirtualhost()
usage syntax and made a symlink to it in /var/lib/mailman/Mailman, so
it shouldn't be a matter of a missing file.
I'm not sure what I'm missing or even if this is the best way to
accomplish the task, and rather than go through the time-consuming
task of learning the semantics of another programming languate, I
figured I'd ask the experts. :) If anyone knows of a good way to do
this, I'd greatly appreciate a heads-up. If this ends up being some
sort of informal feature request to be included in the next latest
and greatest version, that'd be cool too. Thanks in advance for any
help offered!
--
Scott 'Simba' Garron
Hi - just a quick question:
In the UPGRADING file in the tarball for mailman 2.1.8, there are no
notes for upgrading to 2.1.8. Is that because there is nothing to
look out for? I'm upgrading from 2.1.5.
Thanks!
Kristina
To: webmaster(a)python.org
During the past month or so, there have been at least two periods of a
few days or more each during which any attempts to commit changes to
the Mailman FAQ <http://www.python.org/cgi-bin/faqw-mm.py> have
produced errors like the following:
Sorry, an error occurred
Can't write file faq01.011.htp ([Errno 13] Permission denied:
'faq01.011.htp').
During the periods that this has been occurring the same error (except
for file name) occurs on any commit of changes to an existing entry or
addition of a new entry.
It appears to be working OK now, but at least once before, it started
working again and then the problem reappeared for a few days.
Can you shed any light on what was happening?
Can you suggest a procedure to follow if this occurs again.
--
Mark Sapiro <msapiro(a)value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
Our mail server is choking on a (syntactically incorrect) recipient
address for a message in Mailman's queue. The message has been
delivered to some of the recipients, but Mailman keeps retrying this one
address and not continuing with the rest:
2006-04-27 09:10:18 SMTP call from localhost (hostname.removed)
[127.0.0.1] U=list dropped: too many syntax or protocol errors (last
command was "rcpt TO:<'username@domain'>")
2006-04-27 09:25:19 SMTP call from localhost (hostname.removed)
[127.0.0.1] U=list dropped: too many syntax or protocol errors (last
command was "rcpt TO:<'username@domain'>")
I've replaced the email address in those logs, but the invalid part is
the ''s around it. Is there any way I can remove the invalid address
from the message to allow it to deliver to the rest of the recipients?
Thanks,
Sam
I am currently maintaining a mailman install that has 5000+ lists, many high
volume. The
archive volume is nearly 80GB in size between the archives and mboxes for
the various
lists. Even after doing acrobatics to only archive the lists that have
changed within the
last 24hours it is extremely time consuming to rebuild the archives from the
cumulative
mbox files.
I am considering rotating the mbox daily, and only processing the the mbox
for that day.
This would mean using the arch without --wipe. My question is, what pitfalls
do I need to
lookout for with this approach?
thanks,
--
--Matt
Our mail server crashed and we didn't have a back up of the Exim
configuration file. We had some mailman lists running and I remember
there was a command I put up at the top on the configuration file but I
can't remember what is was. Can someone refresh my memory?
I believe it was something along the lines of
MM_LISTS=lists.list1.tld:lists.list2.tld
Am I right? I already have the MAILMAN_HOME and MAILMAN_WRAP already
set.
Thanks!
I have just completed a new announcement list script.
I find that this is more complete and flexible than the current ones
which I could find on the net. Also, unlike all the other scripts, this
doesn't require bash (only sh), so it should be more cross platform, and
save people from having to install bash on systems which don't have it
on a default install.
Thanks Patrick for steering me on the right path earlier for setting the
moderation bit for a user.
Feel free to use it for whatever purpose if you wish to do so, also, you
can link to it at
http://www.netera.ca/mailinglists/MakeAnnounce.shhttp://www.netera.ca/mailinglists/changemod.py
--
Matthew Clarkson
from Mailman import mm_cfg
from Mailman.Errors import NotAMemberError
def setMemberModeratedFlag (mlist, addr, mod):
mlist.setMemberOption (addr, mm_cfg.Moderate, mod)
mlist.Save()
#!/bin/sh
#-----------------------------------------------------------------------------
#
# Mailman Announce Script
# Apr 26 2006 - Matthew Clarkson (matt _at_ netera (dot) ca)
#
# This script will create an announce list out of specified mailing lists
# I have used two other scripts as a basis for this one, however, I find
# that this is much more flexible, and easier to use after set up.
# This script also uses sh, so you don't have to rely on a computer
# to have bash, unlike the other scripts, which makes it a bit friendlier
# to cross platform setups
#
# The reference scripts that I used are found at
# http://mail.python.org/pipermail/mailman-users/2005-February/042392.html
# http://mail.python.org/pipermail/mailman-users/2005-February/042392.html
#
# This script requires one other file to operate
# changemod.py, place this file in ~mailman/bin
#
# In order to operate, the list must be created first, with appropriate
# settings, I would recommend the following be selected
#
# /admin/netera-announce-l/general
# send_reminders -> No
# send_welcome_msg -> No
# send_goodbye_msg -> No
# /admin/<listname>/privacy/sender
# default_member_moderation -> Yes
# member_moderation_action -> ( Reject | Discard )
# generic_nonmember_action -> Discard
#
# This script uses the following files (I will use announce-l as my list)
#
# announce-l - list of mailing lists in mailman
# announce-l.extra - list of additional email address'
# announce-l.allow - list of email address' of people who can post
# the list
#
# The files must have the same name as the list itself, all files must
# be plaintext
#
#-----------------------------------------------------------------------------
# General Usage message, it exits right after this is called
usage()
{
echo 1>&2 "usage: ./MakeAnnounce <filename>"
exit 127
}
# We must have one, and only 1 argument for this script, other wise print
# the usage mssage to the user, and exit
if [ $# -ne 1 ]; then
usage
fi
# We must get the filename directly, since we want the list name, and not
# a name like /path/to/announce-l
filename=`basename $1`
# Make sure that there is a corresponding list for the filename, if not, print
# usage message and exit
EXISTS="`~mailman/bin/list_lists | grep -i $filename`"
if [ -z "$EXISTS" ]; then
usage
fi
# Loop through the main file, collecting all address' from all the lists in
# the main file, and then adding them to /tmp/<listname>.tmp
while read -r current_line
do
# to verify that the list exists (using bin/list_lists)
EXISTS="`~mailman/bin/list_lists | grep -i $current_line | \
awk '{print $1 }'`"
# if the list does not exist, print an error and continue on with the
# next line
if [ -z "$EXISTS" ]; then
printf "ERROR: %s does not exist\n" "$current_line"
else
# add every address in the current list to the announce file
printf "Adding %s to list\n" "$current_line"
`~mailman/bin/list_members $current_line >> \
/tmp/$filename.tmp`
fi
done < $1
# if the .extra file exists, then add every address in this file to the
# announce file
if [ -f "$1.extra" ]; then
while read -r current_line
do
`echo $current_line >> /tmp/$filename.tmp`
done < $1.extra
fi
# sort the list alphabetically and remove duplicates. sync_members will remove
# all duplicates, so the '-u' can be removed, although, it's easier to go
# through the text file when there are no dupes, if you ever want to do that.
cat /tmp/$filename.tmp | sort -u > /tmp/$filename.tmp.final
# add all address' in the .tmp.final file. This also removes all address' from
# the list which are not in the .tmp.final file, output goes to /dev/null
~mailman/bin/sync_members -f /tmp/$filename.tmp.final $filename > /dev/null
# now we set the moderation bit to every user that is in the .allow file
if [ -f "$1.allow" ]; then
while read -r current_line
do
# see if user exists in the announce .tmp.final file
EXISTS="`~mailman/bin/list_members $filename | \
grep -i $current_line`"
# if the user is not in this file, then display an error message
if [ -z "$EXISTS" ]; then
printf "ERROR: %s is not a member\n" "$current_line"
# if the user is in the file, then unset their moderator bit
else
`~mailman/bin/withlist -q -l -r \
changemod.setMemberModeratedFlag \
$filename $current_line ''`
fi
done < $1.allow
fi
# remove our working files
rm /tmp/$filename.tmp
rm /tmp/$filename.tmp.final
> Andy wrote:
> >
> >After installing and running Mailman no Mailman web page is visible (no list
> >has been created yet, though).
> >What can be wrong?
>
> You can't run Mailman without at least the site list (mailman).
> mailmanctl won't start.
>
> However, this is not your problem as the web interface doesn't require
> mailmanctl and the qrunners to be running.
>
> See <http://www.list.org/mailman-install/node10.html>.
Thanks for your reply. The admin tried everything he could and it still does
not work. He has virtual hosts, and he suspects that perhaps Mailman cannot
work with virtual hosts, only with proper WWW servers.
Can you please confirm?
Andy
Is there a way to set the moderation bit (on/off) for a user on a
specific list by the command line?
The closest thing I have found is on
http://mail.python.org/pipermail/mailman-users/2005-February/042392.html
but I would like to stay away from using a python script like this if
possible.
--
Matthew Clarkson