[Citadel Development] (no subject)

[IGnatius T Foobar]

 >currently its rather a concern howto do rate limmiting so citserver  
 >doesn't overrun peers or even the DNS server when doing a massive  
 >delivery...  
  
 We probably want to have a "maximum concurrent background tasks" setting,
or something to that effect.  At the moment, restarting citserver on a busy
site causes the whole thing to get hammered as it attempts the entire queue
at once. 
  
 Retry for SMTP is at the discretion of the sender, but the way we implemented
it before was to retry in (I think it was) 15 minutes, and then double the
retry time after every failed attempt up to a maximum of four hours, and then
keep trying every four hours until five days has passed.