Digital Man

There doesn't appear to be any problem with your REP packets.
I just check your "MAP" QWKnet node account here on Vertrauen, and
you have "include Seen-Bys (@VIA)" enabled. Being that that you're

I turned ON after my last email in the hope of understanding the problem Robert seems to think I have with my REP packets.

I noticed that some have VIA:UNKNOWN but many like mine have VIA: a
given origin. On your advice I will turn it Off.

Thank you for the reply it is appreciated and saves me chasing a non-
issue.

Mike













On 14/02/2014 12:44 AM, DIGITAL MAN wrote to mapnet:

Re: Help with Correct REP Pac
By: mapnet to all on Fri Feb 14 2014 01:51 am

Robert / All

@VIA: MAP
@MSGID: <52FB6D87.13585.dove-sys@vert.synchro.net>

Based on the above I believe Robert is saying that VIA:MAP should

NOT

appear in the Message Header Text.

As VIA: is not part of the Wildcat! wcGate structure it is being

added at

REP packet import.

The only Synchronet QWK setting I can see possibly relating to this

is:

[V] Include Message Path (VIA) : No

Which in my case is set to No so it appears unrelated.

Currently I am:

- Exporting REPLIES to VERT.REP
- Uploading to dove.synchro.net VIA the QWK Node Account I

created

- Placing the VERT.REP Packet in the default ftp directory (same as VERT.QWK)

So Am I:

- Uploading to the wrong host?
- Should I have a different Account?
- Am I placing the REP packet in the incorrect location?

It appears logical the VIA: should show where the REPLIES are

entering,

but Robert seems to suggesting it should not show.

If anyone could clarify the correct REP posting process for me it

would be

much appreciated

There doesn't appear to be any problem with your REP packets.

I just check your "MAP" QWKnet node account here on Vertrauen, and

you have

"include Seen-Bys (@VIA)" enabled. Being that that you're running

Wildcat!, you

probably want to turn that off.

digital man

Synchronet "Real Fact" #74:
Rob's alias "digital man" was inspired by a song on Rush's

1982 "Signals" album.

Norco, CA WX: 61.9 F, 46.0% humidity, 0 mph SSE wind, 0.00 inches

rain/24hrs

---
  Synchronet   Vertrauen   Home of Synchronet  

telnet://vert.synchro.net

---
■ MAP-Net

On Feb 14, 2014 01:51am, MAPNET wrote to ALL:

@VIA: MAP
@MSGID: <52FD84D7.13592.dove-sys@vert.synchro.net>
Robert / All

@VIA: MAP
@MSGID: <52FB6D87.13585.dove-sys@vert.synchro.net>

Based on the above I believe Robert is saying that VIA:MAP

should NOT

appear in the Message Header Text.

As VIA: is not part of the Wildcat! wcGate structure it is being

added at

REP packet import.

This is not the problem. Is your username MAPNET or is that the QWK
ID of your BBS?

The only Synchronet QWK setting I can see possibly relating to

this is:

[V] Include Message Path (VIA) : No

Which in my case is set to No so it appears unrelated.

This setting has not effect in wcQWK.

Currently I am:

- Exporting REPLIES to VERT.REP
- Uploading to dove.synchro.net VIA the QWK Node Account I

created

- Placing the VERT.REP Packet in the default ftp directory (same

as

VERT.QWK)

This is what I do. I have scripts that automate this process for
me.

So Am I:

- Uploading to the wrong host?
- Should I have a different Account?
- Am I placing the REP packet in the incorrect location?

It appears logical the VIA: should show where the REPLIES are

entering,

but Robert seems to suggesting it should not show.

VIA in this case does not matter unless you are running Synchronet.

If anyone could clarify the correct REP posting process for me

it would

be much appreciated

What you are doing is fine. I am just curious as to what account
you are poisting with because it would seems to me that the MAPNET
user ID is the QWK ID of your BBS you are using to log in with and
post with (unless you have that same user ID set up on your BBS, in
which case, please ignore all my bantering *smiles*).

---
■ MAP-Net

And a little blurb about your BBS (BBS name and telnet address) here
would be nice, too, so that I can come visit :)

... Platinum Xpress & Wildcat!..... Nice!!!!
---
■ wcQWK 6.4 ≈ RiverNet BBS * Memphis, TN * winserver.us

On Feb 14, 2014 12:44am, DIGITAL MAN wrote to MAPNET:

I just check your "MAP" QWKnet node account here on Vertrauen,

and you

have "include Seen-Bys (@VIA)" enabled. Being that that you're

running

Wildcat!, you probably want to turn that off.

Hmmo, ok, this is what I thought, so please ignore my blurbs before
:) I wasn't sure if he was using MAPNET or MAP as his QWK ID. My
apologies about the non-Synchronet related traffic.

... Platinum Xpress & Wildcat!..... Nice!!!!
---
■ wcQWK 6.4 ≈ RiverNet BBS * Memphis, TN * winserver.us

On Feb 14, 2014 09:01am, MAPNET wrote to DIGITAL MAN:

Thank you for the reply it is appreciated and saves me chasing a

non-

issue.

Mike, sorry about my stepping in there. Guess the Wildcat! sysop in
me wanting to help other Wildcat! folks (only because it seems
Santronics doesn't want to) kicked in again. Sorry about the
confusion.

... Platinum Xpress & Wildcat!..... Nice!!!!
---
■ wcQWK 6.4 ≈ RiverNet BBS * Memphis, TN * winserver.us

Mike, sorry about my stepping in there. Guess the Wildcat! sysop in
me wanting to help other Wildcat! folks (only because it seems
Santronics doesn't want to) kicked in again. Sorry about the
confusion.

I am not familiar with Synchronet processes so I welcome input providing
it does not unnecessarily side track me.

Synchronet is a good package and offers superior support for QWK to that offered by Wildcat! However, in fairness to Santronics they fully support their customers in the use of QWK. There has always been (and always
will be) differences in the level of public versus private contracted support.

This is what I do. I have scripts that automate this process for me.

I am referring to  built-in  IP support for moving QWK/REP packets
between Wildcat to Wildcat and Synchronet to Wildcat Systems.

I am not referring to any form of telnet or ftp scripting language. I have
my own binary utility for importing and exporting so I don t rely solely
upon wcQWK/UUCP

And a little blurb about your BBS (BBS name and telnet address) here

would be nice, too,

I am a general purpose ASM/C developer. The work I have been doing is
for a group that runs a Private Networking Group [SWPNG] that use both Synchronet and Wildcat! What they wanted was a way to transfer QWK
mail between the two platforms purely via IP rather than via scripted or
batch programming solution. As far as I am concerned this benefits both platforms and promotes QWK.

As for  blurb  I wrote TI-BBS (4/4a platform) in 1983 and the VideoText
based FRPBBS software for the C64 in 1987. By the time I moved to IBM
PC platform there were already companies like MSI selling BBS Packages.
So as you can appreciate after 30+ years I have no need or interest in promoting my system through *tags.

Again, thank you to Digital Man for the advice. As my IP testing is now complete I will conclude my contribution to this thread here.


Mike






On 15/02/2014 8:24 AM, ROBERT WOLFE wrote to mapnet:

.On Feb 14, 2014 09:01am, MAPNET wrote to DIGITAL MAN:

Thank you for the reply it is appreciated and saves me chasing a

non-

issue.

Mike, sorry about my stepping in there. Guess the Wildcat! sysop in
me wanting to help other Wildcat! folks (only because it seems
Santronics doesn't want to) kicked in again. Sorry about the
confusion.

... Platinum Xpress & Wildcat!..... Nice!!!!
---
  wcQWK 6.4   RiverNet BBS * Memphis, TN * winserver.us

---
■ MAP-Net

On Feb 16, 2014 03:17am, MAPNET wrote to ROBERT WOLFE:

I am referring to built-in IP support for moving QWK/REP

packets

between Wildcat to Wildcat and Synchronet to Wildcat Systems.

I am not referring to any form of telnet or ftp scripting

language. I

have my own binary utility for importing and exporting so I don

t rely

solely upon wcQWK/UUCP

Wait a minute :) I know someone (including myself) who would be
interested in just this sort of thing :) If you need anyone else to
test it out, I can think of two other people who would be interested
in a utility like this (at LAST two) - me and another Wildcat! sysop
*smiles*.

... Platinum Xpress & Wildcat!..... Nice!!!!
---
■ wcQWK 6.4 ≈ RiverNet BBS * Memphis, TN * winserver.us

@VIA: MAP
@MSGID: <52FDE984.13594.dove-sys@vert.synchro.net>

I turned ON after my last email in the hope of understanding the problem Robert seems to think I have with my REP packets.

I noticed that some have VIA:UNKNOWN but many like mine have VIA: a
given origin. On your advice I will turn it Off.

Thank you for the reply it is appreciated and saves me chasing a non-

Ok, unfortunately, the @VIA: in QWK networking with Synchronet boards is
put in for QWK based "netmail," which, AFAIK, Wildcat! does not support
at this particular point in time. I've been getting your messages just
fine here. Set up Wildcat! 7 on another VM as a testing and development
system and connected this echo to it that way.



---
■ wcQWK 7.0 ≈ Omicron Theta Test System * Memphis TN * winserver.us
■ wcQWK 6.4 ≈ Omicron Theta BBS * Memphis, TN * winserver.us

Correct it s not available in the generally available Retail Build of Wildcat!

As my customer s principle requirement is Wildcat-to-Wildcat QWK/REP
FTPS transfers it is not a priority project for me at this time.

I may revisit QWK / E-QWK in the future as part of a broader update to
several out-dated binaries.


On 28/07/2014 6:24 AM, ROBERT WOLFE wrote to mapnet:

@VIA: MAP
@MSGID: <52FDE984.13594.dove-sys@vert.synchro.net>

I turned ON after my last email in the hope of understanding the

problem

Robert seems to think I have with my REP packets.

I noticed that some have VIA:UNKNOWN but many like mine have

VIA: a

given origin. On your advice I will turn it Off.

Thank you for the reply it is appreciated and saves me chasing a

non-

Ok, unfortunately, the @VIA: in QWK networking with Synchronet

boards is

put in for QWK based "netmail," which, AFAIK, Wildcat! does not

support

at this particular point in time. I've been getting your messages just
fine here. Set up Wildcat! 7 on another VM as a testing and

development

system and connected this echo to it that way.

---
  wcQWK 7.0   Omicron Theta Test System * Memphis TN *

winserver.us

  wcQWK 6.4   Omicron Theta BBS * Memphis, TN * winserver.us

---
wcQWK 7.0.1105 (R) <-> MAP

Correct it s not available in the generally available Retail Build of Wildca

As my customer s principle requirement is Wildcat-to-Wildcat QWK/REP
FTPS transfers it is not a priority project for me at this time.

I may revisit QWK / E-QWK in the future as part of a broader update to several out-dated binaries.

Ah, ok. I have a Wildcat <-> Synchronet / Wildcat <-> Mystic QWK FTP
transfer product that I've written and is generally available. Have
not started on a Wildcat <-> Wildcat one yet.

... Stewardess trainee: "Where does THIS door gooooooooooooo...."
--- Wildcat! (#07-2791) with 367 taglines!
■ wcQWK 6.4 ≈ Omicron Theta BBS * Memphis, TN * winserver.us

@VIA: MAP
@MSGID: <52FDE984.13594.dove-sys@vert.synchro.net>

I turned ON after my last email in the hope of understanding the problem Robert seems to think I have with my REP packets.

I noticed that some have VIA:UNKNOWN but many like mine have VIA: a
given origin. On your advice I will turn it Off.

Thank you for the reply it is appreciated and saves me chasing a non-

Ok, unfortunately, the @VIA: in QWK networking with Synchronet boards is
put in for QWK based "netmail," which, AFAIK, Wildcat! does not support
at this particular point in time. I've been getting your messages just
fine here. Set up Wildcat! 7 on another VM as a testing and development
system and connected this echo to it that way.



---
■ wcQWK 7.0 ≈ Omicron Theta Test System * Memphis TN * winserver.us
■ wcQWK 6.4 ≈ Omicron Theta BBS * Memphis, TN * winserver.us

Correct it s not available in the generally available Retail Build of Wildcat!

As my customer s principle requirement is Wildcat-to-Wildcat QWK/REP
FTPS transfers it is not a priority project for me at this time.

I may revisit QWK / E-QWK in the future as part of a broader update to
several out-dated binaries.


On 28/07/2014 6:24 AM, ROBERT WOLFE wrote to mapnet:

@VIA: MAP
@MSGID: <52FDE984.13594.dove-sys@vert.synchro.net>

I turned ON after my last email in the hope of understanding the

problem

Robert seems to think I have with my REP packets.

I noticed that some have VIA:UNKNOWN but many like mine have

VIA: a

given origin. On your advice I will turn it Off.

Thank you for the reply it is appreciated and saves me chasing a

non-

Ok, unfortunately, the @VIA: in QWK networking with Synchronet

boards is

put in for QWK based "netmail," which, AFAIK, Wildcat! does not

support

at this particular point in time. I've been getting your messages just
fine here. Set up Wildcat! 7 on another VM as a testing and

development

system and connected this echo to it that way.

---
  wcQWK 7.0   Omicron Theta Test System * Memphis TN *

winserver.us

  wcQWK 6.4   Omicron Theta BBS * Memphis, TN * winserver.us

---
wcQWK 7.0.1105 (R) <-> MAP

Correct it s not available in the generally available Retail Build of Wildca

As my customer s principle requirement is Wildcat-to-Wildcat QWK/REP
FTPS transfers it is not a priority project for me at this time.

I may revisit QWK / E-QWK in the future as part of a broader update to several out-dated binaries.

Ah, ok. I have a Wildcat <-> Synchronet / Wildcat <-> Mystic QWK FTP
transfer product that I've written and is generally available. Have
not started on a Wildcat <-> Wildcat one yet.

... Stewardess trainee: "Where does THIS door gooooooooooooo...."
--- Wildcat! (#07-2791) with 367 taglines!
■ wcQWK 6.4 ≈ Omicron Theta BBS * Memphis, TN * winserver.us