It has been brought to my attention by my new fidonet hub, that the via
line that is added by magimail is missing the @domain, like so x:xxx:xxxx@fidonet

Is that a thing you can configure in magimail.prefs? I have not found
anything about that.

Best Regards,
Mindsurfer

--- MagickaBBS v0.15alpha (Linux/armv7l)
* Origin: FuNToPia | telnet://funtopia.ddnss.eu:2023 (21:3/119)

It has been brought to my attention by my new fidonet hub, that the
via line that is added by magimail is missing the @domain, like so x:xxx:xxxx@fidonet

Is that a thing you can configure in magimail.prefs? I have not
found anything about that.

Ok, i took some time to look up the fidonet standard about via lines
Its obviously not correct to demand the FTN address to have @domain
attached to it, As it is defined as optional in FTS-4009.
See 3. Example of valid usage are http://ftsc.org/docs/fts-4009.001

Regards,
Mindsurfer

--- MagickaBBS v0.15alpha (Linux/armv7l)
* Origin: FuNToPia | telnet://funtopia.ddnss.eu:2023 (21:3/119)

Mindsurfer wrote to Mindsurfer <=-

Ok, i took some time to look up the fidonet standard about via lines
Its obviously not correct to demand the FTN address to have @domain attached to it, As it is defined as optional in FTS-4009.
See 3. Example of valid usage are http://ftsc.org/docs/fts-4009.001

Who is your fidonet hub and have you pointed this out to him/her? I would suspect that there are several, older tossers being used in various parts
of the network which don't have the domain attached.

Mike @ 1:2320/105


... Keep your stick on the ice
--- MultiMail
* Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)

Who is your fidonet hub and have you pointed this out to him/her? I
would suspect that there are several, older tossers being used in
various parts of the network which don't have the domain attached.

well, i guess in the long run i have to do as i am told since i am new and a node only and he is an experienced and long-serving RC and surely knows what
he is talking about. I just thought the ftsc standards are what matters. Its maybe a good thing to have that @domain added to the Kludge. I dont know and
i dont want any bad blood at all. But it feels a little strange when you can find in the ftsc files that the domain is defined as optional and your RC
says it is not. Yes there has been a particular proposal in 2003 changing Kludge in regards of domain and more. But as far as i know it has not been accepted. I am currently trying to get
husky hpt up and running.(hpt was recommended) To bad that i have everything done and working with Magimail/Crashmail2 already. I hope i can make hpt run together with MagickaBBS and everyone is happy again. It should be possible.

Regards,
Mindsurfer

PS: who knows if hpt can have a netmail area per network?

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
* Origin: BlackICE BBS (BlackICE.BBSindex.com:23) (21:1/106)

Hello Mindsurfer,

PS: who knows if hpt can have a netmail area per network?

I ran husky with magicka before and it worked well. I had a problem with netmail to filefix when I had a different netmail area per net. I think that can be solved with the CC funtions.

I also ran MagiMail and found it to be a great tosser.

I don't know what tosser your RC is using but I have never heard this "your @via line must contain @domain" before and am sorry for your troubles.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

I don't know what tosser your RC is using but I have never heard this "you

r @via line must contain @domain" before and am sorry for your troubles.

Sounds like a good reason to stay away from fidonet.

I'm sure if you said you were using crashmail, this never would have come
up...

So now you have to use HPT, which works ok, but it's less than ideal (HPT
is buggy with JAM - but I have added some work arounds). Crashmail is
also buggy as, but I think I fixed most of them in magimail.

But this is what you get for developing BBS software in 2020.

I say just stay away from fidonet...

Andrew


--- TitanFTN (Linux/x86_64)
* Origin: Wunderlust BBS - wunderlust.ddns.net:2023 (21:1/126)

Hello apam,

I don't know what tosser your RC is using but I have never heard
this "your @via line must contain @domain" before and am sorry for
your troubles.

Sounds like a good reason to stay away from fidonet.

I've had a few stinky encounters in fidoland but the majority of my encounters have been good and positive.

I'm sure if you said you were using crashmail, this never would have
come up...

I would use my tosser of choice and if it doesn't work with a particular link I would link elsewhere if that's the way it needed to be.

So now you have to use HPT, which works ok, but it's less than ideal
(HPT is buggy with JAM - but I have added some work arounds).
Crashmail is also buggy as, but I think I fixed most of them in
magimail.

Yep, I had not a single problem with magimail.

But this is what you get for developing BBS software in 2020.

Don't let them get you down.

I say just stay away from fidonet...

That idea has occurred to me from time to time.. but I can't. :)

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

I'm sure if you said you were using crashmail, this never would
have come up...

sure, he first saw the name Magimail in the Kludge, but i told him that
this basicly is a crashmail2 fork after that.

So now you have to use HPT, which works ok, but it's less than
ideal (HPT is buggy with JAM - but I have added some work arounds).

hmm,. great

Mindsurfer

--- MagickaBBS v0.15alpha (Linux/armv7l)
* Origin: FuNToPia | telnet://funtopia.ddnss.eu:2023 (21:3/119)

hmm,. great

Don't worry, HPT will work. Al had it running, I can't exactly remember
what the bug was, I think it was something to do with origin addresses,
and HPT doesn't fill it in in the JAM message base. It was reported,
maybe they've fixed it?

Anyway, I added a work around that if it doesn't exist in the JAM
headers, it will pull it out of the origin line. If that fails due to
someone not using an origin line or invalid origin line or whatever, it's
not a deal breaker, it just means you won't know the origin of the
message.

sure, he first saw the name Magimail in the Kludge, but i told him that this basicly is a crashmail2 fork after that.

Yeah, i figured as much.

HPT will work, and in HPT you can split up your config file into multiple files. You won't be able to process any filefix requests with it though,
but I imagine it's a non-issue if you're not hosting any areas.

Andrew


--- TitanFTN (Linux/x86_64)
* Origin: Wunderlust BBS - wunderlust.ddns.net:2023 (21:1/126)

I've had a few stinky encounters in fidoland but the majority of my encoun

ters have been good and positive.

I haven't really had any, I joined up a year or so ago. The uplink I had
was nice enough, but any areas I was interested in had zero traffic,
other areas were disgusting, though I've heard the cooking echo is ok
(though I'm not really interested in cooking).

Perhaps there are more interesting things in other languages.

Don't let them get you down.

Yeah.

Andrew


--- TitanFTN (Linux/x86_64)
* Origin: Wunderlust BBS - wunderlust.ddns.net:2023 (21:1/126)

base. It was reported, maybe they've fixed it?

seems the husky project moved over to github this year. at least if i understand that right. the main project page is still on sourceforge.
but i dont know if there is an active bugfixing or even development going
on currently.
i git clone'd all tools around hpt from github and compiled it on my
raspberry pi. As Al mentioned, i want to have one netmail area only with
husky and
clone to other ones that i have in MagickaBBS from there. htick, another
husky tool, is taking care about tossing files and areafix. nltools seems
to read in nodelists.

Anyway, I added a work around that if it doesn't exist in the JAM
headers, it will pull it out of the origin line. If that fails due
to someone not using an origin line or invalid origin line or
whatever, it's not a deal breaker, it just means you won't know the
origin of the message.

Ok, thanks for that.

HPT will work, and in HPT you can split up your config file into
multiple files. You won't be able to process any filefix requests
with it though, but I imagine it's a non-issue if you're not
hosting any areas.

As said, there are some more husky tools beside hpt that should take care
of
that. i could still use the file tosser that comes with MagickaBBS, but i
think its better to switch that to husky too.

Magimail did do both, Echo and Netmail on Scan. With hpt that are two
different
commands. one is 'scan', one is 'pack'. i will just call both successive
when mail.out is touched.

And if i did not say it yet, thanks for all the work you have put into MagickaBBS, Magimail and everything connected to BBSs!

Regards,
Stephan

PS: the MagickaBBS Message Editor still needs some love i guess. when you
write
into a line that is filled up to the end already and it moves the part of
the text to the next line, that can mix up things badly sometimes.


--- MagickaBBS v0.15alpha (Linux/armv7l)
* Origin: FuNToPia | telnet://funtopia.ddnss.eu:2023 (21:3/119)

PS: the MagickaBBS Message Editor still needs some love i guess. when you write
into a line that is filled up to the end already and it moves the part of the text to the next line, that can mix up things badly sometimes.

Yeah, I think I really need to start over with the editor.

At present it mostly works, so I've put it off.

Andrew


--- TitanFTN (Linux/x86_64)
* Origin: Wunderlust BBS - wunderlust.ddns.net:2023 (21:1/126)

Mindsurfer wrote to Blue White <=-

well, i guess in the long run i have to do as i am told since i am new
and a node only and he is an experienced and long-serving RC and surely knows what he is talking about. I just thought the ftsc standards are

Just switch HUBS. I'll give you a feed if you want one.

what matters. Its maybe a good thing to have that @domain added to the Kludge. I dont know and i dont want any bad blood at all. But it feels
a little strange when you can find in the ftsc files that the domain is defined as optional and your RC says it is not. Yes there has been a

I can't support it here my tosser is 25+ years old.

Shawn

... Oh no! I forgot which friends I told the truth to!

--- EzyBlueWave V3.00 01FB001F
* Origin: Tiny's BBS - telnet://tinysbbs.com:3023 (21:1/130)

apam wrote to Al <=-

But this is what you get for developing BBS software in 2020.

This is why people like you burn out. Idiots who demand stupid kludges
that no one uses.

I say just stay away from fidonet...

It's very toxic. Just use a different HUB, talk to Nick Andre he's a greatguy
and doesn't give a single fart about the dim wits.

Shawn

... Advertising is legalized lying.

--- EzyBlueWave V3.00 01FB001F
* Origin: Tiny's BBS - telnet://tinysbbs.com:3023 (21:1/130)

Hello Mindsurfer,

seems the husky project moved over to github this year. at least if i understand that right. the main project page is still on sourceforge.
but i dont know if there is an active bugfixing or even development
going on currently.

I'm not sure there is development going on but they do maintain husky. The version I run is from early 2020, only a small fix for txt2pkt from earlier versions but they do have eyes on it and could go into development mode if they wanted or needed to.

I'm not sure if these Jam problems have been looked at or not but if we brought it up we could find out if they can or will be solved.

i git clone'd all tools around hpt from github and compiled it on my raspberry pi.

Yes, I have done this too but I usually wait for a new release being available at download.huskyproject.org.

As Al mentioned, i want to have one netmail area only with husky and
clone to other ones that i have in MagickaBBS from there. htick,
another husky tool, is taking care about tossing files and areafix. nltools seems to read in nodelists.

I don't mind a netmail area per net but I prefer a single netmail area but it would require the untangling of AKA matching. Apam may get to that, I'm not sure.

It would solve a problem I had with filefix but I think there are other solutions for that also that could be explored.

As said, there are some more husky tools beside hpt that should take
care of that. i could still use the file tosser that comes with MagickaBBS, but i think its better to switch that to husky too.

I had a MagickaBBS running in a linode. It was a great setup but it's gone away for the time being for lack of funds.

I was talking to Apam about all that and I think with input from sysops running those tools, in time it could all be made to work. The development of these things does take time though.

Magimail did do both, Echo and Netmail on Scan. With hpt that are two different commands. one is 'scan', one is 'pack'. i will just call
both successive when mail.out is touched.

hpt will toss both echomail and netmail when you toss if netmail areas are listed in your export.log or echotoss.log (not sure which now) if you configure it so but I always scan and pack.

And if i did not say it yet, thanks for all the work you have put into MagickaBBS, Magimail and everything connected to BBSs!

I concure, absolutely, thank you Apam. :)

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Hello Mindsurfer,

hpt will toss both echomail and netmail when you toss if netmail areas
are listed in your export.log or echotoss.log (not sure which now) if
you configure it so but I always scan and pack.

I said toss but I meant scan.. ;) hpt will scan out netmail also if listed/configured so.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 14 Aug 2020, apam said the following...

I've had a few stinky encounters in fidoland but the majority of my encounters have been good and positive.

I haven't really had any, I joined up a year or so ago. The uplink I had was nice enough, but any areas I was interested in had zero traffic,
other areas were disgusting, though I've heard the cooking echo is ok (though I'm not really interested in cooking).

Fidonet is not what it once was to be sure, but I still do my best in support of it. The cooking echo is always in the top 10 as far as traffic goes but I also can't participate. I can eat but I am no cook.

Perhaps there are more interesting things in other languages.

Yes, there are many russian echoes that I can't read and I suspect are doing quite well. Z4 also had a lot of Spanish (I think) areas but being an english only speaker/writter I don't know what goes on there.

Don't let them get you down.

Yeah.

Really, truly.

Ttyl :-),
Al

--- Mystic BBS v1.12 A46 2020/08/11 (Linux/64)
* Origin: Equinox BBS - Penticton, BC Canada (21:4/106.2)

Al wrote to apam <=-

Fidonet is not what it once was to be sure, but I still do my best in support of it. The cooking echo is always in the top 10 as far as
traffic goes but I also can't participate. I can eat but I am no cook.

They are a great bunch in that echo. You can post reviews of places you've
eaten you know? The rules are very slack.

Shawn

... 90% of the time I'm right, so why worry about the 3%?

--- EzyBlueWave V3.00 01FB001F
* Origin: Tiny's BBS - telnet://tinysbbs.com:3023 (21:1/130)

apam wrote to Al <=-

I haven't really had any, I joined up a year or so ago. The uplink I
had was nice enough, but any areas I was interested in had zero
traffic, other areas were disgusting, though I've heard the cooking
echo is ok (though I'm not really interested in cooking).

Cooking, Memories, Coffee_Klatsch are OK and can be pretty active
(especially Cooking). The sysop echos are often all interlaced with
politics (both FIDO and "political" politics) and I don't read any of those.




... Keep your stick on the ice
--- MultiMail
* Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)

Mindsurfer wrote to Blue White <=-

trying to get husky hpt up and running.(hpt was recommended) To bad
that i have everything done and working with Magimail/Crashmail2
already. I hope i can make hpt run together with MagickaBBS and
everyone is happy again. It should be possible.

Well, Magimail/Crashmail are both open source, so it would be possible for someone who can program in whatever language they are in to make them 5D compliant.

That said, since it is not the standard I suspect your RC is mistaken.

You can always maintain that RC connection for netmail only (that is all
that is required in Fido), and use a different hub for echomail, as others
have suggested. Tiny has volunteered, someone volunteered Nick, and you
are also free to set up a connection with my hub system, if you like.

PS: who knows if hpt can have a netmail area per network?

I do not know.



... Direct from the Ministry of Silly Walks
--- MultiMail
* Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)

apam wrote (2020-08-14):

So now you have to use HPT, which works ok, but it's less than ideal (HPT is buggy with JAM - but I have added some work arounds). Crashmail is
also buggy as, but I think I fixed most of them in magimail.

Why don't you send patches / PRs to the crashmail project? ;) In FTN-land everything is forked over and over again until nobody knows which version to use ...

---
* Origin: (21:3/102)

Why don't you send patches / PRs to the crashmail project? ;) In FTN-land everything is forked over and over again until nobody knows which version to use ...

Because a lot of my changes are only useful to magicka users.

I don't know that every thing is forked over and over again? What things are you talking about?

Andrew


--- TitanFTN (Linux/x86_64)
* Origin: Wunderlust BBS - wunderlust.ddns.net:2023 (21:1/126)