It means the post was not sent as a follow up.(possibly no reference in the header. The mailing list does not know it is a reply, so made it a new post.

If you can list the examples and the original message's subject. I will find the reason.

Basically the thread by subject works by:

1) The message needs to have Re: in the beginning of the subject before the script even starts to worry about finding a thread.
2) "Re: asdf" will match thread's title with
asdf
Re: asdf

"Re: Re: asdf" will match thread's title with
asdf
Re: asdf
Re: Re: asdf

"Re: Re: Re: asdf" will match

Re: asdf
Re: Re: asdf
Re: Re: asdf
Re: Re: Re: asdf
(not match with asdf)

It will find the oldest thread, and will use the newest post as the parent message id (only used when the forum reader uses non-inline display mode).

Should be left at 0.

thank you lierduh - I did look into the files and found it. :)

Default = 0. Set to 0 : Check if another instance of gateway.php is running. Set to 1 : Do not check.

I'm using the NNTP gateway script to provide users access to our internal news server. As such, I'm creating user accounts under vBulletin which matches the LHS of their email address (i.e. anything before the @ sign). When posting to the news server, I'm getting a copy of the message ID as the From: header. I want to be able to post with a legitimate email address.

For example:

xxxxxxx.rrrrr@domain.name

(where xxxxxxxx is the normal LHS email name and rrrrr is the message ID)

whereas I'd like it to just be:

xxxxxxx@domain.name

Is there an easy way of doing this/changing the current gateway.php file to handle this?

Regards,

MArtyn

Hey, lierduh -

Is there a reason why the nntp_groups table is ISAM instead of MyISAM? I know if you convert the table to MyISAM the script fails - and since it's usually a tiny table it probably wouldn't benefit much from optimizing, but having to deselect it when optimizing the forum database might be something to look at.

cheers -

allan

lierduh

Is there a limitation on the subject line size?

I received some messages (all via the same mailserver) as follows

Original message http://proteluser.com/bbs3/showpost....63&postcount=1

Original subject line [dxp] A rule for allowing two components on top of each other?

Then I seen a reply which was not threaded

Reply http://proteluser.com/bbs3/showpost....17&postcount=1

Subject line Re: [dxp] A rule for allowing two components on top of eachother?

Notice the space is missing between the last 2 words "each other" is now "eachother". Hence the reason for none threading.

But the reply as i see it in my mailbox, from the same email server (the same message), is actually correct and does read Re: [dxp] A rule for allowing two components on top of each other?

So the originating message was actually correct, it was not edited by the user. But i did notice that the subject line was wrapped to a new line between these words in the actual header. Perhaps related to the issues with the strange end of line characters in some posts?

Any information appreciated.

I forward a copy of the message headers for this non threaded reply to the mailbox i set up for you (same mail server again)

allan, you are using the very original table created by Gilby's original hack. I remember in that SQL, the tables were created as ISAM.

If someone started new with the vB3 hack, the tables will be created using MyISAM table type.

I can't see the reason why MyISAM will cause the script to fail. Both of my nntp tables are MyISAM.

I've set you up an account, details are in pm. There are only a few examples at this moment, since most of them i had already merged manually.

[edit] ok by now there are plenty examples :D[/edit]

Hi lierduh,

if possible, could you tell me what I have to do to make gateway.php pause between connecting to different ng?s ?
I guess it?s the same function like this:

Should only be another table-name and selectable value. Some newsservers are blocking the script in case the gateway is way to fast for an old and slow newsserver. (Err-Msg: "Too many connections. Your IP is temporarly blocked.")

TIA,
Marv.