Re: [Mailman-Users] User unknown error on gentoo

2018-03-08 Thread Alexander

Thanks. this resolved my problem


On 08/03/2018 15:48, Mark Sapiro wrote:

On 03/07/2018 11:34 PM, Alexander wrote:

On 08/03/2018 13:53, Mark Sapiro wrote:> On 03/07/2018 09:26 PM,

as well as a sample of the content of

/var/lib/mailman/data/virtual-mailman# STANZA START: mailman
# CREATED: Thu Feb 22 22:07:59 2018
mail...@xxx.com  mail...@xxx.com
mailman-ad...@xxx.com    mailman-ad...@xxx.com
mailman-boun...@xxx.com  mailman-boun...@xxx.com
mailman-conf...@xxx.com  mailman-conf...@xxx.com
mailman-j...@xxx.com mailman-j...@xxx.com
mailman-le...@xxx.com    mailman-le...@xxx.com
mailman-ow...@xxx.com    mailman-ow...@xxx.com
mailman-requ...@xxx.com  mailman-requ...@xxx.com
mailman-subscr...@xxx.com    mailman-subscr...@xxx.com
mailman-unsubscr...@xxx.com  mailman-unsubscr...@xxx.com
# STANZA END: mailman

# STANZA START: 704staff
# CREATED: Thu Feb 22 22:07:59 2018
704st...@xxx.com  704st...@xxx.com
704staff-ad...@xxx.com    704staff-ad...@xxx.com
704staff-boun...@xxx.com  704staff-boun...@xxx.com
704staff-conf...@xxx.com  704staff-conf...@xxx.com
704staff-j...@xxx.com 704staff-j...@xxx.com
704staff-le...@xxx.com    704staff-le...@xxx.com.
704staff-ow...@xxx.com    704staff-ow...@xxx.com
704staff-requ...@xxx.com  704staff-requ...@xxx.com
704staff-subscr...@xxx.com    704staff-subscr...@xxx.com
704staff-unsubscr...@xxx.com  704staff-unsubscr...@xxx.com
# STANZA END: 704staff


I think this is the issue. It appears you have set

VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'XXX.com'

in mm_cfg.py. This is wrong. It is usually OK to not set this in
mm_cfg.py and leave it at the default None, but if you have to set it,
you need to set it to something in mydestination such as 'localhost'.
I.e. it MUST be a local domain, not a virtual domain.



--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] HELP! Just broke Mailman with a bogus list.

2018-03-08 Thread The Mailing List Server Admin

Mark Sapiro recently wrote...


I would be interested in knowing what's wrong and how it
happened. Unfortunately, this issue probably prevents even
running withlist on this list. I.e., Mailman's 'bin/withlist
LISTNAME' will probably throw the same error.


It does.  I did try compiling the original configuration file I
used to create the list and there were no syntax errors.  But
then I would expect a config file with syntax errors not to be
accepted when creating a new list.


To "fix" the problem just move the lists/LISTNAME directory
containing the config.pck and perhaps a few other files out of
the lists/ directory.


That worked and was my first instinct, but I didn't know if that
might cause other issues -- having a list directory that Mailman
was 'expecting' to suddenly be gone.  In any case, moving the
list's own subdirectory out of `~mailman/lists` directory got the
`list_lists` command line and `mailman/listinfo` web page working
again.

So the good news is that it was definitely this new list that
threw a spanner into the machinery, and not some other mysterious
event.

Thanks for the fix.  The files you requested are on the way.

--
  Cordially,
  the UNH Mailing List Server Admins
  Bill Costa, Adjunct Admin
  (603) 862-3056
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] Switching a list to port 443

2018-03-08 Thread Lindsay Haisley
On Wed, 2018-03-07 at 08:40 -0800, Mark Sapiro wrote:
> The most likely explanation for what you observed is you never ran
> fix_url on the affected lists after you changed DEFAULT_URL_HOST to
> "www.fmp.com" so their web_page_url attribute still had the prior
> domain.

I suppose it's possible, and certainly it was a misconfiguration on my
part to _not_ have an add_virtualhost call for "www.fmp.com". The
web_page_url in effect, though, seems to have been the one set with 
--urlhost when newlist was invoked to create the list, and after
running https.py the absence of an appropriate add_virtualhost() came
to the fore and the web_page_url was rewritten using the old
DEFAULT_URL_HOST, even though I'd added a proper add_virtualhost() by
the time I ran https.py.

Interesting, but not serious since the issue was identified and
remedied in pretty short order :)

-- 
Lindsay Haisley   |  "Humor will get you through times of no humor
FMP Computer Services |  better than no humor will get you through
512-259-1190  | times of humor."
http://www.fmp.com|- Butch Hancock

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


[Mailman-Users] How to remove "cc" of sender but retain "sender"?

2018-03-08 Thread Richard Johnson
Hi!  I hope this isn't just a matter of my not having searched enough!  I 
searched through all of the configuration I see, but didn't find a way to 
configure a mailing list to (1) set the "From" as the list address, while also 
(2) NOT including the sender in to any "CC" list, and instead including the 
sender in a "Sender" header.  Why do I want this?  I want all replies to go 
back to the list, but without any CC's going back to the sender, and while 
still retaining enough Sender information so that people can see from whom the 
message originated.

Maybe there's some better way or some good reason why I really don't want this?

(What I'm seeing is that some mail user agents will sometimes include the 
sender of the message to which they are replying as well as their own address 
into a "CC" list.  I'm hoping to avoid the duplicate messages, if possible.)

/raj

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] How to remove "cc" of sender but retain "sender"?

2018-03-08 Thread Mark Sapiro
On 03/08/2018 04:22 PM, Richard Johnson wrote:
> Hi!  I hope this isn't just a matter of my not having searched enough!  I 
> searched through all of the configuration I see, but didn't find a way to 
> configure a mailing list to (1) set the "From" as the list address, while 
> also (2) NOT including the sender in to any "CC" list, and instead including 
> the sender in a "Sender" header.  Why do I want this?  I want all replies to 
> go back to the list, but without any CC's going back to the sender, and while 
> still retaining enough Sender information so that people can see from whom 
> the message originated.


You can't do it without modifying code.

The things that come closest are:

1) first_strip_reply_to = Yes
   reply_goes_to_list = This List
   from_is_list = Munge From

This sets the list in both From: and Reply-To: but also puts the
original From: in Cc:

2) anonymous_list = yes

This sets the list in From: but hides the original sender completely.


> Maybe there's some better way or some good reason why I really don't want 
> this?
> 
> (What I'm seeing is that some mail user agents will sometimes include the 
> sender of the message to which they are replying as well as their own address 
> into a "CC" list.  I'm hoping to avoid the duplicate messages, if possible.)


Even if you did modify the code to do what you say you want, you'll find
that some MUAs will reply to the Sender: and others will make it
difficult or impossible to see the Sender: at all.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] How to remove "cc" of sender but retain "sender"?

2018-03-08 Thread Mark Sapiro
On 03/08/2018 05:51 PM, Mark Sapiro wrote:
> 
> The things that come closest are:
> 
> 1) first_strip_reply_to = Yes
>reply_goes_to_list = This List
>from_is_list = Munge From
> 
> This sets the list in both From: and Reply-To: but also puts the
> original From: in Cc:
> 
> 2) anonymous_list = yes
> 
> This sets the list in From: but hides the original sender completely.


and 3) first_strip_reply_to = Yes
   reply_goes_to_list = Poster
   from_is_list = Munge From

Which is like 1) except the original From: is in Reply-To: rather than Cc:

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org


Re: [Mailman-Users] How to remove "cc" of sender but retain "sender"?

2018-03-08 Thread Grant Taylor via Mailman-Users

On 03/08/2018 05:22 PM, Richard Johnson wrote:
(1) set the "From" as the list address, while also (2) NOT including 
the sender in to any "CC" list, and instead including the sender in a 
"Sender" header.


That really sounds like something that I would tackle with Procmail or a 
specially written filter (Perl or Python).


1)  Extract and save the From:.
2)  Remove all To: / From: / CC: headers
3)  Add a new To: set to the list.
4)  Add a new Sender: set to the saved From:.

Aside:  I'd likely also remove other headers that tend to break things, 
like DKIM* / Authentication* / et al.




--
Grant. . . .
unix || die

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org