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
Hello,
I'm trying to figure out some performance issues with mailman. I have it configured for SMTP direct, and pointed at localhost, port 25. The MTA is sendmail. Sendmail is configured to use our exchange server as a smart host. We have two lists configured and send out 1 message a month to each list. It usually takes about 12-24 hours to finish sending all the messages. There are never more than about 5 to 10 messages in the sendmail queue at any given time, so this leads me to believe that the bottleneck is not on the sendmail side.
I've configured mailman for 48 outgoing qrunners, and have tried as many as 72 qrunners, with no noticeable difference, it's like it's using only the 1st outgoing qrunner to process the message and the rest stay there idle. And then it uses that one qrunner process to create each separate message. So 12k individual messages processed by one qrunner thread each time. Is there some way to speed this up and/or get it to use multiple outgoing qrunners simultaneously for the same post, since with personalization it has to create individual copies of each message?
The other odd thing is it doesn't log all 12K messages in the smtp log from mailman, but it logs more than 1. I would have thought it would either log only 1 message, or all 12K messages.
Here is the SMTP log from mailman:
Sep 26 14:13:17 2013 (12407) <mailman.0.1380222786.19117.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 10.368 seconds
Sep 26 15:11:57 2013 (12439) <mailman.0.1380226308.21360.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 8.107 seconds
Sep 26 15:42:19 2013 (12381) <mailman.0.1380228138.22559.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 0.086 seconds
Sep 26 16:56:31 2013 (12458) <mailman.0.1380232579.25376.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 11.179 seconds
Sep 26 17:21:12 2013 (12469) <mailman.0.1380234070.26307.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 1.012 seconds
Sep 26 19:10:10 2013 (12429) <mailman.0.1380240598.30473.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 10.988 seconds
Sep 26 20:23:43 2013 (12449) <mailman.0.1380245014.711.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 6.958 seconds
Sep 27 00:47:25 2013 (12380) <mailman.0.1380260837.10913.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 6.096 seconds
Sep 27 01:17:13 2013 (12448) <mailman.0.1380262626.12154.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 6.166 seconds
Sep 27 02:11:27 2013 (12442) <mailman.0.1380265881.14347.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 5.095 seconds
Sep 27 02:30:36 2013 (12399) <mailman.0.1380267029.15040.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 6.013 seconds
Sep 27 02:40:08 2013 (12472) <mailman.0.1380267601.15415.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 5.356 seconds
Sep 27 05:07:31 2013 (12380) <mailman.0.1380276450.12376.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 0.083 seconds
Sep 27 05:08:20 2013 (12422) <mailman.1.1380276500.12376.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 0.077 seconds
Sep 27 05:08:23 2013 (12474) <mailman.2.1380276502.12376.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 0.073 seconds
Sep 27 05:31:24 2013 (12438) <mailman.0.1380277874.22335.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 10.251 seconds
Sep 27 06:56:34 2013 (12469) <mailman.0.1380282987.25737.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 5.967 seconds
Sep 27 06:56:50 2013 (12396) <mailman.0.1380283004.25755.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 5.153 seconds
Sep 27 07:02:33 2013 (12452) <mailman.0.1380283341.25998.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 10.248 seconds
Sep 27 07:59:36 2013 (12406) <mailman.0.1380286763.28405.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 11.085 seconds
Sep 27 08:05:46 2013 (12417) <mailman.0.1380287135.28700.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 10.141 seconds
Sep 27 08:10:38 2013 (12449) <mailman.0.1380287426.28903.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 10.232 seconds
Sep 27 08:11:40 2013 (12435) <mailman.0.1380287489.28951.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 10.093 seconds
Sep 27 08:28:37 2013 (12473) <mailman.0.1380288511.29608.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 5.124 seconds
Sep 27 08:35:08 2013 (12409) <mailman.0.1380288897.29894.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 10.346 seconds
Sep 27 09:51:39 2013 (12428) <mailman.0.1380293492.733.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 5.045 seconds
Sep 27 10:34:31 2013 (12393) <mailman.0.1380296069.2689.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 0.049 seconds
Sep 27 11:39:33 2013 (12396) <mailman.0.1380299956.5227.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 15.162 seconds
Sep 27 11:40:15 2013 (12389) <mailman.0.1380300003.5287.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 10.073 seconds
Sep 27 11:53:41 2013 (12438) <mailman.0.1380300815.5850.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 5.098 seconds
Sep 27 13:00:33 2013 (12430) <mailman.0.1380304821.8504.newsletter(a)rigaku.com> smtp to newsletter for 1 recips, completed in 10.125 seconds
Thanks in advance for any advice/help you can give.
Bryan
Hello
I would like to know if the current or the future versions of mailman havve
any mobile version too.
Javad Hoseini
www.IranNopendar.Com
Tel/Fax: +98-21-22369938
Mobile: +98-935-416-7938
Skype: javad2625
Hello
I tried to retrieve the list of members of my mailing list using WHO
command, but it does not return any names. It only returns my own name and
says that the other members are hidden. I also tried to retrieve the list of
members from the info-page of group, entering my Admin password, but again
it was in vain. It says that the members are hidden. It only shows my own
email address. Of course I can retrieve the list of members from the control
panel of the mailing list too, but I would like to have a list of members as
a text file or comma-seperated file or Excel file or something like that.
That's because I want to have a backup of list-members.
What do you suggest?
Javad Hoseini