Skip to Content.
Sympa Menu

en - [sympa-users] Bounce management clarification...

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Marco Gaiarin <address@concealed>
  • To: address@concealed
  • Subject: [sympa-users] Bounce management clarification...
  • Date: Thu, 18 Apr 2013 18:47:50 +0200


Still i'm seeking some feedback...

[ This is a repost of the following article: ]
[ From: Marco Gaiarin <address@concealed> ]
[ Subject: Bounce management clarification... ]
[ Newsgroups: lists.sympa.users ]
[ Message-ID: <address@concealed> ]


In our organization we are using Sympa (debian squeeze, 6.0.1) to manage
some lists.

We are facing a little trouble: there's no management of bounce, seems to me
because the trigger never apply.

The help of the installer sympa version say:

Bounces

"Bounces" represent the subscribers whose address is in error, i.e.
subscribers who can not receive the messages sent to the list. This can be
due to many reasons: obsolete email addresses, addresses temporarily
unavailable when messages were sent, inbox quota exceeded, etc.

The 'Bounce management' section defines two rates:

The warn rate indicates the bouncing email addresses rate from which the
list owner will receive a notice entitled 'Bounce rate too high' inviting
him/her to delete bouncing subscribers from the list.
The halt rate indicates the bouncing email addresses rate from which the
message distribution will automatically be stopped up to the resolution of
the problem (generally through the deletion of bouncing subscribers).

The 'Management of bouncers, 1st level' and 'Management of bouncers, 2nd
level' sections allow you to perform automatic tasks with regard to bouncing
subscribers. You can define:

the score ranges that define level 1 and level 2 bouncers. By default,
level 1 bouncers have a score comprised between 45 and 74 and level 2
bouncers have a score comprised between 75 and 100;

The score depends on the number, type and frequency of errors. If the
bouncing time is too short or if there have not been many errors, the
bouncer is not given a score.
the task to perform towards the subscribers concerned: no task, notice,
deletion from the list;
the person to be notified when a task is carried out: no one, the list
owners, the listmasters. The notice sent when a task is carried out involves
the names of all the subscribers concerned as well as precise information
about the task.

To manage bounces (reset errors for some subscribers, unsubscribe bouncing
subscribers, request a subscription reminder, etc.), go to the 'Bounces'
page of the list administration module.

BE CAREFUL: do not forget to click on the 'Update' button on bottom of page
to save all your changes.

But does not explain how bounce scores are calculated.

Current docs seems a bit more clear:

http://www.sympa.org/manual/bounces

eg, the formula is:

Score = bounce_count * type_rate * regularity_rate

but my theresold values are expressed in percentual, while these seems
absolute value, or better, there's a 'rate' (%) and 'theresold' (points).


Anyway to properly account 'bounce_count', i've also to tweak
'minimum_bouncing_count' and 'minimum_bouncing_period', but these are
''global'' parameters, non ''per list'' one.


I'm a bit confused. ;-)

--
Le persone ti pesano? Non metterle sulle tue spalle.
Portale nel cuore. (Don Helder Camara)

--
Ragazzi, lavoriamo per il Signore:
la paga non è un granchè, ma la pensione è roba dell'altro Mondo!!!
(letta su una maglietta, da Stefy)




Archive powered by MHonArc 2.6.19+.

Top of Page