C:\BBS\FMAIL>grep "Toss Active" TOSSER.LOG
22:45:11 Toss Active: 0.015 sec.
22:46:00 Toss Active: 0.171 sec.
13:30:16 Toss Active: 2.125 sec.
13:52:33 Toss Active: 0.172 sec.
14:09:49 Toss Active: 0.171 sec.
16:16:57 Toss Active: 0.203 sec.
18:45:29 Toss Active: 0.203 sec.
18:58:05 Toss Active: 0.218 sec.
18:58:19 Toss Active: 0.203 sec.
19:09:40 Toss Active: 7.884 sec.
13:46:53 Toss Active: 0.313 sec.
13:54:08 Toss Active: 4.218 sec.
14:00:51 Toss Active: 0.218 sec.
14:01:46 Toss Active: 1.859 sec.
10:04:48 Toss Active: 1.860 sec.
18:23:26 Toss Active: 1.781 sec.
18:24:20 Toss Active: 0.406 sec.
10:20:22 Toss Active: 1.616 sec.
As you can see, it is not as fast as your Linux system, it is not bad though.
The biggest delay is unpacking my daily digest of FSXNET. Those are the times
FMail exceed a 1000ms.
ON>> I do this, as I get 100's of port scans a minute that would
ON>> normally trigger a "FMAIL TOSS" and really eat CPU...
WV> I get hardly any port scans on the binkp port. And binkd only triggers
WV> a toss if there was a true mailer session, and pkt's received...
Correct, however, if I put FMail Scan in my STARTBBS.BAT - I would scan way too
often. ;-)
** Off to research ECHOMAIL.JAM....
Ozz
--- FMail-W32 2.0.1.4
* Origin: Richmond VA (RVA) Fidonet Support (1:275/362)
