Hello Maurice,

On 13 Nov 16 16:32, Maurice Kinal wrote to Nicholas Boel:

 NB>> I hadn't realized you could switch it up on the fly.

 MK> Yep.  I used to have another path not too long ago.  I am beginning to
 MK> wonder if it was a bad idea to switch it off now.  :-/

If you insist on using type 2.2 packets, then is may very well have been.

 NB>> Was 2.2 packets ever fully adopted?

 NB>> Seems like quite a few softwares don't support it.

 MK> It was working with yours.  Beats me why it now doesn't as I am doing
 MK> it exactly the same.  I did notice that you started zipping msgs
 MK> destined for me around the same time it broke.  Is that the cause?  I
 MK> don't do zip nor support it in any way shape or form.

I've recently switched from using my BBS as a mail hub, to running a separate
mail hub using hpt as the tosser. While my BBS software did indeed support 2.2
packets, it doesn't look like hpt does.

Also, I've changed your config to compression type: none.

There were some small settings I may have missed in the move (like that one).
:)

 MK> Anyhow I see there are missing messages that didn't make it through
 MK> the loop and I am unsure if there is anything I can do about it at
 MK> this end other than to pay myself off with the 15 year old scotch.  I
 MK> am willing to try again with the route through you but don't know what
 MK> your node now expects from mine.

They were stopped here, most likely because they were type 2.2 packets. At the
moment my node is expecting type 2+ packets. If I can find something in the
documentation that states I can change that, I will most definitely let you
know.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20160827