On 2000-11-30, at 22:51 +0100, Phillip Helbig wrote:
> Sometimes the sender might have his OWN Reply-To: address. What happens
> then? The SENSIBLE thing to do would be that the list software inserts
> this into the From: header, and has the original From: address in an
> X-Originally-From: header or something similar.
Yes, you can configure all that in pine. But why would anybody writing to a
mailing list would want to add a "Reply to:" himself. I don't find any rational
reason for doing so, unless the sender is using one email address to post and
wants to receive at the other. In any case, the "Reply to:" header added by the
list will override.
> You DON'T have a space after the "--" above!
This seems to be a problem in this list.
Some more work for you Ian.
> Is this just a Pine thing or is there some official standard, RFC etc
> which says that .sigs should begin with "-- "? (I don't use pine but
> have added a space after my "--".)
As I mentioned above, there seems to be some problem in the list software
regarding this. There's no space visible after the "--". I'll have to reread
RFC822, I'm not sure whether it says so. However, you can make pine to strip
off the mail below the sigdashes while replying. That makes it fairly
convenient in case seombody has a 1.5 kB signature file (I've, indeed, come
across such signature files.) The disclaimers that the mailers in some
companies attach are even longer.
p.s. Some points to check out for Ian:
(1) Why don't I get the mails that I post?
(2) Why do people send autoreplies to mails on a mailing list? I'd personally
urge them not to do so. They can use some mail filter to sort out the mails
from a list and then let the autoresponder do the work for the rest of the
mails.
(3) Why does the trailing space "-- " in my sig disappear when I post on the
list? It never (*never*) disappears otherwise. Thanks to Phillip Helbig for
pointing this out.
--
Mohit Agarwal ([log in to unmask])
--------------------------------------------------------------------------------
|