Hello Paul!

04 Dec 22 21:26, you wrote to all:

3 Dec:04:2022:21:23:21 Linking area NETMAIL
A Dec:04:2022:21:23:21 JAM ERROR: wrongly sized subfield occured!
A Dec:04:2022:21:23:22 JAM ERROR: wrongly sized subfield occured!
A Dec:04:2022:21:23:23 JAM ERROR: subfield is suspiciously large! (1414879828 bytes) A Dec:04:2022:21:23:23 JAM ERROR: wrongly sized subfield occured! A Dec:04:2022:21:23:24 JAM ERROR: subfield is suspiciously large! (976302592 bytes) A Dec:04:2022:21:23:24 JAM
ERROR: subfield is suspiciously large! (825360384 bytes) ----------------------- Sun 04 Dec 2022, hpt/lnx 1.9 2022-07-03

[...]

Dec:04:2022:21:23:25 Areas summary: 1 Dec:04:2022:21:23:25 End

when I view the message base using GoldED the last 4-5 messages are
empty.

Do you have a "-$m xxxx" on the line for that area, and have you been running sqpack?



Stephen


--- GoldED+/LNX 1.1.5-b20220409
* Origin: Dragon's Lair BBS, Telnet: dragon.vk3heg.net (3:633/280)

Hi Paul!

Sunday December 04 2022 21:26, you wrote to All:

I'm starting to see this error in my logs

3 Dec:04:2022:21:23:21 Linking area NETMAIL
A Dec:04:2022:21:23:21 JAM ERROR: wrongly sized subfield occured!
A Dec:04:2022:21:23:22 JAM ERROR: wrongly sized subfield occured!
A Dec:04:2022:21:23:23 JAM ERROR: subfield is suspiciously large!

[...skipped...]

when I view the message base using GoldED the last 4-5 messages are
empty.

is the base corrupt? How best to resolve?

Any tips/advice appreciated.

I would recommend storing netmail in OPUS MSG base and using https://brorabbit.g0x.ru/files/perl/maintmsg.pl

Have a nice night.
Stas Mishchenkov.

--- Have You daily sexual life? Hide it proper from Your wife! ;)
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

04 Dec 22 21:26, Paul Hayton wrote to All:

Hi there

I'm starting to see this error in my logs

3 Dec:04:2022:21:23:21 Linking area NETMAIL
A Dec:04:2022:21:23:21 JAM ERROR: wrongly sized subfield occured!
A Dec:04:2022:21:23:22 JAM ERROR: wrongly sized subfield occured!
A Dec:04:2022:21:23:23 JAM ERROR: subfield is suspiciously large! (1414879828 bytes)
A Dec:04:2022:21:23:23 JAM ERROR: wrongly sized subfield occured!
A Dec:04:2022:21:23:24 JAM ERROR: subfield is suspiciously large! (976302592 bytes)
A Dec:04:2022:21:23:24 JAM ERROR: subfield is suspiciously large! (825360384 bytes)
----------------------- Sun 04 Dec 2022, hpt/lnx 1.9 2022-07-03
1 Dec:04:2022:21:23:25 Start
1 Dec:04:2022:21:23:25 Start packing...
4 Dec:04:2022:21:23:25 EchoTossLogFile not found -> Scanning all areas
4 Dec:04:2022:21:23:25 Scanning NetmailArea NETMAIL
A Dec:04:2022:21:23:25 JAM ERROR: wrongly sized subfield occured!
4 Dec:04:2022:21:23:25 Scanning NetmailArea NETMSG
D Dec:04:2022:21:23:25 Statistics
D Dec:04:2022:21:23:25 areas: 2 msgs: 54
D Dec:04:2022:21:23:25 exported: 0
E Dec:04:2022:21:23:25 Areas summary:
1 Dec:04:2022:21:23:25 End

when I view the message base using GoldED the last 4-5 messages are empty.

is the base corrupt? How best to resolve?

I have seen the same. You could try to delete those empty messages with GoldED and then run "sqpack NETMAIL".

'Tommi

---
* Origin: rbb.fidonet.fi (2:221/360)

On 05 Dec 2022 at 09:55p, Stephen Walsh pondered and said...

Do you have a "-$m xxxx" on the line for that area, and have you been running sqpack?

No and no... I have some learning/reading to do.
I ended up just deleting the base and starting over after copying the files to a temp folder

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 05 Dec 2022 at 02:58p, Stas Mishchenkov pondered and said...

Any tips/advice appreciated.

I would recommend storing netmail in OPUS MSG base and using https://brorabbit.g0x.ru/files/perl/maintmsg.pl

thanks will check this out Stas.. :)

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 06 Dec 2022 at 09:29p, Tommi Koivula pondered and said...

I have seen the same. You could try to delete those empty messages with GoldED and then run "sqpack NETMAIL".

Thanks for this tip Tommi :)

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Hi Paul!

Wednesday December 07 2022 12:44, you wrote to me:

Any tips/advice appreciated.

I would recommend storing netmail in OPUS MSG base and using
https://brorabbit.g0x.ru/files/perl/maintmsg.pl

thanks will check this out Stas.. :)

I don't know for what reason, but it seems to me that storing netmail in jam or squish is unnatural for it. I've noticed that this isn't the first time that netmail has gotten into trouble with jam or squish.

Have a nice night.
Stas Mishchenkov.

--- Have You daily sexual life? Hide it proper from Your wife! ;)
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

On 07 Dec 2022 at 09:29a, Stas Mishchenkov pondered and said...

I don't know for what reason, but it seems to me that storing netmail in jam or squish is unnatural for it. I've noticed that this isn't the
first time that netmail has gotten into trouble with jam or squish.

Have a nice night.

thanks, yes it's new to me so far had never had any issues until now.

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

Hi Tommi!

Friday December 09 2022 09:39, you wrote to me:

I don't know for what reason, but it seems to me that storing netmail
in jam or squish is unnatural for it. I've noticed that this isn't
the first time that netmail has gotten into trouble with jam or
squish.

I have never seen JAM related problems in netmail and I have used JAM netmail from day zero with GEcho/GoldED/Concord/Etc...

I can't say that I understand why this is happening. I just noticed that there are regular questions about netmail crashes in JAM or Squish in various echo conferences. And no one has ever complained about MSG.

Have a nice night.
Stas Mishchenkov.

--- Have You daily sexual life? Hide it proper from Your wife! ;)
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

On 11.12.2022 11:38, Stas Mishchenkov wrote:

SM>> I don't know for what reason, but it seems to me that storing netmail
SM>> in jam or squish is unnatural for it. I've noticed that this isn't
SM>> the first time that netmail has gotten into trouble with jam or
SM>> squish.

TK> I have never seen JAM related problems in netmail and I have used JAM
TK> netmail from day zero with GEcho/GoldED/Concord/Etc...

I can't say that I understand why this is happening. I just noticed that there are regular questions about netmail crashes in JAM or Squish in
various echo conferences. And no one has ever complained about MSG.

Hmm, strange. Well this is husky echo, are those questions/complaints related to husky?

'Tommi

---
* Origin: rbb.fidonet.fi - Lake Ylo - Finland (2:221/360)

Hi Tommi!

Sunday December 11 2022 12:03, you wrote to me:

TK> I have never seen JAM related problems in netmail and I have used
JAM
TK> netmail from day zero with GEcho/GoldED/Concord/Etc...

I can't say that I understand why this is happening. I just noticed that
there are regular questions about netmail crashes in JAM or Squish in
various echo conferences. And no one has ever complained about MSG.

Hmm, strange. Well this is husky echo, are those questions/complaints related to husky?

I'm not sure that only with the husky. However, since in Russian-speaking areas this is the most common tosser, then, highly likely, it is most often associated with it.

Have a nice night.
Stas Mishchenkov.

--- Have You daily sexual life? Hide it proper from Your wife! ;)
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hello, Tommi Koivula.
On 9/12/22 9:27 you wrote:

The only problem running SQPACK is that it always renumbers the
message base. Not acceptable with nntp clients. :(

Is that because sqpack doesn't have an option to not renumber, or is something about the Squish format itself?

--
Carlos
--- Hotdoged/2.13.5/Android
* Origin: cyberiada mobile point (2:341/234.12)

Hi Carlos.

11 Dec 22 16:00:00, you wrote to me:

The only problem running SQPACK is that it always renumbers the
message base. Not acceptable with nntp clients. :(

Is that because sqpack doesn't have an option to not renumber,

Yes.

something about the Squish format itself?

Nope, Fastecho for example can purge and pack without renumbering. Both JAM and Squish.

'Tommi

---
* Origin: - rbb.fidonet.fi - Finland - (2:221/6)

27 Jan 2023 10:48, you wrote to me:

How do you purge messages in JAM without renumbering?

CrashMail II's 'crashmaint PACK' seems to work fine.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

Hi Carlos.

How do you purge messages in JAM without renumbering?

CrashMail II's 'crashmaint PACK' seems to work fine.

Thanks, I'll check it some day.

Does it work ok in Linux/64bit? Jamnntpd does not, and they are related...

'Tommi

---
* Origin: rbb.fidonet.fi (2:221/360)

26 Apr 2023 18:38, you wrote to me:

How do you purge messages in JAM without renumbering?

CrashMail II's 'crashmaint PACK' seems to work fine.

Thanks, I'll check it some day.

Does it work ok in Linux/64bit? Jamnntpd does not, and they are
related...

No idea, sorry. I checked with a Win32 version.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234.1)

Tommi wrote (2023-04-26):

Hi Carlos.

How do you purge messages in JAM without renumbering?

CrashMail II's 'crashmaint PACK' seems to work fine.

Thanks, I'll check it some day.

Does it work ok in Linux/64bit? Jamnntpd does not, and they are related...

I haven't tested it, but I believe so. Both are available for Debian in 64-bit. Do we have to file a bug report?

* Origin: This site requires JavaScript (2:280/464.47)

Hi Oli.

Does it work ok in Linux/64bit? Jamnntpd does not, and they are related...

I haven't tested it, but I believe so.

Not good enough for me. Not a matter of religion. :)

Both are available for Debian in 64-bit. Do we have to file a bug
report?

In this debian 64bit I tried "sudo apt install crashmail", then created a very basic crashmail.prefs with one area

area rbb.test.9 2:221/6 jam /bbs/piste/msgbase/rbb.test.9
keepnum 99
keepdays 99

crashmaint maint verbose
Processing rbb.test.9...
0 messages deleted by number, 4278124318 messages left
0 messages deleted by date, 4278124318 messages left

And the jam base is now broken. Hpt cannot work with it, Golded cannot work with it. :(

So yes, we have to file a bug report. Just test by yourself and go ahead.

'Tommi

--- FMail-lnx64 2.2.0.0
* Origin: ------------------------> (2:221/6.600)

* Originally in fidosoft.husky
* Crossposted in jamnntpd

Hi Oli.

Both are available for Debian in 64-bit. Do we have to file a bug
report?

In this debian 64bit I tried "sudo apt install crashmail", then created a very
basic crashmail.prefs with one area

area rbb.test.9 2:221/6 jam /bbs/piste/msgbase/rbb.test.9
keepnum 99
keepdays 99

crashmaint maint verbose
Processing rbb.test.9...
0 messages deleted by number, 4278124318 messages left
0 messages deleted by date, 4278124318 messages left

And the jam base is now broken. Hpt cannot work with it, Golded cannot work
with it. :(

So yes, we have to file a bug report. Just test by yourself and go ahead.

I repeated the same procedure in this Raspian OS 32bit RPI 3B+ system. Works very nice. So 64bit is to blame.

'Tommi

--- GoldED+/LNX 1.1.5-b20220409
* Origin: Linux 6.1.21-v7+ armv7l (2:221/360)

Hello Tommi,

On Sat Apr 29 2023 19:19:30, you wrote to Oli:

Both are available for Debian in 64-bit. Do we have to file a bug
report?

In this debian 64bit I tried "sudo apt install crashmail", then
created a very basic crashmail.prefs with one area

area rbb.test.9 2:221/6 jam /bbs/piste/msgbase/rbb.test.9
keepnum 99
keepdays 99

crashmaint maint verbose
Processing rbb.test.9...
0 messages deleted by number, 4278124318 messages left
0 messages deleted by date, 4278124318 messages left

And the jam base is now broken. Hpt cannot work with it, Golded cannot work with it. :(

So yes, we have to file a bug report. Just test by yourself and go
ahead.

If I'm not mistaken, the crashmail debian stuff was maintained by RJ Clay (as was most FTN related debian packages), who hasn't been around in at *least* 2 years, and a small search does show someone with his name unfortunately passed away on October 28, 2021. The bug report may not go anywhere for you if he was the only person with read/write access. You may want to try one of the forks (or create your own) and proceed from there. Just an FYI.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20230205
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hi Nicholas.

30 Apr 23 09:35, you wrote to me:

And the jam base is now broken. Hpt cannot work with it, Golded cannot
work with it. :(

So yes, we have to file a bug report. Just test by yourself and go
ahead.

If I'm not mistaken, the crashmail debian stuff was maintained by RJ Clay (as
was most FTN related debian packages), who hasn't been around in at *least* 2
years, and a small search does show someone with his name unfortunately passed
away on October 28, 2021. The bug report may not go anywhere for you if he was
the only person with read/write access. You may want to try one of the forks
(or create your own) and proceed from there. Just an FYI.

Too bad there is broken software in debian repositories...

I think I stay in SMAPI things and JamNNTPd/32bit (and Crashmaint/32bit maybe if really needed).

'Tommi

--- GoldED+/LNX 1.1.5-b20220409
* Origin: Linux 6.1.21-v7+ armv7l (2:221/360)

Nicholas wrote (2023-04-30):

And the jam base is now broken. Hpt cannot work with it, Golded
cannot work with it. :(

So yes, we have to file a bug report. Just test by yourself and go
ahead.

If I'm not mistaken, the crashmail debian stuff was maintained by RJ Clay (as was most FTN related debian packages),

Yes, he was the maintainer.

who hasn't been around in at *least* 2 years,

There are also no github commits after 2019.

and a small search does show someone with his name
unfortunately passed away on October 28, 2021.

which might also be another person.

The bug report may not go anywhere for you if he was the only person
with read/write access.

The bug reports are public. Even if nobody will fix it, we have at least a documentation of the problem. The package is orphaned an maintainer is "Debian QA Group".

https://tracker.debian.org/pkg/crashmail https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982204

You may want to try one of the forks (or create
your own) and proceed from there. Just an FYI.

I think the repository from RJ Clay is the most recent one (but last time I checked as last year, IIRC).

---
* Origin: This site requires JavaScript (2:280/464.47)

Tommi wrote (2023-04-29):

Hi Oli.

Does it work ok in Linux/64bit? Jamnntpd does not, and they are
related...

I haven't tested it, but I believe so.

Not good enough for me. Not a matter of religion. :)

;)

Both are available for Debian in 64-bit. Do we have to file a bug
report?

In this debian 64bit I tried "sudo apt install crashmail", then created a very basic crashmail.prefs with one area

area rbb.test.9 2:221/6 jam /bbs/piste/msgbase/rbb.test.9
keepnum 99
keepdays 99

Had the area been created by crashmail or another tosser?

crashmaint maint verbose
Processing rbb.test.9...
0 messages deleted by number, 4278124318 messages left
0 messages deleted by date, 4278124318 messages left

And the jam base is now broken. Hpt cannot work with it, Golded cannot work with it. :(

Did you try to compare the .j?? files from before and after running crashmaint?

Did you try to run crashmaint a second time over the broken JAM base?

---
* Origin: This site requires JavaScript (2:280/464.47)