Re: [Mailman-Users] "Prevent" Reply-all

2016-10-25 Thread Bernd Petrovitsch
Hi! On Tue, 2016-10-25 at 21:46 +, Ryan C Stasel wrote: [...] > User A send message to list. List members get the mail, but it > “appears” to be from User A and not from the list. So a Reply and And the mail actually *was* from user A - it was just replicated and distributed to many others

Re: [Mailman-Users] "Prevent" Reply-all

2016-10-25 Thread Ryan C Stasel
> On Oct 25, 2016, at 15:42 , Mark Sapiro wrote: > > On 10/25/2016 02:46 PM, Ryan C Stasel wrote: >> > There's not much you can do with list configuration. > > Mailman ensures the list posting address is always in To: or Cc:, so you > have to modify code

Re: [Mailman-Users] "Prevent" Reply-all

2016-10-25 Thread Mark Sapiro
On 10/25/2016 02:46 PM, Ryan C Stasel wrote: > > What I want is really what rpschwar wanted back then. > > User A send message to list. List members get the mail, but it “appears” to > be from User A and not from the list. So a Reply and Reply-all both do the > same thing. To really

[Mailman-Users] "Prevent" Reply-all

2016-10-25 Thread Ryan C Stasel
Hi everyone, I’ve been googling a bit, but the only thing I can find is from back in 2010 (https://mail.python.org/pipermail/mailman-users/2010-May/069388.html) as to if it’s possible to configure a mailman list to “prevent” reply-all. Basically, I support a lot of users that seem to not

Re: [Mailman-Users] Migrating Mailman to New Server (Same Domain)

2016-10-25 Thread Matthias Schmidt via Mailman-Users
> Am 24.10.2016 um 22:41 schrieb Jewel Brueggeman-Makda > : > > Would it be best to copy the entire mailman directory to the new server or > just the lists and archives? > Command issued on new server to copy data from old. > rsync -avr