After I requested a big rescan I seemed to receive no mail more.
Then I found .zip files but not with .zip extension in my inbound.
I unzipped them and then the .pkt files were tossed.
How can I convince Winpoint to unzip self again in the future?
After I requested a big rescan I seemed to receive no mail more. Then I
found .zip files but not with .zip extension in my inbound. I unzipped
them and then the .pkt files were tossed.
How can I convince Winpoint to unzip self again in the future?
Don't know where to configure that but if that is the problem I expect that tomorrow, a .th* day, the problem will be over. We'll see.
Don't know where to configure that but if that is the problem I expect
that tomorrow, a .th* day, the problem will be over. We'll see.
Hello Michiel,
on 15.04.26 at 16:25:20 You wrote in area WINPOINT to Chris Jacobs about "Winpoint unzipt ineens niet meer".
After I requested a big rescan I seemed to receive no mail more. Then I
found .zip files but not with .zip extension in my inbound. I unzipped
them and then the .pkt files were tossed.
How can I convince Winpoint to unzip self again in the future?
Don't know where to configure that but if that is the problem I expect that tomorrow, a .th* day, the problem will be over. We'll see.
Regards,Chris Jacobs
--- WinPoint 415.0
* Origin: Original WinPoint Origin! (2:280/5555.11)
Don't know where to configure that but if that is the problem I expect
that tomorrow, a .th* day, the problem will be over. We'll see.
And the problem is back.
Now I have two problems.
Don't know where to configure that but if that is the problem I expect
that tomorrow, a .th* day, the problem will be over. We'll see.
And the problem is back.
Now I have two problems.
On my Winpoint point I have no problem when receiving compressed bundles like *.su1 (today).
Under File -> Options -> Archivers -> pkzip -> properties, I have these:
PKZip
pkzip
Integrated UnZIP
Did you change any of those (default) options?
Carlos
--- WinPoint 415.0
* Origin: another cyberiada point (2:341/234.5)
And the problem is back.
Now I have two problems.
On my Winpoint point I have no problem when receiving compressed
bundles like *.su1 (today).
I also have no problems with packets like *.SU1 (weekday + digit)
The problem arises when i receive more than 10 times on a day.
And it is with packets like *.WEA (weekday + letter)
When I receive more than 10 times on a day.
On my Winpoint point I have no problem when receiving compressed bundles
like *.su1 (today).
I also have no problems with packets like *.SU1 (weekday + digit) The problem arises when i receive more than 10 times on a day. And it is with packets like *.WEA (weekday + letter) When I receive more than 10 times
on a day.
I also have no problems with packets like *.SU1 (weekday + digit) The
problem arises when i receive more than 10 times on a day. And it is
with packets like *.WEA (weekday + letter) When I receive more than 10
times on a day.
I also have no problems with packets like *.SU1 (weekday + digit)
The problem arises when i receive more than 10 times on a day.
And it is with packets like *.WEA (weekday + letter) When I
receive more than 10 times on a day.
Until this issue is solved, I suggest you switch to uncompressed PKTs.
On my Winpoint point I have no problem when receiving compressed
bundles like *.su1 (today).
Just checked with *.SUA. No, it doesn't process it unless you rename
to *.SU9 (for example).
I also have no problems with packets like *.SU1 (weekday + digit) The
problem arises when i receive more than 10 times on a day. And it is
with packets like *.WEA (weekday + letter) When I receive more than 10
times on a day.
Until this issue is solved, I suggest you switch to uncompressed PKTs.
Carlos
--- WinPoint 415.0
* Origin: Original WinPoint Origin (2:341/234.5)
Can I get an MN flag?
I also have no problems with packets like *.SU1 (weekday +
digit) The problem arises when i receive more than 10 times on a
day. And it is with packets like *.WEA (weekday + letter) When I
receive more than 10 times on a day.
That was when Winpoint suddently wanted to do maintenance again.
See Subject: Maintenance hangs
One solution is to not poll more than nine times a day. The better solution would be if Tim would update Winpoint to make it accept
[A-Z].
One solution is to not poll more than nine times a day. The
better solution would be if Tim would update Winpoint to make it
accept [A-Z].
Another solution might be that his bossnode sets this option to 'No'
in his Fmail config:
Extended bundle names
Use 0-9 and A-Z instead of only 0-9 for mail bundle name
extensions. Warning: Some programs do not recognize
bundle name extensions that do not end on a digit.
Yes, it is an option in Fmail. It is however a global setting. If I
set that to "no", it will affect all my links that use compression.
Oh c'mon... Using [0-Z] for bundle name extensions has been common practise for decades. If it turns out that Winpoint does indeed not support it, it should be fixed in the next update.
Don't know where to configure that but if that is the problem I
expect that tomorrow, a .th* day, the problem will be over.
We'll see.
Happy Thursday!
For now the problem is over.
Don't know where to configure that but if that is the problem I expect
that tomorrow, a .th* day, the problem will be over. We'll see.
Happy Thursday!
For now the problem is over.
Until this issue is solved, I suggest you switch to uncompressed
PKTs.
Uncompressed is my default setting voor nodes that I can crash.
For points I'd rather not use uncompressed packets because if they do
not poll ver often, it will clog my outbound with hundreds of unsent packets...
Yes, it is an option in Fmail. It is however a global setting. If I
set that to "no", it will affect all my links that use compression.
Oh c'mon... Using [0-Z] for bundle name extensions has been common practise for decades. If it turns out that Winpoint does indeed not support it, it should be fixed in the next update.
Uncompressed is my default setting voor nodes that I can crash.
Ok.
For points I'd rather not use uncompressed packets because if
they do not poll ver often, it will clog my outbound with
hundreds of unsent packets...
Another option would be setting a filebox...
Oh c'mon... Using [0-Z] for bundle name extensions has been
common practise for decades. If it turns out that Winpoint does
indeed not support it, it should be fixed in the next update.
I agree. Let's see if Tim reads us and fixes this issue.
In the meantime, if Chris polls so frequently I suppose that raw PKTs would be for him... but it's up to his boss, of course :-)
I agree. Let's see if Tim reads us and fixes this issue.
He must be busy writing FTSC documents, and/or setting up his 2:2/29 node...
Another option would be setting a filebox...
Or activate the option of not using Winpoint's internal tosser but something else instead. Like Fmail....
Another option would be setting a filebox...
Or activate the option of not using Winpoint's internal tosser
but something else instead. Like Fmail....
I think that the point of Winpoint is that it's a full point package
that doesn't require installing a tosser or anything else.
Anyway, AFAIK that would not be possible because it uses its own messagebase format.
Another option would be setting a filebox...
Or activate the option of not using Winpoint's internal tosser but
something else instead. Like Fmail....
I think that the point of Winpoint is that it's a full point package
that doesn't require installing a tosser or anything else.
Anyway, AFAIK that would not be possible because it uses its own
messagebase format.
Hello Michiel,
on 22.04.26 at 19:37:50 You wrote in area WINPOINT to Carlos Navarro
about "Winpoint unzipt ineens niet meer".
Another option would be setting a filebox...
Or activate the option of not using Winpoint's internal tosser but
something else instead. Like Fmail....
I think that the point of Winpoint is that it's a full point package
that doesn't require installing a tosser or anything else.
Anyway, AFAIK that would not be possible because it uses its own
messagebase format.
Grok says it is not possible.
Copilot says it is possible and made a .pdf describing what it thinks the settings should be. Copilot says the messagebase is JAM.
My important data are in OneDrive and in IMAP
If I blow up my system I can re�nstall Windows and download my data from there.
Regards,
Chris Jacobs
--- WinPoint 415.0
* Origin: https://drschrisjacobs.nl (2:280/5555.11)
I think that the point of Winpoint is that it's a full point
package that doesn't require installing a tosser or anything
else.
By now I know FMail is not an option.
I did not have FMail configured properly yet but run in a problem that
has nothing to do with FMail Calling external programs from Winpoint,
a 32 bit program, on a system with OneDrive is unreliable.
I made a simple oneline .bat program:
echo External Programm started >
c:\Users\chris\OneDrive\Desktop\echo.txt
I have it called every time a netmail to user TEST comes in.
It does not work.
Too bad. If I could use FMail I could answer PINGs.
Anyway, AFAIK that would not be possible because it uses its
own messagebase format.
Grok says it is not possible.
Copilot says it is possible and made a .pdf describing what it
thinks the settings should be. Copilot says the messagebase is
JAM.
My important data are in OneDrive and in IMAP
If I blow up my system I can re�nstall Windows and download my
data from there.
| Sysop: | DaiTengu |
|---|---|
| Location: | Appleton, WI |
| Users: | 1,114 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 492507:07:43 |
| Calls: | 14,267 |
| Calls today: | 3 |
| Files: | 186,320 |
| D/L today: |
16,388 files (4,998M bytes) |
| Messages: | 2,518,271 |