Re: Protocol logging and date

2009-07-06 Thread Privateofcourse
Hello Roelof,

This is what you said on Sat, 4 Jul 2009 18:09:47 +0200 your time:

 The contents of the sent or received messages might give you some idea
 of  the  date  of  the  transaction.  The protocol log is intended for
 problem hunting, not for keeping permanent stats.

Well, for starters, I'm not using protocol logging for keeping permanent
stats. I'm actually using it for it's intended purpose, 'problem hunting'.
As I've been monitoring a problem POP3 mailbox for the last week, due to
intermittent 10060 errors, I wanted to be able to identify the date and time
of the errors so that the hosting company could check their own logs. And as
I've left TB! up and running for this purpose, it would have been good to be
able to differentiate between days.

There is not really any good reason not to add the date as well as the time
to the logging.

-- 
Simon (Privateofcourse)
# 1989. Dew Grew Shoo-In? ¶
 
 
 TB! 4.2.6  WinXP Pro Service Pack 3





Current version is 4.2.6 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: Protocol logging and date

2009-07-05 Thread MFPA
Hi

On Saturday 4 July 2009 at 6:37:03 PM, in
mid:113279542.20090704183...@privateofcourse.co.uk, Privateofcourse
wrote:


 As I've been monitoring a problem POP3 mailbox for the last week,
 due to intermittent 10060 errors, I wanted to be able to identify
 the date and time of the errors so that the hosting company could
 check their own logs.

Presumably you can correlate the info in the protocol log with that in
the account log and work it out from there?

I don't know how frequent you are attempting to collect from this POP
box but if several times a day, it will be evident when the next day
has started.(-;


 And as I've left TB! up and running for this purpose, it would have
 been good to be able to differentiate between days.

Life's not always easy.

 There is not really any good reason not to add the date
 as well as the time to the logging.

You could always request this under The Bat! wishes at
https://www.ritlabs.com/bt and see what happens.



-- 
Best regards,
 
MFPA

ETHERNET(n): device used to catch the Ether bunny

Using The Bat! v4.0.38 on Windows XP 5.1 Build 2600  



Current version is 4.2.6 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: Protocol logging and date

2009-07-05 Thread Privateofcourse
Hello MFPA,

This is what you said on Sun, 5 Jul 2009 15:58:22 +0100 your time:

 Presumably you can correlate the info in the protocol log with that in
 the account log and work it out from there?

Yes, indeed. I could do as you suggest.

 I don't know how frequent you are attempting to collect from this POP box
 but if several times a day, it will be evident when the next day has
 started. (-;

Regularly.

 And as I've left TB! up and running for this purpose, it would have been
 good to be able to differentiate between days.

 Life's not always easy.

Thanks for the aphorism :-D

 You could always request this under The Bat! wishes at
 https://www.ritlabs.com/bt and see what happens.

Yes, I'll do that, thanks. 'No point sitting on my hands' ;-)

-- 
Simon (Privateofcourse)
#33301. Nod O'er Hew Wigs? ¶
 
 
 TB! 4.2.6  WinXP Pro Service Pack 3





Current version is 4.2.6 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Protocol logging and date

2009-07-04 Thread Privateofcourse
Hello TBUDL,

 Is there any way to enable the date in the protocol logging logs? The time
 is displayed but no date.

-- 
Simon (Privateofcourse)
# 2419. Dor Weighs On We? ¶
 
 
 TB! 4.2.6  WinXP Pro Service Pack 3





Current version is 4.2.6 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: Protocol logging and date

2009-07-04 Thread Roelof Otten
Hallo Privateofcourse,

On Sat, 4 Jul 2009 14:38:50 +0100GMT (4-7-2009, 15:38 +0200, where I
live), you wrote:

P  Is there any way to enable the date in the protocol logging logs?

Not that I'm aware of.

P  The time is displayed but no date.

The contents of the sent or received messages might give you some idea
of  the  date  of  the  transaction.  The protocol log is intended for
problem hunting, not for keeping permanent stats.

-- 
Groetjes, Roelof

4 aces beats full house. Smith  Wesson beats 4 aces.
http://www.voormijalleen.nl/
The Bat! 4.2.6
Windows Vista 6.0 Build 6001 Service Pack 1
6 pop3 accounts, 1 imap account
OTFE enabled
Quad Core 2.4GHz
4 GB RAM

pgpAYi7zQFcbD.pgp
Description: PGP signature

Current version is 4.2.6 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html

Re: Protocol logging and date

2009-07-04 Thread Privateofcourse
Hello Roelof,

This is what you said on Sat, 4 Jul 2009 18:09:47 +0200 your time:

 The contents of the sent or received messages might give you some idea
 of  the  date  of  the  transaction.  The protocol log is intended for
 problem hunting, not for keeping permanent stats.

Well, for starters, I'm not using protocol logging for keeping permanent
stats. I'm actually using it for it's intended purpose, 'problem hunting'.
As I've been monitoring a problem POP3 mailbox for the last week, due to
intermittent 10060 errors, I wanted to be able to identify the date and time
of the errors so that the hosting company could check their own logs. And as
I've left TB! up and running for this purpose, it would have been good to be
able to differentiate between days.

There is not really any good reason not to add the date as well as the time
to the logging.

-- 
Simon (Privateofcourse)
# 1989. Dew Grew Shoo-In? ¶
 
 
 TB! 4.2.6  WinXP Pro Service Pack 3





Current version is 4.2.6 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html