The primary method of matching threads is by a reference number which is inthe headers of newsgroup posts and emails. This was written by Lierduh and is highly effective. All newsgroups thread pretty much perfectly just by this method.

Some mail groups (my personal experience is with Yahoo groups) do not reliably put the reference number in the header of the email, therefore I wrote a secondary check (case insensitive!) which checks again before starting a new thread. The "Re: " can appear anywhere in the subject title.

If you really, really have problems, you can find in the script where it searches for "Re: " and change it to "", and it will search every post that comes through for a subject match. This WILL slow things down, and will also match a thread from (say) 3 years ago if it has the same title. This is completely untested (and not recommended) as the basic threading will pick up most of them.

Lierduh cooked the Sunday roast, I just made some gravy :cheeky:

Thanks Kevin

I undestand a little better now, so ill dig deeper.

the source of the list is a private server using Lyris, its not yahoo or anything like that.

I might try using"" as this list server only has 50 or so posts a day so is never busy enough to slow the server down.

Also if using "" it should only d/l message that are in the pop3 box so it might not cause a flood.

The roast and the gravy make a fine combo mate, sweet :)

Oh nuts

Just seen the glitch again

This time i ran the script directly

But this was a reply to an earlier one and has Re in it

Header from first messsage/thread

Header from reply messsage

Is this because the Message ID is different? Or is the filter being confused between ID's in the reply and only seeing the first one (different) and not the second one (match)

John

When I run gateway.php, I get the message:

Gateway version 2.1.0 1 group(s) gatewayed.
Could not connect to NNTP-serverNot connectedNot connected

What's the problem?

I am trying to do this for the newsgroup rec.sport.golf

you are not allowed to access newsgroup via script or you have settings wrong (username/password if required).

I remommend you do a test first.
Use-------
- msnews.microsoft.com as SERVER
- microsoft.public.security as NEWSGROUP

NOTE: add 58700 as LAST MESSAGE or check the XREF # in header of last message found in usergroup.

I tried that microsoft newsgroup and i got the same message. should i try to reinstall?

I still get the message.
And ... yes, I am using the code posted on that POST.

Would you care to see the file?
I've made some "visual/html" modifcations to the file ... however, everything is clearly marked where the changes have been made (your mini-hacks , etc,)

yes, start from scratch ... make sure you read the instructions carefully

Anyone else using email delivery method and found problems with the script crashing?

I have been sending most things I could think of at the script and it has crashed twice, big time.

The first time was when a message was forwarded to the lists, the forward contained multiple forwarded messages and no subject. In this case the first message was part entered into the database (with no subject filled in) but nothing on the rest.

The second time was when a message was sent to the lists with no subject, perhaps it was still recovering from the first crash.

I might go back and try the nntp feed instead of email.

:ermm: My forums stopped grabbing new Usenet messages on 6/21. I'm trying to finger out exactly where the log jam has occured. My cron job is still going off like clockwork.

This is the entire content of my cron results minus the header garbage.


Any ideas as to what is happening? It looks like it only hits one group... then stops. ? :ermm: