Mark,
Finally, I was able to get "service mailman start" to work, but in
www.domain.com/mailman/listinfo only shows the list "mailman", none of my
old list are showing up.
By the way, SElinux was the culprit, and once it was stopped, I was able to
start mailman using: service mailman start.
On
withlist -l -r fix_url [listname}
Okay, the lists are there now after I fixed the url. I will let you
know see if it work when I
get back to work tomorrow. Once again, thank you so much for your help and time.
Charles
On Wed, Nov 6, 2013 at 1:03 AM, c cc wrote:
> Mark,
>
> Finally, I was ab
Steven Clift writes:
> Has this been a growing issue with Mailman served lists?
I wouldn't say it's growing. For quite a while (a decade or so) we
have been getting the occasional request for help in getting mail
delivered to the major freemail services and portals, including Gmail,
Yahoo!, Hot
Mark,
Thanks. I will double check all the permission on /var/lib/mailman/lists/
to make sure that they are all the same with the "mailman" list permission
since that particular list was working fine before I moved the old lists
over.
I will send you the log files to your email tomorrow. Once agai
Has this been a growing issue with Mailman served lists?
Articles like this sort of explain to rougher territory for legit
email generators:
http://bit.ly/1hhDQo6
We actually use the open source GroupServer.org package (a cousin to
Mailman) and if this is a growing problem, we need some sort of
d
On 11/05/2013 06:38 PM, c cc wrote:
> Mark,
>
> No luck.
>
> [root@es1 bin]# ./check_perms -f
> directory must be at least 02775: /usr/lib/mailman (fixing)
...
> directory permissions must be 02775: /usr/lib/mailman/templates/eu (fixing)
The permissions issues you have are with /var/lib/mailm
Richard Damon writes:
> It is not clear to me that mailman should add the Resent-* headers. The
> RFC states:
No, it's not clear to me, either. I do have a very strong opinion in
favor, to the extent that I would make it an option defaulting to ON.
> "Resent fields SHOULD be added to any mes
Mark,
No luck.
[root@es1 bin]# ./check_perms -f
directory must be at least 02775: /usr/lib/mailman (fixing)
directory permissions must be 02775: /usr/lib/mailman/mail (fixing)
directory permissions must be 02775: /usr/lib/mailman/cgi-bin (fixing)
directory permissions must be 02775: /usr/lib/mail
Mark,
Yes, we got "we hit a bug" message. Thanks!
Charles
On Tue, Nov 5, 2013 at 8:29 PM, Mark Sapiro wrote:
> On 11/05/2013 06:18 PM, c cc wrote:
> >
> > I am not sure this would help; I got this error message in
> > /var/log/mailman/error
> >
> > IOError reading list extension: [Errno 13] P
On 11/05/2013 06:18 PM, c cc wrote:
>
> I am not sure this would help; I got this error message in
> /var/log/mailman/error
>
> IOError reading list extension: [Errno 13] Permission denied:
> '/var/lib/mailman/lists/mailman/extend.py'
> Nov 05 20:16:53 2013 mailmanctl(31641): Site list is missing
On 11/5/13, 6:59 PM, Stephen J. Turnbull wrote:
> Note that the subject is incorrect. Mailman is not reusing the
> Message-ID, it is refusing to alter it which is correct behavior
> according to RFC 5322 (Message-ID is an originator field).
>
> I believe that according to RFC 5322 (and predecessor
Mark,
I am not sure this would help; I got this error message in
/var/log/mailman/error
IOError reading list extension: [Errno 13] Permission denied:
'/var/lib/mailman/lists/mailman/extend.py'
Nov 05 20:16:53 2013 mailmanctl(31641): Site list is missing: mailman
Thanks,
Charles
On Tue, Nov 5,
Mark,
Thanks!
"And at that point, where was the lists/mailman/config.pck file?"
I assume it was in /var/lib/mailman/lists/mailman/config.pck because I did
not move the config file when I moved the old list over.
"And to where did you move those losts/LISTNAME/config.pck files."
I move the whole
On 11/05/2013 05:19 PM, c cc wrote:
>
> Let me clarify this: No, I can't open the old list's listinfo page, but
> I can see the list using list_lists command.
OK.
> When I did the fresh installation and created the "mailman" list before
> moving any old lists over, I was able to start mailman
Mark,
Let me clarify this: No, I can't open the old list's listinfo page, but I
can see the list using list_lists command.
When I did the fresh installation and created the "mailman" list before
moving any old lists over, I was able to start mailman using: service
mailman start.
As soon I moved
On 11/05/2013 03:55 PM, c cc wrote:
>
> Is it possible that the old lists are not compatible? By the way, the
> mailman version on the old server is 2..1.9 and the version on the new
> server is 2.1.12. Any suggestions and help would be appreciated.
Not likely and not if you can open the old lis
Ralf Hildebrandt writes:
> Strictly speaking, all that womand wanted was to know if the message
> passed both mailing lists... So she should have more faith :)
For lists hosted by the same Mailman, Mailman 3 might be able to
handle this by adding *both* List-Ids to the header, and only adding
t
Note that the subject is incorrect. Mailman is not reusing the
Message-ID, it is refusing to alter it which is correct behavior
according to RFC 5322 (Message-ID is an originator field).
I believe that according to RFC 5322 (and predecessors) Mailman SHOULD
add a Resent-Message-ID to indicate tha
Mark,
Here what I just found out:
I removed and reinstalled mailman again and just created a list named
mailman--it works fine. But mailman wont' start as soon as I migrated the
old lists over to the new server.
Is it possible that the old lists are not compatible? By the way, the
mailman versio
On 11/05/2013 07:14 AM, Ralf Hildebrandt wrote:
>
> Strictly speaking, all that womand wanted was to know if the message
> passed both mailing lists... So she should have more faith :)
In cases like this, I suggest that the user check the list's archive.
--
Mark Sapiro The highway is f
On 11/05/2013 11:14 AM, c cc wrote:
>
> It seems like /etc/init.d/mailman and /etc/rc.d/mailman both are runing
> /usr/lib/mailman/bin/mailmanctl, as you can you below:
Do you mean /etc/rc.d/init.d/mailman? In RedHat/CentOS, /etc/init.d/ is
a symlink to /etc/rc.d/init.d/.
> MAILMANHOME=/usr/li
On Tue, 2013-11-05 at 13:14 -0600, c cc wrote:
> Mark,
>
> It seems like /etc/init.d/mailman and /etc/rc.d/mailman both are runing
> /usr/lib/mailman/bin/mailmanctl, as you can you below:
>
> MAILMANHOME=/usr/lib/mailman
> MAILMANCTL=$MAILMANHOME/bin/mailmanctl
>
> Here how I moved my lists over
Mark,
It seems like /etc/init.d/mailman and /etc/rc.d/mailman both are runing
/usr/lib/mailman/bin/mailmanctl, as you can you below:
MAILMANHOME=/usr/lib/mailman
MAILMANCTL=$MAILMANHOME/bin/mailmanctl
Here how I moved my lists over to the new server:
1. I renamed the /usr/lib/mailman to mailman
On 11/05/2013 10:34 AM, c cc wrote:
>
> Thanks! I was able to start using /usr/lib/mailman/bin/mailmanctl
> start--without any problem.
So 'service mailman start' which runs the script at /etc/init.d/mailman
(or /etc/rc.d/init.d/mailman) is running a different mailmanctl. Look at
that script and
Mark,
Thanks! I was able to start using /usr/lib/mailman/bin/mailmanctl
start--without any problem.
I have only have one mailman instance installed on this server and now, it
still does not show all my lists though. Any suggestions. Thanks!
Charles
On Mon, Nov 4, 2013 at 9:45 PM, Mark Sapiro
* Barry Warsaw :
> On Nov 05, 2013, at 02:46 PM, Ralf Hildebrandt wrote:
>
> >There's not way of turning this off on Exchange
>
> Sounds like the same bit of "helpfulness" that Gmail performs.
>
> http://wiki.list.org/x/2IA9
>
> It's a tough problem, but I think Mailman's retention of the origi
On Nov 05, 2013, at 02:46 PM, Ralf Hildebrandt wrote:
>There's not way of turning this off on Exchange
Sounds like the same bit of "helpfulness" that Gmail performs.
http://wiki.list.org/x/2IA9
It's a tough problem, but I think Mailman's retention of the original
Message-Ids is the right-er app
--On November 5, 2013 10:25:20 AM +0100 Ralf Hildebrandt
wrote:
Who's to blame? Mailman for re-using the message-id? Exchange for
dropping the second mail on the floor?
The messages are duplicates, so they should have the same Message-ID.
Whether to suppress delivery of duplicates is t
* Richard Damon :
> This is really a tough problem. Presumably, since mailman doesn't
> significantly alter the message (which is one reason it is allowed to
> maintain the message-id) it should really matter that the recipient only
> gets one copy of the message, or which one.
Yes, only the Subj
On 11/5/13, 4:25 AM, Ralf Hildebrandt wrote:
> Hi!
>
> Mailman re-uses the message-id of the original email. In our case an
> exchange user is recipient of two mailing-lists. Both mails are
> adressed in the original message, both lists distribute the list, two
> emails having the same message-id a
Hi!
Mailman re-uses the message-id of the original email. In our case an
exchange user is recipient of two mailing-lists. Both mails are
adressed in the original message, both lists distribute the list, two
emails having the same message-id arrive at the Exchange server, which
seems to discard the
31 matches
Mail list logo
