Sam Varshavchik <[EMAIL PROTECTED]> writes: > That's not quite the point. The original issue is whether you want to > start using time.inode.hostname in this day and age. The original > answer was no, because you will collide with time.pid.hostname. WV > dismisses this, claiming that nobody's using time.pid.hostname. Well, > that's clearly not true. Plenty of stuff uses time.pid.hostname. > > This isn't the first time WV changed Postfix in a way that broke stuff > that worked before.
The patch he issues was clearly and unmistakably marked as "tentative" and inofficial, the final code is not yet released. It's a bit too early to claim "Wietse broke things that used to work." -- the Postfix releases are still at time.pid.hostname, which, as we know now, is lacking. -- Matthias Andree ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
