[Dovecot] Regarding: **OFF LIST** subject declaration
Seriously, I just have to ask this question. Why mark via the subject line a message as "OFF LIST" and then send it via the normal list framework. Doing so only insures that the message is actually "ON LIST" irregardless of what nomenclature is used in the subject line. If a message is truly supposed to be "OFF LIST", then why not send it directly to its intended recipient(s)? If, on the other hand, it is meant for general review by the groups members, then why mark it "OFF LIST" to begin with?
I am aware of the prefix "OT" used in several forums; however, that is usually only used to thwart the moderator of the forum from banning the message or chastising the OP. Its use is of dubious success.
-- Jerry gesbbb@yahoo.com
|::::======= |::::======= |=========== |=========== |
The course of true anything never does run smooth.
Samuel Butler
On Feb 24, 2010, at 2:06 PM, Jerry wrote:
Seriously, I just have to ask this question. Why mark via the subject line a message as "OFF LIST" and then send it via the normal list framework. Doing so only insures that the message is actually "ON LIST" irregardless of what nomenclature is used in the subject
line. If a message is truly supposed to be "OFF LIST", then why not send it directly to its intended recipient(s)? If, on the other hand, it is meant for general review by the groups members, then why mark it "OFF LIST" to begin with?
Um, wow. Like you've never intended to send someone an off-list
message, got finished typing it, then forgot to change the To: line?
-Dave
-- Dave McGuire Port Charlotte, FL
On Wed, 24 Feb 2010 14:10:40 -0500 Dave McGuire mcguire@neurotica.com articulated:
On Feb 24, 2010, at 2:06 PM, Jerry wrote:
Seriously, I just have to ask this question. Why mark via the subject line a message as "OFF LIST" and then send it via the normal list framework. Doing so only insures that the message is actually "ON LIST" irregardless of what nomenclature is used in the subject line. If a message is truly supposed to be "OFF LIST", then why not send it directly to its intended recipient(s)? If, on the other hand, it is meant for general review by the groups members, then why mark it "OFF LIST" to begin with?
Um, wow. Like you've never intended to send someone an off-list
message, got finished typing it, then forgot to change the To: line?
Not that I am aware of and why would I put a declaration like that in the subject line if I was sending it directly to its intended recipient? In any case, I certainly would not follow it up with an "ON LIST" declaration. Admit it, it does seem rather absurd.
In any case, it makes no difference to me. I was just curious.
-- Jerry gesbbb@yahoo.com
|::::======= |::::======= |=========== |=========== |
Standing on head makes smile of frown, but rest of face also upside down.
On Feb 24, 2010, at 2:39 PM, Jerry wrote:
Seriously, I just have to ask this question. Why mark via the subject line a message as "OFF LIST" and then send it via the normal list framework. Doing so only insures that the message is actually "ON LIST" irregardless of what nomenclature is used in the subject line. If a message is truly supposed to be "OFF LIST", then why not send it directly to its intended recipient(s)? If, on the other hand, it is meant for general review by the groups members, then why mark it "OFF LIST" to begin with?
Um, wow. Like you've never intended to send someone an off-list message, got finished typing it, then forgot to change the To: line?
Not that I am aware of
Well, you're less error-prone than I, then. I've been "doing
email" for upwards of thirty years and still make that mistake from
time to time.
and why would I put a declaration like that in the subject line if I was sending it directly to its intended recipient?
That's simple list(member) etiquette. When you see a message pop
into your inbox with the same (or similar) subject as a list thread,
it's natural to assume that it's a list message. When replying, one
might be tempted to set the reply to the list. If the person sending
the "off list" message doesn't want that information to accidentally
become public, that person should say so.
In any case, I certainly would not follow it up with an "ON LIST" declaration. Admit it, it does seem rather absurd.
Well, the "on list" part is kinda obvious. ;)
-Dave
-- Dave McGuire Port Charlotte, FL
Jerry put forth on 2/24/2010 1:39 PM:
Not that I am aware of and why would I put a declaration like that in the subject line if I was sending it directly to its intended recipient? In any case, I certainly would not follow it up with an "ON LIST" declaration. Admit it, it does seem rather absurd.
In any case, it makes no difference to me. I was just curious.
Jerry, this is pretty simple. If you'd been paying attention to the thread in question you'd already have figured out what happened. Apparently you only read subject lines, not the actual content of list messages.
If you go back and read the thread, you'll see that at one point Timo asked me to send him a copy of an mbox file from my production dovecot server. This request was the very last line of his email. This is private data, obviously. I replied off list with the URL. Later, I replied back to the list omitting the private URL, which was the only reason to go off list in the first place. When I replied back to the list, I forgot to change the subject line. When I realized the mistake, I corrected it. Simple, logical.
To answer the "yeah but" question on the tip of your tongue, yes, I could have sent Timo a separate email with the URL. However, I'm no list nub, and experience tells me that Timo would have continued replying through the off list channel, and thus no one on the list, or those later searching the archives, would benefit from the exchange.
Is this all clear for you now? That **OFF LIST** was a simple mistake of forgetting to edit the subject line before getting the discussion back on the list?
-- Stan
On Wed, 24 Feb 2010 21:28:29 -0600 Stan Hoeppner stan@hardwarefreak.com articulated:
Is this all clear for you now? That **OFF LIST** was a simple mistake of forgetting to edit the subject line before getting the discussion back on the list?
Interestingly enough, the 'OFF LIST" declaration has now populated itself, which was what I meant in my original post. Personally, I feel that subject line declarations like "OT", etc are just a wasted finger exercise. It ranks up there with those totally useless and legally unenforceable 'disclaimer' declarations. (see example below)
By the way, this was in no way directed at you, or anyone else in particular. I was just curious as to why someone (anyone) would employ this tactic.
In any case, it is time to retire this post.
-- Jerry gesbbb@yahoo.com
|::::======= |::::======= |=========== |=========== |
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient of this transmission, please delete it immediately.
Obviously, I am the idiot who sent it to you by mistake. Furthermore, there is no way I can force you to delete it. Worse, by the time you have reached this disclaimer you have all ready read the document. Telling you to forget it would seem absurd. In any event, I have no legal right to force you to take any action upon this email anyway.
This entire disclaimer is just a waste of everyone's time and bandwidth. Therefore, let us just forget the whole thing and enjoy a cold beer instead.
participants (4)
-
Dan Swartzendruber
-
Dave McGuire
-
Jerry
-
Stan Hoeppner