Pete,
You're one of those "Reply-All" people aren't you :)
FYI, I had a customer press Reply-All on a message with 1,880
recipients on Thursday...he still can't use his account. The number of
recipients uncovered a bug in more than one E-mail server where it
couldn't figure out if it had bounced the message successfully, so it
kept retrying and retrying. These messages were also rather large, and
our URIBL component went nuts while trying to process every address
with DNS lookups so it was almost a denial of service for us as the
recipient.
Just figured I would give you or anyone else a kick out of the
Reply-All habit :)
Matt
Pete McNeil wrote:
GREAT!
_M
On Tuesday, October 11, 2005, 10:58:10 AM, Stephen wrote:
Pete,
It's working fine now...
agseap2t 20051011023411
d249f017a01ec.smd 0 16 Match 29721 60 1549
1571 63
agseap2t 20051011023411
d249f017a01ec.smd 0 16 Final 67573 52 0 3954
63
agseap2t 20051011030147
d2b19014f0222.smd 15 0 White 74524 0 1 621
51
agseap2t 20051011030147
d2b19014f0222.smd 15 0 Final 74524 0 0 2854
51
agseap2t 20051011031628
d2e89017a0237.smd 15 16 Match 506947 61 20 32
58
agseap2t 20051011031628
d2e89017a0237.smd 15 16 Match 183021 61 1975
1984 58
agseap2t 20051011031628
d2e89017a0237.smd 15 16 Final 506947 61 0
6622 58
agseap2t 20051011032054
-INITIALIZING- 0 0 ERROR_RULE_AUTH 73 0 0 0 0
agseap2t 20051011032054
-INITIALIZING- 0 0 ERROR_RULE_AUTH 73 0 0 0 0
agseap2t 20051011032054
-INITIALIZING- 0 0 ERROR_RULE_AUTH 73 0 0 0 0
agseap2t 20051011032055
-INITIALIZING- 0 0 ERROR_RULE_AUTH 73 0 0 0 0
--- Continued
---
agseap2t 20051011033829
-INITIALIZING- 0 0 ERROR_RULE_AUTH 73 0 0 0 0
agseap2t 20051011033829
-INITIALIZING- 0 0 ERROR_RULE_AUTH 73 0 0 0 0
agseap2t 20051011033829
-INITIALIZING- 0 0 ERROR_RULE_AUTH 73 0 0 0 0
agseap2t 20051011033830
-INITIALIZING- 0 0 ERROR_RULE_AUTH 73 0 0 0 0
agseap2t 20051011033830
-INITIALIZING- 0 0 ERROR_RULE_AUTH 73 0 0 0 0
agseap2t 20051011034716
d35c001550253.smd 0 94 Clean 0 0 0 2529 57
agseap2t 20051011043007
d3fc80174028a.smd 16 16 Match 232386 63 1 46
60
agseap2t 20051011043007
d3fc80174028a.smd 16 16 Match 459995 58 6557
6599 60
agseap2t 20051011043007
d3fc80174028a.smd 16 16 Final 459995 58 0
6727 60
agseap2t 20051011043140
d401d017a028c.smd 0 31 Match 510479 52 217
280 57
agseap2t 20051011043140
d401d017a028c.smd 0 31 Match 496805 58 5770
5782 57
agseap2t 20051011043140
d401d017a028c.smd 0 31 Match 465550 59 7180
7218 57
agseap2t 20051011043140
d401d017a028c.smd 0 31 Final 510479 52 0 7335
57
agseap2t 20051011043619
d413f018f028f.smd 16 16 Match 506947 61 20 32
50
--- Continued
---
agseap2t 20051011145215
dd19b0195073f.smd 0 16 Clean 0 0 0 6736 66
agseap2t 20051011145219
dd19f018f0741.smd 0 31 Match 48763 61 1 44
43
agseap2t 20051011145219
dd19f018f0741.smd 0 31 Match 462947 61 1598
1613 43
agseap2t 20051011145219
dd19f018f0741.smd 0 31 Final 48763 61 0 15686
43
agseap2t 20051011145415
dd213016d0744.smd 0 47 White 257246 0 0 163
50
agseap2t 20051011145415
dd213016d0744.smd 0 47 Final 257246 0 0 13308
50
Todays log of a new upload :
--07:43:37-- http://www.sortmonster.net/Sniffer/Updates/agseap2t.snf
= `agseap2t.new.gz'
Resolvingwww.sortmonster.net... done.
Connecting towww.sortmonster.net[207.97.229.114]:80... connected.
HTTP request sent, awaiting response...
200 OK
Length: unspecified
[application/x-sortmonster]
Remote file is newer, retrieving.
--07:43:43-- http://www.sortmonster.net/Sniffer/Updates/agseap2t.snf
= `agseap2t.new.gz'
Connecting towww.sortmonster.net[207.97.229.114]:80... connected.
HTTP request sent, awaiting response...
200 OK
Length: unspecified
[application/x-sortmonster]
