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
Today I check the subscribers list ("Membership Management...
Section") on one of our lists and called up
the legend using "Click here to include the legend for this table."
After clicking on that link, the page did indeed display the legend,
but the page now starts with:
Error: The form lifetime has expired. (request forgery check)
--
Ralf Hildebrandt Charite Universitätsmedizin Berlin
ralf.hildebrandt(a)charite.de Campus Benjamin Franklin
http://www.charite.de Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155
Hello
some of my list are being spammed with bot subscription request. I am
looking for a way to add a hidden field to the subscription page of each
list that a bot would see but a human user will not.
I would like to have Mailman automatically drop any subscription request
that has the hidden field fill out.
below is the subscription area for the list and I have added the subject
field. the subject field is what i would like to hide and have drop the
request.
Subscribe-Box>
</font>
</TD>
<TD WIDTH="12%"><font face="Verdana" size="2"> </font></TD></TR>
<tr>
<td bgcolor="#dddddd" width="55%"><font face="Verdana"
size="2">Your name & City/Company (required):</font></td>
<td width="33%"><font face="Verdana"
size="2"><mm-fullname-box></font></td>
<TD WIDTH="12%"><font face="Verdana" size="2"> </font></TD></TR>
<TR>
<td bgcolor="#dddddd" width="55%"><font face="Verdana" size="2">Subject
(required):</font></td>
<td width="33%"><font face="Verdana"
size="2"><mm-fullname-box></font></td>
<TD WIDTH="12%"><font face="Verdana" size="2"> </font></TD></TR>
<TR>
I am new to HTML and this is as far as i can get at the moment. If anyone
has any suggestions I would greatly appreciate it. I am running Mailman on
a Linux server.
Thank you
Doug
On 2/21/2013 2:35 AM, Máire Jones wrote:
>
> Yes, these are two different questions. In the first I was wondering if
> it is possible to allow any address from @domain post to each and every
> mailman list on our mailman server. \\
Assuming you don't want to just add a regexp to accept_these_nonmembers
to all lists which is easy to do, at least for existing lists, with the
script at <http://www.msapiro.net/scripts/non_members>, you would need
to do this with a custom handler which would set approved=True in the
message's metadata if the sender was from the white listed domain.
The problem with this approach is that the custom handler would have to
be in the pipeline prior to Moderate to avoid list membership tests, and
this would also then bypass all the miscellaneous holds such as too many
recipients, implicit destination, too big, administrivia, etc.
See the FAQ at <http://wiki.list.org/x/l4A9> for info on custom handlers.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
We recently upgraded Mailman from 2.1.13 on Solaris 10 to 2.1.15 on
RHEL6. We are seeing an issue now where when posts are held for
moderator approval, they show up in the pending requests webpage, but
you can't take any action on them. Defer/Reject/Allow/Discard... no
matter what you choose, the page just refreshes without anything
actually happening. The kicker is that this only occurs on lists that
were created in the new environment, the lists that we transferred over
from 2.1.13 work just fine.
When I delete the heldmsg-<LISTNAME>-##.pck manually, the held message
disappears from the "held for approval" page. However, new held
messages exhibit the same problems. Other messages sent to the listserv
that don't ever get held, are delivered to the members just fine.
We've compared config.pck files between an old and new lists and the
only difference we have seen is that all of the 0's are now "False" and
the 1's are now "True".
There have not been any HTML changes to the files in question. We have
run check_perms and it has come back with NO errors.
Mailman Version: 2.1.15
Python Version: 2.6.6
RHEL Version: 6.2
Kernel Version: 2.6.32-220.13.1.el6.x86_64
Apache Version: 2.2.15
Thank you in advance for your assistance,
Breeze
--
Breeze P. Howard bhoward(a)fsu.edu (850)645-8008
Email and Linux Administrators its-unixadmins(a)fsu.edu (850)644-2591
Information Technology Services The Florida State University
Hello,
I've been using Mailman for years and have a situation that I can't find
in docs & FAQs. I have the reply to address set to "list" and I have
senders email addresses hidden to protect privacy and prevent spam abuse.
Occasionally, I - as the administrator - need to see the actual poster
of a message sent by a member. They sent an inappropriate message, or
perhaps their email is spam virus infected and they are unknowingly
spamming. When I go to archives, all I can find in the emails is the
obfuscated information about a message, but not the actual senders email
address. If they don't sig the email, I have no way to know who they
are.
How can I find out, while maintaining privacy so that addresses are not
exposed to the list at large?
Here is a sample message header from my archives
>From jam at australianbakery.com Fri Feb 22 13:54:16 2013
From: jam at australianbakery.com (Aussie Bakery Jam)
Date: Fri, 22 Feb 2013 15:54:16 -0500
Subject: [Aussie BG Jam] Musicians needed
Message-ID: <mailman.7.1361566462.28962.jam_australianbakery.com(a)host414.hostmonster.com>
Thanks very much, and if I've overlooked the answer already posted, sorry.
regards,
Greg
--
Protect your privacy <http://donttrack.us/> & break out of the bubble
<http://dontbubble.us/> - Search with DuckDuckGo <https://duckduckgo.com/>
We receive an error "We're sorry, we hit a bug!" Upon inspection, we found that we run out of space on the server. We found that the error log file in /usr/local/mailman/logs grows rapidly. We delete one a couple days ago at 33GB in size. 3 days pass and it grows to 11GB.
How do we check if verbose logging is on?
Thank you,
Hi all,
I have just got started with mailman and have noticed that
in non digest mode subscribers recieve posts from ie in
their mail client FROM: field
listname@domain
but in digest mode from;
listname-request@domain
I would prefer the former for both but cant seem to find how
to change this?
Thanks!
I have not made any changes (intentionally) to mailman in many months
but suddenly mail from the list has listname-bounces as the from header
rather then the original poster. I have to assume that one of my CentOS
updates changed something, although I don't recall seeing any automatic
updates to mailman. I can't seem to find where to set that header. In
any case wherever I set it before must have been wrong for an update to
overwrite it (assuming that is what caused this).
Also, I'm guessing this is related, bounced messages are now being
handled as uncaught bounces.
The attached message was received as a bounce, but either the bounce
format was not recognized, or no member addresses could be extracted
from it. This mailing list has been configured to send all
unrecognized bounce messages to the list administrator(s).
This is in spite of the fact that the reason for the bounce and the bad address are quite clear in the bounced message (sanitized).
Sorry, we were unable to deliver your message to the following address.
<******(a)aol.com>:
Remote host said: 550 5.1.1 <*******(a)aol.com>: Recipient address rejected: aol.com [RCPT_TO]
If the reason is because that address is not a recognized member address, then how did it get sent there in the first place? The content was indeed a list message.
Can someone help sort out what is wrong and how to prevent it in the future? Thanks.