Hallo Cory, On Mon, 29 Aug 2005 09:37:53 +0200GMT (29-8-2005, 9:37 +0200, where I live), you wrote:
C> Ditto (v2.12 here); this same "behaviour" also alters the addressee C> (To:) when composing a reply. When the original message's Sender: or C> Reply-To: is in the format Lastname, Firstname <[EMAIL PROTECTED]> C> (Lastname, Firstname part *not* enclosed in quotes), the reply will be C> send to [EMAIL PROTECTED], "Lastname" < [EMAIL PROTECTED]>. C> The reply will be delivered correctly ot the intended recipient, but C> it also will either be sent to an undesired local recipient or trigger C> a delivery failure on the local domain. That is as it should. It is possible to set multiple reply-to addresses and to do that you need to use the comma as address separator. So if you want replies to go to both your home and office addresses, you set your headers so: Reply-To: [EMAIL PROTECTED], [EMAIL PROTECTED] Therefore a reply-to with a comma that's not enclosed in quotes should be used as address separator. So when you've got contacts using lastname, firstname <address> without quotes around the name, you should rebuke them for non RFC compliant behaviour, not TB. I don't know about other clients, but TB (at least my version) is properly setting the quotes when a comma is encountered. -- Groetjes, Roelof Apple (c) Copyright 1767, Sir Isaac Newton The Bat! 3.60.05 Forerunner (Beta) Windows XP 5.1 Build 2600 Service Pack 2 1 pop3 account, server on LAN OTFE enabled P4 3GHz 2 GB RAM
pgpFqp0quHaJV.pgp
Description: PGP signature
________________________________________________ Current version is 3.51.10 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
