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
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.
Hi - I have searched FAQ and archives to find an answer. Hoping you can
I have a new list (with previously imported addresses) for announcements
only, and wish these announcements to be received immediately.
I set the defaults to allow non-digest and to not allow digest.
I wish to send out announcements in html, and so wish to make the
default for new subscribers be MIME. While I see a setting under Digest
Options (MIME_is_Default_Digest), I don't see any equivalent option
under Non-Digest Options... and new subscribers continue to come in as
In order to avoid having to manually change this option for each
existing subscriber, is there a way to force all existing subscribers to
receive MIME in Non-Digest mode?
If not, is there a way to force all NEW subscribers to be enrolled with
MIME as their default?
Also, is there a way to "lock" the MIME switch on, so that users who try
to change their option to plain text will be prevented from doing so?
I've got another problem with Qmail/Plesk/Mailman (same customer,
rebuilt server). Plesk is 7.5.4 reloaded.
Mail delivered fails with "need GID 110 got 101" error. I set up the
brute-force wrapper to deliver with GID 110, and set the permissions
correctly for it to work. Now, I'm getting the following (broken up
into multiple lines for courtesy):
qmail: 1157518628.995172 delivery 726: success:
I'm about ready to pull my hair out. I even added the popuser user to
the mailman group in /etc/passwd.
So, that being said, are there any ideas out there? I have been
messing with this for a week, and have not come up with anything else
Douglas G. Phillips
Simple Business Solutions
This message was sent using IMP, the Internet Messaging Program.
I have the task of setting up a replacement for an existing
Mailman/Postfix server. I am new to Mailman and I am looking for some
guidance in this transition. Mailman is currently being used solely as
a diffusion of information. That is, it does not accept contributions
from list members (read-only).
Firstly, should I attempt to migrate data/files over to the new system
or should I start fresh?
The new system will be running OpenBSD 4.0.
Other comments welcome.
Recently, my Mailman list users who use either a HotMail or MSN.COM email address have not received any messages. Mailman does not record a "bounce" from these email addresses, but they do not receive any of the list traffic. When trying to send a message to a Mailman list, the user gets the following error message:
"This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed."
And it lists the Mailman list email address. However, Mailman does not receive a bounce message. (My server is not listed with SpamHaus.org, or any of the other blacklists, so it should not be a spam filter sort of thing).
One user requested help from MSN, and they responded with:
"You are experiencing this issue because your .Net Passport <user's email address here> Profile (which is extensively used for authentication purposes) is corrupted (not updated). In order to resolve this issue, I would suggest you to Update your .NET passport profile."
They follow that with instructions to go to their MSN .NET Passport profile and re-type all the information by hand (not by cut and paste). Then a 15-step procedure is given to delete all cookies, history and temporary internet files and re-set the disk cache (space for files) to 10MB. They believe that will solve the problem but alas, it has not for the 4 users I have with MSN or HotMail email addresses.
Anyone else run into this and resolved it? I didn't see anything in the archives. If any of you have users with MSN or HotMail addresses, be advised they probably will not be able to receive emails, but you will not get "bounce" messages. They only way they will know is if they try to post to a Mailman list.
Hi to all,
Is there a way to disable users-members from changing
some or all of their configuration options?
I think this is very important because some of these
options should in some cases be available only to
In my case I want to have a public list in terms on
can post to the list but I want the list to be private
in terms of who can access the archives and to whom
messages can be forwarded to.
About the private archives there is an option and can
be configured only by the admin. But for me I want
posts to be forwarded only to people that are members
of the list and belong to my domain and not to the
members that do not belong to my domain.
This way my mail server wont forward spam to other
domains (via the list) and people outside my domain
will still be able to read the list's posts.
This could be solved if the option to Enable mail
delivery was not available in user's configuration
page, or if the user could be dissalowed to change
his options somehow.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
Did you ever find a solution to this issue?
I realize that this is a really old posting:
I send an eMail to one of the lists, I can see in my /var/log/maillog;
Jun 10 11:27:03 osiris sendmail: h5A9R392002756:
from=<Niklas.Nikitin at xxx
size=502, class=0, nrcpts=1,
msgid=<184.108.40.206.2.20030610112857.00b9b740 at xxx
Jun 10 11:27:03 osiris sendmail: h5A9R392002756:
to="|/usr/local/mailman/mail/mailman post nicke-test",
ctladdr=<nicke-test at xxx
<http://mail.python.org/mailman/listinfo/mailman-users> > (8/0),
mailer=prog, pri=30704, dsn=2.0.0, stat=Sent
that the server is receiving the eMail and is forwarding it to
Mailman. But in Mailman's logs I will not find any information
that it has received the eMail and no eMail is sent to the members
on the list. If I dump all members of the list to a file, remove
the list, create the list again and add all members, the list is
working again for a while, and then it repeats again.
but I've run into a very similar problem with two mailing lists that are
managed using the current release of Mailman.
The first symptom was that messages sent to the mailing lists were not
distributed to the list, and did not show up in the list archive.
After my ISP reinstalled Mailman, messages to the list started to show
up in the list archive again. But the messages were still not distributed
to members of the list.
We found that if we add a new user, then a message to the list *is*
delivered to that new user, but still not to any of the existing users.
If the *new* user posts a message, that message appears in the list
archive and the message is delivered to the entire mailing list.
There doesn't seem to be a way to dump and reload the mailing list that
preserves all per-list-member configuration options, so if possible,
we'd like to avoid that workaround. Especially if it only works
Any insight / help / pointers appreciated.
> -----Original Message-----
> From: Mark Sapiro [mailto:email@example.com]
> Sent: Thursday, April 26, 2007 10:31 PM
> To: Aaron Crosman; mailman-users(a)python.org
> Subject: Re: [Mailman-Users] Server migration problems
> ----- Original Message ---------------
> Subject: [Mailman-Users] Server migration problems
> From: "Aaron Crosman" <ACrosman(a)afsc.org>
> Date: Thu, 26 Apr 2007 14:22:19 -0400
> To: <mailman-users(a)python.org>
> >I know this comes up all the time, but having carefully reviewed the
> >and archives, I still haven't been able to solve my problem.
> >I'm working on migrating my mailman setup from an old SuSE server to
> >new Debian (4.0) server. For the most part everything has gone
> >smoothly, but the existing lists have a couple of problems I can't
> >the cause. I moved the lists, archive, and data directories from
> >old server, and ran update, check_perms and check_db on all the
> >If I run list_lists, mailman sees all the lists just fine, but when
> >the web interface I don't see anything. I naturally assumed that had
> >somehow become private during the move, so I exported the
> >of one of them, and saw "advertised = True" and while I know in
> >it shouldn't matter, I went ahead and updated it to be "advertised =
> >no difference. If I browse to the list's admin interface directly it
> >seems to work.
> This certainly seems like FAQ 4.62 to me
> Have you run fix_url?
> >I'm also having trouble getting into the archives. The files are
> >and the sym-links are correct but the permissions seem to be wrong.
> And what are they? And what's in the web server's error log?
> >assuming I'm having a problem similar to the advertising (that mm
> >to be over-tightening permissions somewhat), but I can't find the
> >cause. Any suggestions on where to look?
> Look at the permissions and whether the web server is allowed to
> symlinks, and if all that is OK, it might be a SeLinux or other kind
> of security polict issue.
> Mark Sapiro <msapiro(a)value.net> The highway is for gamblers,
> San Francisco Bay Area, California better use your sense - B. Dylan
Thanks, you were right on about the domain problem. I looked right
passed it, since the server will end up at the same domain, but
currently I'm accessing by IP address (I hosts file update on my local
machine solved that problem).
The archives problem persists. You gave me the right place to look here
as well. The archives are all owned by list (group list), but the
private archives have restricted access that blocks other users from
ls of /var/lib/mailman/archives:
drwxrws--- 200 list list 8.0K 2007-04-25 14:26 private
drwxrwsr-x 2 list list 4.0K 2007-04-25 14:23 public
A sample from the private directory is:
drwxrwsr-x 4 list list 4.0K 2007-04-25 14:18 itd_test
Apache's error log:
[Fri Apr 27 11:42:14 2007] [error] [client 172.17.201.205] Symbolic link
not allowed or link target not accessible:
I can't browse the file system (in bash) to those directories. I did
double check the links in public as root, and they do work just fine, so
I'm at a permissions problem. What should the perms here be? Or am I
missing something else?
We started using mailman for announce only mailing list for our school
district. We have all the subscribers setup to be moderated so they
can't post to the list.
The school principals and school secretaries are subscribers as well
but have the moderation bit turned off.
For some reason when they post I still have to goto a web-page and
approve the request.
I listed them as moderators and also as admin yet I still have to goto
the web page and approve the request. Is there anyway around this?
(other than adding a password to the email header)
We just need a list where a specified list of people can post to send
news to our parents, without me having to intervene for every email
they want to send out.
I've google searched this, searched for "announce only" in the mailman
list archives and read the FAQ here