Quoting Geoff Deering ([EMAIL PROTECTED]):
> Mark Sapiro said the following on 14/01/2007 11:55 AM:
> > I agree, but in the case of VERP_CONFIRMATIONS, this is a site setting.
> > It defaults to No rather than Yes, because that is the 'safer' setting
> > because some MTA's will not be configured to
Mark Sapiro said the following on 14/01/2007 11:55 AM:
> I agree, but in the case of VERP_CONFIRMATIONS, this is a site setting.
> It defaults to No rather than Yes, because that is the 'safer' setting
> because some MTA's will not be configured to handle the reply address
> with confirmation token
Geoff Deering wrote:
>Thanks for clarifying that Mark. That's good, but I still think it has
>a basic interface problem if one is not aware of these features and is
>just running a standard mail list. It can be quite a problem for the
>average moderator.
I agree, but in the case of VERP_CON
Thanks for clarifying that Mark. That's good, but I still think it has
a basic interface problem if one is not aware of these features and is
just running a standard mail list. It can be quite a problem for the
average moderator.
Regards
Geoff
Mark Sapiro said the following on 14/01/2007 1
Geoff Deering wrote:
>. At first glance it looks like any old spammer phishing for login
>information. Is it possible to modify the mass mailout subscribe/invite
>so there is a custom subject header?
If you set
VERP_CONFIRMATIONS = Yes
in mm_cfg.py, the subject will be "You have been invite
Hi,
A few months back I moved one lot of subscriptions to a new site and
list (used as an announce list) and invited people to subscribe. Very
few people took this up, and after a poorly attended major event I got a
lot of feedback that people who thought they had subscribed found out
they mi
