Manao ahoana, Hello, Bonjour,
This is my system:
r...@second-camel:~# dpkg -l | awk '/^ii .+courier/{print $2,$3}'
courier-authdaemon 0.61.0-1+lenny1
courier-authlib 0.61.0-1+lenny1
courier-authlib-mysql 0.61.0-1+lenny1
courier-authlib-userdb 0.61.0-1+lenny1
courier-base 0.60.0-2
courier-imap 4.4.0-2
courier-pop 0.60.0-2
When POP'ing an account, I get this:
telnet second-camel 110
Trying 43.24.13.68...
Connected to second-camel.
Escape character is '^]'.
+OK Hello there.
USER [email protected]
+OK Password required.
PASS azerty
+OK logged in.
UIDL
+OK
1 UID430555-1244045323
2 UID430556-1244045323
3 UID430557-1244045323
4 UID430558-1244045323
5 UID430559-1244045323
6 UID431130-1244045323
[...]
286 UID437024-1244045323
287 UID437025-1244045323
288 UID437026-1244045323
289 UID437027-1244045323
290 UID437028-1244045323
291 UID437029-1244045323
In my version of courier, how are UIDLs built?
I noticed that after my accidental remove of courier* files (cf. the
thread "accidentally removed ~/Maildir/courier*") the UIDL listing
changed to start with UID1-NNNNNNN.
So, saying the UIDs are in he form UID{P}-{N} would you know how is the
P and the N choosen?
I ask, because I must have the same listing with another fallback POP
server (not running courier, sharing the same Maildir filesystem over
NFS) to avoid clients to re-downloads messages.
I have then to know how each POP server build the UIDL.
Misaotra, Thanks, Merci.
--
Architecte Informatique chez Blueline/Gulfsat:
Administration Systeme, Recherche & Developpement
+261 34 29 155 34 / +261 33 11 207 36
------------------------------------------------------------------------------
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
