-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Harm van Tilborg wrote: > During the migration I've changed the hostname of the server, from > mail.example.com to pop1.mail.example.com and pop2.mail.example.com. I > can remember there were some problems from users by getting their mail > (through qmail-pop3d). At that time, I've changed the server's hostname > back to mail.example.com (at both servers), and every mail could be > reached smoothly again by our customers.
The hostname of a system is not important, especially when dealing with protocols for retrieving mail. > Nowadays both servers are still called mail.example.com. However, I > finally want to get rid of those names. So I was wondering what could > have caused these problems? Unfortunately, you haven't provided enough detail to even know what the problems were, let alone enough to provide a possible solution. > vdelivermail generates the mail's new filename, based on the hostname, > process id, timestamp and perhaps the Maildir++'s 'S=yyyy'. I was > wondering whether any of the delivery agents (such qmail-pop3d or > bincimap) makes use of the hostname to give out such mails. qmail-pop3d is not a delivery agent, nor is bincimap. > Or was this maybe a misbehavior of vpopmail around those version numbers. The Maildir specification does not specify the format for message filenames, it simply states they are unique. How you arrive at a unique filename is entirely up to the delivery process. Processes reading these files, like a POP3 or IMAP server, do not care what the filename is. Therefore, unless vpopmail was trying to re-create the same filenames over and over, there was no misbehavior in previous versions. - -- /* Matt Brookings <m...@inter7.com> GnuPG Key D9414F70 Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknvG6YACgkQ6QgvSNlBT3DkRwCfTGbuFypRhfpMNlbA/X9EhLpI S1cAoJASBFiuL1wvrjFzfjMBUUqhdcej =b8wW -----END PGP SIGNATURE-----