You could setup the user level logging for the problem user to
catch the imap events..
g_log_user "fred@xyz.com"
then send me user_fred@xyz.com.log
ChrisP.
On 20/09/2016 11:10 a.m., Eric Vey
wrote:
Where would I look
for messages
that have gotten stuck and won't download on imap account?
It's hard for me
to believe the
same number of log entries would occur over and over without
there being a
pattern.
Maybe I should
give you more of
my log?
Eric Vey
On
September 19, 2016 6:59:16 PM surgemail-support
<surgemail-support@netwinsite.com> wrote:
There are probably more factors to it yes, but I
don't think it has any significance.
ChrisP.
On 20/09/2016 1:14 a.m., Eric
Vey wrote:
Chris,
Hmmm. I'm only getting these on one account. I'm
thinking it is a phone doing this since the IPs belong
to a cellular phone company.
If it was what you say, wouldn't that affect more
than one account?
Eric Vey
------ Original Message ------
Sent: 9/18/2016 10:36:20 PM
Subject: Re: [SurgeMail List] log filling up with
these entries
I will reduce that logging in future builds. It's
a flag change causing the log entry when the user
reads the message and it should only log the main
burst operation when the uid is assigned not the
read event.
ChrisP.
On 19/09/2016 12:19 p.m.,
Eric Vey wrote:
I'm getting this block of log entries in my
msg.log four or five times an hour. Always the
same account. Different URLs, though.
18 19:19:37[0] burst 66.87.97.178 . < >
0 . "burst u53137~2,SR(0,38341)[1473367077] -->
u53137~2,S(0,38341)[1473367077]"
18 19:19:37[0] burst 66.87.97.178 . <>
0 . "burst u53133~2,SR(0,86403)[1473777498] -->
u53133~2,S(0,86403)[1473777498]"
18 19:19:37[0] burst 66.87.97.178 . <>
0 . "burst u53134~2,SR(0,86395)[1473615534] -->
u53134~2,S(0,86395)[1473615534]"
18 19:19:37[0] burst 66.87.97.178 . <>
0 . "burst u53135~2,SR(0,13354)[1473508946] -->
u53135~2,S(0,13354)[1473508946]"
18 19:19:37[0] burst 66.87.97.178 . <>
0 . "burst u53141~2,SR(0,33173)[1473745931] -->
u53141~2,S(0,33173)[1473745931]"
18 19:19:37[0] burst 66.87.97.178 . <>
0 . "burst u53132~2,SR(0,19164)[1473459539] -->
u53132~2,S(0,19164)[1473459539]"
18 19:19:37[0] burst 66.87.97.178 . <>
0 . "burst u53140~2,SR(0,11958)[1473689936] -->
u53140~2,S(0,11958)[1473689936]"
18 19:19:37[0] burst 66.87.97.178 . <>
0 . "burst u53139~2,SR(0,49964)[1473424697] -->
u53139~2,S(0,49964)[1473424697]"
18 19:19:37[0] burst 66.87.97.178 . <>
0 . "burst u53138~2,SR(0,31320)[1474004332] -->
u53138~2,S(0,31320)[1474004332]"
18 19:19:37[0] burst 66.87.97.178 . <>
0 . "burst u53131~2,SR(0,86555)[1473706860] -->
u53131~2,S(0,86555)[1473706860]"
Anybody have any ideas?
Eric Vey
|
This email has been
checked for viruses by Avast antivirus
software.
www.avast.com
|
|
This email has been checked
for viruses by Avast antivirus software.
www.avast.com
|
|