| SMTP/POP3 Log files not being saved - auto delete |
Posted by
Paul Newey
on Sunday, October 15, 2006 at 3:34:58 AM (EST)
I need to keep the logs from the SMTP / POP3 servers and have configured them to be kept for 31 days - at the end of the month, I then move them to an archive. This procedure has worked really well for the last 2 years Now, as soon as the date changes, the logs are being auto deleted even though I wish to keep them I have configured the logs to be kept for 31 days and have the log file size as 2048kb - I have also tried various settings but this still does not keep the logs. Is this a recent change anyone else has noticed? Has anyone resolved the issue of logs not being saved? Any help would be useful Thanks
|
Posted by
Russell Waddington
on Sunday, October 15, 2006 at 3:58:42 PM (EST)
I am having this same problem too. The logs files are being deleted at the end of each day. I have the a 7 days retenation set. The other thing I have noticed, is if Lansuite has to restart, for instance if rebooting the computer, lansute overwrites the existing daily log. On a Lansuite restart it used to append to the log file on restarts, but now it is overwriting. So you can not see the messages prior to the start up, and check for any problems.
|
Posted by
Testuser Testpass
on Tuesday, October 17, 2006 at 2:01:08 AM (EST)
Same here, I have configured to delete logs after 31 days, but all I have there are some older logs, the newest are ever deleted at the end of each day. Looks like a bug :(
|
Posted by
Robert Smith
on Tuesday, October 17, 2006 at 10:43:06 AM (EST)
I reported it as a bug and got back that this'll be fixed in a new build that should be out this week or next.
|
Posted by
Paul Newey
on Tuesday, October 17, 2006 at 1:45:25 PM (EST)
When I posted this onto the forum, I also posted to the 'bugs' area of tech support - they have investigated it and have found it to be a bug. Jimi from support appended this to the 'bug' ticket:- This appears to be a bug in the software. I have reported this to our developers, and we will hopefully have a new build to fix this issue available very soon.
|
|