Re: [Mailman-Users] ****SPAM**** Re: Block reply to all

[Stephen J. Turnbull]

"Shop at \" Just Brits \"" writes:

 > So my only remaining question is "Why a MM List at all. ?" ??

So that members can update their own addresses and other information
(eg, turn delivery off when on vacation).  The MUA group solution
requires that the director update that information.

Also, when we move to MM3, a member database with lots of other
interesting information (eg, members' instruments, members with
instruments to loan, members who can play instruments they don't
currently own) could be attached in lieu of the rather impoverished
database we use now.
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Block reply to all

[Stephen J. Turnbull]

rpsch...@knology.net writes:

 > Let me give further explanation of why I need this.  The site I
 > support is a community band.  When there is an email set to
 > everyone from the director about something, we do not want each
 > person to reply to all.  They should only be replying back to the
 > person who sent the email (the director).  That is why we want to
 > limit the reply to all.

The obvious solution is to have a dedicated announce list for the
director's use for such announcements.  Set the reply-to to the
director's preferred mail address for receiving such responses.  Set
member post to no.  Set the allowed posters to the director's
addresses, plus the addresses of any other "responsible parties" who
should be allowed to post (vice director, listmaster relaying a phone
message from the director, etc).  Finally, set a privacy rule to
discard (possibly reject) unauthorized posts.  There's more info in
the FAQ, a search for "announcement list" should pull it up.  Also,
"clone list" (since you'll want a convenient way to copy the
membership list).

Rationale: everything should be obvious except the use of a separate
list, and the discard vs reject issue.  Using a separate list allows
you to have different rules for announcements (band member polls, I
guess?) and for discussion.  Since only the director needs to post to
it, only he/she needs to learn to use it, and it shouldn't be too hard
to learn if use is at all frequent.  Everybody else only really needs
to know the discussion list posting address.  The biggest cost is that
somebody needs to make sure that every new member is on both lists.
(Yes, this is stupid, and it will be fixed in Mailman 3, but we're not
there yet.  It also has the advantage that people who don't want to
receive general discussion can tune out without losing the important
announcements from the director.)

"Discard" means "without notifying the sender".  "Reject" means with
notification.  For the expected reply, there are three cases:

1.  The respondent sends only to the director: the list filter is not
involved at all.  No problem with any list settings! :-)
2.  The respondent does reply-to-all: the personal copy to the
director is sent and received, the copy to the list filtered.
With discard, the director is informed and the respondent is not
spammed with a reject notice.  This is what you want.  With
reject, the respondent is spammed, may try again, and worse, may
contact you for help.  Yucky.
3.  The respondent removes the director's address and sends only to
the list.  With "discard", they never know; with "reject", they
are informed of their mistake.  However, this is perverse
behavior.  It seems unlikely to be a frequent problem, since it
requires both doing reply-to-all and deliberately removing the
director's address, which will *always* be one of the addresses.

Unexpected replies are probably of the form "it's a band list, if I
reply to it, it will go to the band".  I can't really call this
"perverse", just, ah, "uneducated".  I suggest calling the list "XYZ
Band Director Announcement", and even if people accidentally send to
it thinking it's the discussion list, they'll be a little sheepish
about it, which will reduce the likelihood of complaints.

When first introducing the system, you might consider "hold" instead
of "discard"; this would allow you to recover inadvertant real posts,
at the cost of having to explicitly discard a possibly large number of
reply-to-alls.  After a reasonable educational period (you'd have to
decide that based on the band members), switch to discard.  Keep stats
on how many reply-to-alls are received vs. inadvertant real posts;
that will convince any reasonable person that the educational period
is really a burden on the list moderator, and should be kept short.

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Limitations on the subscriptions

[Mark Sapiro]

Nicolas Seichepine wrote:
>
>The problem is that no matter how many times I repeat to administrators and 
>users to use only these addresses, subscriptions are regularly made with other 
>addresses, which are rejected and generate a lot of bounces.
>
>I would like to know if there is a mean to verify automatically during the 
>subscription process if the address is something like x...@domain.ext...


You should be able to use the ban_list for this (Privacy options... ->
Subscription rules -> ban_list). The operation of the ban_list has
been improved somewhat since 2.1.5, e.g. In 2.1.5 you couldn't
subscribe a banned address, but you could change your address to a
banned address, but it should work for your purpose.

A regexp like:

^.+@(?!domain\.ext$)

will ban every address that is not @domain.ext.

-- 
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Nonexistent user receiving a monthly passwordreminder

[Mark Sapiro]

Pat Plummer wrote:
>
>A few months ago, I had to restore my server from back up due to catastrophic 
>drive failure. Since then I have had a single user that was deleted over 3 
>years ago that has begun to get monthly password reminders for a list she no 
>longer belongs to. Her name does not show up in any list member lists/dumps 
>and the problem does not respond to the scripts for addresses that have 
>unusual or upper case characters, etc etc. I have tried to look through the 
>script that handles this (mailpasswds), but cannot figure out where this 
>script gets its user info. She does not receive the list traffic that this 
>active list has -- only the reminders.


It gets its information from the config.pck files of the the various
lists.


>I have also tried adding her and re-deleting her, logging into the page that 
>is sent in email (the page comes up in the browser, but does not respond to 
>logins/auth failed error), and have tried to look through config files that 
>appear to be likely suspects, but cannot find her email address anywhere.
>
>If someone could at least point me in the right direction or suggest relevant 
>sections in the fine manual that might apply, I'd be grateful. I rather not 
>turn off monthly reminders for everyone else if possible.


Turning off reminders for the current list won't solve the problem
because the reminders are coming from some other test/back-up/whatever
Mailman instance that is running cron/mailpasswds against some old
data.

Look at all the Received: headers in the reminder mail. They should
tell you from what server the reminder originated. If it is not the
current server, find it and remove Mailman's crontab. If it is the
current server do

locate mailpasswds

or

find / -name mailpasswds

to find the 'other' Mailman.

-- 
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Limitations on the subscriptions

[Nicolas Seichepine]

Hello,

I take care of a server with mailman 2.1.5 and numerous lists, but I administer 
only a small part of them.

Besides, my SMTP relay allows me to send e-mails only on a particular domain 
(university addresses).

The problem is that no matter how many times I repeat to administrators and 
users to use only these addresses, subscriptions are regularly made with other 
addresses, which are rejected and generate a lot of bounces.

I would like to know if there is a mean to verify automatically during the 
subscription process if the address is something like x...@domain.ext...

Thank you very much,

Nicolas   
_
Consultez vos emails Orange, Gmail, Yahoo!, Free ... directement depuis HOTMAIL 
!
http://www.windowslive.fr/hotmail/agregation/
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Nonexistent user receiving a monthly password reminder

[Pat Plummer]

I have an interesting problem. I have been reading google hits and mailman 
archives for the last several hours and have not been able to find anything 
that addresses the above problem.

Here's the deal:

A few months ago, I had to restore my server from back up due to catastrophic 
drive failure. Since then I have had a single user that was deleted over 3 
years ago that has begun to get monthly password reminders for a list she no 
longer belongs to. Her name does not show up in any list member lists/dumps and 
the problem does not respond to the scripts for addresses that have unusual or 
upper case characters, etc etc. I have tried to look through the script that 
handles this (mailpasswds), but cannot figure out where this script gets its 
user info. She does not receive the list traffic that this active list has -- 
only the reminders.

I have also tried adding her and re-deleting her, logging into the page that is 
sent in email (the page comes up in the browser, but does not respond to 
logins/auth failed error), and have tried to look through config files that 
appear to be likely suspects, but cannot find her email address anywhere.

If someone could at least point me in the right direction or suggest relevant 
sections in the fine manual that might apply, I'd be grateful. I rather not 
turn off monthly reminders for everyone else if possible.

Thanks in advance!

Pat

--
Pat Plummer
blacksun at ix dot gotdns dot org
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] ****SPAM**** Re: Block reply to all

[Shop at " Just Brits "]

I am sure [most Mark -:)] know that I AM a huge fan & supporter
of MM even tho I am stuck with the cPanel version.

I have been reading all the mails on this subject with a bunch of
questions swirling around my teeny brain -:) !!

<< Let me give further explanation of why I need this. The site I 
support is a community band. When there is an email set to everyone from 
the director about something, we do not want each person to reply to 
all. They should only be replying back to the person who sent the email 
(the director). That is why we want to limit the reply to all. >>


So my only remaining question is "Why a MM List at all. ?" ??

Simply have the Director set-up a 'Group' in his eMail Client,
SEND to the 'Group' and then there would ONLY be ONE
person anyone in the 'Group' could "Reply-to:" [or even
"Reply-all:"  which would only yield the Director] ?!?!?

Even an 'Announcement Only' type List does NOT make sense
to me ?!?!?!

Ed
Please visit MY site at:
www.justbrits.com

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] ****SPAM**** Re: Block reply to all

[Mark Sapiro]

rpsch...@knology.net wrote:

>Let me give further explanation of why I need this.  The site I support is a 
>community band.  When there is an email set to 
>everyone from the director about something, we do not want each person to 
>reply to all.  They should only be replying back 
>to the person who sent the email (the director).  That is why we want to limit 
>the reply to all.


See the FAQ at  on how to set up this kind
of list.

-- 
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] ****SPAM**** Re: Block reply to all

[rpschwar]

Let me give further explanation of why I need this.  The site I support is a 
community band.  When there is an email set to 
everyone from the director about something, we do not want each person to reply 
to all.  They should only be replying back 
to the person who sent the email (the director).  That is why we want to limit 
the reply to all.

Robert
On Sun 02/05/10  7:01 PM , Grant Taylor gtay...@riverviewtech.net sent:
> Geoff Shang wrote:
> > Frankly, I think the best approach would be just to
> moderate the list.  > If people realise that follow-ups aren't going to
> get posted, they'll > stop sending them.
> 
> *chuckle*
> 
> From my experience, you over estimate some of the user base that I have
> had the pleasure of supporting.  ;-)
> 
> 
> 
> Grant. . . .
> --
> Mailman-Users mailing list Mail
> man-us...@python.orghttp://mail.python.org/mailman/listinfo/mailman-usersMailman
>  FAQ: http://wiki.list.org/x/AgA3Security 
Policy: http://wiki.list.org/x/QIA9Searchable Archives: 
http://www.mail-archive.com/mailman-users%40python.org/Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/rpschwar%4
> 0knology.net
> 
> 


--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Changing host names, revisited... POSTFIX_STYLE_VIRTUAL_DOMAINS?

[Mark Sapiro]

Tanstaafl wrote:

>On 2010-05-02 5:22 PM, Mark Sapiro wrote:
>
>> If your list mail goes to @example.com and example.com is a local
>> domain in Postfix (i.e. in mydestinations), you don't want
>> POSTFIX_STYLE_VIRTUAL_DOMAINS at all and you don't want any references
>> to Mailman's virtual-mailman in virtual_alias_maps in Postfix.
>
>It's not local, I'm using virtual_mailbox_domains/maps... I do host
>email for two other domains, just no lists (and no need for them)...


This gets complicated. My question at this point is how is mail to
listn...@example.com getting to Mailman. Any virtual mappings in
Mailman's virtual-mailman will be for the listn...@myhost.example.com,
etc. addresses, so Postfix can't be relying on that for delivery. So
if example.com is not a local domain, how is mail to that domain
getting to Postfix's local delivery in order that Mailman's pipe
aliases are effective. Are transport maps involved for this domain?

I probably need to see "postconf -n" and to understand whether there
are only list addresses @example.com or if there are non-list virtual
mailbox users @example.com too.

Also, there are mailman generated addresses such as list-bounces, and
these are currently all generated @myhost.example.com, so how is that
mail delivered?

-- 
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Block reply to all

[Grant Taylor]

Geoff Shang wrote:
Frankly, I think the best approach would be just to moderate the list.  
If people realise that follow-ups aren't going to get posted, they'll 
stop sending them.


*chuckle*

From my experience, you over estimate some of the user base that I have 
had the pleasure of supporting.  ;-)




Grant. . . .
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Block reply to all

[Geoff Shang]

Hi,

Frankly, I think the best approach would be just to moderate the list.  If 
people realise that follow-ups aren't going to get posted, they'll stop 
sending them.


Geoff.

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Changing host names, revisited... POSTFIX_STYLE_VIRTUAL_DOMAINS?

[Tanstaafl]

On 2010-05-02 5:22 PM, Mark Sapiro wrote:
> On 5/2/2010 12:41 PM, Tanstaafl wrote:
>> The first question I have is about POSTFIX_STYLE_VIRTUAL_DOMAINS. In the
>> FAQs about changing hostnames, this setting is not mentioned.
>>
>> Now, this server only hosts lists for one domain: example.com.
>>
>> So - should I also change that setting to lists.example.com too (per
>> below)? Or, since I am not running lists for more than one domain, can
>> my setup be simplified somehow? Or does it even come into play?

> Since the email domain for all your lists is (or should be) example.com,
> anything other than example .com in POSTFIX_STYLE_VIRTUAL_DOMAINS has no
> effect. I.e.

Ok, so, after your previous, I'm confused as to what to do to fix this...

>> Defaults.py currently contains
>>
>>> DEFAULT_EMAIL_HOST = 'myhost.example.com'
>>> DEFAULT_URL_HOST = 'myhost.example.com'

> probably wrong.

Yeah, I kind of figured that, so now I just need to know how to fix it
without breaking anything...

> The order of the above two is wrong. "VIRTUAL_HOSTS.clear()" clears the
> VIRTOUAL_HOSTS dictionary. You don't want it after your add_virtualhost
> as you will end up with nothing. You first want
> 
> VIRTUAL_HOSTS.clear()
> 
> to remove any incorrect or irrelevant entry from Defaults.py. This is
> followed by
> 
> add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> 
> to add the newly defined values.

Thanks, fixed...

>>> DEFAULT_URL_PATTERN = 'https://%s/mailman/'
>>> #POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.example.com']
>>> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['myhost.example.com']
>>> ALLOW_SITE_ADMIN_COOKIES = Yes

> If your list mail goes to @example.com and example.com is a local
> domain in Postfix (i.e. in mydestinations), you don't want
> POSTFIX_STYLE_VIRTUAL_DOMAINS at all and you don't want any references
> to Mailman's virtual-mailman in virtual_alias_maps in Postfix.

It's not local, I'm using virtual_mailbox_domains/maps... I do host
email for two other domains, just no lists (and no need for them)...

So, now my new mm_cfg.py is:

> ##
> # Put YOUR site-specific settings below this line.
> MTA = 'Postfix'
> #DEFAULT_EMAIL_HOST = 'example.com'
> #DEFAULT_URL_HOST = 'lists.example.com'
> #VIRTUAL_HOSTS.clear()
> #add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> DEFAULT_URL_PATTERN = 'https://%s/mailman/'
> #POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.example.com']
> #POSTFIX_STYLE_VIRTUAL_DOMAINS = ['myhost.example.com']
> ALLOW_SITE_ADMIN_COOKIES = Yes

?

Or, should I make POSTFIX_STYLE_VIRTUAL_DOMAINS = ['example.com']

-- 

Charles
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Changing host names, revisited... DEFAULT_EMAIL_HOST

[Tanstaafl]

On 2010-05-02 5:03 PM, Mark Sapiro wrote:
> If you go to the list's listinfo page, what does it say the list posting
> address is? If it says listn...@example.com, then either you had
> different settings when you created the list, or you changed the list's
> host_name attribute on the General Options admin page from
> myhost.example.com to example.com.

The list posting address is set to:

listn...@myhost.example.com

The host name (in the web options interface) is set to:

myhost.example.com

> On the other hand, if the listinfo page says listn...@myhost.example.com
> then all the email addresses Mailman generates for this list are
> @myhost.example.com. Now they probably work because
> 
>>> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['myhost.example.com']
> 
> says generate virtual alias maps for Postfix for any list that has
> host_name myhost.example.com, so if Postfix is configured to use
> Mailman's data/virtual-mailman, mail sent to list addresses
> @myhost.example.com will be properly delivered.
> 
> Note that all DEFAULT_EMAIL_HOST does is set the default host_name
> attribute for new lists. Once a list is created, it has no effect.

Ok... so, apparently this is slightly broken, but working...?

I would strongly prefer to fix this properly.

Thanks for your help Mark, your courtesy and expertise never cease to
amaze...

-- 

Charles
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Changing host names, revisited... final steps...

[Mark Sapiro]

Tanstaafl wrote:
>
>Is there any special order for making these changes, or just:
>
>1. Make the changes to mm_cfg.py per below
>
>2. Restart mailman
>
>3. Run $prefix/bin/withlist -l -a -r fix_url to fix all existing lists
>
>4. Restart mailman
>
>5. Done...?


It probably isn't necessary to restart Mailman at all for these
changes. I would skip the step 2 restart and just to be safe, do the
one after fix_url. Or to be really safe, stop Mailman before step 1
and start Mailman at step 4

What about web server changes for the lists.example.com vs.
myhost.example.com change (there may not be any), and DNS for the
lists.example.com domain?


Note that if 'example.com' is a virtual domain in Postfix, you will need

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['example.com']

and in that case, I recommend step 0 stop Postfix, Step 3.5 Run
$prefix/bin/genaliases, step 4.5 start Postfix.

-- 
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Changing host names, revisited... POSTFIX_STYLE_VIRTUAL_DOMAINS?

[Mark Sapiro]

On 5/2/2010 12:41 PM, Tanstaafl wrote:
> 
> The first question I have is about POSTFIX_STYLE_VIRTUAL_DOMAINS. In the
> FAQs about changing hostnames, this setting is not mentioned.
> 
> Now, this server only hosts lists for one domain: example.com.
> 
> So - should I also change that setting to lists.example.com too (per
> below)? Or, since I am not running lists for more than one domain, can
> my setup be simplified somehow? Or does it even come into play?


Since the email domain for all your lists is (or should be) example.com,
anything other than example .com in POSTFIX_STYLE_VIRTUAL_DOMAINS has no
effect. I.e.

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['myhost.example.com']

would only do anything for a list whose host_name (email domain) is
myhost.example.com, and changing it to

POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.example.com']

would only do anything for a list whose host_name (email domain) is
lists.example.com.
> Defaults.py currently contains
> 
>> DEFAULT_EMAIL_HOST = 'myhost.example.com'
>> DEFAULT_URL_HOST = 'myhost.example.com'

probably wrong.


>> DEFAULT_URL_PATTERN = 'http://%s/mailman/'
>
> And my current/recently edited mm_cfg.py - the commented settings/lines
> below are the changes I've added, in preparation for the change, and
> will just comment/uncomment the relevant ones to 'flip the switch':
> 
>> ##
>> # Put YOUR site-specific settings below this line.
>> MTA = 'Postfix'
>> #DEFAULT_EMAIL_HOST = 'example.com'
>> #DEFAULT_URL_HOST = 'lists.example.com'
>> #add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
>> #VIRTUAL_HOSTS.clear()

The order of the above two is wrong. "VIRTUAL_HOSTS.clear()" clears the
VIRTOUAL_HOSTS dictionary. You don't want it after your add_virtualhost
as you will end up with nothing. You first want

VIRTUAL_HOSTS.clear()

to remove any incorrect or irrelevant entry from Defaults.py. This is
followed by

add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)

to add the newly defined values.


>> DEFAULT_URL_PATTERN = 'https://%s/mailman/'
>> #POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.example.com']
>> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['myhost.example.com']
>> ALLOW_SITE_ADMIN_COOKIES = Yes


If your list mail goes to @example.com and example.com is a local
domain in Postfix (i.e. in mydestinations), you don't want
POSTFIX_STYLE_VIRTUAL_DOMAINS at all and you don't want any references
to Mailman's virtual-mailman in virtual_alias_maps in Postfix.

-- 
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Changing host names, revisited... final steps...

[Tanstaafl]

Lastly...

Is there any special order for making these changes, or just:

1. Make the changes to mm_cfg.py per below

2. Restart mailman

3. Run $prefix/bin/withlist -l -a -r fix_url to fix all existing lists

4. Restart mailman

5. Done...?

Thanks again,

Charles

*** My current and proposed new settings:

Defaults.py currently contains

> DEFAULT_EMAIL_HOST = 'myhost.example.com'
> DEFAULT_URL_HOST = 'myhost.example.com'
> DEFAULT_URL_PATTERN = 'http://%s/mailman/'

And my current/recently edited mm_cfg.py - the commented settings/lines
below are the changes I've added, in preparation for the change, and
will just comment/uncomment the relevant ones to 'flip the switch':

> ##
> # Put YOUR site-specific settings below this line.
> MTA = 'Postfix'
> #DEFAULT_EMAIL_HOST = 'example.com'
> #DEFAULT_URL_HOST = 'lists.example.com'
> #add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> #VIRTUAL_HOSTS.clear()
> DEFAULT_URL_PATTERN = 'https://%s/mailman/'
> #POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.example.com']
> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['myhost.example.com']
> ALLOW_SITE_ADMIN_COOKIES = Yes
-- 

Charles
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Changing host names, revisited... DEFAULT_EMAIL_HOST

[Mark Sapiro]

On 5/2/2010 1:21 PM, Tanstaafl wrote:
> The second question I have is about the DEFAULT_EMAIL_HOST setting...
> 
> Currently, people send to my lists using listn...@example.com and
> everything is working fine. But, while prepping for this change I found
> this commented section from someone's mm_cfg.py (these comments aren't
> in mine for some reason):
> 
> # For example, if people visit your Mailman system with
> # "http://www.dom.ain/mailman"; then your url fqdn is "www.dom.ain",
> # and if people send mail to your system via "yourl...@dom.ain" then
> # your email fqdn is "dom.ain".  DEFAULT_URL_HOST controls the former,
> # and DEFAULT_EMAIL_HOST controls the latter.


The comments are in some downstream package. They aren't in the default
GNU Mailman distribution.


> According to this, my DEFAULT_EMAIL_HOST should just be 'example.com',
> but it isn't, it is myhost.example.com - so why is mine working ok?


If you go to the list's listinfo page, what does it say the list posting
address is? If it says listn...@example.com, then either you had
different settings when you created the list, or you changed the list's
host_name attribute on the General Options admin page from
myhost.example.com to example.com.

On the other hand, if the listinfo page says listn...@myhost.example.com
then all the email addresses Mailman generates for this list are
@myhost.example.com. Now they probably work because

>> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['myhost.example.com']

says generate virtual alias maps for Postfix for any list that has
host_name myhost.example.com, so if Postfix is configured to use
Mailman's data/virtual-mailman, mail sent to list addresses
@myhost.example.com will be properly delivered.

Note that all DEFAULT_EMAIL_HOST does is set the default host_name
attribute for new lists. Once a list is created, it has no effect.

-- 
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Block reply to all

[Mark Sapiro]

On 5/2/2010 12:10 PM, rpsch...@knology.net wrote:
> 
> This is what I'm trying to do. User x sends a post to listy. User z
> receives the post from the list.
> 
> I want user Z only to be able to reply to user x and otherwise to be
> required to send a new, origional, not-preply message to the list.


Thanks for the explanation. The short answer is you can't remove the
list posting address from all the headers. Normally it will be in the
To: header or Cc: header and 'reply-all' will include the list. If the
personalization options are available to you, you can set the list(s) to
Full Personalization which will replace the To: header with one that is
To: the recipient of the message, but this will not help because Mailman
will in this case add a Cc: to the list posting address in order to
facilitate including the list in replies.

Mailman works this way because it is designed mainly for discussion
lists where people carry out a multi-way conversation on the list.

Thus, the only thing you can do is as has been suggested, apply
header_filter_rules to not accept posts that contain In-Reply-To: and/or
References: headers, or use max_num_recipients = 2 to hold all posts
with more than one recipient.

To this latter suggestion, you replied:

> That didn't work because the first message sent will go to yourself
> and the mailing list which will be blocked. If you tell it not to send
> it to yourself, the first message will send. If you try to reply to all
> to this message it will also be sent because the reply to will only have
> the member list.


This reply raises other questions. The first sentence seems to indicate
you want to send to the list with Cc: to yourself, and yes, such a post
would be held as it would have 2 recipients. However, the last sentence
indicates you are concerned about people replying-all to their own
posts. Is this a real concern, or is it just something you encountered
in testing with replying to your own post? I.e., normally, a reply-all
would include the list and the poster and would be held for 2
recipients. Only in the case where you are replying-all to your own post
and not editing the recipients, would the post have only one recipient.

Of course with a recipient limit, the user could still do a reply-all
and then remove all but the list address from the addressees before
sending, and this reply would go to the list if you were only checking
the number of recipients, so it seems if you want to block all
non-original messages, header_filter_rules would be the way to go.

-- 
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
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Changing host names, revisited... DEFAULT_EMAIL_HOST

[Tanstaafl]

The second question I have is about the DEFAULT_EMAIL_HOST setting...

Currently, people send to my lists using listn...@example.com and
everything is working fine. But, while prepping for this change I found
this commented section from someone's mm_cfg.py (these comments aren't
in mine for some reason):

# For example, if people visit your Mailman system with
# "http://www.dom.ain/mailman"; then your url fqdn is "www.dom.ain",
# and if people send mail to your system via "yourl...@dom.ain" then
# your email fqdn is "dom.ain".  DEFAULT_URL_HOST controls the former,
# and DEFAULT_EMAIL_HOST controls the latter.

According to this, my DEFAULT_EMAIL_HOST should just be 'example.com',
but it isn't, it is myhost.example.com - so why is mine working ok?

Thanks,

Charles

*** My current and proposed new settings:

Defaults.py currently contains

> DEFAULT_EMAIL_HOST = 'myhost.example.com'
> DEFAULT_URL_HOST = 'myhost.example.com'
> DEFAULT_URL_PATTERN = 'http://%s/mailman/'

And my current/recently edited mm_cfg.py - the commented settings/lines
below are the changes I've added, in preparation for the change, and
will just comment/uncomment the relevant ones to 'flip the switch':

> ##
> # Put YOUR site-specific settings below this line.
> MTA = 'Postfix'
> #DEFAULT_EMAIL_HOST = 'example.com'
> #DEFAULT_URL_HOST = 'lists.example.com'
> #add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> #VIRTUAL_HOSTS.clear()
> DEFAULT_URL_PATTERN = 'https://%s/mailman/'
> #POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.example.com']
> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['myhost.example.com']
> ALLOW_SITE_ADMIN_COOKIES = Yes
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Changing host names, revisited... POSTFIX_STYLE_VIRTUAL_DOMAINS?

[Tanstaafl]

Ok, I got sidetracked a long time ago, and because this isn't pressing,
it went to a back-burner, but I'm ready to do this now. My apologies in
advance if I'm being overly cautious, but I've avoided a lot of
problems, some major, by asking a lot of questions before doing
something like this that I've never done before.

Goal is simple: change the URL/hostname for my lists from their current
'myhost.example.com' to 'lists.example.com'.

If it matters, these lists are *not* publicly accessible, and they are
*not* archived.

After re-reading the two FAQs regarding this, I have a few things I'm
not certain of, so will pose the questions one at a time, and will
include my current Defaults.py and my new mm_cfg.py with the new
settings/changes commented at the bottom of each message.

The first question I have is about POSTFIX_STYLE_VIRTUAL_DOMAINS. In the
FAQs about changing hostnames, this setting is not mentioned.

Now, this server only hosts lists for one domain: example.com.

So - should I also change that setting to lists.example.com too (per
below)? Or, since I am not running lists for more than one domain, can
my setup be simplified somehow? Or does it even come into play?

Thanks,

Charles

*** My current and proposed new settings:

Defaults.py currently contains

> DEFAULT_EMAIL_HOST = 'myhost.example.com'
> DEFAULT_URL_HOST = 'myhost.example.com'
> DEFAULT_URL_PATTERN = 'http://%s/mailman/'

And my current/recently edited mm_cfg.py - the commented settings/lines
below are the changes I've added, in preparation for the change, and
will just comment/uncomment the relevant ones to 'flip the switch':

> ##
> # Put YOUR site-specific settings below this line.
> MTA = 'Postfix'
> #DEFAULT_EMAIL_HOST = 'example.com'
> #DEFAULT_URL_HOST = 'lists.example.com'
> #add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
> #VIRTUAL_HOSTS.clear()
> DEFAULT_URL_PATTERN = 'https://%s/mailman/'
> #POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.example.com']
> POSTFIX_STYLE_VIRTUAL_DOMAINS = ['myhost.example.com']
> ALLOW_SITE_ADMIN_COOKIES = Yes
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org