Mark,
It works fine now after I stopped the SELinux. Once again, thanks for your
help.
Charles
On Wed, Nov 6, 2013 at 1:17 AM, c cc wrote:
> 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
In cases like this, I suggest that the user check the list's archive.
Only if the list has an archive.
--Barry Finkel
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: h
On Nov 06, 2013, at 09:51 AM, Ralf Hildebrandt wrote:
>> I believe that according to RFC 5322 (and predecessors) Mailman SHOULD
>> add a Resent-Message-ID to indicate that it handled the message, but I
>> doubt this would change the duplicate-suppression behavior of Gmail
>> and MS Exchange.
This
On Nov 06, 2013, at 09:05 AM, Stephen J. Turnbull wrote:
>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
>the (other) RFC 2369 headers for the list(s) the user is subscribed
>to. Of course this requires person
* Stephen J. Turnbull :
> 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
> ad
* Mark Sapiro :
> 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.
Good point
* Stephen J. Turnbull :
> 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
In my case its two lists on the s
