From: Anne W. <can...@go...> - 2007-08-27 20:33:05
|
On Monday 27 Aug 2007, Rob MacGregor wrote: > [ Sent to the list so others know what happened ] > > On 8/27/07, Anne Wilson <can...@go...> wrote: > > Mystery solved. It was not being blocked by the list, nor by googlemail. > > It was being forwarded to me, as it should be. However, the problem was > > a recently added procmail recipe, obviously faulty. When procmail > > encounters a problem that confuses it, it puts the messages 'in a safe > > place'. I have just found the messages with another 100 or so, to be > > sorted through. Thankfully, the fetchmail recipe was the only one > > following the faulty one, or there could have been thousands. > > > > Apologies to all for wasting bandwidth. Now to address the problem. > > Hey, at least you've learned to check the destination of last resort. > It's something that's worth checking regularly and, along with your > mail log, is something worth checking any time things seem to be going > wrong. > This happened to me just once before, about three years ago. I had looked for the missing emails in what I remembered to be the place I found them last time, but things have moved on :-) > It's also worth saying that any time there are problems with mail > to/from a list it's worth checking any archive of that list to see if > mail is reaching it, and if others are replying. It's also worth > trying contacting the list administrators via the -owner address (in > this case fetchmail-users-owner@), which you did indirectly do in this > case ;) If the faulty recipe had been earlier in the queue, I'd have realised that messages were missing from many folders, and found the problem much quicker. Just the way it goes, I guess. I hadn't thought of checking the archives, though, and that's a really stupid oversight. Anne |