Testing smapinntpd with native ipv6 support and ssl via stunnel.
TK> Testing smapinntpd with native ipv6 support and ssl via stunnel.
Do you mean this one: SmapiNNTPd/Linux-Pi/IPv6 1.3 20181115?
Anyways, I'm still wondering why the latest Thunderbirds mess the
"from" line... It is not the " -> ", because "def_showto" can be set "off".
TK> Anyways, I'm still wondering why the latest Thunderbirds mess the
TK> "from" line... It is not the " -> ", because "def_showto" can be set
TK> "off".
It's beyond my pay grade too. Through a comedy of errors, I have only a single functioning Thunderbird and that's the one: version 31.4 on my netbook, since any later models fuck up in some way or another. Or, I haven't bothered to install one. If I do, it will be an older version.
Sylpheed is quite nice for reading newsgroups. It's available for
linux as well as windows.
--- Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
@MSGID: 2:221/360 5bee6ffa150
@PID: SmapiNNTPd/Linux-Pi/IPv6 1.3 20181115
@CHRS: IBMPC 2
@TID: hpt/lnx 1.9.0-cur 2018-09-09
Testing smapinntpd with native ipv6 support and ssl via stunnel.
---
* Origin: *** nntps://rpi.rbb.bbs.fi *** (2:221/360)
SEEN-BY: 221/0 1 6 360 280/464 5555 320/219 640/305 1384 3634/12 123/25
SEEN-BY: 123/755 135/300 153/7715 154/10 261/38 3634/15 27 50 119 123/50 SEEN-BY: 3634/12 0 18/0 123/0 1/120
@PATH: 221/0 640/1384 3634/12
Anyways, I'm still wondering why the latest Thunderbirds mess the
"from" line... It is not the " -> ", because "def_showto" can be set "off".
Anyways, I'm still wondering why the latest Thunderbirds mess the "from" line... It is not the " -> ", because "def_showto" can be set "off".
it is because they are enforcing the internet email format user@host.domain... they simply do not recognise the fidonet format that
was working out of luck...
it is because they are enforcing the internet email format
user@host.domain... they simply do not recognise the fidonet format that
was working out of luck...
I already tried to apply that "address patch" from jamnntpd to
smapinntpd. Somehow it seems not to work.
From David Drummond To Tommi Koivula
Your message appeared to have originated from "test" instead of a FTN address in this version of TB (31.8 on Win7).
On 17.11.2018 11:35, 3640/305 wrote:
From David Drummond To Tommi Koivula
Your message appeared to have originated from "test" instead of a FTN
address in this version of TB (31.8 on Win7).
Yes. I found out that if there is something in REPLYADDR, Thunderbird shows the from line ok.
In this message there should be "123" as my email address.
Now using TB v60.
Ooh... mmmm...
(Note that I have quoted your 'quote' line to David. Your 'From' line also read "Tommi Koivula -> David Drummond<123>".)
Are you using a JAM messagebase?
It's just it's hard to tell since
you're using SMAPI. Johan specifically states that any REPLYADDR magic formatting works in conjunction with JAM messagebase.
Whenever I had a choice in any/every JamNNTPd configuration I've always turned the REPLYADDR option off (i.e. disabled).
Ooh... mmmm...
Indeed.. Now my email address is set to "2:221/360.9999" in this Thunderbird 60.3.1. :)
Ooh... mmmm...Indeed.. Now my email address is set to "2:221/360.9999" in this Thunderbird 60.3.1. :)
It's just it's hard to tell since you're using SMAPI. Johan
specifically states that anyREPLYADDR magic formatting works in
conjunction with JAM messagebase.
Hmm.. Ok..
From Paul Quinn To Tommi Koivula
Indeed.. Now my email address is set to "2:221/360.9999" in this
Thunderbird 60.3.1. :)
Yeah, but you do have a UUCP gateway at your back. :)
Johan also stated that SMAPI was an experiment. Look Ma, no hands!
@MSGID: 2:221/10.0 5befe218
@REPLY: 2:221/10.0 5befe10a
@PID: SmapiNNTPd/Linux/IPv6 1.3 20181115
@REPLYADDR "2:221/360.9999"
@CHRS: UTF-8 2
@TZUTC: 0200
@TID: hpt/lnx 1.9.0-cur 2018-09-09
Ooh... mmmm...
Indeed.. Now my email address is set to "2:221/360.9999" in this
Thunderbird 60.3.1. :)
And it shows fine:
"Tommi Koivula -> Paul Quinn <2:221/360.9999>"
Maybe a faked REPLYADDR should fix this... Hmm... :)
* Origin: *** smapinntpd/linux @ news://fidonet.fi *** (2:221/10.0)
Maybe a faked REPLYADDR should fix this... Hmm... :)
* Origin: *** smapinntpd/linux @ news://fidonet.fi *** (2:221/10.0)
That is sick. Do I need an account there too? ;-)
Replies from echomail newsgroup to netmail newsgroup doesn't work
right now.
Johan also stated that SMAPI was an experiment. Look Ma, noExperiment that works quite fine. :)
hands!
Maybe a faked REPLYADDR should fix this... Hmm... :)
That is sick. Do I need an account there too? ;-)
All the accounts from my Jamnntpd should work!
Maybe a faked REPLYADDR should fix this... Hmm... :)
That is sick. Do I need an account there too? ;-)
All the accounts from my Jamnntpd should work!
I was just foolin'. The order of the 'From' line data in the newsgroup
is illogical, though not your fault.
I was just foolin'. The order of the 'From' line data in the
newsgroup is illogical, though not your fault.
Well, you _are_ upsidedown... ;-)
Anyways, I'm still wondering why the latest Thunderbirds mess the
"from" line... It is not the " -> ", because "def_showto" can be set
"off".
it is because they are enforcing the internet email format
user@host.domain... they simply do not recognise the fidonet format
that was working out of luck...
I already tried to apply that "address patch" from jamnntpd to
smapinntpd. Somehow it seems not to work.
Your message appeared to have originated from "test" instead of a FTN
address in this version of TB (31.8 on Win7).
Yes. I found out that if there is something in REPLYADDR, Thunderbird shows the from line ok.
In this message there should be "123" as my email address.
Hi! Tommi,
On 17 Nov 18 13:18, you wrote to me:
I was just foolin'. The order of the 'From' line data in the
newsgroup is illogical, though not your fault.
Well, you _are_ upsidedown... ;-)
That's just one of our super powers.
Well, you _are_ upsidedown... ;-)
That's just one of our super powers.
We have super powers???
Or is it just you (and a royal we)?
it is because they are enforcing the internet email format
user@host.domain... they simply do not recognise the fidonet format
that was working out of luck...
I already tried to apply that "address patch" from jamnntpd to
smapinntpd. Somehow it seems not to work.
AIUI, the format must be a valid email address format...
i don't know and cannot check since i do not run jamnntpd any more...
it is because they are enforcing the internet email format
user@host.domain... they simply do not recognise the fidonet
format that was working out of luck...
I already tried to apply that "address patch" from jamnntpd to
smapinntpd. Somehow it seems not to work.
AIUI, the format must be a valid email address format...
That is not true.
REPLYADDR may contain anything, including a valid fidonet address, and
it shows ok in the new TB.
Like "From: "Tommi Koivula -> Paul Quinn" <"2:221/360.9999">"
i don't know and cannot check since i do not run jamnntpd any more...
Bad for you. B)
AIUI, the format must be a valid email address format...
That is not true.
i'm talking about on the t-bird side of the fence...
not really... my current solution doesn't crash/hang on me all the
time... TTBOMK, other various problems are completely eliminated as well... especially things like the problems that arise when purging and renumbering areas or even just having areas locked while maint or
tossing is being done ;)
* Origin: *** smapinntpd/linux @ news://fidonet.fi *** (2:221/10.0)I'm trying to compile smapinntpd for OS/2. Without any success, because of some
I'm trying to compile smapinntpd for OS/2. Without any success, because
of some strange errors around ld.exe.
Did you ever tried to compile smapinntpd for os/2?
Well... it works, not full configured, but the first test is successful. :-)Did you ever tried to compile smapinntpd for os/2?I tried but no success here either. :(
'TommiBye/2 Torsten
60.3.1 here, unless something messes up on it's way out of here it seems to be working fine.
--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101Thunderbird/31.4.0
--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60
Oh, and long time no see. ;)
Well... it works, not full configured, but the first test is successful. :-)192.168.0.55
19-Nov-18 23:38:56 SmapiNNTPd/2 1.1 is running on port 5000
19-Nov-18 23:38:56 Compiled Nov 19 2018 23:19:02
19-Nov-18 23:45:42 (192.168.0.55:50546) Connection established to
19-Nov-18 23:45:42 (192.168.0.55:50546) Failed to open JAM messagebase "e:\dbahn\msg\netmail\NETMAIL"
19-Nov-18 23:45:42 (192.168.0.55:50546) Connection closed
19-Nov-18 23:46:08 SmapiNNTPd/2 exited
Mine... NB>> --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101
Thunderbird/31.4.0Â NB>> --- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
Yours...
Same/similar base code, mostly. Does yours 'shoot around corners'
(quote from a 'Robin Hood' movie [not the one you're thinking of]) or
will it make my coffee? I am unexcited at the prospect of more code bloat when the one I have does my Fidonet NNTP and basic email.
A lot of water under the bridge, for sure. Much happenings behind the scenes here, with disasters & disappointments. I am unhappy with my
main node's plight with its tosser. I cannot find a decent replacement that's not attached to a BBS trying to be the Swiss Army Knife answer to
a question that nobody really thought to ask.
Such is life. I need chocolate...
Why so many disappointments? There's always the turn of cheek method
where you can just not look at this stuff for like 10 months like I just did. ;)
What plights are you having?
What are you looking for a decent replacement for, or what are you currently using?
What have you looked at so far? And what did you *not* like about them?
Such is life. I need chocolate...Seems to do the trick, albeit only temporarily. ;)
Well it started with the demise of my 25 year-old MS-DOS/Windows 98SE system due to an incompatible SVGA adapter driver after a VirtualBox (vBox) *update*, on my 32-bit Xubuntu (X'u) desktop. It works fine on
my 8 year-old Dell 64-bit X'u desktop but cannot run with the same 24/7@365 reliability that I require, due to its UPS battery being exhausted. It's too late to bring it back on-line now, and, considering its limited future IAC, it's really a lost cause.
FMail32/lnx, which requires a Windows 32-bit FMail configuration program. As you may know, FMail is stuck in middle-90s Fidonet DOS think. Its netmail packer/router logic sux megakilos and is limited in basic functionality, so I'm using CF-Route or Crashmail (still),
requiring that both of those configurations are updated in parallel with FMail's. The scripting solutions are a wonder of modern DOS-think.
I don't keep a diary. And we both don't really have the time to pick things apart. My operating requirements are a bit tight considering
that my current Fidonet vBox server is a 32-bit X'u 14.04 LTS, with 4Gb RAM in the cheapest HP 'junkbox' I could buy. Its OS needs updating by April next year, according to the warning I get when SSH-ing to it... or else. ;)
After exhaustive research (both in Fido or on the WWW) and/or thought experiments, I am currently playing with a limited Mystic BBS installation, sufficient to feed the current pseudo-hub cross-up/down echomail links. Trial(s) will begin next week. Frankly, I am unsure of its netmail routing capability or even of its co-operation with a
JamNNTPd configuration (/NB/ I know it has its own _but_ do you know if JamNNTPd could work with it?).
In brief, I have discounted: other DOS vBox arrangements; HPT (based on indirect advice from Tommi); various Windows vBox arrangements; an MBSE config trashed; a theoretical Syncronet/lnx config; or, even an (unknown-capability) hack of SBBSecho (I did make a nice PDF of its Wiki entry too... it looks vaguely familiar and beaut). Plus a -lot- of variations.
Do you even have to incorporate your video card into Vbox? I thought you could use their built in drivers..
Bummer. I was hoping Wilfred would have gotten to that by now, but I can see the motivation level has to be pretty high these days to ditch real life and work on software for this hobby. However when it does happen I don't mind testing it. ;)
About a year ago I picked up a dedicated HP proliant server machine specifically for this stuff. Once everything was setup and the quirks;)
were taken care of, I hadn't had to touch it for months. I'm beginning
to wonder if that's the reason I got bored and found other things to do.
I believe James had worked out any indifferences in Mystic's JAM message base implementation. That being said, it works with Golded wonderfully,
so I don't see why it wouldn't be able to share it's messsage base with JAMNNTPd either. Obviously some settings in Mystic would need to be done like making sure you don't pack or renumber the message bases, but other than that should be good to go.
I've used HPT for quite awhile now, and honestly can't think of any
major issues besides my own misconfigurations or forgetfulness (for example, adding a route line when a new link is connected, simple things like that) I've ever had with it.
For the guest Windows system. The stock Win98se driver would only give 640x480 resolution, maximum. On my two Win98se systems, each was using
a different SVGA driver providing 1024x768. Much, much better (I have screen capture videos showing such).
The wildcat 'beta' type on the Fido vBox got rejected in a recent vBox update, and turned into a roiling blackhole from which nothing
radiated... not even light. The other didn't have trouble and still
runs great, but I found through early experimentation that it neither
will run DOS programs in a window nor full-screen.
Yes. Tell me about your gaming. Are you doing any ARMA 3? (I'm seriously following the ShackTac boys.) And, am liking the Star Citizen stuff (especially the 'Con' demo vids).
Yes, I'm looking forward to being able to have another server for Björn to advertise. That's something else that FMail failed at.
I had some bad luck with the Husky stuff in its _early_ days and I've developed a cringe attitude to HPT. I eventually got the nodelist and diff-handling working but had real strife with its TIC & echomail but
even then it required that I invest in some DOS voodoo to settle the beast. :)
So with this being said, are you referring to Win98se's display *before* VBox is even involved? If so, then it's probably not an issue with VBox itself. Otherwise, If it only happens in VBox, you can probably try to
use the built in default drivers in VBox settings.
runs great, but I found through early experimentation that it neither
will run DOS programs in a window nor full-screen.
VBox or Win98se?
I thought the whole point of this was *not* to use a "swiss army knife" BBS software? I mean whatever works for you of course, and I know you've used Mystic for quite some time, so obviously the comfort level is there for you.
All the software is there, you just have to write batch files or scripts to use them in a way that works for you obviously. Not sure how much DOS voodoo you would need, as I thought all, or most of your VMs were Linux based?
Is there some kind of issue stopping you from using a newer version
of Windows? Or even scrapping Windows altogether and using a Linux
GUI to host your Vbox sessions? That said, using a Linux GUI to host
may even allow for no need for Vbox at all..?
Me personally? No. I don't use anything 20+ years old here as I have no need for it. All of my hardware is much newer than that, and can handle just about anything I throw at it. I use the free version of VMWare ESXi on my server machine, which runs 3-4 Archlinux 64-bit instances that powers all of my BBS/FTN operations, as well as a media center.
Sounds like you have still have some hair pulling operations needing
some sorting out over there. ;)
Crashmail II I guess, but I believe you've already tried that. HPT is obviously the main choice up to now.
Sounds like there may be an option in the (whoknowswhen) future as far
as D'Bridge goes. But that may end up somewhere in the same realm as
FMail as far as stuck DOS related things going on there. But who knows,
I would be inclinded to give it a test-go.
I run a separate Mystic system here not available to the public for testing purposes as well. I have for quite some time. Quite a bit of the early FTN/BinkP integration was by my request and whatever assistance I could give in testing.
Yes. Actually I don't 'do' Windows any longer. Both my hosts have Xubuntu OSs, currently running four vBox PCs: one private node (Linux), for network testing and nodelist-sandboxing; one non-Fido Win98se
server, running (now-unused) proxies, intranet http server and pop3/smtp servers; the Mystic (Linux) test system; and, my other favourite Linux (below...).
These things just serve me now, where the LAN used to support a family
of four. (I'm scaling back - an astonishing thought...) The old Dell, recently recovered, relocated & re-built, used to host 5x vBox tasks but is only doing one now. It's hosting my very first Linux PC (from 2005) now as a vBox!, still running LAN services (e.g. DLNA media server for
my MP3 & photos collection). It's multi-talented too, and has a Fido test system also installed.
CM II still runs here on one node 24/7 & this point. It has been my experience that with both the distribution Linux binaries and locally-compiled versions of the sources for version 0.71 will strip SEENBYs
and mangle PATHs on echomail flowing through a non-leaf node.
Yes. Really? That was a passing thought of mine a decade ago, just about when Windows lost its shine for me. I didn't see much of a future for D'Bridge then but I'm sure it's a damned fine system still.
Ah, I thought so. You done good, except the BSO looks weird. But, if it works then I ain't gonna argue. ;-)
I see. I take it Win98se is the last license you bought for Windows? I could only imagine the insecurities and vulnerabilities they've fixed since then. ;)
my MP3 & photos collection). It's multi-talented too, and has a Fido
test system also installed.
From 2005 meaning never updated? Or have you been maintaining since then?
for D'Bridge then but I'm sure it's a damned fine system still.
As far as I can tell there's still quite a bit of work being done. At
this point I think it's just service packs for minor fixes until Nick
can do some major changes (ie: I guess v4.0 has a Linux flavor in the works).
What looks wierd about the BSO? Is it because it's 5D outbound directory naming whereas most of us are used to only 4D?
JAMNNTPd - There I mentioned it so we're still on topic. I don't know
what the strictness level is on this echo as far as that. If we need to move echos to keep the discussion going let me know.
At this point in time we should just be grateful someone is saying *something* somewhere. ;)
I want a _good_ Linux tosser that serves JAMNNTPd.
Simple.I want a _good_ Linux tosser that serves JAMNNTPd.
HPT, the best. :) There's also a perl script to create groups file.
>> I want a _good_ Linux tosser that serves JAMNNTPd.
TK> HPT, the best. :) There's also a perl script to create groups file. Simple.
Ah, I see where I went wrong. Back on the 19th you told Mark Lewis that "Sqpack from Husky renumbers automatically". Not knowing better I took
it to mean JAM areas. On reflection, that might mean Squish areas...true?
Disk space is not an issue nowadays.
The automatic renumbering seems to affect both jam and squish. So I
don't pack/purge until I find an utility which does not renumber. Disk space is not an issue nowadays.
TK> Disk space is not an issue nowadays.
True. Comment linking time however still is.
Thanks, mate. That's nice to know.
"hpt -q link -j" is very fast ("-j" links jam with crc). Still not an issue.
Thanks, mate. That's nice to know.Â
"hpt -q link -j" is very fast ("-j" links jam with crc). Still not an issue.
Even when the area exceeds 100k messages?
Anyway, I'm not ready for hpt. Crashmail II by Johan is still my forte.
Johan Billing's crashmaint (part of the crashmail II suite) does
NOT renumber the JAM areas -- only the .MSG areas.
I've used it for 14 years now without a single problem.
'crashmaint MAINT PACK' works like a charm every time. YMMV... 8-)
And the good news for smapinntpd users: "hptutil purge/pack" seems not
to renumber squish base. Jam yes. :(
Message count does not really matter, linking is done only for the just-tossed messages.
it chews SEENBYs and invents _new_ PATHs, even for traffic passingthrough.
I can't find a Linux Squish. If there was one, then I'd jump to be first in line to use it. I used to use it, even _with_ FastEcho, since FE didn't know how to maintain Squish areas.
it chews SEENBYs and invents _new_ PATHs, even for traffic
passing through.
CrashMaint does that? Strange...
the linux version but I found that it worked the same as I remember it working with Dos and OS/2.
I didn't use it extensively.. so beware.. ;)
Message count does not really matter, linking is done only for the
just-tossed messages.
???
In order to find the message linking to, surely the program must search the entire message base?
I guess I'm just trying to figure out why you seem to stick with
Win98se. I mean I know the usual reasons like comfort, used to it, ease
of use, etc. But is there something there that newer Windows OSes are lacking?
Never updated. They got it right the first time... well, it's
Puppy version 4.12 (Linux v2.5.x), and version 2.00 of the
particular edition (MacPuppy).
Yikes! Linux 2.5, you may even be able to setup that broken version of Irex for Linux on there. ;)
the 'default' zone. No real testing yet.
If I remember right, the default zone setting would obviously be your default Fidonet outbound directory for zone 3. However, every other zone should have their own directory (ie: if default zone is "fidonet", you should have fidonet.001, fidonet.002, and fidonet.004 if links for those zones are in your config and you've sent netmail to them). Then for any other network you setup it would have a different directory naming
scheme, not using the "fidonet" prefix, it would use the actual name of the network.
Dude. That's why I'm here. I want a _good_ Linux tosser that serves
JAMNNTPd. A fixed CM II 2.xx would be a wonderful winner.
Seems as though you've tried the limited options out there. Also seems
as though since CM II hasn't been touched in forever besides adding a couple text files and moving it to sourceforge or github, it may not
ever get fixed. ;(
2. Win98se needs only 128Mb RAM,
2. Win98se needs only 128Mb RAM,
Only?
TinyXP Rev10
- Hard Disk Space Used = 833Mb
- RAM Usage = 60.3Mb
- Services Started = 20
2. Win98se needs only 128Mb RAM,
Only?
1. An overriding RAM restriction: 4Gb per host. 2. Win98se needs only 128Mb RAM, and the older Puppy systems only need 256-512Mb/per. 3. No income, as all of my wealth is tied up in assets.
...outlook and scale...
version of Irex for Linux on there. ;)
Excuse me? I've never run iRex for anything. I confused you. Sorry.
Thanks for the information. Because of this, I have to take a look into the source code. I think, some very old husky smapi was used to compile.Did you ever tried to compile smapinntpd for os/2?I tried but no success here either. :(
'TommiBye/2 Torsten
It's beyond my pay grade too. Through a comedy of errors, I have only a single functioning Thunderbird and that's the one: version 31.4 on my netbook, since any later models fuck up in some way or another. Or, I haven't bothered to install one. If I do, it will be an older version.
Firstly, there is /nil/ support in vBox for anything Win9x. T'ain't no "Guest Additions" and no working OOTB Windows SVGA driver, so, the SVGA driver had been written by a third party to fill the gap. The vBox people say it is all exceedingly very bloody difficult and don't even recommend installing Win9x in vBox. Hence, no support.
OTOH, wouldn't you want to use a multi-tasking GUI OS that only uses
128Mb RAM (maybe just 64Mb but I didn't want to be overly stingy)? Especially if such can give renewed life to 20+ years-old accumulated utilities & custom scripts. :)
The alternate (vBox) SVGA driver-supported system. (Entirely different driver, BTW.) It's been running happily as a Win98se system for quite a few years, so long as I throw Windows *only* apps at it. Any attempted windowed/full-screen DOS sessions lock it up. It still runs so long as I'm careful.
There's another 32-bit Linux tosser? Where? What? Hunh? Pray tell, as I have not heard of one other than HPT.
Mystic fitted nicely into my hardware & software constraints. I am very pleased with it. I haven't been this happy for nearly a decade. Can't you tell from my smile? :)
I don't do DOS any more. Just simple procedural bash-ing.
Actually the last is my wife's XP SP2. (I don't use it any longer.) It used to run on her Ubuntu PC as a vBox but she only ever saw XP full-screen. Same difference though WRT updates.
Never updated. They got it right the first time... well, it's Puppy version 4.12 (Linux v2.5.x), and version 2.00 of the particular edition (MacPuppy).
I recall Nick saying that won't happen. Maybe I'm wrong... probably I'm wrong. Nearly exactly three years back he said he was working on v4.xx for a "multitude of OS platforms". I thought he said since that he's somewhat disappointed that he couldn't.
Ermm... mine seems to want to use a single outbound for -all- of
Fidonet, regardless of zone. Early days, as it might only have created the 'default' zone. No real testing yet.
Dude. That's why I'm here. I want a _good_ Linux tosser that serves JAMNNTPd. A fixed CM II 2.xx would be a wonderful winner.
Sysop: | DaiTengu |
---|---|
Location: | Appleton, WI |
Users: | 766 |
Nodes: | 10 (1 / 9) |
Uptime: | 03:17:01 |
Calls: | 10,581 |
Calls today: | 1 |
Files: | 185,898 |
Messages: | 1,676,701 |
Posted today: | 1 |