Re: BPQMail with WinPack
- Hi All, K.O. have developed a system for WinPack users to use the BPQ Telnet Server to automatically acquire headers from the BPQMail BBS.
We have pasted the methodology onto the "http://vk2dot.dyndns.org" web site under "Setting Up WinPack with BPQMail for BPQ Telnet Operation of Header Download:".
Hopefully one hasn't any errors in the text. If you find any, please advise.
--- In BPQ32@yahoogroups.com, John Wiseman <john.wiseman@...> wrote:
> Sorry, I don't understand how a user can see the ui headers if he is on telnet.
> -----Original Message-----
> From: "vk2dot" <vk2dot@...>
> To: BPQ32@yahoogroups.com
> Sent: 28/05/10 09:04
> Subject: [BPQ32] Re: BPQMail with WinPack
> John, this is the info we just received from users trying to automatically download headers from BPQMail.
> Still no go with auto Winpack Rod as below
> c vk2dot.dyndns.org:6301
> *** TELNET CONNECTED to vk2dot.dyndns.org
> Callsign:*** TELNET DISCONNECTED from vk2dot.dyndns.org
> Reply 2 Manual 6301 as below
> c vk2dot.dyndns.org:6301
> *** TELNET CONNECTED to vk2dot.dyndns.org
> Welcome to VK2DOT's Telnet Server
> Enter ? for list of commands
> *** Connected to SWITCH
> The users have no problems with Linux/XFbb, automatically downloading BBS Headers.
> Regards Rod......////
> --- In BPQ32@yahoogroups.com, "John Wiseman" <john.wiseman@> wrote:
> > Thanks Rod for some very useful feedback. As you probably know I'm away
> > sailing at the moment, but will reply more fully when I have time to
> > look more closely to your comments.One point though - the code does have
> > a Header transmission system that worked with WinPack last time I tried
> > it. Check "Enable UI System" on the main config screen to enable it.
> > 73,
> > John
> > -----Original Message-----
> > From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of
> > vk2dot
> > Sent: 26 May 2010 10:32
> > To: BPQ32@yahoogroups.com
> > Subject: [BPQ32] Re: BPQMailChat vs WinFbb
> > Hi All.
> > Please do not take the following as a criticism, but as an objective
> > analysis of the question, which may be built on over time.
> > 1: One thinks that BPQMail will eventually take over from Fbb over time,
> > but NOW to replace Fbb is not the time.
> > 2: Even I like WinFbb, but it becomes a burden with BPQMail - You need
> > two screens [monitors] at least to view all BPQMailChat & WinFbb
> > operations at once. It becomes a clutter with all of the BPQMail Screens
> > plus the WinFbb screen on the one monitor.
> > I went away from WinFbb a number of years ago to Linux/XFbb and have
> > been looking at going back to WinFbb because of BPQMailChat; But find
> > that Linux/XFbb is very stable and with FbbW running on a Windows
> > machine [remotely connected to Linux/XFbb] gives a great deal of
> > flexibility.
> > 3: A lot of us were spoilt rotten over time by using XRouter. But
> > unfortunately it has not been updated for a number of years and only
> > runs on a DOS machine. One of the good things about XRouter, being that
> > it ported TCP/IP. I do not expect John [G8BPQ] to go this route, as we
> > can use other systems connected to BPQ32 to do this job.
> > 4: The problems that a number of us are having with BPQMail, require a
> > lot of us to have XFbb/Node or WinFbb or XRouter on separate systems are
> > -
> > A: BPQMail does not have Header transmissions to enable remote WinPack
> > to automatically download bulletin & message Headers. WinPack users have
> > to do it manually.
> > B: BPQMail does not have Telnet out option for forwarding. We have to
> > connect to a second system such as Linux/XFbb, XRouter, Linux/Node or
> > WinFbb, then telnet out of that BBS or Router to be able to forward to a
> > Linux partner. These Telnet forward partners can telnet back via the BPQ
> > telnet Server to BPQMail. Ie We have to run more than one computer to do
> > a complete BBS task of forwarding.
> > C: John [G8BPQ] has told me that he is updating his Alias option with
> > BPQ32 to enable more that 8 Alias's. This Alias option enables users to
> > use your BPQ32 as a gateway to other Packet systems around the country
> > and world. Thus, making packet more interesting than just BBS transfers
> > for Packet system operators. Ie. On the VK2DOT-1 BPQ32 node, you can
> > type in UK & go to the United Kingdom, or VE and go to Canada, etc. We
> > are trying to entice more packet users - In Australia, packet is dying,
> > we have to make it more interesting for packet users and entice more
> > amateurs back to packet radio. This is an area where a number of users
> > and BBS system operators should be thinking seriously about this
> > problem.
> > D: An APRS RS232 Port would enable us to use BPQ32 for our APRS node,
> > that would allow us to remove XRouter or Linux/Node from our system for
> > this purpose. This would allow BBS system operators or users to send
> > traffic onto the APRS local network & Monitor APRS from a BPQ32 port. If
> > BPQ32 supported generic digipeating for RELAY, WIDE, TRACE, TRACEn-n AND
> > WIDEn-N aliases, it would be good. If BPQ32 allowed non APRS users
> > [BPQ32 users] to exchange messages with APRS/UI-View users and also to
> > send and read bulletins and announcements, that would also be very good.
> > In XRouter, we are allowed to make available on port 8000, APRS data to
> > run under UI-View on a remote PC. Users can connect to your system on
> > port 8000 and view all APRS traffic - really good stuff.
> > E: If proxy connections were allowed in BPQ32, this would allow external
> > [RF or AXUDP] users to directly connect to a remote target call, instead
> > of having to connect to BPQ32 then connect to another station via
> > another port. This would allow external users to use a remote BPQ32
> > system to connect to your local BBS by using the BBS's callsign in the
> > remote connect. We have here a number of external remote nodes, that
> > allow the remote users to just send a remote RF connect to VK2DOT - they
> > are then automatically connected to my BPQMail or XFbb software via an
> > AXUDP link from the external node. The user does not need to know the
> > path used. Saves a lot of problems for the remote users.
> > F: There is a problem with the BPQ32 access control for incoming Telnet
> > port 23 [or other Telnet port number] connections. Many of us have run
> > BBS's for over 20 years and have used an open system approach, with no
> > problems. If BPQ32 had a more liberal approach to telnet-ing into BPQ32,
> > we would be able to remove XRouter or Linux/Node for Telnet into our
> > systems. BPQ32 Telnet Server would have to be changed to give us the
> > following options to connect via Telnet protocol:-
> > (1) Enable valid callsign required.
> > (2) Enable Password required
> > Most of use have (1) above enabled, but (2) NOT enabled. In other words,
> > BBS's who do not trust there internet users would have (2) above
> > enabled. These options are available on XRouter or Linux/Node software.
> > We have never had a problem with this open system concept. It is amazing
> > when you look at the logs for this operation, where function (1) "valid
> > call-sign required" is enabled, it stops all the robots from entering
> > the system.
> > This can also be further enhanced by having a list of call-signs barred
> > from getting to BPQ32 via the Telnet Server.
> > Plus, you would still use a password for BPQMail connection on another
> > port [eg 6300], if needed; Different to Telnet 23 port.
> > 5: When the above has been implemented, then a lot of us will drop our
> > other systems such as WinFbb, Linux/Fbb, Linux/Node, XRouter, etc and
> > just run BPQ32 & BPQMailChat.
> > 6: One last item, the documentation - Very good, but being from the old
> > school I like to print it out, go to bed and read it. That is very
> > difficult with BPQMailChat. My arms get tired holding the laptop. One
> > document for the lot, would be just great, but we cannot burden the
> > developers with too many requests. We can do this with Fbb and other BBS
> > software. This should be a very low priority.
> > One has dissertated on items more than the requested question, however
> > it should point in a fashion, to where some of us hope that BPQMailChat
> > will go. John [G8BPQ] seems to be the only amateur radio BBS developer
> > doing good, I wish him well for BPQMailChat for the future. There are
> > probably more items that need to be added to the list to enhance
> > BPQMailChat here.
> > My present system comprises of VK2DOT-1 as the BPQ32 node, VK2DOT-0 as
> > the main BBS BPQMail and VK2DOT-7as BPQChat on a WinXP machine; Plus
> > VK2DOT-9 as XRouter on a DOS machine; Plus VK2DOT-2 as Linux/XFbb, and
> > VK2DOT-8 as Linux/Node on a separate machine. As you can see, the main
> > BBS is the BPQMailChat machine, however we need the DOS/XRouter & the
> > Linux/XFbb/Node machines to full fill all operational situations.
> > Another machine is being used to put the XRouter operations onto a
> > single Linux machine; then when BPQMailChat has grown up, BPQMailChat
> > will replace the XRouter & Linux machines.
> > One hopes that the above has been a little help than a hinder.
> > Regards Rod VK2DOT../////