I'm learning a lot about Mailman all of a sudden.
I had a user move a list from another provider onto an install on my
system yesterday. Instead of uploading a <CR>-delimited file with
one email address per line, they uploaded a tab-delimited file with a
tab between each address. As an added factor, they mistakenly had
the interface set to send a welcome message.
Interestingly, the effect of this was that no one got subscribed to
the list because Mailman read every single address as a null email
address with the actual email address quoted. Mailman then happily
proceeded to pass 8,000+ null-addressed welcome messages to my mail
server, which decided to ignore the quotes and send all the messages
Is this a bug or a feature? =)
Jesse Sanford <jesse(a)seedboxconnect.com>
System Designer, Seedbox Connect
On version 2.1.5, on the listinfo page, an email adres 'mailman@domain'
is mentioned. We have a situation where our clients work with
mailinglists on 'lists.domain' but receive their mail at 'domain'.
So, instead of having the listinfo page list 'mailman(a)list.domain.com' we
would like it to display 'mailman(a)domain.com' but we can not find a way
how to do that. Can you help !?
The manipulation of objects is much easier than
objecting to manipulation
Suares & Co, Open Source Solutions
mail: Sans Souci #11, Willemstad, Curacao (NA)
phone: +599 786 23 73
fax: +31 848 707 705
web: http://www.suares.an email: ace(a)suares.an
I am doing a new Mailman installation on Red Hat.
I am doing the install as a member of the Mailman group.
I have made sure that the installation directory can be written to by that
I have run 'configure' and 'make' successfullly.
When I run 'make install', I get the following:
[chris@gatsby mailman-2.1.8]$ make install
Creating architecture independent directories...
chmod o-r /usr/local/mailman/archives/private
chmod: changing permissions of `/usr/local/mailman/archives/private':
Operation not permitted
make: *** [doinstall] Error 1
So, assuming that the problem was changing the permissions for the
archives/private directory, I made the change as root and then went back to
do the 'make install'. I get the same message, even though I manually had
changed the permissions.
If I run check_perms, I get this:
[root@gatsby bin]# ./check_perms
Warning: Private archive directory is other-executable (o+x).
This could allow other users on your system to read private
If you're on a shared multiuser system, you should consult the
installation manual on how to fix this.
No problems found
Can someone give me some suggestions?
Dallas Bethune wrote:
>For our uses just
>changing that list-bounces address to something less ominous looking
It definitely looks to me as if something needs to be done. I think
perhaps offering 3 options either to the list admin on a per-list
basis with a site default or just a site option. I lean towards
per-list although it's more work to add to the GUI.
The options I see are
1) current behavior with perhaps the addition of putting the original
Sender: in another header.
2) like 1) only use list address instead of list-bounces.
3) don't touch Sender: at all.
Mark Sapiro <msapiro(a)value.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
And your point is?
Of course I be deluded and imagining the error response I got back
but then again 17 days is a long time in the life of a file's
btw: I think I have seen comments about the same problem in recent
postings to the recent mailman-user archives by other users. Can
anyone confirm whether they have seen a similar problem or is it just
me being picked on by the FAQ wizard.
On 27 Apr 2006, at 15:32, Barry Warsaw wrote:
> On Mon, 2006-04-10 at 00:53 +0100, Richard Barrett wrote:
>> Sorry, an error occurred
>> Can't write file faq01.011.htp ([Errno 13] Permission denied:
> I just tried editing item 1.29 and it worked for me.
I apologize if this has been asked before, but I have googled day in and day
out so, if you could point me in the right direction:
All digests include the email information for each email such as:
Date: Tue, 25 Apr 2006 09:57:37 -0400
From: Apache <apache(a)domain.com>
Subject: Status- Client, Demo
We are using our lists in an automated method, therefore it will always be
generated from an automated source so this information is irrelevant and
over the course of a digest with 200+ emails it adds up to be alot of
Where can I go to remove it. Even if it is a global change. I was poking
around in the Handlers Directory, but am not sure if there is a better place
to do this.
Thanks in advance for your expert advice.
169 Central Ave
Albany, NY 12206
As a response to the "set show" command, I obtain:
delivery off (a causa degli errori il Wed, 12 Apr 2006 01:21:46 -0000)
cause of errors on
I've tried to send a "delivery on" command, but this seems not to work.
What's the problem?
Only the administrator can fix this?
Thanks and regards Manlio Perillo
SHORT VERSION...sending to "-owner" gets delivered fine, but sending to
"-admin" gets vanishes (no bounce) and tallys a bounce count against the
owner address. What would cause this??
- I have an announcement-style Mailman list (let's call it LIST)
- LIST is hosted on a shared web server running cPanel
- LIST is configured to send the owner subscription notifications
- A few weeks ago, I stopped getting subscription notifications
- A few days later, I got a message from Mailman saying that my address
had excessive bounces and was disabled. I had to re-enable MY OWN
This prompted me to test the "LIST-owner" and "LIST-admin" addresses...
- The "-owner" address is delivered to me just fine.
- The "-admin" address never delivers. No bounce msg to sender either.
- EVEN WORSE...each mail sent to "-admin" seems to get treated as a
BOUNCE event against MY (owner) address!
WHAT I'VE DONE:
- I have checked my /etc/valiases/<domain> file and all the forwarders
to mailman are exactly as they used to be. All looks perfect.
- I tried creating a brand new list with all default settings...same
- I got other people from my web host to try the same on other
servers...some work fine, and some servers have the same problem as mine.
ANY IDEAS?? I found this thread from 3 years ago which seems to be a
similar problem, but the thread fizzled without a solution:
I'm ready to pull my hair out!