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, This problem is not caused by mailman, but I still want to give it a
shot here. I'm hosting a mailing list on top of mailman. Emails are
supposed to be sent out by AWS ses. However, ses requires that sender
address must be verified, which leads to a problem that emails sent by
subscribers to mailing list cannot be sent to other subcirbers, since their
addresses are not verified. And it is impossible to verified every
subscriber. Are there smtp service providers allowing unverified email
address to send out emails, or do I have other solutions?
Thanks.
Leon
Hi,
This is a weird one. I think of myself as knowing my way around Mailman
pretty well for a user/admin/installer/upgrader. I'm upgrading to a
Debian 9 system from CentOS 6.5. Debian's Apache configs took a bit of
getting used to, but I actually like them better. It uses Apache 2.4.2.
I wanted to install Mailman from source, since the latest version is
2.1.26, Debian has 2.1.23, and IIRC that's too old to have some screen
reader optimizations I want. So I built, installed, all working well. I
copied over the Mailman config from my CentOS system to use in Apache,
making some changes so it'd work under 2.4.2. Here it is:
--------------------
#
# httpd configuration settings for use with mailman.
#
ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/
<Directory /usr/lib/mailman/cgi-bin/>
AllowOverride None
Options ExecCGI
Require all granted
</Directory>
Alias /pipermail/ /var/lib/mailman/archives/public/
<Directory /var/lib/mailman/archives/public>
Options Indexes MultiViews FollowSymLinks
AllowOverride None
Require all granted
AddDefaultCharset Off
</Directory>
# Uncomment the following line, to redirect queries to /mailman to the
# listinfo page (recommended).
# RedirectMatch ^/mailman[/]*$ /mailman/listinfo
--------------------
The problem is that the CGI isn't working. If I go to
http://temphostname/mailman/listinfo/mailman for example, Apache says
/usr/lib/mailman/cgi-bin/listinfo/mailman doesn't exist. If I just go to
/mailman/listinfo I get an Elf binary thrown at me, rather than the page
saying there are no advertised lists. If I do the same thing from the
server using the Lynx web browser, I get the same binary thrown at me,
with a page title, "Mailman CGI error!" It sounds to me like Apache
2.4.2 isn't seeing that /usr/lib/mailman/cgi-bin is, in fact, CGI
scripts, and is trying to treat them like regular files. Has something
else changed between Apache versions?
Thanks,
Jayson
i just did make one vm instance Ubuntu 18.04 on google compute
engine. barely i did install postfix at there. hmm if possible, i wish
to run mailing service for my family and me -- it needs a little bit some comunication plus some
records about family history. yes i want GNU Mailman very
much!!! google compute engine blocked port 25 by default. in this case i
can run mailman with other port (example 625)? again question, Mailman
can act with 625 or 1625 or 2625, ...?
Sincerely, Byung-Hee from South Korea.
--
^고맙습니다 _地平天成_ 감사합니다_^))//
Dear Mailman Cognoscenti,
I'm helping one of my list owners send out 5K plus invitations to
students to subscribe to his mailing list. Our current configuration:
Mailman v2.1.20
RHEL v5.11
Semdmail v8.13.8
Apache v2.2.3
Since this was the first time doing this, I suggested breaking the
batch input into 3 groups, 50, 500, and the rest. The 50 went fine,
as did the 500, but the largest batch gave him a generic web server
error:
> Internal Server Error
>
> The server encountered an internal error or misconfiguration and was
> unable to complete your request.
>
> Please contact the server administrator, root(a)conundrum.unh.edu and
> inform them of the time the error occurred, and anything you might
> have done that may have caused the error.
>
> More information about this error may be available in the server
> error log.
I looked at the logs and I couldn't find anything that hinted at what
went wrong. So I asked the owner to send me the last back and I'd
give it a try. I wrote a script that removed folks already subscribed
to his list and split the remaining subscribers up into 6 files with a
thousand records each. I just tried uploading the 1st batch of 1K,
with the following options:
Subscribe these users now... (*) Invite
Send welcome message... (*) No
Send notifications... (*) No
And entered a 7 line paragraph explaining the invitation.
I ended up having the same error happen. Looking at the Mailman logs,
I can't see any difference before or after my submission. In the
HTTPD logs, I see:
>> [Fri Aug 26 19:59:23 2016] [warn] [client 132.177.215.132] Timeout
>> waiting for output from CGI script
>> /usr/local/mailman/cgi-bin/admin, referer:
>> https://lists.unh.edu/mailman/admin/campus.connection/members/add
>> [Fri Aug 26 19:59:23 2016] [error] [client 132.177.215.132]
>> Premature end of script headers: admin, referer:
>> https://lists.unh.edu/mailman/admin/campus.connection/members/add
So is there an inherent limit to the number of invites that can be
submitted via the web form?
As a work around, how would I do large invites on behalf of the owner
from the command line, including the 'extra text' that is allowed via
the web interface?
--
Cordially,
the UNH Mailing List Server Admins
Bill Costa, senior admin
(603) 862-3056
Hello all,
I have my postfix mail server running mm 2.1.26 installed via apt on Ubuntu 18.04. I wish to upgrade to 2.1.29 but it’s not in the official repos.
I tried installing from source, after first running mailman-config to gather the configure parameters (thanks Lindsay!). It installed no sweat BUT failed to start afterwards. It kept complaining of a pid file being unreadable.
So I started over (restored snapshot) and then tried adding a ppa apt source which contains 2.1.29:
https://launchpad.net/~mailman-administrivia/+archive/ubuntu/ppa
Installed with an IO error over a lock file purported to be from one of my lists but otherwise started ok. But sending an email produced an error complaining:
The mail system
<list@localhost>: Command died with status 2: "/var/lib/mailman/mail/mailman
post list". Command output: Group mismatch error. Mailman expected the
mail wrapper script to be executed as group "daemon", but the system's mail
server executed the mail script as group "list". Try tweaking the mail
server to run the script as group "daemon", or re-run configure, providing
the command line option `--with-mail-gid=list'.
So that gid is what I used when I tried from source.
Does anyone have any ideas? Thanks.
--
Fabian S.
OpenPGP:
0xA1250C2112D2D0E53E5BD964BBB5B16CFB701CD7
Quick link to shared public key:
https://keys.mailvelope.com/pks/lookup?op=get&search=0xBBB5B16CFB701CD7
Greetings,
Migrated mailman to another server and updated it.
Site Admin can see the pending queue on all lists but the lists
owners/administrators cannot.
Running Centos7 and current build of mailman. (2.1.15)
Lists have been migrated and are functioning properly. Permissions fix
finds nothing.
Any help appreciated.
--
Ryan McClung
Systems Administrator @ Afilias Canada
A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8
<https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…>
W. www.afilias.info
T. +1.416.646.3304 x4186
I've supported a dozen Mailman listservers for over a dozen years.
This doesn't represent much real effort most of the time. I've had to
block specific users often and specific domains rarely, but this is
the first time I've had to block an entire TLD.
Recently I've been gifted with an inordinate amount of UCE from many
different domains under the '.icu' TLD.
Since Python RE's are _almost_ the same as the UNIX RE's I used many
years ago, if I put
^@.*\.icu$
in discard_these_nonmembers, will it block all domains in that TLD?
And not block anyone else?
Thanks,
-Chip Davis-
Mailman 2.1.27
shared host
linux 2.6.32-696.18.7.el6.x86_64
cPanel 80.0.10
Hello,
this is unrelated to using mm itself but was wondering if anyone here
had any insight they could share;
i run a mailing list on mm 2.x. periodically i send out an event opening
email
to the list. this is typically followed by a conclusion email at the end
of a specific period. in the interim period i would like to send out
reminders of the event to the list but would like to automate this task.
i want the reminders to be triggered by my opening email and
end with my conclusion email.
has anyone done this and how? i've looked at ifttt and zapier but wasn't
sure. thanks.
--
Fabian S.
OpenPGP:
0xA1250C2112D2D0E53E5BD964BBB5B16CFB701CD7