Re: [foxboro] Response to Cassandra never make it....

  • From: <duc.do@xxxxxxxxxxxxxx>
  • To: <foxboro@xxxxxxxxxxxxx>
  • Date: Mon, 13 Mar 2006 12:35:36 -0500

Russ,

There seems to be a problem, but I don't know for sure where.

In general, the foxboro@xxxxxxxxxxxxx list is set up so that a "Reply"
would send your reply back to the list address. At worst, a
"Reply-to-All" would accomplish the same thing, albeit with the original
poster (the one you reply to) getting two copies, one directly addressed
to him/her, one delivered via the list.

Now, in your case, I noticed that sometimes (but not always) your e-mail
client sent the reply back to foxboro-bounce@xxxxxxxxxxxxx, instead of
the list address foxboro@xxxxxxxxxxxxxx Those were the ones that didn't
get delivered to the list, of course. I have no idea why this happened,
but I do get a copy when it showed up addressed to
foxboro-bounce@xxxxxxxxxxxxxx

For those of you not interested in the nitty-gritty of e-mail headers
and transport, you can skip this next section.

If you look at the headers of a typical freelists.org e-mail, you can
see that it has, among other things, these headers:

  From: "Boulay, Russ" <russ.boulay@xxxxxxxxxxxxxxxx>
  To: foxboro@xxxxxxxxxxxxx
  Subject: [foxboro] Response to Cassandra never make it....
  Date: Mon, 13 Mar 2006 09:20:46 -0500
  X-Mailer: Internet Mail Service (5.5.2657.72)
  Sender: foxboro-bounce@xxxxxxxxxxxxx
  Errors-To: foxboro-bounce@xxxxxxxxxxxxx
  X-original-sender: russ.boulay@xxxxxxxxxxxxxxxx
  Reply-To: foxboro@xxxxxxxxxxxxx

Note that the foxboro-bounce@xxxxxxxxxxxxx address is used as the
Sender: (used to be called Envelope-from: in some other mailing list
software) and its primary use is to allow other systems to send bounces
to, instead of to the original author (From: header) or the list address
(To: header).

With the included Reply-To: header, the list is explicitly included when
you select "Reply" or "Reply-to-All". The list address should be
included in the addressees list in either case.

After all that, it gets back to I don't know why your mail program
(Outlook of unknown vintage, deciphered from the X-Mailer: header above)
insists on sending the reply back to foxboro-bounce@xxxxxxxxxxxxx
instead of the right address of foxboro@xxxxxxxxxxxxxx I also use
Outlook here at work, and I've never experienced this problem.

You may want to pay attention to what's included in the To: line before
sending mail to the foxboro list. Beyond that, I'm stumped. Sorry that I
can't be of much more help than that.

Duc


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Boulay, Russ
Sent: Monday, March 13, 2006 9:21 AM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: [foxboro] Response to Cassandra never make it....

Does anyone else ever experience their responses not making it to the
list.

About 2 out of 5 of my responses to several key email trails never make
it.
I end up sending directly to requestor.

Last week was very bad on getting responses thru.








=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 

Other related posts: