Hi Team
I have observed few options those are present in Mailman 2 are not found in
Mailman 3 some of them are mentioned below. If the mentioned options are
already enabled please let me know where can I access them.
1.We have Bounce Processing as separate option in Mailman 2 but in Mailman
3 I h
This is with reference to a discussion in a thread [1] here:
I need two requirements :
- I need an object of a user which has an attribute which tells us what are all
the emails of the following user.
- I need an object of an email having an attribute which tells us what
mailing-lists that email
On Fri, Jan 07, 2011 at 07:30:51PM -0500, Barry Warsaw wrote:
> There are a couple of interesting things in MM3 that makes it different from
> MM2. In MM3, users and addresses are global to the system, while membership
> is specific to a mailing list. This means if we register a bounce on an
> ad
Barry Warsaw writes:
> There are a couple of interesting things in MM3 that makes it different from
> MM2. In MM3, users and addresses are global to the system, while membership
> is specific to a mailing list. This means if we register a bounce on an
> address, we can have that score affect
* Barry Warsaw :
> One of the last major subsystems that I need to get working in Mailman 3 is
> bounce processing. This is different than bounce detection, which has been
> successfully ported from Mailman 2, but doesn't differ in any significant
> way. The question I am thinking about now is wh
One of the last major subsystems that I need to get working in Mailman 3 is
bounce processing. This is different than bounce detection, which has been
successfully ported from Mailman 2, but doesn't differ in any significant
way. The question I am thinking about now is what to do with a bounce on
Greetings:
I currently manage a mailman installation on a Redhat system with a total of 229,000
subs spread fairly evenly over 72 announce only lists (averaging 3k users each) .
Recently I upgraded from 2.1.1 to 2.1.3 primarily because of the fix for the cross
site scripting bug but also for th
On Wed, Oct 15, 2003 at 12:17:14PM +0200, J?rgen A.Erhard wrote:
> Please, give me (us) some way to look at a bounce message. I feel
> so... powerless. It feels Microsofty... or, worse, Apple-y (sorry
> Chuq ;-). "You don't need to look at a bounce message, you won't
> understand it anyway." We
Hi Mailmen,
just got such a message from python-list:
python-list-request> Your membership in the mailing list Python-list has been
disabled due
python-list-request> to excessive bounces The last bounce received from you was
dated
python-list-request> 14-Oct-2003. You will not get
On Wed, 2003-07-23 at 08:39, Juan Enrique Gómez wrote:
> Hi!
>
> I have been looking how works the bounce daemon, and i see thtat
> everytime it processes a bounce, it rewrites the list file complete, is
> this possible?, if so i think this is a crazyness cause in lists with
> 200k users, every bo
Hi!
I have been looking how works the bounce daemon, and i see thtat
everytime it processes a bounce, it rewrites the list file complete, is
this possible?, if so i think this is a crazyness cause in lists with
200k users, every bounce takes to looong...
thanks for the info.
Best,
--
---
> "bob" == <[EMAIL PROTECTED]> writes:
bob> Also, don't forget that you need to ignore days that go by
bob> without posts. You need to count "posting" days.
I think I convinced myself that you don't, last time I thought hard
about it. I could be wrong, but I also believe not wor
Also, don't forget that you need to ignore days that go by without posts. You
need to count "posting" days.
Bob
>
>> 1) are we a member? No, return
>> 2) do we have previous bounces? No, register it skip to step 7
>> 3) is the member disabled? yes, quit
>> 4) is the bounce info from today?
> 1) are we a member? No, return
> 2) do we have previous bounces? No, register it skip to step 7
> 3) is the member disabled? yes, quit
> 4) is the bounce info from today? yes, don't increment, skip to step 7
> 5) is the info stale? yes, reset it and skip to step 7
> 6) increment score for
> "DM" == Dan Mick <[EMAIL PROTECTED]> writes:
DM> I could be high, but it looks like the sequence in Bouncer.py
DM> is:
| 1) are we a member? No, return
| 2) do we have previous bounces? No, register it and quit
| 3) is the member disabled? yes, quit
| 4) is the
I could be high, but it looks like the sequence in Bouncer.py is:
1) are we a member? No, return
2) do we have previous bounces? No, register it and quit
3) is the member disabled? yes, quit
4) is the bounce info from today? yes, quit
5) is the info stale? yes, clear it out
6) start looking
16 matches
Mail list logo
