/[pkg-listmaster]/trunk/bits/list-update-200803
ViewVC logotype

Diff of /trunk/bits/list-update-200803

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 146 by don, Fri Feb 8 21:24:12 2008 UTC revision 147 by cord, Fri Feb 8 21:33:39 2008 UTC
# Line 5  Subject: Bits from the listmaster team Line 5  Subject: Bits from the listmaster team
5  Hi everyone,  Hi everyone,
6    
7  the listmaster team is constantly trying to improve the setup of our  the listmaster team is constantly trying to improve the setup of our
8  listserver. Thus, quite a few things have happend since our last update in September  listserver. Thus, quite a few things have happend since our last update in
9  of last year. Here are some highlights:  September of last year. Here are some highlights:
10    
11    
12  lists.debian.org moved to a new hosting location  lists.debian.org moved to a new hosting location
# Line 17  service to the new machine (located at m Line 17  service to the new machine (located at m
17  list archives to that machine (which means the list archives are on the  list archives to that machine (which means the list archives are on the
18  same machine as the MX, and consequently fewer delays).  same machine as the MX, and consequently fewer delays).
19    
20    If you didn't have already we ask you to add the new IP 82.195.75.100 to your
21    whitelists.
22    
23    
24  New list archive search engine  New list archive search engine
25  ------------------------------  ------------------------------
# Line 41  Config clean up Line 44  Config clean up
44    
45  The Config Cleanup is another big project which seems to turn into an ongoing  The Config Cleanup is another big project which seems to turn into an ongoing
46  task. Since the last update we dicided to unify some global files for all  task. Since the last update we dicided to unify some global files for all
47  lists, and move all list specific config to extra files. (This follows the layout the  lists, and move all list specific config to extra files. (This follows the
48  inventors of smartlist had in mind)  layout the inventors of smartlist had in mind)
49    
50  We also want to move some information like moderation-status or maximum  We also want to move some information like moderation-status or maximum
51  mailsize per message to a global file, which is also used by the listarchive  mailsize per message to a global file, which is also used by the listarchive
52  and some more informational or statistical tools.  and some more informational or statistical tools.
53    
54  To check if lists are configured correctly Cord subscribed an address to all 182  To check if lists are configured correctly we subscribed an address to all 182
55  mailinglists and checked back a month later mainly for Ham/Spam-ratio, identified  mailinglists and checked back a month later for Ham/Spam-ratio, and other
56  incorrect spam rules, which were leading to some false positives. He also found  anomalies. We found some wrong spam-rules, which led to some false positives
57  lists which are supposed to carry only informational mails from an automtic  and other 'backdoors' which bypassed some of our spamrules, which lead to
58  system, so the rules were tightened even more while droping the  false negatives.  We also found lists which are supposed to carry only
59  usual spamfilters, so distribution is faster less CPU/Memory  informational mails from an automatic system, so we could tighten the rules,
60  is needed to get a single message through.  and on the other hand we could drop the usual spamfilters for those lists, so
61    distribution gets faster and we need less CPU/Memory ressources to get one
62  Cord also implemented the usual 'Precedence' and 'List-*'-Headers on some Lists  mail through.
63  and Automatic Responses, so we are now a little more net-friendly with our  
64  service.  We also implemented the usual 'Precedence' and 'List-*'-Headers on all lists
65    (we had some lists where those were missing) and Automatic Responses, so we
66    are now a little more net-friendly with our service.
67    
68  While reviewing things Cord also found that our bounce-handling had some issues.  While reviewing things we found that our bounce-handling had some issues, see
69    the next chapter for that.
70    
71  Better bounce handling  Better bounce handling
72  ----------------------  ----------------------
73  While checked our bounce-handling, because we get tons of bounces for some lists,  
74  Cord found that we didn't have working bounce handling for some lists  We checked our bounce-handling, because we got 500+ bounces for some lists,
75  (other-*, deity, *-digest, debian-private). It was also found that we couldn't  and found that we didn't have a working bounce handling for some lists
76  recognize bounces from mailaddresses containing a = or a !-character.  (other-*, deity, *-digest, debian-private). There were also problems in
77    handling and recognizing mailadresses containing = or !-characters.
78    
79  To address all these issues Cord rewrote some parts of our bounce-handler.  To address these issues we rewrote some parts of our bounce-handler.
80    
81  While analysing the bounces streaming in, it was also found that a lot of bounces are  While analysing the bounces streaming in, we found that a lot of bounces are
82  caused by Content-Filters which rejects listmail back to us. (which violates  caused by Content-Filters which reject listmail back to us (which violates
83  the RfC). Even worse: the majority of those are false positives.  the RfC). Even worse: the majority of those are false positives.
84    
85  To let those people know, a notification-system was implemented, which  To let those people know we implemented a notification-system, which
86  reports once a week the bounces to those adresses.  will notify users about bounces at maximum of once a week.
87    
88  A notification which informs forcibly unsubscribed users  We also implemented a notification which informs forcibly unsubscribed users
89  about the unsubscription was also implemented. This is a service for those people with a  about the unsubscription. This is a service for those people with a
90  temporarily unavailable or broken mailbox, so they can resubscribe back to all  temporarily unavailable or broken mailbox, so they can resubscribe back to all
91  lists. These notification will be sent out once a week, and up to a month  lists after their mailaddress is functional again. These notification will be
92  after the last unsubscription happened.  sent out once a week, up to a month after the last unsubscription happened.
93    
94  Both notification systems are in alpha-testing now and will be activated in  Both notification systems are in alpha-testing now and will be activated in
95  the next weeks.  the next weeks.
Legend:
Removed from v.146  
changed lines
  Added in v.147
  ViewVC Help
Powered by ViewVC 1.1.5