Hi all,
I'm at a complete loss for why my posts are double posting.
Does anyone have any idea why? The email address I'm using appears to be
the same as everyone elses.
**Confused**
They don't seem to be appearing twice for me, are you BCCing yourself? Mail filters grabbing things out of your 'sent' directory, or some other sort of unexpected behaviour?
One way to check if things really are appearing twice is to check the headers: messages that actually go out to the list have 'X-Mail-Count' set (ferinstance, your message was 'X-Mail-Count: 197438'
matthew smillie.
···
On Jun 15, 2006, at 13:09, Daniel N wrote:
Hi all,
I'm at a complete loss for why my posts are double posting.
Does anyone have any idea why? The email address I'm using appears to be
the same as everyone elses.**Confused**
Does anyone have any idea why? The email address I'm using appears to be
the same as everyone elses.
It's a Gmail thing. It appears once when you respond and then appears
again when your message is received from the mailing list. Only one
message is actually sent to the list.
Farrel
it's a GMail glitch,
your response is added to the conversation, then it's sent back to you,
because you are part of the list, so it's added to the conversation again.
···
2006/6/15, Daniel N <has.sox@gmail.com>:
Hi all,
I'm at a complete loss for why my posts are double posting.
Does anyone have any idea why? The email address I'm using appears to be
the same as everyone elses.**Confused**
--
Swallow this, it will make you feel better.
"You've got a disease that there is no known cure for. We have run the
appropriate tests and found alarming conclusions. This is a very troubling
circumstance. But what is more troubling is how you developed this
condition. It seems that due to constant exposure to the dangerous realities
around you, this extremely rare virus has infected you. I am afraid there is
no known cure. On top of this, the disease is extremely contagious as well."
Perplexed as usual, I had to ask, "What is the disease?" The answer: "An
unyeilding hunger for the truth, a passion for the people around you, and
sorrow for those who still lie in darkness. To put it plainly, you have a
heart. We must amputate immediately."
--Andrew Schwab (Taken from the book "We Caught You Plotting Murder")
It appears twice in my inbox. Must be something to do with gmail.
Thanx
···
On 6/15/06, Matthew Smillie <M.B.Smillie@sms.ed.ac.uk> wrote:
On Jun 15, 2006, at 13:09, Daniel N wrote:
> Hi all,
>
> I'm at a complete loss for why my posts are double posting.
>
> Does anyone have any idea why? The email address I'm using appears
> to be
> the same as everyone elses.
>
> **Confused**They don't seem to be appearing twice for me, are you BCCing
yourself? Mail filters grabbing things out of your 'sent' directory,
or some other sort of unexpected behaviour?One way to check if things really are appearing twice is to check the
headers: messages that actually go out to the list have 'X-Mail-
Count' set (ferinstance, your message was 'X-Mail-Count: 197438'matthew smillie.
No offense intended here, but your signature, while clever, is a bit long. You posted three lines of content followed by eleven lines extra fluff. Most people try to keep their signatures at four lines or less.
James Edward Gray II
···
On Jun 15, 2006, at 7:27 AM, Dirk Meijer wrote:
it's a GMail glitch,
your response is added to the conversation, then it's sent back to you,
because you are part of the list, so it's added to the conversation again.--
Swallow this, it will make you feel better.
"You've got a disease that there is no known cure for. We have run the
appropriate tests and found alarming conclusions. This is a very troubling
circumstance. But what is more troubling is how you developed this
condition. It seems that due to constant exposure to the dangerous realities
around you, this extremely rare virus has infected you. I am afraid there is
no known cure. On top of this, the disease is extremely contagious as well."
Perplexed as usual, I had to ask, "What is the disease?" The answer: "An
unyeilding hunger for the truth, a passion for the people around you, and
sorrow for those who still lie in darkness. To put it plainly, you have a
heart. We must amputate immediately."--Andrew Schwab (Taken from the book "We Caught You Plotting Murder")
I would consider it more of a ruby-talk glitch since it doesn't happen
with any other list serves to which I am currently subscribed (MySQL,
PostgreSQL, PHP, and two LUGs).
···
On 6/15/06, Dirk Meijer <hawkman.gelooft@gmail.com> wrote:
it's a GMail glitch,
--
Greg Donald
http://destiney.com/
While Etiquette is on the table, can someone please tell me why replying at
the top of a post is considered bad form?
Cheers
···
On 6/15/06, James Edward Gray II <james@grayproductions.net> wrote:
On Jun 15, 2006, at 7:27 AM, Dirk Meijer wrote:
> it's a GMail glitch,
> your response is added to the conversation, then it's sent back to
> you,
> because you are part of the list, so it's added to the conversation
> again.
>
> --
> Swallow this, it will make you feel better.
> "You've got a disease that there is no known cure for. We have run the
> appropriate tests and found alarming conclusions. This is a very
> troubling
> circumstance. But what is more troubling is how you developed this
> condition. It seems that due to constant exposure to the dangerous
> realities
> around you, this extremely rare virus has infected you. I am afraid
> there is
> no known cure. On top of this, the disease is extremely contagious
> as well."
> Perplexed as usual, I had to ask, "What is the disease?" The
> answer: "An
> unyeilding hunger for the truth, a passion for the people around
> you, and
> sorrow for those who still lie in darkness. To put it plainly, you
> have a
> heart. We must amputate immediately."
>
> --Andrew Schwab (Taken from the book "We Caught You Plotting Murder")No offense intended here, but your signature, while clever, is a bit
long. You posted three lines of content followed by eleven lines
extra fluff. Most people try to keep their signatures at four lines
or less.James Edward Gray II
hmm, i understand people won't be too happy about the length..
sorry about that, i'll make sure it won't happen again 
i think there should be written rules about stuff like this, which people
should agree to before they are a part of this list, and before they enter
ruby-forum.com (though i doubt how much that will help..)
greetings, Dirk.
···
2006/6/15, James Edward Gray II <james@grayproductions.net>:
<snip>
No offense intended here, but your signature, while clever, is a bit
long. You posted three lines of content followed by eleven lines
extra fluff. Most people try to keep their signatures at four lines
or less.
<snip>
It's a Gmail glitch.
You *can*, however, control the glitch to a degree at the loss of some
information. At one point, Gmail used to keep sent messages of a
conversation in the Sent Mail folder. Ruby-talk is initially
configured to send you your own messages. Therefore, you see your sent
message and then you receive your own message from ruby-talk with
additional headers marked up that provide you the message number so
you can specifically say which message yours was.
If you *really* don't like the behaviour and want to lose that
information, change your configuration on the ruby-talk mailing list
(use ruby-talk-ctl at ruby-lang.org to do this) so that you aren't
sent copies of your own messages.
It's proper list behaviour; Gmail should probably be a little more
intelligent about what it sees and deal with it cleanly. The
behaviour, though, is no different than if you were using Thunderbird
or Outlook with an option that saves your sent messages in the folders
you were using or with their reply-antecedents.
-austin
···
On 6/15/06, Greg Donald <gdonald@gmail.com> wrote:
On 6/15/06, Dirk Meijer <hawkman.gelooft@gmail.com> wrote:
> it's a GMail glitch,
I would consider it more of a ruby-talk glitch since it doesn't happen
with any other list serves to which I am currently subscribed (MySQL,
PostgreSQL, PHP, and two LUGs).
--
Austin Ziegler * halostatue@gmail.com * http://www.halostatue.ca/
* austin@halostatue.ca * You are in a maze of twisty little passages, all alike. // halo • statue
* austin@zieglers.ca
Someone on this list (sorry, I forget who) has a signature that sums it up beautifully. It goes like this:
"Yes."
Is top posting bad?
In other words, the answer doesn't make sense before the question is asked.
James Edward Gray II
···
On Jun 15, 2006, at 8:21 AM, Daniel N wrote:
While Etiquette is on the table, can someone please tell me why replying at
the top of a post is considered bad form?
No, it's a ruby-talk glitch. Otherwise I would see the same issue
with other lists.
···
On 6/15/06, Austin Ziegler <halostatue@gmail.com> wrote:
It's a Gmail glitch.
--
Greg Donald
http://destiney.com/
> it's a GMail glitch,
I would consider it more of a ruby-talk glitch since it doesn't happen
with any other list serves to which I am currently subscribed (MySQL,
PostgreSQL, PHP, and two LUGs).It's a Gmail glitch.
I'd have to be a little weary about that statement. I see this exact same behaviour using Mail on OSX 10.4 from my own mail server -- none of my other lists or whatnot experience this same problem, only ruby-talk. However, in my case, it's *all* messages to ruby-talk get sent twice, not just my own.
···
On 15-Jun-06, at 2:32 PM, Austin Ziegler wrote:
On 6/15/06, Greg Donald <gdonald@gmail.com> wrote:
On 6/15/06, Dirk Meijer <hawkman.gelooft@gmail.com> wrote:
Austin Ziegler
--
Jeremy Tregunna
jtregunna@blurgle.ca
"One serious obstacle to the adoption of good programming languages is the notion that everything has to be sacrificed for speed. In computer languages as in life, speed kills." -- Mike Vanier
True.. Thanx for pointing that out.
···
On 6/15/06, James Edward Gray II <james@grayproductions.net> wrote:
On Jun 15, 2006, at 8:21 AM, Daniel N wrote:
> While Etiquette is on the table, can someone please tell me why
> replying at
> the top of a post is considered bad form?Someone on this list (sorry, I forget who) has a signature that sums
it up beautifully. It goes like this:"Yes."
Is top posting bad?In other words, the answer doesn't make sense before the question is
asked.James Edward Gray II
> While Etiquette is on the table, can someone please tell me why
> replying at
> the top of a post is considered bad form?
It's all about context. If you reply inline, you have it. If you reply
at the top of a post, you don't.
Someone on this list (sorry, I forget who)
Eric Hodel
has a signature that sums
it up beautifully. It goes like this:"Yes."
Is top posting bad?In other words, the answer doesn't make sense before the question is
asked.
Top posting also encourages (or maybe it doesn't discourage) huge
emails with none of the extraneous quoted material trimmed. Be a
good netizen, trim your quotes and reply inline -- everyone will
benefit.
···
On 6/15/06, James Edward Gray II <james@grayproductions.net> wrote:
On Jun 15, 2006, at 8:21 AM, Daniel N wrote:
James Edward Gray II
--
thanks,
-pate
-------------------------
Go check your configuration on those other lists, before you make a
fool of yourself.
If those other lists are not set up for "send me my own message" --
which ruby-talk *is* set up for by default -- you won't get duplicate
messages.
And ruby-talk's default setting is the right one. Gmail's setting
(which is not changeable) is the wrong one.
-austin
···
On 6/15/06, Greg Donald <gdonald@gmail.com> wrote:
On 6/15/06, Austin Ziegler <halostatue@gmail.com> wrote:
> It's a Gmail glitch.
No, it's a ruby-talk glitch. Otherwise I would see the same issue
with other lists.
--
Austin Ziegler * halostatue@gmail.com * http://www.halostatue.ca/
* austin@halostatue.ca * You are in a maze of twisty little passages, all alike. // halo • statue
* austin@zieglers.ca
No, it's a gmail glitch, otherwise you'd see the same issue in other mail clients.
Gmail doesn't deal all that gracefully with messages from yourself that you also receive. For example, it seems to silently ignore BCCs to your own address. Presumably, this is because on the web interface you don't need that BCC, but it fails to impress when you're using it over POP3.
matthew smillie.
···
On Jun 15, 2006, at 19:40, Greg Donald wrote:
On 6/15/06, Austin Ziegler <halostatue@gmail.com> wrote:
It's a Gmail glitch.
No, it's a ruby-talk glitch. Otherwise I would see the same issue
with other lists.
In your case, it's probably because you're double subscribed or
something. Not at all the same problem. Regarding the OP's problem, I
can indeed verify that it is a gmail "feature". When I post to
ruby-talk using my gmail account, I also see the post duplicated. From
the beginning I suspected this was a gmail thing, and believed it when
others suggested that too. But for the sake of completeness, I
investigated.
For every email in a thread in gmail, you can click the "More options"
link to see a little more detail about the headers for that email. If
that's not enough, from within the "More options" block, you can click
"Show original" to see the email in all its plain text glory, headers
intact.
Going to a thread to which I've posted, I see the two "duplicate"
emails one right after the other. Clicking "More options" for both, I
can see that the first email I see has a "To:" and a "From:", while
the second has a "To:", "Reply-To:" and "From:". The "Reply-To:" for
the second is set to "ruby-talk@ruby-lang.org", just as it is for all
other emails from the list. This is because the ruby-talk list
software does what is commonly known as Reply-To munging. *Every*
email that comes from the list has this Reply-to header. But the first
copy of my email does not -- it *can't* have come from the list. So
where did it come from?
Look over to the right hand side in that "More options" box, there's
the value of the Mailed-By header. Guess what, for every email from
the list, including the second copy of my email, it says
"ruby-lang.org". But for the first copy, the Mailed-By header is
"gmail.com". In other words, it is the email that was *sent* by gmail,
not one you *received*.
Need further evidence? Go to your "Sent Mail" folder. Choose a
ruby-talk thread and click on it. What's the first unfolded message it
shows? That's right, the first copy of your email, which is embedded
right into the thread. It opens to that one because it's the one you
*sent*.
In short, you see two copies of your email in the thread because gmail
shows both the original sent copy along with the copy you received
from ruby-talk.
I don't call this a glitch or bug in gmail, since it's useful behavior
for most circumstances. Most people using gmail probably don't CC
themselves when they send an email out, so if they want to see their
email included into the thread, it makes sense to show the sent copy.
But when the mailing list sends you a copy of its own, you see a
"duplicate". That's all that's happening. If it's not happening for
other lists, it must be because they aren't sending you a copy of your
own messages -- which is perfectly fine. It's just that ruby-talk's
default is different, and you *can* change it if you want.
Jacob Fugal
···
On 6/15/06, Jeremy Tregunna <jtregunna@blurgle.ca> wrote:
On 15-Jun-06, at 2:32 PM, Austin Ziegler wrote:
> It's a Gmail glitch.I'd have to be a little weary about that statement. I see this exact
same behaviour using Mail on OSX 10.4 from my own mail server -- none
of my other lists or whatnot experience this same problem, only ruby-
talk. However, in my case, it's *all* messages to ruby-talk get sent
twice, not just my own.
Hi,
It's a Gmail glitch.
No, it's a ruby-talk glitch. Otherwise I would see the same issue
with other lists.
This is interesting. The mechanism of duplicated messages is as
explained in [ruby-talk:197553]. I do want to know how other lists
avoid this problem. Regretting messages to the posters is just no
way. I have ever heard that setting up skip filters for author copied
messages to ruby-talk might work. But I am not sure if filters on
Gmail work for author copies.
matz.
···
In message "Re: Why do my posts appear twice?" on Fri, 16 Jun 2006 03:40:25 +0900, "Greg Donald" <gdonald@gmail.com> writes:
Austin Ziegler wrote:
Go check your configuration on those other lists, before you make a
fool of yourself.
What an arse you are.
···
--
Posted via http://www.ruby-forum.com/\.