Loren Wilton a écrit :
Differentiating between personal accounts and company email systems, how
do
you all classify OOO messages?
Personally if they are a reply to a mailing list I consider them spam, but
generally not a spam that should be reported, merely one that should be
quietly dropped. (There are exceptions.)
Why do I consider them not reportable? Because:
a) It is reasonable in some companies to subscribe from mailing lists at
work
b) Some companies REQUIRE that you have an OOO message if you are OOO. Some
companies set them up automatically, or the person's boss does the day after
the user goes on vacation.
that's ok, but that's their own problem. their internal policy can't be
enforced outside.
c) Not all people run Unix mail clients, and thus many either don't know how
to do an OOO that will only respond in-company, or that won't respond to
mailing list messages
I don't care if it's unix or amiga. the vacation program is written in
C, which works on almost all platforms. and one can use perl, python,
javascript, visual basic, .. to implement a vacation program. the issue
isn't the platform. the issue is:
- some developpers reinvent the wheel without taking the time to check
what has been done, what should be done, ...
- some users just "plug and play", and use broken solutions.
I don't think anyone can solve these two problems.
d) Most people (sigh) use MS mail "tools" (as I am) and the ffing MS idiots
have never even considered the *possibility* that someone might want a
different auto-response to a list message than a personal message. Or to a
spam.
The result is OOO messages, even if the person would like that to not
happen.
well, I don't cry/shout if the ooo is sent to the envelope sender (or
return path). after all, I also get "over quota" and "message
quarantined" sometimes...
but if it's sent to the from header, then it's clearly a bug/misfeature.
we then have the right to list the "guilty" companies as having poor
processes/solutions:)
So I have a moderately decent filter rule in OE that catches most of them
and quietly deletes them. Seems a reasonable compromise for things that
most people really can't control.
I didn't try this because I find it risky. what rules do you use for that?
Now, there are eggregious cases that are reportable. Like the idiots in
customer service at some companies that signed the "customer comments"
mailbox up to a bunch of mailing lists, so anytime a message is posted the
company sends out a "thank you for your inquiry about our wonderful
products; someone will get back to you in several days". Or the
autoresponders that autorespond to their own OOO messages with another OOO
message.
not better are the autoresponders that give me phone numbers and email
addresses when I'm just a foreign guy...
