Evan Platt wrote:
> Agreeed. OoO is pointless. No point in it. I can't count how
> many times I
> post to a list, and get an e-mail back that "I am out of the office.
> Contact Joe @ XXX-XXX-XXXX in my absence. Until the OoO reply can be
> configured to not reply to spam, not reply to group mails,
> not reply to ...
> heck until it can be configured to only reply to a message
> that requires an
> immediate reply, it's useless. i.e. "Hey, hope all is well,
> let's do lunch
> when you're free" does not need a OoO reply, however "I need
> to know your
> decision on the Thompson blueprints ASAP!" does. Until OoO
> can make that
> determination, turn it off.
>
> Evan
I'd like to see OoO as an extension to SMTP, so it can all be handled in the
SMTP conversation. Something like:
--> MAIL FROM: [EMAIL PROTECTED]
<-- OK, go ahead
--> RCPT TO: [EMAIL PROTECTED]
<-- OOO, Joe's out of the office.
--> OOO-NODELIVER: Never mind, this email is moot then.
or
--> OOO-DELIVER-NOAUTOREPLY: Deliver anyway. I'll tell Frieda that Joe is OoO.
or
--> OOO-DELIVER-AUTOREPLY: Oh dear! Please email Frieda alternate contact info.
or
--> OOO-REQUEST-ALTERNATE: Hmmm... is there someone else I can talk to?
<-- OOO-ALTERNATE: Yes, [EMAIL PROTECTED]
[EMAIL PROTECTED] 805.964.4554 x902
Hispanic Business Inc./HireDiversity.com Software Engineer
perl -e"map{y/a-z/l-za-k/;print}shift" "Jjhi pcdiwtg Ptga wprztg,"
