CAcert Code Development list.

[Benny Baumann <benbe AT cacert.org>]

Hi Wytze,

Am 25.09.2014 10:48, schrieb Eva Stöwe:
> Hello,
> 
> thank you all for your great help.
thanks from me too.
> 
> On the timing:
> I do not think that we need an increased mail rate for something as policy
> informations. This is not time-critical in the sense that 24h make a real
> difference. In such a case it is muche more important to consider how to
> prevent that mails are marked as spam by automated spam-filters.
That's my point of view here too. While technically we DID use 10
mails/second for the Heartbleed mailing we encountered some issues with
spam traps. as usually spam traps respond to fast sending of mails
(alongside other signs) the decision was made to use the much more
consevative 5 mails/second rate which is still a lot faster than the
originl rate used at the beginning of the Heartbleed mailing.
> 
> This may be something else if a mailing is about security relevant
> information.
> 
> On Thu, 25 Sep 2014 09:19:34 +0200, Wytze van der Raay 
> <wytze AT cacert.org>
> wrote:
>> Hi Benny and others,
>>
>> On 09/24/2014 09:00 AM, Benny Baumann wrote:
>>> there finally is a reviewed version of the CCA policy mailing script, to
>>> be sent out to our users ASAP. The script was reviewed by Dirk Astrath
>>> and me and is based on the script used in the Heartbleed mailing; except
>>> for the following changes:
>>> * No German or other non-English text version
>>> * Incorporated the speed-up to use 5 Mails per Second
>>> * Adopted a unique file name for the restart information
>>> * Some minor clean up in the script
>>>
>>> Execution of the script has been agreed to by Eva.
>>>
>>> The script can be found in the latest version of the release branch as
>>> scripts/send_policy_cca_20140916.php or attached to this mail.
>>>
>>> Please report any issues with the execution of the script back to
>>> Software and the Policy Officer.
>>
>> The mailing script has been started on Sep 24, 09:45 CEST, and it
>> finished on Sep 25, 06:07 CEST. The total number of messages sent
>> out was 237.187. Since the system was sending out its regular mails
>> also, only approximate mail delivery statistics can be shown for
>> this mailing (compiled from the log with pflogsumm):
>>
>>  239689   received
>>  235122   delivered
>>       1   forwarded
>>    9786   deferred  (70825  deferrals)
>>   27462   bounced
>>       0   rejected (0%)
>>       0   reject warnings
>>       0   held
>>       0   discarded (0%)
>>
>>    1282m  bytes received
>>    1312m  bytes delivered
>>       1   senders
>>       1   sending hosts/domains
>>  205452   recipients
>>   95811   recipient hosts/domains
Interesting stats. Although some things don't seem to add up. IMHO.
Shouldn't it be more like about 280k mails? Or do we really have about
50k deleted accounts?
>>
>> Currently (Sep 25, 09:15 CEST) there are still some 4400 e-mails
>> queued for possible later delivery (or eventual failure). The
>> normal number of queued e-mails is around 50, so nearly all of these
>> queued mails can be attributed to the CCA mailing.
>>
>> For a next mail shot, I recommend to use a bit more agressive timing.
>> While sending out 5 mails/second allowed us to complete this mailing
>> within 24 hours, my estimate is that the system can handle 10 mails/
>> second without problems for its regular operations. This would cut
>> the required time for the mailing in half, to less than 12 hours.
>>
>> Regards,
>> -- wytze
> 

Regards,
BenBE.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature