I want all mails sent to the list to come from the list's email address...
But, in this case, if the user forgets to sign their name at the
bottom of their mail body, effectively the mail to the list is
anonymous...!
Is there a way to add the user name (or email address) to the top of
each mail so that the mails have the name of the sender, while the
mail itself comes from the list address?
I have looked high and low for an answer, but noone seems to have the solution.
Thank you!
Mal
Hi,
I received the following error this morning. So I rerun configure again with the following command: ./configure --with-cgi-id=apache --prefix=/var/mailman. I'm still getting the same error. Is there any place that I can look for so that I can debug this problem better? Perhaps, looking at the config history file or something. Any other places that I can check the cause of this error?
"Mailman CGI error!!!
The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog:
Group mismatch error. Mailman expected the CGI
wrapper script to be executed as group "nobody", but
the system's web server executed the CGI script as
group "apache". Try tweaking the web server to run the
script as group "nobody", or re-run configure,
providing the command line option `--with-cgi-gid=apache'."
Thanks
Mary
Hi - I have searched FAQ and archives to find an answer. Hoping you can
help.
I have a new list (with previously imported addresses) for announcements
only, and wish these announcements to be received immediately.
I set the defaults to allow non-digest and to not allow digest.
I wish to send out announcements in html, and so wish to make the
default for new subscribers be MIME. While I see a setting under Digest
Options (MIME_is_Default_Digest), I don't see any equivalent option
under Non-Digest Options... and new subscribers continue to come in as
plain text.
QUESTIONS:
In order to avoid having to manually change this option for each
existing subscriber, is there a way to force all existing subscribers to
receive MIME in Non-Digest mode?
If not, is there a way to force all NEW subscribers to be enrolled with
MIME as their default?
Also, is there a way to "lock" the MIME switch on, so that users who try
to change their option to plain text will be prevented from doing so?
Thanks -
Steve
I'm getting regular mailman crashes every 2-4 weeks. I've had 4 so
far. I'm running a centos VPS with mailman 2.1.13.
What is the best way to restart mailman? I've been restarting the
entire vps, which obviously is a bad idea. What can I do to prevent
this from happening?
Here is the error log entries from when it crashed:
Oct 13 01:30:23 2010 mailmanctl(19680): No child with pid: 3683
Oct 13 01:30:23 2010 mailmanctl(19680): [Errno 3] No such process
Oct 13 01:30:23 2010 mailmanctl(19680): Stale pid file removed.
Oct 13 01:30:23 2010 mailmanctl(19694): Traceback (most recent call last):
Oct 13 01:30:23 2010 mailmanctl(19694): File
"/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 548, in ?
Oct 13 01:30:23 2010 mailmanctl(19694): main()
Oct 13 01:30:23 2010 mailmanctl(19694): File
"/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 367, in main
Oct 13 01:30:23 2010 mailmanctl(19694): check_for_site_list()
Oct 13 01:30:23 2010 mailmanctl(19694): File
"/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 277, in
check_for_site_list
Oct 13 01:30:23 2010 mailmanctl(19694): sitelist =
MailList(sitelistname, lock=0)
Oct 13 01:30:23 2010 mailmanctl(19694): File
"/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 115, in
__init__
Oct 13 01:30:23 2010 mailmanctl(19694): execfile(filename, dict)
Oct 13 01:30:23 2010 mailmanctl(19694): File
"/usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py", line 5, in ?
Oct 13 01:30:23 2010 mailmanctl(19694): from
Mailman.MysqlMemberships import MysqlMemberships
Oct 13 01:30:23 2010 mailmanctl(19694): File
"/usr/local/cpanel/3rdparty/mailman/Mailman/MysqlMemberships.py", line
49, in ?
Oct 13 01:30:23 2010 mailmanctl(19694): import MySQLdb
Oct 13 01:30:23 2010 mailmanctl(19694): File
"build/bdist.linux-x86_64/egg/MySQLdb/__init__.py", line 19, in ?
Oct 13 01:30:23 2010 mailmanctl(19694): File
"build/bdist.linux-x86_64/egg/_mysql.py", line 7, in ?
Oct 13 01:30:23 2010 mailmanctl(19694): File
"build/bdist.linux-x86_64/egg/_mysql.py", line 4, in __bootstrap__
Oct 13 01:30:23 2010 mailmanctl(19694): File
"/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py",
line 881, in resource_filename
Oct 13 01:30:23 2010 mailmanctl(19694): return
get_provider(package_or_requirement).get_resource_filename(
Oct 13 01:30:23 2010 mailmanctl(19694): File
"/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py",
line 1351, in get_resource_filename
Oct 13 01:30:23 2010 mailmanctl(19694):
self._extract_resource(manager, self._eager_to_zip(name))
Oct 13 01:30:23 2010 mailmanctl(19694): File
"/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py",
line 1372, in _extract_resource
Oct 13 01:30:23 2010 mailmanctl(19694): real_path =
manager.get_cache_path(
Oct 13 01:30:23 2010 mailmanctl(19694): File
"/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py",
line 962, in get_cache_path
Oct 13 01:30:23 2010 mailmanctl(19694): self.extraction_error()
Oct 13 01:30:23 2010 mailmanctl(19694): File
"/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py",
line 928, in extraction_error
Oct 13 01:30:23 2010 mailmanctl(19694): raise err
Oct 13 01:30:23 2010 mailmanctl(19694): pkg_resources . ExtractionError
: Can't extract file(s) to egg cache
The following error occurred while trying to extract file(s) to the
Python egg
cache:
[Errno 13] Permission denied: '/root/.python-eggs'
The Python egg cache directory is currently set to:
/root/.python-eggs
Perhaps your account does not have write access to this directory? You can
change the cache directory by setting the PYTHON_EGG_CACHE environment
variable to point to an accessible directory.
Oct 13 01:30:23 2010 mailmanctl(19694):
Oct 13 01:31:11 2010 mailmanctl(22029): PID unreadable in:
/usr/local/cpanel/3rdparty/mailman/data/master-qrunner.pid
Oct 13 01:31:11 2010 mailmanctl(22029): [Errno 2] No such file or
directory: '/usr/local/cpanel/3rdparty/mailman/data/master-qrunner.pid'
Oct 13 01:31:11 2010 mailmanctl(22029): Is qrunner even running?
Oct 13 01:31:14 2010 mailmanctl(22123): Traceback (most recent call last):
Oct 13 01:31:14 2010 mailmanctl(22123): File
"/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 548, in ?
Oct 13 01:31:14 2010 mailmanctl(22123): main()
Oct 13 01:31:14 2010 mailmanctl(22123): File
"/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 367, in main
Oct 13 01:31:14 2010 mailmanctl(22123): check_for_site_list()
Oct 13 01:31:14 2010 mailmanctl(22123): File
"/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 277, in
check_for_site_list
Oct 13 01:31:14 2010 mailmanctl(22123): sitelist =
MailList(sitelistname, lock=0)
Oct 13 01:31:14 2010 mailmanctl(22123): File
"/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 115, in
__init__
Oct 13 01:31:14 2010 mailmanctl(22123): execfile(filename, dict)
Oct 13 01:31:14 2010 mailmanctl(22123): File
"/usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py", line 5, in ?
Oct 13 01:31:14 2010 mailmanctl(22123): from
Mailman.MysqlMemberships import MysqlMemberships
Oct 13 01:31:14 2010 mailmanctl(22123): File
"/usr/local/cpanel/3rdparty/mailman/Mailman/MysqlMemberships.py", line
49, in ?
Oct 13 01:31:14 2010 mailmanctl(22123): import MySQLdb
Oct 13 01:31:14 2010 mailmanctl(22123): File
"build/bdist.linux-x86_64/egg/MySQLdb/__init__.py", line 19, in ?
Oct 13 01:31:14 2010 mailmanctl(22123): File
"build/bdist.linux-x86_64/egg/_mysql.py", line 7, in ?
Oct 13 01:31:14 2010 mailmanctl(22123): File
"build/bdist.linux-x86_64/egg/_mysql.py", line 4, in __bootstrap__
Oct 13 01:31:14 2010 mailmanctl(22123): File
"/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py",
line 881, in resource_filename
Oct 13 01:31:14 2010 mailmanctl(22123): return
get_provider(package_or_requirement).get_resource_filename(
Oct 13 01:31:14 2010 mailmanctl(22123): File
"/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py",
line 1351, in get_resource_filename
Oct 13 01:31:14 2010 mailmanctl(22123):
self._extract_resource(manager, self._eager_to_zip(name))
Oct 13 01:31:14 2010 mailmanctl(22123): File
"/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py",
line 1372, in _extract_resource
Oct 13 01:31:14 2010 mailmanctl(22123): real_path =
manager.get_cache_path(
Oct 13 01:31:14 2010 mailmanctl(22123): File
"/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py",
line 962, in get_cache_path
Oct 13 01:31:14 2010 mailmanctl(22123): self.extraction_error()
Oct 13 01:31:14 2010 mailmanctl(22123): File
"/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py",
line 928, in extraction_error
Oct 13 01:31:14 2010 mailmanctl(22123): raise err
Oct 13 01:31:14 2010 mailmanctl(22123): pkg_resources . ExtractionError
: Can't extract file(s) to egg cache
The following error occurred while trying to extract file(s) to the
Python egg
cache:
[Errno 13] Permission denied: '/root/.python-eggs'
The Python egg cache directory is currently set to:
/root/.python-eggs
Perhaps your account does not have write access to this directory? You can
change the cache directory by setting the PYTHON_EGG_CACHE environment
variable to point to an accessible directory.
Oct 13 01:31:14 2010 mailmanctl(22123):
--
Energy Justice Communities Map Developer - http://www.energyjustice.net/map
On 10/29/2010 8:11 AM, André van Kan wrote:
> Hi Larry,
>
> Although we have the same problem, ours is even weird in
> some aspects. I made an test-list - groep3 - with two members.
> If mail is send by a non-member, all messages are discarded
> after approval:
>
> Oct 29 15:59:09 2010 (20460) groep3: Discarded posting:
> From: acvankan(a)gmail.com
> Subject: test after restart
> Oct 29 16:04:30 2010 (21937) groep3: Discarded posting:
> From: acvankan(a)gmail.com
> Subject: last one
Please post to the list, not to me personally.
However, the above messages, presumably from Mailman's vette log, come
from two different PIDs. Thus, I'm guessing that you are approving these
messages via the admindb web interface, and something is going wrong in
that process resulting in the message being discarded by the admindb CGI
itself.
> BUT if messages are sent by senders as mentioned in [Sender Filters] /
> "List of non-member addresses whose postings should be automatically accepted"
> THEN messages are delivered (of course without the necessity of approval).
>
> Since the vette-contents is rather concise, I editted
> IncomingRunner.py'sErrors.DiscardMessage as follows, according
> a earlier posting about this subject:
> syslog('vette', 'Message discarded, msgid: %s, handler: %s',
> msg.get('message-id', 'n/a'), handler)
> but to no avail. Nothing changes in the output-format.
Because the message is not discarded by IncomingRunner. It is discarded
by the HandleRequest method in Mailman/ListAdmin.py called from
Mailman/Cgi/admindb.py.
> Since all our lists suffer the same problem, a generic
> configuration error may be assumed, but I've no idea
> how to fix it. Any hint would be gratly appreciated.
Have you modified admindb.py in any way?
Does the web admin interface work?
What Mailman version is this?
How exactly are you approving messages?
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
(Apologies for re-raising a topic I asked about here a couple of years
ago. The instructions on Sourceforge have changed a bit since then.)
New server runs OpenBSD 4.7, postfix 2.65, mailman 2.1.14, and virtual
domains. Mail sent to/from virtual domains works fine.
Different story with Mailman. Although postfix says a message addressed
to a list is "sent" to all addresses, subscribers from virtual domains
on this server do not receive the message. Subscribers on other domains
not on this server do receive the message. There's no indication of
trouble in the Mailman logs or in maillog.
I've followed the setup instructions here, doing section 6.1.2 before
6.1.1 (given the link about doing virtual stuff first):
http://mailman.sourceforge.net/mailman-install/postfix-virtual.htmlhttp://mailman.sourceforge.net/mailman-install/postfix-integration.html
I've pasted the config files below.
Thanks in advance for clues on getting Mailman to deliver to virtual
addresses on this server.
dn
server hostname:
mail.domain1.tld
virtual domains:
domain1.tld # (not its real name!)
domain2.tld
domain3.tld
-----
from /etc/postfix/main.cf:
..
myhostname = mail.domain1.tld
mydomain = domain1.tld
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
..
alias_maps = hash:/etc/mail/aliases, hash:/usr/local/mailman/data/aliases
virtual_alias_maps =
proxy:mysql:/etc/postfix/sql/forwardings.cf
proxy:mysql:/etc/postfix/sql/email2email.cf
hash:/usr/local/mailman/data/domain1-tld
hash:/usr/local/mailman/data/virtual-mailman
-----
from /usr/local/mailman/Mailman/mm_cfg.py:
MTA = 'Postfix'
MAILMAN_SITE_LIST = 'mailman'
DEFAULT_EMAIL_HOST = 'domain1.tld'
DEFAULT_URL_HOST = 'mail.domain1.tld'
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'
IMAGE_LOGOS = '/icons/'
POSTFIX_ALIAS_CMD = '/usr/local/sbin/postalias'
POSTFIX_MAP_CMD = '/usr/local/sbin/postmap'
POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'domain2.tld', 'domain3.tld' ]
# Clear the Defaults.py VIRTUAL_HOSTS entry
VIRTUAL_HOSTS.clear()
add_virtualhost('DEFAULT_EMAIL_HOST', 'DEFAULT_URL_HOST')
add_virtualhost('domain2.tld', 'domain2.tld')
add_virtualhost('domain3.tld', 'domain3.tld')
-----
/usr/local/mailman/data/aliases
# The ultimate loop stopper address
mailman-loop: /usr/local/mailman/data/owner-bounces.mbox
# STANZA START: mailman
# CREATED: Sat Oct 30 11:23:37 2010
mailman: "|/usr/local/mailman/mail/mailman post mailman"
mailman-admin: "|/usr/local/mailman/mail/mailman admin mailman"
mailman-bounces: "|/usr/local/mailman/mail/mailman bounces mailman"
mailman-confirm: "|/usr/local/mailman/mail/mailman confirm mailman"
mailman-join: "|/usr/local/mailman/mail/mailman join mailman"
mailman-leave: "|/usr/local/mailman/mail/mailman leave mailman"
mailman-owner: "|/usr/local/mailman/mail/mailman owner mailman"
mailman-request: "|/usr/local/mailman/mail/mailman request mailman"
mailman-subscribe: "|/usr/local/mailman/mail/mailman subscribe mailman"
mailman-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe mailman"
# STANZA END: mailman
# STANZA START: s
# CREATED: Sat Oct 30 11:35:12 2010
s: "|/usr/local/mailman/mail/mailman post s"
s-admin: "|/usr/local/mailman/mail/mailman admin s"
s-bounces: "|/usr/local/mailman/mail/mailman bounces s"
s-confirm: "|/usr/local/mailman/mail/mailman confirm s"
s-join: "|/usr/local/mailman/mail/mailman join s"
s-leave: "|/usr/local/mailman/mail/mailman leave s"
s-owner: "|/usr/local/mailman/mail/mailman owner s"
s-request: "|/usr/local/mailman/mail/mailman request s"
s-subscribe: "|/usr/local/mailman/mail/mailman subscribe s"
s-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe s"
# STANZA END: s
-----
/usr/local/etc/mailman/data/domain1-tld:
domain1.tld IGNORE
@domain1.tld @mail.domain1.tld
-----
/usr/local/mailman/data/virtual-mailman:
# LOOP ADDRESSES START
mailman-loop(a)domain1.tld mailman-loop
# LOOP ADDRESSES END
# STANZA START: s
# CREATED: Sat Oct 30 11:35:12 2010
s(a)domain1.tld s
s-admin(a)domain1.tld s-admin
s-bounces(a)domain1.tld s-bounces
s-confirm(a)domain1.tld s-confirm
s-join(a)domain1.tld s-join
s-leave(a)domain1.tld s-leave
s-owner(a)domain1.tld s-owner
s-request(a)domain1.tld s-request
s-subscribe(a)domain1.tld s-subscribe
s-unsubscribe(a)domain1.tld s-unsubscribe
# STANZA END: s
-----
Hello,
We are changing student email from mailboxes, to forwarding addresses. Among other challenges, we are exploring various ways to deal with students who are subscribed to closed (only subscribers may post) mailing lists.
(There are a lot of similar challenges when switching to an email forwarding model - any list members who have gone through this, I would love to pick your brain!)
One possibility we're exploring, is to change a student's mailing list subscriptions, when they change their forwarding address. We would iterate through these address changes and run clone_member, like:
Clone_member --remove --admin old(a)our.domain new(a)outside.domain
We could end up processing as many as 500 address changes nightly (running clone_member for each one), with each run of clone_member iterating through all mailing lists. I'm concerned that this is much more than clone_member was intended for.
Can Mailman developers or heavy uses of Mailman comment on this?
Thanks very much,
Ivan.
Greetings,
We had a series of longer than battery outages on wednesday, and
when we came back online, mailman refused to run. Heres the messages:
mailman# tail -f error
Oct 30 02:28:06 2010 (11862) couldn't load config file
/usr/mailman/lists/[listname]/config.pck.last 1778451844
Oct 30 02:28:06 2010 (11862) couldn't load config file
/usr/mailman/lists/[listname]/config.db
[Errno 2] No such file or directory:
'/usr/mailman/lists/[listname]/config.db'
Oct 30 02:28:06 2010 (11862) couldn't load config file
/usr/mailman/lists/[listname]/config.db.last
[Errno 2] No such file or directory:
'/usr/mailman/lists/[listname]/config.db.last'
Oct 30 02:28:06 2010 (11862) All [listname]B fallbacks were corrupt,
giving up
Oct 30 02:28:06 2010 (11862) error opening list: [listname]
[Errno 2] No such file or directory:
'/usr/mailman/lists/[listname]/config.db.last'
Please tell me theres a reasonable recovery for this on 2.1.21 (plus a
patch)?
Thanks!
//Alif
--
"Never belong to any party, always oppose privileged classes and public
plunderers, never lack sympathy with the poor, always remain devoted to
the public welfare, never be satisfied with merely printing news, always
be drastically independent, never be afraid to attack wrong, whether by
predatory plutocracy or predatory poverty."
Joseph Pulitzer, 1907 Speech
Hi,
we recently moved our Mailman server from a RHEL 3 machine running Mailman
2.1.9 to a RHEL 5 system running Mailman 2.1.14. Everything went very
smoothly, but today I noticed one small issue. For various reasons we use
'lists.uni-koeln.de' as URL_HOST, but as EMAIL_HOST we use 'uni-koeln.de'.
So the address for the sitelist is mailman(a)uni-koeln.de. On the old system
we were able to receive mail for @lists.uni-koeln.de addresses as well, but
on the new system we can't. But the listinfo CGI uses
mailman(a)lists.uni-koeln.de as the site address. I checked out the code, but
didn't really understand it – I'm more of a Perl guy ;)
def get_site_email(hostname=None, extra=None):
if hostname is None:
hostname = mm_cfg.VIRTUAL_HOSTS.get(get_domain(), get_domain())
if extra is None:
return '%s@%s' % (mm_cfg.MAILMAN_SITE_LIST, hostname)
return '%s-%s@%s' % (mm_cfg.MAILMAN_SITE_LIST, extra, hostname)
Shouldn't that use the DEFAULT_EMAIL_HOST instead? I fixed our specific
problem by hardcoding the return value, but it seems to me that could be a
more general issue ...
Thanks, Sebastian
--
.:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:.
.:.Regionales Rechenzentrum (RRZK).:.
.:.Universität zu Köln / Cologne University - ✆ +49-221-478-5587.:.
Barry Finkel wrote:
>>I have a customer who wants a announce-only list. She does not want
>>any replies to the list or to the poster.
>>
>>In production we are running 2.1.13, and I have 2.1.14 on my test
>>machine. We made the list anonymous
>>
>> anonymous_list = yes
Mark Sapiro replied:
>Why, Is this needed or is it just an attempt to make replies not go to
>the poster?
This is a mailing to a club membership, and is for announcements only.
The one or two people who will do the monthly postings do not want to
get replies sent to their mailboxes, and they do not want replies sent
back to the list. They have changed the list footer to read:
All mail/replies should be sent to <xxx>.
where "<xxx>" is another list for the club officers where anyone can
post.
----------------------------------------------------------------------
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory Phone: +1 (630) 252-7277
9700 South Cass Avenue Facsimile:+1 (630) 252-4601
Building 240, Room 5.B.8 Internet: BSFinkel(a)anl.gov
Argonne, IL 60439-4828 IBMMAIL: I1004994