[Added alt.windows7.general]

Zaidy036 <Eric@bloch.com> wrote:
> On 6/27/2022 3:39 PM, J. P. Gilliver (John) wrote:
> > On Mon, 27 Jun 2022 at 13:10:57, Zaidy036 <Eric@Bloch.com> wrote (my
> > responses usually FOLLOW):
> > []
> >> One alternative is to leave UAC active but run a program from a batch
> >> initiated from a shortcut which uses a "button pusher" like PTFBpro to
> >> acknowledge the UAC. That way when you run from the shortcut UAC is
> >> accepted but if something else tries to run a program UAC is still
> >> invoked.
> >
> > Eric/Zaidy, your above post appeared three times, at least here - all
> > dated today, but timestamped (I think my local time [BST, GMT+1])
> > 18:8:59, 18:9:57, and 18:10:57.
> >
> > (Interesting idea by the way.)
>
> It seems an e-s problem and I tried to delete after I saw the dups.

Yes, it's some kind of eternal-september.org problem and it's all over
the place. (Also two from Mayayana in this thread.)

Multiple - sometimes upto five or so - copies of the same - or very
similar - posts with slightly different timestamps and different
Message-IDs.

It's rather annoying (and a waste of space for people/news-servers
who/which keep articles for a long(er) time).

Anyone knows what's going on?

On Tue, 28 Jun 2022 at 15:09:45, Frank Slootweg <this@ddress.is.invalid>
wrote (my responses usually FOLLOW):
>[Added alt.windows7.general]
>
>Zaidy036 <Eric@bloch.com> wrote:
>> On 6/27/2022 3:39 PM, J. P. Gilliver (John) wrote:
[]
>> > Eric/Zaidy, your above post appeared three times, at least here - all
>> > dated today, but timestamped (I think my local time [BST, GMT+1])
>> > 18:8:59, 18:9:57, and 18:10:57.
>> >
>> > (Interesting idea by the way.)
>>
>> It seems an e-s problem and I tried to delete after I saw the dups.
>
> Yes, it's some kind of eternal-september.org problem and it's all over
>the place. (Also two from Mayayana in this thread.)

Ah, apologies - I thought it might be Zaidy's problem.
>
> Multiple - sometimes upto five or so - copies of the same - or very
>similar - posts with slightly different timestamps and different
>Message-IDs.
>
> It's rather annoying (and a waste of space for people/news-servers
>who/which keep articles for a long(er) time).
>
> Anyone knows what's going on?

Steady on - I would imagine Ray is looking at it; given that we (I,
anyway) use E-S for free, I wouldn't quite put it quite like that -
report fact yes (the additional fact abut MIDs might be useful), tone
perhaps different?
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

The best way to achieve immortality is by not dying.

On 6/28/2022 11:09 AM, Frank Slootweg wrote:
> [Added alt.windows7.general]
>
> Zaidy036 <Eric@bloch.com> wrote:
>> On 6/27/2022 3:39 PM, J. P. Gilliver (John) wrote:
>>> On Mon, 27 Jun 2022 at 13:10:57, Zaidy036 <Eric@Bloch.com> wrote (my
>>> responses usually FOLLOW):
>>> []
>>>> One alternative is to leave UAC active but run a program from a batch
>>>> initiated from a shortcut which uses a "button pusher" like PTFBpro to
>>>> acknowledge the UAC. That way when you run from the shortcut UAC is
>>>> accepted but if something else tries to run a program UAC is still
>>>> invoked.
>>>
>>> Eric/Zaidy, your above post appeared three times, at least here - all
>>> dated today, but timestamped (I think my local time [BST, GMT+1])
>>> 18:8:59, 18:9:57, and 18:10:57.
>>>
>>> (Interesting idea by the way.)
>>
>> It seems an e-s problem and I tried to delete after I saw the dups.
>
> Yes, it's some kind of eternal-september.org problem and it's all over
> the place. (Also two from Mayayana in this thread.)
>
> Multiple - sometimes upto five or so - copies of the same - or very
> similar - posts with slightly different timestamps and different
> Message-IDs.
>
> It's rather annoying (and a waste of space for people/news-servers
> who/which keep articles for a long(er) time).
>
> Anyone knows what's going on?
>

What's going on, is some database message is coming back
from E-S, once a post is submitted. The database message
indicates an error. The client thinks the post did not make
it. The server thinks the post made it.

Clients with automatic-retry capability, will in this
situation go nuts.

I tried reproducing this today, and it would not work for me.

Paul

Paul <nospam@needed.invalid> wrote:
> On 6/28/2022 11:09 AM, Frank Slootweg wrote:
> > [Added alt.windows7.general]
> >
> > Zaidy036 <Eric@bloch.com> wrote:
> >> On 6/27/2022 3:39 PM, J. P. Gilliver (John) wrote:
> >>> On Mon, 27 Jun 2022 at 13:10:57, Zaidy036 <Eric@Bloch.com> wrote (my
> >>> responses usually FOLLOW):
> >>> []
> >>>> One alternative is to leave UAC active but run a program from a batch
> >>>> initiated from a shortcut which uses a "button pusher" like PTFBpro to
> >>>> acknowledge the UAC. That way when you run from the shortcut UAC is
> >>>> accepted but if something else tries to run a program UAC is still
> >>>> invoked.
> >>>
> >>> Eric/Zaidy, your above post appeared three times, at least here - all
> >>> dated today, but timestamped (I think my local time [BST, GMT+1])
> >>> 18:8:59, 18:9:57, and 18:10:57.
> >>>
> >>> (Interesting idea by the way.)
> >>
> >> It seems an e-s problem and I tried to delete after I saw the dups.
> >
> > Yes, it's some kind of eternal-september.org problem and it's all over
> > the place. (Also two from Mayayana in this thread.)
> >
> > Multiple - sometimes upto five or so - copies of the same - or very
> > similar - posts with slightly different timestamps and different
> > Message-IDs.
> >
> > It's rather annoying (and a waste of space for people/news-servers
> > who/which keep articles for a long(er) time).
> >
> > Anyone knows what's going on?
> >
>
> What's going on, is some database message is coming back
> from E-S, once a post is submitted. The database message
> indicates an error. The client thinks the post did not make
> it. The server thinks the post made it.
>
> Clients with automatic-retry capability, will in this
> situation go nuts.

Thanks for the info. In this case, I think 'the client' is the human,
not the (newsreader) software. Zaidy uses Thunderbird, Mayayana uses
Outlook Express. I'm quite sure that Thunderbird will give an error
message and will not auto-retry. Probably the same for Outlook Express.

> I tried reproducing this today, and it would not work for me.

That's probaly because your newsreader doesn't only catch rats, but
apparently also server failures! :-)

"J. P. Gilliver (John)" <G6JPG@255soft.uk> wrote:
> On Tue, 28 Jun 2022 at 15:09:45, Frank Slootweg <this@ddress.is.invalid>
> wrote (my responses usually FOLLOW):
> >[Added alt.windows7.general]
> >
> >Zaidy036 <Eric@bloch.com> wrote:
> >> On 6/27/2022 3:39 PM, J. P. Gilliver (John) wrote:
> []
> >> > Eric/Zaidy, your above post appeared three times, at least here - all
> >> > dated today, but timestamped (I think my local time [BST, GMT+1])
> >> > 18:8:59, 18:9:57, and 18:10:57.
> >> >
> >> > (Interesting idea by the way.)
> >>
> >> It seems an e-s problem and I tried to delete after I saw the dups.
> >
> > Yes, it's some kind of eternal-september.org problem and it's all over
> >the place. (Also two from Mayayana in this thread.)
>
> Ah, apologies - I thought it might be Zaidy's problem.
> >
> > Multiple - sometimes upto five or so - copies of the same - or very
> >similar - posts with slightly different timestamps and different
> >Message-IDs.
> >
> > It's rather annoying (and a waste of space for people/news-servers
> >who/which keep articles for a long(er) time).
> >
> > Anyone knows what's going on?
>
> Steady on - I would imagine Ray is looking at it; given that we (I,
> anyway) use E-S for free, I wouldn't quite put it quite like that -
> report fact yes (the additional fact abut MIDs might be useful), tone
> perhaps different?

"tone perhaps different?" Huh!? I'm not 'reporting' anything, I'm just
describing a problem with posts from E-S. If I had realized you're an
E-S user, I would have asked/addressed you. (You're one of the few E-S
users who have changed/set their 'Organization:' header.)

If I was using E-S, I would of course have checked with them first,
but I'm not and never have been.