[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [New Search]
> I didn't understand this comment from Toby earlier because I thought Greg > had already set this up. Don't they all get [T3] added unless it's already > there? It adds [T3] to the beginning of the subject -- but does not do so if there is a 'Re:' at the beginning. This is a simple way to avoid a build-up of [T3]s in a series of replies -- that is, to avoid: Subject: [T3] RE: [T3] Re: [T3] Re: [T3] fuel inectors You know, I think I can squeak by in my limited procmail to try to make this a wee bit more clever, so that some of the "Re: blah" messages become "[T3] Re: blah" or "Re: [T3] blah". (If I don't get it quite right, we may get a few "[T3] Re: [T3] blah" messages, but it's worth a shot.) It's probably a bit more certain if folks filter for [T3] *and* for other headers that have 'type3@vwtype3.org' in them in the meantime. > While we're making suggestions, it would be great if the reply-to address > was set to the list, so we don't mistakenly reply to the sender rather than This issue is not quite so simple as it appears at first glance. There are two reasons for this. First, a poorly-configured mail server can hook into the Reply-to: field improperly and create a mail loop. Second, the precise combination of which header addresses (From:, To:, Cc:, and REply-to:) that are used when a user hits "reply" varies tremendously from client to client; some even let you set the reply behavior in the preferences. It is impossible to configure the list in a way that will have predictable consequences in every mail client. Cheers, -Greg Merritt ------------------------------------------------------------------- Search old messages on the Web! Visit http://www.vwtype3.org/list/