[Citadel Support] Re:Remote POP3 retrieval only works on Citadel startup

[mgwigglesworth]

>I am still having the same issues that I did before, however, I am going to
>reinstall, using the new version of citadel.


>As this individual is able to see the password, etc, for all the right mail
>retrieval, I never saw any of this.  Does citadel supposed to indicated
>similar output as seen in this individual's log files when checking external
>pop3 mail?  Did I just have a faulty install in the first place? 


> I never saw "Connected" or anything like that, however, noone ever
>mentioned this, so I am wondering if I just had a bad install. 


>Sun Jun 08 2008 06:58:33 PM EDT from [EMAIL PROTECTED] 
>Subject: Re:Remote POP3 retrieval only works on Citadel startup
>
>  


>
>
>I set the log level to "-x7" and took a look at the log file. Upon startup,
>Citadel dutifully collects POP3 mail, generating entries such as:
>
>  Jun  8 12:23:06 server1 citadel: Connecting to 
>  Jun  8 12:23:06 server1 citadel: Connected!
>  Jun  8 12:23:06 server1 citadel: >+OK POP3 localhost v2000.69hw server
>ready
>  Jun  8 12:23:06 server1 citadel: 
>  Jun  8 12:23:06 server1 citadel: >+OK User name accepted, password please
>  Jun  8 12:23:06 server1 citadel: 
>  Jun  8 12:23:06 server1 citadel: >+OK Mailbox open, 0 messages
>  Jun  8 12:23:06 server1 citadel: 
>  Jun  8 12:23:06 server1 citadel: >+OK Mailbox scan listing follows
>  Jun  8 12:23:06 server1 citadel: >.
>  Jun  8 12:23:06 server1 citadel: 
>  Jun  8 12:23:06 server1 citadel: >+OK Sayonara 
>
>(In this case there were no waiting messages.)
>
> Then we get a countdown to the next network processing event:  Jun  8
>12:24:04 server1 citadel: Network full processing in 539 seconds.
>  Jun  8 12:24:04 server1 citadel: network: nothing in inbound queue
>  Jun  8 12:24:04 server1 citadel: network: queue run completed
>  Jun  8 12:24:04 server1 citadel: Thread "IGnet Network" (0xb76d1ba0)
>exited.
>
> Then when the clock ticks all the way down, we get:
>
>  Jun  8 12:33:13 server1 citadel: Created a new thread "IGnet Network"
>(0xb76d1ba0).
>  Jun  8 12:33:13 server1 citadel: network: loading outbound queue
>  Jun  8 12:33:13 server1 citadel: network: running outbound queue
>  ...
>
>  Jun  8 12:33:13 server1 citadel: Networking started for <0000000001.Mail>
>  Jun  8 12:33:13 server1 citadel: Networking started for
><0000000001.Contacts>
>  Jun  8 12:33:13 server1 citadel: Networking started for
><0000000001.Calendar>
>  Jun  8 12:33:13 server1 citadel: network: nothing in inbound queue
>  Jun  8 12:33:13 server1 citadel: network: queue run completed
>  Jun  8 12:33:13 server1 citadel: Thread "IGnet Network" (0xb76d1ba0)
>exited.
>  Jun  8 12:33:14 server1 citadel: Garbage Collection for thread "IGnet
>Network" (0xb76d1ba0).
>  Jun  8 12:33:14 server1 citadel: SMTP client: processing outbound queue
>  Jun  8 12:33:14 server1 citadel: SMTP client: queue run completed
>  Jun  8 12:33:14 server1 citadel: pop3client started
>  Jun  8 12:33:14 server1 citadel: pop3client ended
>  Jun  8 12:33:14 server1 citadel: serv_extnotify: processing notify queue
>  Jun  8 12:33:14 server1 citadel: serv_extnotify: queue run completed
>
>Then we get the countdown started again:
>
>  Jun  8 12:34:14 server1 citadel: Network full processing in 539 seconds.
>
>During several cycles of this in the log file throughout the day, there are
>no POP3 remote retrieval sessions reported, the only ones are those that took
>place when Citadel was started up.
>
>Any ideas of how to fix this? I'm going to have to delay centralizing email
>delivery through Citadel until this is working, have to go back to each
>individual user doing POP3 directly into Thunderbird...