Outpost Packet Message Manager

BBS and PBBS Information


 

Telpac / Winlink BBS

General Information:

27-Mar-07: Winlink brings a robust messaging infrastructure to the Packet community with the intent to support emergency communications.  Outpost will implement client support with Winlink access by Telpac using a terminal-based connection approach.  Forwarding (supports a more rich set of features) is not implemented in Outpost.

References:

http://www.winlink.org/

http://www.winlink.org/B2F.htm

User Settings: None identified.
Outpost Notes:

IMPLEMENTATION
SID = [WL2K-3.1.2-B2FIHM$]
Outpost looks for the "[WL2K" phrase of the SID as the means for identifying this BBS.  Prompts will automatically be identified by Outpost at connect time.

CONFIRMATION
Confirmed as part of the v2.2 Release.

 

CONSIDERATIONS

1.  Attachments.  This implementation does not support attachments of any kind.  Outpost is merely emulating the manual keystrokes that you would perform if sitting in front of a terminal mode program.  Winlink does not pass attachments typically found in internet mail programs to Telpac.

 

BBS Notes:

SPECIAL CONFIGURATIONS, SETTINGS

None.

Listing:

CMS Example:  The following is a typical listing presented by a dorect connect to a Winlink CMS node by telnet could be seen by Outpost.

 

TCPIP: Connecting to the Network Interface... connected!

 

Callsign :

.KN6PE

Password :

CMSTELNET

[WL2K-1.6.1.0-B2FIHM$]

;PQ: 48397221

SanDiego CMS >

LM

EK6PA0FF1KK5 2008/10/17 14:38 1035 VE9BUF 195: no problem...

 

SanDiego CMS >

R EK6PA0FF1KK5

Message ID: EK6PA0FF1KK5

Date: 2008/10/17 14:38

From: VE9BUF

To: KN6PE; SMTP:OBERMAIL@ATT.NET 

Source: VE9BUF

CMS Site: Halifax

Subject: 195: no problem...

 

Hello Jim, not a problem at all to send people in the right 

   :

   :

73 de Jean-Guy/ve9buf

Message sent using Outpost 2.3.0 c21

 

SanDiego CMS >

K EK6PA0FF1KK5

EK6PA0FF1KK5 completed...

SanDiego CMS >

B

Session End

TCPIP: Disconnecting from the TCPIP Interface... Closed

 

 

RMS Example:  The following is a typical listing presented when connecting to Winlink via an RMS node as seen by Outpost.

  

cmd:connect K6MTV-10

cmd:*** CONNECTED to K6MTV-10

City of Mountain View RACES

[WL2K-1.6.1.0-B2FIHM$]

;PQ: 07411810

Perth CMS via K6MTV-10 >

LM

0TWMPL8ILW1A 2008/10/18 22:30 125 KN6PE CUP131: Next Meeting

 

Perth CMS via K6MTV-10 >

R 0TWMPL8ILW1A

Message ID: 0TWMPL8ILW1A

Date: 2008/10/18 22:30

From: KN6PE

To: K6KP 

Source: KN6PE

CMS Site: SanDiego

Subject: CUP131: Next Meeting

 

Hello,

The agenda for the next CARES meeting will be the prep for the annual S.E.T. Details to follow.

 

regards,

jim o

 

Perth CMS via K6MTV-10 >

K 0TWMPL8ILW1A

0TWMPL8ILW1A completed...

Perth CMS via K6MTV-10 >

B

Session End

*** DISCONNECTED

cmd:  

 

General Feedback

Please send any feedback to

updated:  December 30, 2009