Are any of you using IREX? If so, how do you make it to stop sending dupes? I have it set up per the manual(limited info there) and it is still sending dupes to the networks that I am connected to. The packets are fine unit Irex gets hold of it. And it does delete the packet in the outbound directory. Not too sure what is going on. Running 2.29 if that helps

-Scuz

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: 2o fOr beeRS bbS>>20ForBeers.com:1337 (1:105/420)

Are any of you using IREX? If so, how do you make it to stop sending dupe have it set up per the manual(limited info there) and it is still sending dupes to the networks that I am connected to. The packets are fine unit I gets hold of it. And it does delete the packet in the outbound directory. Not too sure what is going on. Running 2.29 if that helps

Been using Irex for almost 15 years. Never had it send dupes. Usually it's your TOSSER causing this, such as FastEcho or Fmail. Use GEcho.

... I'm The Best at what I do, and what I do isn't very nice.

--- Renegade v1.35/DOS
* Origin: The Titantic BBS Telnet - ttb.rgbbs.info (1:129/305)

Been using Irex for almost 15 years. Never had it send dupes. Usually it's your TOSSER causing this, such as FastEcho or Fmail. Use GEcho.

Got it tracked down, it was actually IREX causing it. not sure why, but whatever I changed last night fixed it. I was watching the logs from OBV/2 to Gecho to IREX and it would generate it in IREX. But, it's fixed now :) Thanks for responding!

-mitch

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Been using Irex for almost 15 years. Never had it send dupes. Usually it's your TOSSER causing this, such as FastEcho or Fmail. Use GEcho.

forgot to mention, other systems weren't having dupe replies or posts. it was just the packets being sent as dupes.

-mitch

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Been using Irex for almost 15 years. Never had it send dupes. Usual it's your TOSSER causing this, such as FastEcho or Fmail. Use GEcho

forgot to mention, other systems weren't having dupe replies or posts. it just the packets being sent as dupes.

That's just weird.

... I'm another roadkill on the Information Superhighway.

--- Renegade v1.35/DOS
* Origin: The Titantic BBS Telnet - ttb.rgbbs.info (1:129/305)

Are you using Gecho? Out of the blue, it stopped tossing inbound packaged to two of my nets. I have no clue what's going on with it. Gecho logs says that it tossed the packages, but they are just sitting in the inbound directory. It has worked fine for months and nothing has changed configuration wise.

-mitch

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Are you using Gecho? Out of the blue, it stopped tossing inbound packaged two of my nets. I have no clue what's going on with it. Gecho logs says it tossed the packages, but they are just sitting in the inbound directory It has worked fine for months and nothing has changed configuration wise.

Yup, for the last 31 years. Can you toss them manually? I know every now and then when I add a node (copy), it will default my fidonet address to the packet, even tho node manager says its MetroNet. I have to delete the node and create from scratch to fix. It just started happening a year or 2 ago.

Are you tossing *.MSG? Jus a shot out of the blue, try a reset on the PC. you never know. Some old door or some shit might be haning in the memory GEcho uses. Seen weirder shit.

... It's not a bug, it's an undocumented feature.

--- Renegade v1.35/DOS
* Origin: The Titantic BBS Telnet - ttb.rgbbs.info (1:129/305)

Yup, for the last 31 years. Can you toss them manually? I know every now and then when I add a node (copy), it will default my fidonet
address to the packet, even tho node manager says its MetroNet. I have to delete the node and create from scratch to fix. It just started
Are you tossing *.MSG? Jus a shot out of the blue, try a reset on the PC. you never know. Some old door or some shit might be haning in the memory GEcho uses. Seen weirder shit.

It won't even toss them manually, I've restarted everything and the PC. Just tried again and it is just ignoring the packets from those two nets. Agoranet and tqwNEt.. fsxNEt is working just fine. I'm stumped with this one.

-mitch

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

I just ran a test message. the packet is not being extracted so that it can be tossed.

-mitch

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

I figured it out. for some odd reason the packet decompression option was turned off for these two nets.


-mitch

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

It won't even toss them manually, I've restarted everything and the PC. J tried again and it is just ignoring the packets from those two nets. Agora and tqwNEt.. fsxNEt is working just fine. I'm stumped with this one.

Other possible reason it did toss them, and now it thinks they are "dupes" but is ignoring the packet. Get someone to send a test message from that net in and echo and see if it passes through.

Seen that happen a couple of times.

... The way to a woman's heart is through her ribs.

--- Renegade v1.35/DOS
* Origin: The Titantic BBS Telnet - ttb.rgbbs.info (1:129/305)

tossed.
I just ran a test message. the packet is not being extracted so that it ca

Can't find pkunzip/pkzip in your path? Try uncompressing it and then run Gecho Toss.

... Experience=a name everyone gives to his mistakes.

--- Renegade v1.35/DOS
* Origin: The Titantic BBS Telnet - ttb.rgbbs.info (1:129/305)