Hello Martin,
Thank you for providing the requested RPOP logs.
Let’s try to understand what is happening after succesfully login to the remote server:
… so there are 6812 messages, using ~875 MB
2020-01-20 17:46:08 +0100 16 mx RPOP:00000001: >> STAT
2020-01-20 17:46:08 +0100 16 mx RPOP:00000001: << +OK 6812 875332586
… and Axigen will ask to receive the unique ID for all messages
2020-01-20 17:46:08 +0100 16 mx RPOP:00000001: >> UIDL
2020-01-20 17:46:08 +0100 16 mx RPOP:00000001: << +OK 6812 messages, listing follows:
2020-01-20 17:46:08 +0100 16 mx RPOP:00000001: << 1 668660e2e0a010faacf049fa830f537c
...
2020-01-20 17:46:08 +0100 16 mx RPOP:00000001: << 6812 89f5ade97dbb2ba152d5690df48acc77
2020-01-20 17:46:08 +0100 16 mx RPOP:00000001: << .
… now starts the interesting part - Axigen is rechecking, for all messages, the received IDs
… but the remote server starts to answer with 5 sec delay
… examples for ~3 sec delay
2020-01-20 17:46:31 +0100 16 mx RPOP:00000001: >> UIDL 28
2020-01-20 17:46:34 +0100 16 mx RPOP:00000001: << +OK 28 3685b5c55de078fc72c27eafbd73abf5
2020-01-20 17:46:44 +0100 16 mx RPOP:00000001: >> UIDL 33
2020-01-20 17:46:47 +0100 16 mx RPOP:00000001: << +OK 33 c299b04a33d9a8b015f91d9a07a9b555
… examples of ~5 sec delay
2020-01-20 17:47:27 +0100 16 mx RPOP:00000001: >> UIDL 50
2020-01-20 17:47:32 +0100 16 mx RPOP:00000001: << +OK 50 429f68a0101f801924f047632724dac2
2020-01-20 17:47:32 +0100 16 mx RPOP:00000001: >> UIDL 51
2020-01-20 17:47:37 +0100 16 mx RPOP:00000001: << +OK 51 0804c24da239654b4f1a2be5f9f8d647
2020-01-20 17:47:37 +0100 16 mx RPOP:00000001: >> UIDL 52
2020-01-20 17:47:42 +0100 16 mx RPOP:00000001: << +OK 52 16bb60ed6c50d8a61cee4fc5182678fd
2020-01-20 17:47:42 +0100 16 mx RPOP:00000001: >> UIDL 53
2020-01-20 17:47:47 +0100 16 mx RPOP:00000001: << +OK 53 f56fac9fcb0dfc99c89f0a7a390205d9
2020-01-20 17:47:47 +0100 16 mx RPOP:00000001: >> UIDL 54
...
2020-01-21 03:14:04 +0100 16 mx RPOP:00000001: >> UIDL 6807
2020-01-21 03:14:09 +0100 16 mx RPOP:00000001: << +OK 6807 1a01a7c8df53c8fb00db237bf5ac12a6
…so here you have:
6087 POP3 UIDL commands requested by Axigen and answered by remote sever in ~9.5 hours
…and finally is retrieving 4 messages that were not already downloaded
2020-01-21 03:14:09 +0100 16 mx RPOP:00000001: >> UIDL 6808
2020-01-21 03:14:14 +0100 16 mx RPOP:00000001: << +OK 6808 959d1e1c5104d49c8b448058a38b0a0d
2020-01-21 03:14:14 +0100 16 mx RPOP:00000001: >> RETR 6808
2020-01-21 03:14:14 +0100 16 mx RPOP:00000001: << +OK Message follows:
...
2020-01-21 03:14:15 +0100 16 mx RPOP:00000001: >> UIDL 6812
2020-01-21 03:14:15 +0100 16 mx RPOP:00000001: << +OK 6812 89f5ade97dbb2ba152d5690df48acc77
2020-01-21 03:14:15 +0100 16 mx RPOP:00000001: >> RETR 6812
2020-01-21 03:14:15 +0100 16 mx RPOP:00000001: << +OK Message follows:
2020-01-21 03:14:15 +0100 16 mx RPOP:00000001: >> QUIT
Now I let you conclude - is Axigen to blame, the remote server or the owner of the mailbox?
- maybe in Axigen we could make some improvements (to be checked internally)
- but why the remote is delaying the answer to POP3 UIDL messages is something that you will have to check
My suggestions are:
1/ ask the owner of the remote mailbox to archive old messages in a subfolder so there will not be so many messages to be checked
2/ test RemotePOP with 6800 messages when the remote server is Axigen (very easy to configure, just use another mailbox on the same Axigen server) - is the same delay observed?
3/ bring this topic in attention of the remote server support team so they could provide an explanation for POP3 UIDL responses delayed by 5 sec
HTH,
Ioan
PS: please remember that here you are receiving answers from a public community, depending on the availability of each one. I’m strongly advise you to use the dedicated support channel in case you are interested in a better response time.