Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: [lpc2000] Posting problems

2006-05-02 by Leon Heller

----- Original Message ----- 
From: "Robert Adsett" <subscriptions@...>
To: <lpc2000@yahoogroups.com>
Sent: Tuesday, May 02, 2006 5:59 PM
Subject: Re: [lpc2000] Posting problems


> At 05:50 PM 5/2/06 +0100, Leon Heller wrote:
>>From: "Richard" <nospam@...>
>>To: <lpc2000@yahoogroups.com>
>>Sent: Tuesday, May 02, 2006 5:29 PM
>>Subject: [lpc2000] Posting problems
>>
>>
>> > Could anybody offer any suggestions as to why posts from me take 3 to 4
>> > days to turn up on the list?  There does not seem to be a simple way of
>> > finding the answer in the help system.
>> >
>> > Normally I post by replying to an email.  This time I'm using the WEB
>> > interface to see if it makes any difference.
>>
>>This one seems to have gone through very quickly. Someone on another group
>>mentioned a similar problem, I think it was suggested that with a large
>>group it takes a long time to process the mail if one joined a long time 
>>ago
>>(I see you joined in May, 2004) but I don't know if that is actually the
>>reason.
>
> Well, my membership dates from Nov, '03.  So if that's a factor it can't 
> be
> the whole reason.  On the other hand I've had a time or two when yahoo had
> to intervene to get things going again so maybe that cleared up whatever
> the underlying factor is.

I just tried searching on Google for something relevant, it seems to be a 
common problem with other groups from time to time. Sometimes it's been 
caused by viruses, apparently. I suppose they have to hold the emails while 
they sort out the problem, as some are spread via email attachments.

Leon 

---
[This E-mail has been scanned for viruses but it is your responsibility 
to maintain up to date anti virus software on the device that you are
currently using to read this email. ]

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.