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 am running mailman on one machine which hosts several different
virtual hosts. However what I configured as the "mailman" virtual host
is "lists.myhost.com". Everything works fine (mail delivery, web site
url management) except for one thing: in the web admin url, it's
rewriting the links to "myhost.com/..." instead of "lists.myhost.com".
This is causing HTTP posts when doing some admin changes to fail as it's
hitting the "myhost.com" host instead of "lists.myhost.com".
in my mm_cfg.py:
# The name of the list Mailman uses to send password reminders
# and similar. Don't change if you want mailman-owner to be
# a valid local part.
MAILMAN_SITE_LIST = 'mailman'
#-------------------------------------------------------------
# If you change these, you have to configure your http server
# accordingly (Alias and ScriptAlias directives in most httpds)
#DEFAULT_URL_PATTERN = 'http://%s/cgi-bin/mailman/'
DEFAULT_URL_PATTERN = 'http://%s/'
PRIVATE_ARCHIVE_URL = '/cgi-bin/mailman/private'
IMAGE_LOGOS = '/images/mailman/'
#-------------------------------------------------------------
# Default domain for email addresses of newly created MLs
DEFAULT_EMAIL_HOST = 'myhost.com'
#-------------------------------------------------------------
# Default host for web interface of newly created MLs
DEFAULT_URL_HOST = 'lists.myhost.com'
#-------------------------------------------------------------
# Required when setting any of its arguments.
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
mailman virtual host file
<VirtualHost *:80>
ServerName lists.myhost.com
DocumentRoot /var/www/lists
ErrorLog /var/log/apache2/lists-error.log
CustomLog /var/log/apache2/lists-access.log combined
<Directory /var/lib/mailman/archives/>
Options Indexes FollowSymLinks
AllowOverride None
</Directory>
Alias /pipermail/ /var/lib/mailman/archives/public/
Alias /images/mailman/ /usr/share/images/mailman/
ScriptAlias /admin /usr/lib/cgi-bin/mailman/admin
ScriptAlias /admindb /usr/lib/cgi-bin/mailman/admindb
ScriptAlias /confirm /usr/lib/cgi-bin/mailman/confirm
ScriptAlias /create /usr/lib/cgi-bin/mailman/create
ScriptAlias /edithtml /usr/lib/cgi-bin/mailman/edithtml
ScriptAlias /listinfo /usr/lib/cgi-bin/mailman/listinfo
ScriptAlias /options /usr/lib/cgi-bin/mailman/options
ScriptAlias /private /usr/lib/cgi-bin/mailman/private
ScriptAlias /rmlist /usr/lib/cgi-bin/mailman/rmlist
ScriptAlias /roster /usr/lib/cgi-bin/mailman/roster
ScriptAlias /subscribe /usr/lib/cgi-bin/mailman/subscribe
ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/
</VirtualHost>
hello all,
i want to temporary disable one of my mailing lists while keeping the
archives available. i run mailman 2.1.12 with sendmail. i was thinking
about doing the following:
. remove the appropriate aliases from /path/to/aliases (redirecting the
<mailling-list>-owner of the affected list to some real address)
. move the /path/to/mailman/lists/<disabled-list> directory to a
temporary location
is this the proper way to disable a list? is there anything else that
needs to be done?
greetings,
Stoyan
Hello Mailman Users,
Systers has developed the ability for a user to subscribe and unsubscribe
from threads via Dynamic Sub-Lists. We've have gsoc students working on
bug-fixes and improvements the last two years and we'd really like to make
the feature available to the larger community running 2.1.x.
Right now it's a code branch on http://launchpad.net/systers that we use to
update our production server via bzr.
We've only tested against 2.1.10.
Should we make a down-loadable .tgz of the source code? Or is it better
offered as a patch to be applied against GNU MM 2.1.10? What is the easiest
delivery method for those of you who might want to take a look at the
functionality?
You can read more here:
http://systers.org/systers-dev/doku.php/good_to_know and some
additional information about our changes at the bottom of this
page:
http://systers.org/systers-dev/doku.php/how_stuff_works_both_default_mailma…
.
Thanks,
Jen
When authorizing a moderated list posting is it possible to change the
date/time on the outgoing authorized list message to the time it was
approved instead of the message showing the time it was first received
by mailman?
Thanks
Paul
Hello all. I'm a long time Mailman user, and am the person behind the
Mailman/Joomla bridge mentioned in this Wiki article:
http://wiki.list.org/pages/viewpage.action?pageId=4030527
The "bridge" is a PHP script that runs inside my CMS (Joomla) that figures
out the user's name and email address, gets the list of mailing lists, and
then subscribes them to the mailing list(s) they specify, including setting
them to digest mode if they ask.
I do this by using the URL interface to Joomla and then doing a
"file_get_contents("$url","
FALSE")" in PHP to execute the URL with the appropriate admin password. For
example, to subscribe someone I use the following URL:
http://<domain>/mailman/admin/<listname>
/members/add?subscribe_or_invite=0&send_welcome_msg_to_this_batch=0¬ification_to_list_owner=0&subscribees_upload=
<email-address>&adminpw=<adminpassword>
This works fine (has for a few years now), and we actually documented
several of these URLs here:
http://wiki.list.org/pages/viewpage.action?pageId=4030567
The one I'm having a problem with is the one to set someone to digest mode.
First you have to subscribe them, then you would issue the following URL:
http://<domain>/mailman/admin/<listname>/members?user=<email-address>&
<email-address>
_digest=1&setmemberopts_btn=Submit%20Your%20Changes&allmodbit_val=0&
<email-address>_language=en&<email-address>_nodupes=1&adminpw=
<adminpassword>
This has also worked for a few years, but I just found out that it isn't
working. I can set someone to digest mode by manually accessing that same
page, but the URL no longer does the job. When I issue the URL manually in
my browser, instead of setting the user to digest mode and returning me to
the screen with the user on it, it returns me to the /members page,
displaying a list of users. Thinking maybe Mailman wants an option that I'm
not setting, I even made a longer list of every option that is on the page,
and that didn't work:
http://
<domain>/mailman/admin/<listname>/members?user=<email>&<email>_unsub=0&<email>_mod=0&<email>_hide=0&<email>_nomail=0&<email>_ack=0&<email>_notmetoo=0&<email>_nodupes=0&<email>_digest=1&<email>_plain=0&<email>_language=en&setmemberopts_btn=Submit%20Your%20Changes&allmodbit_val=0&adminpw=<adminpassword>
I am running the Cpanel version of Mailman, version 2.1.3, which I'm
surprised to learn is actually more recent than the version running this
mailing list (2.1.2)!
Any idea of what's going wrong or how I can troubleshoot this thing?
Thanks in advance for any ideas.
Dear all,
there is any option to notify, by email, the user when he attempts to
subscibe and list and his email bellow to ban_list?
Another question. It is possible to configure the following message
(thats appers when a ban_list users attens to subscribe by web interface
that mailling list)
so Subscription results
The email address you supplied is banned from this mailing list. If you
think this restriction is erroneous, please contact the list owners at
[EMAIL].
Thanks in advanced.
--
Ricardo Ruivo
System Administrator
SIC - Serviço de Informática e Comunicações
Department of Informatics Engineering
Faculty of Science and Technology
University of Coimbra | Portugal
My PGP Public Key is available at:
http://pgp.dei.uc.pt:11371/pks/lookup?op=get&search=0x7D4F6A4C
Hi!
I've encountered a problem regarding pending messages for the internal
mailman list for Mailman.
Each day at 8:00AM, as Mailman admin/owner I was getting a message with
the subject "6 Mailman moderator request(s) waiting". The message
mentioned accessing the URL
"http://${hostname}/cgi-bin/mailman/admindb/mailman". However, accessing
it (and typing in the requested password) revealed no pending posts
(such as those described in the message).
The latest message was dated 28th of December 2009 (quite a while ago).
About a week ago I decided to uninstall the Mailman instance but that
message is still sent each day at 8:00AM. I've reinstalled it, accessed
the above URL, but there are still no pending posts.
I've done a recursive grep in /var/lib/mailman (I'm using Debian) for
parts of the message (but found nothing). I've checked all cron entries
(/etc/cron*, /var/spool/cron/crontabs/*) but found nothing relevant.
Could someone please point me to where those pending requests are held
and how can I get rid of them and stop that message from being delivered?
Many thanks,
Razvan
