The SSID has helped a lot. I had misunderstood that you should use lower case for client stations and upper case for server stations, so I changed kv9u to KV9U and KV9U to KV9U-3 at this time.
For packet, I was thinking more along the lines of local use ... or actually not using it. The infrastructure (networks) we used to have are all gone now as are a number of the bbs sysops. One thing that I found was that at least in our area, the sysops did not like to share information. In fact, one actually resented anyone knowing what frequencies the node stacks were on for the 9k6 links.
I consider packet to be close to useless on HF and of very limited use now on VHF. And we have much better protocols as Skip, KH6TY has found work well for weak signal even on FM VHF. Maybe they are too slow though for message systems?
When you send a message, and it can not be delivered, using the Windows JavaPSKmail client, I have not been able to clear this out on the client side, unless I completely delete all outgoing messages from the pskmail program. I can not find any files that store individual messages. Is there some way to to this and also, when you get an incoming message, is it stored in a file somewhere? I have not found anything in the Vista re-directed folders either.
Finally, when I try and send traffic to myself to hold on the server, such as KV9U@KV9U-3, it seems to be sent OK. But how do I get it back if I want to read it again? I have not been able to figure that out.
73, Rick, KV9U Rein Couperus wrote:
comments below...-----Ursprüngliche Nachricht----- Von: "Rick W" <mrfarm@xxxxxxxxxxxxxxx> Gesendet: 07.06.09 21:27:45 An: pskmail@xxxxxxxxxxxxx Betreff: [pskmail] Re: BBS and pskmailIt is probably beyond my abilities, but maybe I can eventually try to do something along the lines you suggest.There is a lot of know-how in the packet community.,.The other suggestion was to use PSKmail as a rudimentary BBS by sending mail to the server. I probably do not have this set up correctly and maybe someone can give the exact specific parameters you would need to make this work. I tried sending to my pskmail_server with a message to kv9u@KV9U. It accepted the mail but I have not been able to retrieve it.Hint: Use an SSID on the server, e.g. KV9U-3, never the smae as your own callsign..Always use UPPER CASE for the callsigns. So e.g. send a mail to KV9U@KV9U-3The server will automatically make a local mail directory for KV9U. The Mbox ~LLIST command will show you your headers in the local mbox. If that does not work pse send us the error message the server produces.Do you need to update different parameters to the server or can you use your regular e-mail information?for the local mbox the server needs no parameters, it works with the call you connect it with.The one thing I am keeping away from is anything related to packet since it no longer really exists in our region anymore except for APRS. And packet requires a fairly good signal to get it to work. If packet had weak signal capabilities probably some of us would use it instead of these alternative systems when using VHF.I never suggested using HF packet, but using pskmail to access the infrastructure behind it. There is still a world-wide IGATE network you can telnet into, providing a host of resources which are hardly used anymore!!!My suggestion is to use these existing resources instead of building new resources from scratch... you will find a lot of sysops running packet BBS'es very cooperative where it relates to connecting a pskmail server to access their services. If you must, I would try to install existing BBS software, and connect it to the pskmail server via telnet.DA5UWG runs a pskmail server, a minidigipeater on VHF with AX25 connection to a BBS in the region, and 2 pactor links to the UK, Turkey and ZL.All this can be handled via connection to the pskmail server. 73, Rein PA0R73, Rick, KV9U Rein Couperus wrote:A simple answer:There is plenty of code for separate BBS'es available, it is just a matter of installing it in the right way. A good example is XNet, we have such a combination on DA5UWG which has a Telnet port. I allows a telnet connect to any BBS on the IGate backbone. Come to think of it, a lot of BBS resources are just available as we speak. Use them!If we would integrate such a BBS in the pskmail server I would have to write new code, and I have other priorities. I hate reinventing the wheel. The command is ~TELNET address port (while connected).If you are interested to add a pskmail/packet gateway, Arno DF3DS (sysop of DA5UWG) has written a drat howto.73, Rein PA0R-----Ursprüngliche Nachricht----- Von: "Rick W" <mrfarm@xxxxxxxxxxxxxxx> Gesendet: 06.06.09 17:31:11 An: pskmail@xxxxxxxxxxxxx Betreff: [pskmail] Re: BBS and pskmail------------------------------------------------------------------------Hi Rein, It is very good to know that you can telnet to a separate BBS.Could you outline the advantages of tying the pskmail_server to a separate BBS versus using the pskmail_server as the BBS?73, Rick, KV9U rein@xxxxxxxxxxxx wrote:PSKmail message from rein@xxxxxxxxxxxx quote Since then, there does not seem to be a practical HF sound card method to do basic BBS type connections other than using packet radio and perhaps something like Multipsk which is the only free sound card packet program that I am aware of.<br> unquoteYou can use the pskmail ~TELNET function to connect to a BBS on the same machine or on another machine in the LAN or to any BBS on the internet.So also here pskmail is already there... I often use the db0pfd packet mailbox to shift mail to other BBS users... 73, Rein PA0R SM/PA0R/M via pskmail------------------------------------------------------------------------No virus found in this incoming message.Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.12.53/2156 - Release Date: 06/05/09 06:24:00No virus found in this incoming message.Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.12.55/2160 - Release Date: 06/07/09 05:53:00------------------------------------------------------------------------No virus found in this incoming message.Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.12.55/2160 - Release Date: 06/07/09 05:53:00
