Hello All!

This is going out via APoint.

Regards,
August

--- APoint 1.25
* Origin: (2:221/1.58)

On 2019 Apr 13 18:55:40, you wrote to All:

@MSGID: 2:221/1.58 5cb230ad
@PID: APoint 1.25
@CHRS: LATIN-1 2
Hello All!

This is going out via APoint.

Regards,
August

--- APoint 1.25
* Origin: (2:221/1.58)
SEEN-BY: 57/0 153/135 250 757 6809 267/67 800 280/464 290/10 317/2 393/68 SEEN-BY: 770/0 1 10 100 330 340 772/0 1 500 3634/12 116/116 123/25 50 120 150
SEEN-BY: 123/755 135/300 153/7715 261/38 3634/15 24 27 50 0 18/0 123/0 1/120
@PATH: 221/1 280/464 770/1 153/250 757 3634/12

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... He was, until he died, more than a mere mortal.
---
* Origin: (1:3634/12.73)

Hello August!

On 13.04.19 at 18:55, August Abolins wrote to All:

Hello All!

This is going out via APoint.

Regards,
August

-+- APoint 1.25
+ Origin: (2:221/1.58)

Ack!

Regards,
Martin

--- OpenXP 5.0.38
* Origin: Marmite-on-Toast (2:240/2188.31)

On 14/04/2019 4:15 a.m., Martin Foster : August Abolins wrote:

 AA> This is going out via APoint.
 AA> -+- APoint 1.25
 AA>  + Origin:  (2:221/1.58)

Ack!

Another lil' thing I noticed with Apoint.. it does not seem to toss packets for an area that is *not* yet created in the program. :(

In other words, it won't auto-create the area.

Further, when that happens, and there *are* inbound messages for an existing area, the whole packet is ignored.

How goes it for you, Martin?

I've disabled auto-deleting the packets. I copy them over for OpenXP, but I can't seem to re-use them there.


.../|ug

--- Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.
* Origin: - nntp://rbb.fidonet.fi - Lake Ylo - Finland - (2:221/360)

Hello August!

On 14.04.19 at 20:15, August Abolins wrote to Martin Foster:

Another lil' thing I noticed with Apoint.. it does not seem to
toss packets for an area that is *not* yet created in the
program. :(

"Configuration -> Options"
On the "Misc" Tab, have you enabled "New areas: Always create".

In other words, it won't auto-create the area.

It does here with the above setting enabled.

Further, when that happens, and there *are* inbound messages for
an existing area, the whole packet is ignored.

How goes it for you, Martin?

Can't reproduce the problem(yet), sorry.

I've disabled auto-deleting the packets.

I've looked and looked and looked but I can't find that setting, where
is it?

I copy them over for OpenXP, but I can't seem to re-use them
there.

In what way can't you re-use them?

Regards,
Martin

--- OpenXP 5.0.38
* Origin: Bitz-Box - Bradford - UK (2:240/2188.31)

Hello August!

On 14.04.19 at 20:15, August Abolins wrote to Martin Foster:

[snip]

How goes it for you, Martin?

Just found a bit of time to do some more experimenting, so I decided to
plug in an external editor(Notepad++). Either I don't understand how this feature is supposed to work or it's broken because when I went to reply to
a message, the internal editor fired up :-/

Regards,
Martin

--- OpenXP 5.0.38
* Origin: Bitz-Box - Braford - UK (2:310/31.3)

Hello Martin!

** 15.04.19 - 13:43, Martin Foster wrote to August Abolins:

On 14.04.19 at 20:15, August Abolins wrote to Martin Foster:

Another lil' thing I noticed with Apoint.. it does not seem to
toss packets for an area that is *not* yet created in the
program. :(

"Configuration -> Options"
On the "Misc" Tab, have you enabled "New areas: Always create".

Oh yes.. I have that set for that. MEANWHILE, I learned that the problem
is that Apoint does not automatically toss (as you had discovered too!)

But when I relaunched Apoint at a later time, the message area would magically populate.

If I don't want to exit the program, the fix is to force a toss with one
of the controls in the top menu.

I've disabled auto-deleting the packets.

I've looked and looked and looked but I can't find that setting, where
is it?

OK, I *thought* I did that, because I noticed there were untossed packets
in the inbound. Turns out that this was because Apoint does not automatically toss anyway. Now after repeated use, there are no more
packets retained. I'm not sure *what* setting made me think I was able
to save packets - sorry.

I copy them over for OpenXP, but I can't seem to re-use them
there.

In what way can't you re-use them?

I would just copy the .pkt files over to the oxp inbound dir and let oxp
toss them. But that didn't seem to work.


../|ug

---
* Origin: /|ug's Point, ONT, CANADA (2:221/1.58)

Hello Martin!

** 15.04.19 - 21:36, Martin Foster wrote to August Abolins:

Just found a bit of time to do some more experimenting, so I decided to plug in an external editor(Notepad++). Either I don't understand how this feature is supposed to work or it's broken because when I went to reply to a message, the internal editor fired up :-/

Me too. Apoint won't launch the external editor (plain ol' notepad.exe in
my case) either. I tried adding the usual %1 arg, but that didn't make
any difference.

That's not too a bit a deal for me. Internal editor is not too bad. I
like having the ability to change the subject or address or names on the
fly. The dictionary option looks good, but I don't know how to make that work. Meanwile I like the t-bird/nntp solution which looks up spelling misteaks very nicely.


../|ug

---
* Origin: /|ug's Point, ONT, CANADA (2:221/1.58)

Hello August!

On 16.04.19 at 19:18:00, August Abolins wrote to Martin Foster:

[snip]

I copy them over for OpenXP, but I can't seem to re-use them there.

In what way can't you re-use them?

I would just copy the .pkt files over to the oxp inbound dir and let oxp toss them. But that didn't seem to work.

That's because you don't do it like that ;)

On the Main Menu, select "OpenXP" -> "Import" -> "Read other format" and then navigate your way to the packet you wish to import. Hitting <Enter> over the packet will initiate the import process. If you need to import more than one packet, you'll need to repeat the procedure for each one. Incidentally, the packets you wish to import can be in *any* directory *and* OpenXP doesn't care where they originated from.

Regards,
Martin

--- WinPoint Beta 5 (359.1)
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello August!

On 16.04.19 at 19:34:00, August Abolins wrote to Martin Foster:

Just found a bit of time to do some more experimenting, so I decided to
plug in an external editor(Notepad++). Either I don't understand how
this feature is supposed to work or it's broken because when I went to
reply to a message, the internal editor fired up :-/

Me too. Apoint won't launch the external editor (plain ol' notepad.exe
in my case) either. I tried adding the usual %1 arg, but that didn't make any difference.

Looks like it's broken, then.

[snip]

The dictionary option looks good, but I don't know how to make that work.

Neither do I because I can't even find it ??

Regards,
Martin

--- WinPoint Beta 5 (359.1)
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

** 17.04.19 - 13:23, Martin Foster wrote to August Abolins:

The dictionary option looks good, but I don't know how to make that work.

Neither do I because I can't even find it ??

See Apoint.cfg:

[editor]
wordwrap=YES
styles=YES
colornormal=0

[snip] 8<

fontname=Arial
fontheight=-18
dictionary= <----- HERE

[snip] 8<

edtextfileheight=0
edtextfilefontname=
[end]


..and I'd swear I saw a setting for it somewhere in the user menus, but I can't find it anymore either! LOL


../|ug

---
* Origin: /|ug's Point, ONT, CANADA (2:221/1.58)

Hello Martin!

** 17.04.19 - 11:59, Martin Foster wrote to August Abolins:

I would just copy the .pkt files over to the oxp inbound dir and let oxp AA>> toss them. But that didn't seem to work.

That's because you don't do it like that ;)

On the Main Menu, select "OpenXP" -> "Import" -> "Read other format" and then navigate your way to the packet you wish to import. Hitting <Enter> over the packet will initiate the import process. If you need to import more than one packet, you'll need to repeat the procedure for each one. Incidentally, the packets you wish to import can be in *any* directory *and* OpenXP doesn't care where they originated from.

Thanks for that. It may prove to be handy a some time.




../|ug

---
* Origin: /|ug's Point, ONT, CANADA (2:221/1.58)

Hello August!

On 17.04.19 at 21:04, August Abolins wrote to Martin Foster:

I would just copy the .pkt files over to the oxp inbound dir and let
oxp toss them. But that didn't seem to work.

That's because you don't do it like that ;)

On the Main Menu, select "OpenXP" -> "Import" -> "Read other format" and
then navigate your way to the packet you wish to import. Hitting <Enter>
over the packet will initiate the import process. If you need to import
more than one packet, you'll need to repeat the procedure for each one.
Incidentally, the packets you wish to import can be in *any* directory
*and* OpenXP doesn't care where they originated from.

Thanks for that. It may prove to be handy a some time.

OpenXP also has the capabilty to export messages to a mail packet :)

Regards,
Martin

--- OpenXP 5.0.38
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello August!

On 17.04.19 at 18:42, August Abolins wrote to Martin Foster:

The dictionary option looks good, but I don't know how to make that
work.

Neither do I because I can't even find it ??

See Apoint.cfg:

[editor]
wordwrap=YES
styles=YES
colornormal=0

[snip] 8<

fontname=Arial
fontheight=-18
dictionary= <----- HERE

[snip] 8<

edtextfileheight=0
edtextfilefontname=
[end]

Ah yes, never thought of looking there, thanks for the pointer. Is
there anything about this in the help file?

Regards,
Martin

--- OpenXP 5.0.38
* Origin: Bitz-Box - Bradford - UK (2:310/31.3)

Hello Martin!

** 17.04.19 - 11:59, Martin Foster wrote to August Abolins:

On the Main Menu, select "OpenXP" -> "Import" -> "Read other format" and then navigate your way to the packet you wish to import. Hitting <Enter> over the packet will initiate the import process. If you need to import more than one packet, you'll need to repeat the procedure for each one. Incidentally, the packets you wish to import can be in *any* directory *and* OpenXP doesn't care where they originated from.

Very cool. Just tried it with a bunch of packets that have arrived at my "other" point address and get them into oxp.



../|ug

---
* Origin: /|ug's Point, ONT, CANADA (2:221/1.58)

Hello August!

On 16/04/2019 at 19:34:00, August Abolins wrote to Martin Foster:

Just found a bit of time to do some more experimenting, so I
decided to plug in an external editor(Notepad++). Either I don't
understand how this feature is supposed to work or it's broken
because when I went to reply to a message, the internal editor
fired up :-/

Me too. Apoint won't launch the external editor (plain ol'
notepad.exe in my case) either. I tried adding the usual %1 arg,
but that didn't make any difference.

Just found time to have another look at this and it turned out that I didn't understand how it's supposed to work :-/

In the message reader, click the "Reply(to sender)" button, which loads the message into the internal editor. Then, click "Edit" in the menubar and then click "Open in external editor" and ..... Bingo! :-)

Regards,
Martin

--- APoint 1.25
* Origin: Bitz-Box - Bradford - UK (2:250/1.1)