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
On 05/10/2013 06:35 AM, Xie, Wei wrote:
>
> Here we have one customer to request migrating all old archived files of
> mailing list ‘kinejapan’ under directory
> /usr/local/mailman/archives/private/kinejapan prior to 2009 (as attached
> file) to Yale university. Yale university IT guys needs us to create a
> mbox file for these old archived file to be easy for them to run
> command ‘archdo migration.
>
>
>
> I check there is no file kinejapan.mbox under directory
> /usr/local/mailman/archives/private/kinejapan.mbox to match these old
> archived files as attached. This mailing list was maintained by our
> pre-mailman admin, who passed away 2011, so I do not know why the mbox
> file was missing.
If ARCHIVE_TO_MBOX is set to 0 in mm_cfg.py, Mailman will not
create/update LISTNAME.mbox/LISTNAME.mbox files.
> Do you know whether there is a tool/method to convert these old archived
> files/directories as attached into a mbox file?
Lots of information is lost if there is no .mbox file.
You can do as well as anything with
cat /usr/local/mailman/archives/private/kinejapan/*.txt > kinejapan.mbox
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
Is there anything open-source to make a Mailman legacy archive searchable?
What would be useful is a way for visitors to a website to be able to
search the Mailman archives using a keyword and have it display those mail
messages. I'm also thinking of having a tag cloud made up of the most
commonly used words from the given Mailman archive. So when one of those
tag cloud words is clicked on it lists as an index those messages. Any
suggestions? Thanks!
David Roth
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,
My mailing lists run on a relay server installed as per FAQ 4.88
Accessing the web interface across the internet works fine but accessing
while on the host network is not so fine.
Instead of the DSL (dyndns) address I use the server name or IP address
and all goes fine unless I query the mailing list addresses. Then i am
returned to login again and so on ad infinitum. Same if I try to list
them.
I note that when I mouse-over the menu options the browser bottom line
shows the server name (or IP) address that I have used. When I
mouse-over the 0-9A-Z membership listing then the DSL forwarding address
shows.
FAQ 4.29 would indicate that I could change the DEFAULT_URL_HOST setting
for existing lists using fix_url.py - in this case perhaps to the IP
address?
I suppose that would foul up admin access from across the internet but
as that is only me we could live with that.
Before fools rush in where angels fear to tread - is this the way to go?
Maybe there is a route to have the best of both worlds (easy access from
the internet and the local network)
many thanks in advance
anotheranne
FYI, I will be releasing 2.1.16rc1 in a few days with a target of a
final release in early September.
I believe the release will be very solid and stable. The main purpose of
the candidate release is to expose any i18n changes so that translators
can submit any updates and get them in the final release. There are a
few new features, contributed programs, i18n changes and bug fixes, all
of which will be announced when the candidate is released.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
We are seeing messages get dropped after passing through moderation on every one of our mailing lists.
== Moderation fails when performed on a *separate* webserver ==
Our Mailman environment is split across two servers, front-end and back-end. The back-end server handles Postfix and the Mailman qrunners, while the front-end server hosts Apache and the Mailman CGI scripts for moderating lists. The two servers share an NFS mount between them that includes all the shared Mailman data. All normal mail flow is working correctly, but when a list moderator logs into the web frontend and approves a message, it disappears without a trace.
1. Postfix smtpd receives the incoming message over SMTP, then
2. Postfix smtpd delivers the message to /usr/lib/mailman/mail/mailman.
3. Mailman marks writes to vette logfile (backend server) that message is held for approval.
4. List moderator uses CGI web interface to mark the message as approved.
5. Mailman writes an entry to vette logfile (on frontend server) saying held message approved.
6. At this point, the .pck file related to the held message disappears, but nothing is delivered, and no further log entries are created.
== Moderation succeeds with web interface on the main Mailman server ==
Although we don't normally run the Mailman web interface on the back-end server (to reduce attack surface), I got it running for testing purposes. When we use the Mailman web interface on the backend server, the message gets delivered normally and we see these log entries as expected.
1. smtp logfile updated with number of recipients and time for completion
2. post logfile updated with list name, message ID, and "success".
== Background ==
The problem started after migrating the Mailman environment to new servers. It didn't crop up on it's own, it's most likely a result of some configuration error that we haven't caught yet. We're using:
- Scientific Linux 6.3 on both servers
- Python 2.6.6 on both servers
- Mailman 2.1.12 installed from OS packages on both servers
- selinux in Permissive mode on backend server
- selinux in Enforcing mode on frontend (web) server, but no log entries with type=AVC are being recorded. Furthermore, using setenforce 0 doesn't fix the problem.
I'm not sure where to look next. Is it supported to run the Mailman frontend on a different server? What are the common points of failure when running a Mailman setup this way?
--
Nic Waller
System Administrator
Phone 250-960-5919
Office ADM 3-2078B
Information Technology Services
University of Northern British Columbia
Hi,
i have a problem with a pending moderation request. Whenever i chose one of the four options for the pending email and submit the form, the page reloads and is still showing this email as pending.
I did not find anything valuable in the log files, but i executed a check_perms to see if mailman can't moderate this email because of a filesystem permission problem.
I don't know where to search for the bug, so i hope, anyone around here could help me.
Thank you very much in advance.
Simon
All --
Anything to be particularly aware of when moving a list from 2.1.11 on a Mac server (where I ignored the Apple pre-installed version of Mailman and set up a new installation from the Mailman source so at least the components are where they are supposed to be, OS X 10.5.8 [!] ) to a Linux server running RHEL 5.x and Mailman 2.1.9.
I wouldn't prefer to downgrade, but consolidation of mailman to a single machine is going to be helpful in the long run. Unfortunately for me, I'm going from the Mac server where I have full control to a Linux server operated by a partner organization where I have somewhat less control in that I can't upgrade Mailman from the RHEL release version.
I've read through the FAQ 3.4 at <http://wiki.list.org/pages/viewpage.action?pageId=4030682> which seems to indicate that it will generally be OK, but I'm looking for any changes that make my 2.1.11 list (which is in Cyrillic, by the way) not work well on the 2.1.9 installation (which does mostly English, and some Spanish & Portuguese, but nothing from a non-Roman alphabet right now).
Thanks,
Drew Tenenholz