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
L.S.
Bug in Mailman version 2.1.15
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited, but the
webmaster can find this information in the Mailman error logs.
The above message shows up on the web pages, unfortunately the last log written
to is qrunner, error is empty, so no info on what it is about.
The last thing changed is the adres of the main pages.
It looks like the mail-system is not affected, any idea what is going on?
Would like to show some logging, but it simply is not there.
--
Roel Wagenaar,
Linux-User #469851 with the Linux Counter; http://linuxcounter.net/
Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen.
Vraag: Waarom is top-posting een slechte gewoonte?
Antw.: Top-posting.
Vraag: Wat is het meest ergerlijke in e-mail?
Why be difficult, when with a bit of effort, you can be impossible?
As a moderator of our list, I know when messages are approved, and I'm seeing very erratic delivery times to my own address, which is on an Exchange server. They used to come through within a minute or so, now they can take 20 minutes or an hour.
I subscribed my gmail address for comparison, and am finding that the same list messages come through to it as quickly as ever.
>From those observations I would conclude that the Exchange server is having problems receiving external mail, but I've found that test messages sent from my gmail account to my Exchange address come through within seconds.
Can I assume this has nothing to do with mailman?
Peter Shute
Sent from my iPad
This probably isn't the forum for questions, and I've submitted a request to join the user mailing list, however, I'm in a bit of a time pinch and would like to know if you guys have seen this before and if so, what might be the cause.
When I run the find_members script natively on the mailman box I get this result:
root@mbox1:/opt/mailman/bin# ./find_member -w k.vernon(a)ntta.com<mailto:k.vernon@ntta.com>
k.vernon(a)ntta.com<mailto:k.vernon@ntta.com> found in:
billinglist
dbdev2-notice (as owner)
it_storage
it_storage (as owner)
san_notify (as owner)
itlist
dbdev1-notice (as owner)
db1-notice (as owner)
ccrb
mailman
mailman (as owner)
nttadallas
db2-notice (as owner)
peoplesoftlist
shap-notice
shap-notice (as owner)
it_unix
it_unix (as owner)
hardwaremaint
scan_results
db3-notice (as owner)
it_dns
it_dns (as owner)
it_server (as owner)
ntta-corporate
it_backup
it_backup (as owner)
page_unix (as owner)
ilom_alerts
ilom_alerts (as owner)
zmanda
zmanda (as owner)
But when I run it from inside a script, I get totally different results:
##################################################################
## NOTE NOTE NOTE NOTE ##
## This part of script produces erroneous ##
## results. Do NOT trust ##
##################################################################
#SSH to mbox1 and run /opt/mailman/bin/find_member
USERNAME=kyle
HOST=mbox1.it.ntta.com
SCRIPT="op mailmanscripts /opt/mailman/bin/find_member -w ${2} "
ssh -o StrictHostkeyChecking=no -l ${USERNAME} ${HOST} "${SCRIPT}"
cas-webomerrors(a)verio.net<mailto:cas-webomerrors@verio.net> found in:
webomusers
k.vernon(a)ntta.com<mailto:k.vernon@ntta.com> found in:
ccrb
it_storage
mailman
ntta-corporate
shap-notice
it_backup
it_unix
hardwaremaint
billinglist
nttadallas
peoplesoftlist
itlist
ilom_alerts
scan_results
it_dns
zmanda
Kyle A. Vernon
IT Systems and Storage Professional
NTT America
1950 N Stemmons Fwy, #2001
Dallas, TX 75207
214-800-7519 office
903-879-1360 cell
________________________________
This email message is intended for the use of the person to whom it has been sent, and may contain information that is confidential or legally protected. If you are not the intended recipient or have received this message in error, you are not authorized to copy, distribute, or otherwise use this message or its attachments. Please notify the sender immediately by return e-mail and permanently delete this message and any attachments. makes no warranty that this email is error or virus free. Thank you.
****************************************************
************
This email message is intended for the use of the person to
whom it has been sent, and may contain information that is
confidential or legally protected. If you are not the intended
recipient or have received this message in error, you are not
authorized to copy, distribute, or otherwise use this message
or its attachments. Please notify the sender immediately by
return e-mail and permanently delete this message and any
attachments. NTT America makes no warranty that this email is
error or virus free. Thank you.
****************************************************
************
Hi,
I seem to have an issue with my mailhost server randomly rejecting emails from my mailman server whenever they are directed externally.
My current setup is I have a mailman server running mailman and sendmail which sends all emails to my mailhost server also running sendmail. Mailhost passes the emails through mailscanner etc. and then relays them either externally or internally based on the target email. Internal relaying works just fine but external relaying seems to sporadically accept some addresses for delivery and reject others. the choice of addresses it chooses to accept or reject is different for every attempt I am so for example for my first attempt it will forward the email to the first and 3rd external email addresses and reject to forward to the rest and on the 2nd attempt it rejects the the 2nd and 3rd and 4th but sends the emails to the 1st and 5th addresses just fine and so on. My mailman server's logs do not show any errors but my mailhost does.
this is the extract in question from my mailhost server mail log file:
Jul 24 09:08:52 mailhost sm-mta[3296]: s6O88pSr003296: from=<Source-email(a)external-domain.com>, size=2260, class=0, nrcpts=1, msgid=<cq0nx1du5icvm2eubfc8lvdy.1406189339980(a)email.android.com>, proto=ESMTP, daemon=MTA-v4, relay=mail-we0-f174.external-domain.com [74.125.82.174]Jul 24 09:08:52 mailhost sm-mta[3296]: s6O88pSr003296: to=<mailman-list(a)dmz.on.internal-domain.com>, delay=00:00:00, mailer=esmtp, pri=32260, stat=queuedJul 24 09:08:53 mailhost MailScanner[2909]: New Batch: Scanning 1 messages, 2837 bytesJul 24 09:08:53 mailhost MailScanner[2909]: Virus and Content Scanning: StartingJul 24 09:09:07 mailhost MailScanner[2909]: MCP Checks: StartingJul 24 09:09:07 mailhost MailScanner[2909]: Uninfected: Delivered 1 messagesJul 24 09:09:07 mailhost MailScanner[2909]: Deleted 1 messages from processing-databaseJul 24 09:09:08 mailhost sendmail[3307]: s6O88pSr003296: to=<mailman-list(a)dmz.on.internal-domain.com>, delay=00:00:16, xdelay=00:00:01, mailer=esmtp, pri=122260, relay=mailman-server.dmz.on.internal-domain.com. [172.16.0.143], dsn=2.0.0, stat=Sent (s6O893Rm003831 Message accepted for delivery)Jul 24 09:09:16 mailhost sm-mta[3309]: s6O89FAL003309: ruleset=check_rcpt, arg1=<target-address(a)external.domain2.com>, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged), reject=550 5.7.1 <target-address(a)external.domain2.com>... Relaying denied. IP name possibly forged [mailhost ip address]Jul 24 09:09:16 mailhost sm-mta[3309]: s6O89FAL003309: from=<mailman-list-bounces(a)dmz.on.internal-domain.com>, size=4645, class=0, nrcpts=0, proto=ESMTP, daemon=MTA-v4, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged)Jul 24 09:09:16 mailhost sm-mta[3309]: s6O89FAN003309: <mailman-list-bounces(a)dmz.on.internal-domain.com>... User unknownJul 24 09:09:16 mailhost sm-mta[3309]: s6O89FAN003309: from=<>, size=0, class=0, nrcpts=0, proto=ESMTP, daemon=MTA-v4, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged)Jul 24 09:09:16 mailhost sm-mta[3309]: s6O89FAP003309: from=<>, size=2657, class=0, nrcpts=1, msgid=<201407240809.s6O89CZP003837(a)mailman-server.dmz.on.internal-domain.com>, proto=ESMTP, daemon=MTA-v4, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged)Jul 24 09:09:16 mailhost sm-mta[3309]: s6O89FAP003309: to=<support-email(a)internal-domain.com>, delay=00:00:00, mailer=esmtp, pri=32657, stat=queuedJul 24 09:09:16 mailhost sm-mta[3310]: s6O89FRV003310: from=<mailman-list-bounces(a)dmz.on.internal-domain.com>, size=4640, class=-30, nrcpts=2, msgid=<cq0nx1du5icvm2eubfc8lvdy.1406189339980(a)email.android.com>, proto=ESMTP, daemon=MTA-v4, relay=mailhost.serscis.eu [mailhost ip address]Jul 24 09:09:16 mailhost sm-mta[3310]: s6O89FRV003310: to=<Source-email(a)external-domain.com>, delay=00:00:00, mailer=esmtp, pri=118640, stat=queuedJul 24 09:09:16 mailhost sm-mta[3310]: s6O89FRV003310: to=<target-address(a)external.domain.com>, delay=00:00:00, mailer=esmtp, pri=118640, stat=queuedJul 24 09:09:16 mailhost sm-mta[3311]: s6O89Fll003311: ruleset=check_rcpt, arg1=<target-address(a)external.domain3.com>, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged), reject=550 5.7.1 <target-address(a)external.domain3.com>... Relaying denied. IP name possibly forged [mailhost ip address]Jul 24 09:09:16 mailhost sm-mta[3311]: s6O89Fll003311: from=<mailman-list-bounces(a)dmz.on.internal-domain.com>, size=4640, class=-30, nrcpts=1, msgid=<cq0nx1du5icvm2eubfc8lvdy.1406189339980(a)email.android.com>, proto=ESMTP, daemon=MTA-v4, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged)Jul 24 09:09:16 mailhost sm-mta[3311]: s6O89Fll003311: to=<target-address(a)internal-domain.com>, delay=00:00:00, mailer=esmtp, pri=88640, stat=queuedJul 24 09:09:17 mailhost sm-mta[3311]: s6O89Fln003311: <mailman-list-bounces(a)dmz.on.internal-domain.com>... User unknownJul 24 09:09:17 mailhost sm-mta[3311]: s6O89Fln003311: from=<>, size=0, class=0, nrcpts=0, proto=ESMTP, daemon=MTA-v4, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged)Jul 24 09:09:17 mailhost sm-mta[3311]: s6O89Flp003311: from=<>, size=2657, class=0, nrcpts=1, msgid=<201407240809.s6O89CZP003841(a)mailman-server.dmz.on.internal-domain.com>, proto=ESMTP, daemon=MTA-v4, relay=mailhost.server.in-dmz.on.internal-domain.com [mailhost ip address] (may be forged)Jul 24 09:09:17 mailhost sm-mta[3311]: s6O89Flp003311: to=<support-email(a)internal-domain.com>, delay=00:00:00, mailer=esmtp, pri=32657, stat=queued
Any help would be appreciated.
ThanksAbZ
Hi,
Does anyone know of any good statistics scripts that either can email
detailed stats to list admins, or even offer stats from within the admin
itself?
We're using Mailman 2.1.18-1
Thanks in advance!
Best Regards,
Peter Knowles
TPN Solutions
Email: pknowles(a)tpnsolutions.com
Phone: 604-229-0715
Skype: tpnsupport
Website: http://www.tpnsolutions.com
Hi,
I just installed mailman on a Centos 6.5 server with Apache, and find that
all the links on the web interface are broken because they point to an
https:// address with /cgi-bin/ in the address rather than an http://
address that works.
The Defaults.py config includes the following line:
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
rather than the folloowing:
DEFAULT_URL_PATTERN = 'https://%s/mailman/cgi-bin/'
which was recommended on one web tutorial I have been using for setup.
While I wouldn't mind having it work at the SSL/https address, I don't have
a working SSL certificate, won't be purchasing one, and would rather not
use a self-signed one that pops up security prompts every time someone
visits. So, I'm inclined to stick with the less secure http://
I've tried configuring it both ways, changing the DEFAULT_URL_PATTERN and
restarting mailman, but either way the site works at
http://www.mysite.com/mailman/listinfo/, but all the web links are to
https://www.mysite.com/cgi-bin/listinfo/.
I've also checked the config files "mm_cfg.py" and "mailman.conf" and don't
see anything that is pointing to an https:// address.
Any suggestions? I am a novice and appreciate your patience.
James
On 07/22/2014 01:56 PM, Chad Rebuck wrote:
> I see a related email from a google seach where you pointed someone to
> the lock files directory. I suppose this isn't normal? Too many lock
> files?
>
> [root@pogo locks]# pwd
> /var/lib/mailman/locks
> [root@pogo locks]# ll
> total 100K
> -rw-rw-r-- 2 http mailman 52 Jul 22 2014 a2-16v-list.lock
> -rw-rw-r-- 1 http mailman 52 Jul 20 18:10 a2-16v-list.lock.pogo.19620.0
> -rw-rw-r-- 2 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20307.0
> -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20309.0
> -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20311.0
> -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20312.0
> -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20313.0
> -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20316.0
> -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20323.0
> -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20351.0
> -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20519.0
> -rw-rw-r-- 1 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20598.0
> -rw-rw-r-- 1 http mailman 52 Jul 20 22:38 a2-16v-list.lock.pogo.20648.0
> -rw-rw-r-- 1 http mailman 52 Jul 20 22:40 a2-16v-list.lock.pogo.20663.0
> -rw-rw-r-- 1 http mailman 52 Jul 20 22:44 a2-16v-list.lock.pogo.20674.0
> -rw-rw-r-- 1 http mailman 52 Jul 20 22:48 a2-16v-list.lock.pogo.20699.0
> -rw-rw-r-- 1 http mailman 52 Jul 20 22:57 a2-16v-list.lock.pogo.20827.0
> -rw-rw-r-- 1 http mailman 52 Jul 20 23:16 a2-16v-list.lock.pogo.20980.0
> -rw-rw-r-- 1 http mailman 52 Jul 20 23:19 a2-16v-list.lock.pogo.20989.0
> -rw-rw-r-- 1 http mailman 52 Jul 20 23:54 a2-16v-list.lock.pogo.21944.0
> -rw-rw-r-- 1 http mailman 50 Jul 21 00:16 a2-16v-list.lock.pogo.406.0
> -rw-rw-r-- 1 http mailman 50 Jul 21 00:20 a2-16v-list.lock.pogo.435.0
> -rw-rw-r-- 1 http mailman 50 Jul 21 00:31 a2-16v-list.lock.pogo.484.0
> -rw-rw-r-- 2 mailman mailman 46 Jul 23 2014 master-qrunner
> -rw-rw-r-- 2 mailman mailman 46 Jul 23 2014 master-qrunner.pogo.341
There is definitely a locking issue. It's not that there are too many
per se, it's that the list is locked by a defunct process and the lock
will never be relinquished.
If you
cat /var/lib/mailman/locks/a2-16v-list.lock
the contents will be the file name of the active lock. Judging from the
link count, it's this one
-rw-rw-r-- 2 http mailman 52 Jul 22 2014 a2-16v-list.lock.pogo.20307.0
do 'ps -fww 20307' or whatever the PID of the active lock is. If that
PID doesn't exist, do
rm /var/lib/mailman/locks/a2-16v-list.lock.pogo.19620.0
and wait a few seconds. If all the locks don't clear, repeat until they do.
If a PID with the lock does exist, ps -fww will show what it is which
may help identfy why it is hung with the list locked.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan