1. Forum
  2. DeveloperNet
  3. Announce

  • RE: Help with Correct REP

    From ROBERT WOLFE@DIGDIST/BATTLEST/FREEWAY to MAPNET on Monday, July 28, 2014 06:24:00
    @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
  • From QWKTest@DIGDIST/BATTLEST/FREEWAY to ROBERT WOLFE on Tuesday, July 29, 2014 02:44:00
    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
  • From ROBERT WOLFE@DIGDIST/BATTLEST/FREEWAY to QWKTEST on Tuesday, July 29, 2014 10:36:00
    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