Hello Bo,

I have quite a few .lng files in my inbound because I'm getting pkt's with messages that are too long. What is the max length of a msg in a pkt? I'm also seeing something about dupe checking, I'll post a piece of my log just FYI.


=== Cut ===
+ 04 Feb 11:40:57 SQSH Begin, Squish/Linux v1.12.003 BETA (mem=9964K - main=0x804ab00)
* 04 Feb 11:40:57 SQSH UnZIPing /max/spool/inbound/0000ff9a.WE0
* 04 Feb 11:40:57 SQSH UnZIPing /max/spool/inbound/p01f4013.WE3
# 04 Feb 11:40:57 SQSH Tossing/scanning msgs from . (secure)
* 04 Feb 11:40:57 SQSH 402118d2.pkt, 02/04/04, 11:07:43, by fe 0.95
- 04 Feb 11:40:57 SQSH Orig=1:132/500.0, Dest=1:132/500.19, Type=2+
! 04 Feb 11:40:58 SQSH Msg too long to toss: skipping to next msg.
! 04 Feb 11:40:58 SQSH Packet contains long msg: renamed to ./402118d2.lng
* 04 Feb 11:40:58 SQSH 402136f0.pkt, 02/04/04, 13:15:59, by fe 0.95
- 04 Feb 11:40:58 SQSH Orig=63:63/1.0, Dest=63:63/103.0, Type=2+
! 04 Feb 11:40:58 SQSH DEBUG: Year is Zero in GetDidHeader in s_dupe.c! Date CRC used for Dupe Checking is invalid!
# 04 Feb 11:40:58 SQSH Scanning messages
# 04 Feb 11:40:58 SQSH Packing from /max/spool/netmail (13 msgs)
: 04 Feb 11:40:58 SQSH Packed=0
# 04 Feb 11:40:58 SQSH Linking messages
+ 04 Feb 11:40:58 SQSH End. Toss=118 (118/s), sent=0 (0/s), mem=9476K
=== Cut ===

I can't seem to build max on the debian box, I think because maxcomm isn't being built. Strange I can build max on mandrake even though maxcomm isn't built. It must be finding what it needs somewhere else on mandrake.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-31012
* Origin: The Rusty MailBox - Penticton, B.C. Canada (1:132/500.19)

I have quite a few .lng files in my inbound because I'm
getting pkt's with messages that are too long. What is the max
length of a msg in a pkt?

according to the FTS specs, there is none... the message body is unbounded...

I'm also seeing something about dupe
checking, I'll post a piece of my log just FYI.

[trim]

I can't seem to build max on the debian box, I think because
maxcomm isn't being built. Strange I can build max on mandrake
even though maxcomm isn't built. It must be finding what it
needs somewhere else on mandrake.

interesting... i've not gotten a good build on my mandrake box since around christmas...

)\/(ark


* Origin: (1:3634/12)

Hello Mark,

I can't seem to build max on the debian box, I think because
maxcomm isn't being built. Strange I can build max on mandrake
even though maxcomm isn't built. It must be finding what it
needs somewhere else on mandrake.

interesting... i've not gotten a good build on my
mandrake box since around christmas...

Hmm. I just did a fresh build on Mandrake and here we are.. but I can't get it to build on Debian. Actually I solved my graphics character problems with mandrake, so I think I'll just stay here anyway.. :)

Ttyl :-),
Al

--- Maximus/UNIX 3.03b
* Origin: The Rusty MailBox - Penticton, B.C. Canada (1:132/500.19)

I can't seem to build max on the debian box, I think because
maxcomm isn't being built. Strange I can build max on
mandrake even though maxcomm isn't built. It must be finding
what it needs somewhere else on mandrake.

interesting... i've not gotten a good build on my
mandrake box since around christmas...

Hmm. I just did a fresh build on Mandrake and here we are..
but I can't get it to build on Debian. Actually I solved my
graphics character problems with mandrake, so I think I'll
just stay here anyway.. :)

i've /just/ started my update script again... lets see what happens... i'll try
to report something in the next 30 minutes or so... it takes that long to run ;-)

oops... i see that this is TUB... i'll make the report in MUFFIN...

)\/(ark


* Origin: (1:3634/12)

Hello, Alan...

Squish (if that's what you are discussing) has limits based upon memory. I don't remember anything about .LNG files, but the real-mode version hangs on messages over 16 or 32k (I forget which).

Regards,

Jerry Schwartz

mailto:jerryschwartz@comfortable.com
http://www.writebynight.com

--- Msged/NT 6.0.1
* Origin: Write by Night (1:142/928)

* Forwarded from 'MUFFIN'
* Originally by mark lewis, 1:3634/12
* Originally to Alan Ianson
* Originally dated Mon 16 Feb 2004 17:33

-*- Forwarded message follows: -*-

i've /just/ started my update script again... lets see what
happens... i'll try to report something in the
next 30 minutes or so... it takes that long to run ;-)

oops... i see that this is TUB... i'll make the report in
MUFFIN...

How did it go? BTW, I'm running Mandrake 9.2 here, the only
thing I've installed is ncurses-5.3.tar.gz.

well, i ended up having to leave before it completed... just finished it a little bit ago and its still failing...

the top starts as

gmake[1]: [depend.mk] Error 1 (ignored)
/usr/bin/ld: cannot find -lmsgapi
collect2: ld returnes 1 exit status
gnake[1]: *** [trackexp] Error 1


and the end of the log goes on about something in maxcomm...

maxcomm.c: In function `main':
maxcomm.c:30: storage size of `tv' isn't known
maxcomm.c:30: warning: unused variable `tv'
gmake[1]: *** [maxcomm.o] Error 1
make: *** [max] Error 2


i suspect the failure is occuring because of the problem with ld and -lmsgapi...

)\/(ark

! Origin: (1:3634/12)


* Origin: (1:3634/12)

Hi, All!

I'm getting the ocassional message that squish won't toss (Netmail). The log says "message too long, renamed to *.lng". Is there any solution, or any way to break up these big messages? Windows 11, 32bit here. Thanks!


Cheers... Dallas
--- timEd/386 1.10.y2k+
* Origin: The BandMaster, Vancouver, CANADA (1:153/7715)

Hello Dallas!

05 Feb 22 17:28, Dallas Hinton wrote to All:

Hi, All!

I'm getting the ocassional message that squish won't toss (Netmail).
The log says "message too long, renamed to *.lng". Is there any solution, or any way to break up these big messages? Windows 11,
32bit here. Thanks!

Dallas, I wrote a quick little utility that takes those long messages and splits them up into manageable pieces. I'm not sure if it will run on Win11 or not. Do you want to give it a try?

Is your NetMail in *.MSG or Squish format?
--- Msged/NT 6.0.1
* Origin: Somewhere in New Hampshire's White Mountains (1:132/174)

Dallas wrote (2022-02-05):

Hi, All!

I'm getting the ocassional message that squish won't toss (Netmail). The log says "message too long, renamed to *.lng". Is there any solution, or any way to break up these big messages? Windows 11, 32bit here. Thanks!

How long are these messages?

64K, >256K?

Which Squish version (for DOS or Windows)?

---
* Origin: Birds aren't real (2:280/464.47)

Oli wrote (2022-02-06):

How long are these messages?

64K, >256K?

That was JamNNTP's smartquote feature... should be:

How long are these messages? >64K, >256K?

* Origin: Birds aren't real (2:280/464.47)

On 2022 Feb 05 17:28:24, you wrote to All:

I'm getting the ocassional message that squish won't toss (Netmail).
The log says "message too long, renamed to *.lng". Is there any
solution, or any way to break up these big messages? Windows 11, 32bit here. Thanks!

there is/was a tool that could split/unsplit long messages in PKTs before the tosser handled them... i do not know its status, any more...

PSRT_14.ZIP 269257 Apr-27-1994
=============================================
PacketSorter v1.4 bug fixes & new features
FidoNet inbound packet processor defragments
packets, speeds up tossing on SQUISH and JAM
- split large messages according to FSC-0047
- sort messages by subject and/or time
- remove garbage from 'bad' packets
- split large packets to a more handy size
- unsplit large messages back to orign. size
- fast & highly configurable
- works with any echomail tosser
- runs with both OS/2 and DOS in 32 bit mode
- quick installation for Squish & CrossPoint
- quick installation for FastEcho & IMail

http://www.tinysbbs.com/files/mailer/PSRT_14.ZIP


FWIW: i would only use it manually on your long message containing packets to split those messages into a new pkt which your squish should then be able to consume... i would do this only on those specific packets so that it affects only your system and not others connected to you... then place the new packet where your squish can get to it and you should now get your previously long netmail as multiple messages identified with the ^ASPLIT protocol from the old FSC-0047.001 proposal http://ftsc.org/docs/fsc-0047.001 ...

)\/(ark

"The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
... Objects under T-Shirt are larger than they appear.
---
* Origin: (1:3634/12.73)

On 2022 Feb 06 05:45:36, you wrote to Dallas Hinton:

I'm getting the ocassional message that squish won't toss (Netmail).
The log says "message too long, renamed to *.lng". Is there any
solution, or any way to break up these big messages? Windows 11,
32bit here. Thanks!

Dallas, I wrote a quick little utility that takes those long messages
and splits them up into manageable pieces. I'm not sure if it will
run on Win11 or not. Do you want to give it a try?

Is your NetMail in *.MSG or Squish format?

he needs this to work at the PKT level so his tosser can then handle them afterward...

)\/(ark

"The soul of a small kitten in the body of a mighty dragon. Look on my majesty, ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!"
... Learn from your parent's mistakes: Use Birth Control!
---
* Origin: (1:3634/12.73)

Hello mark!

06 Feb 22 07:30, mark lewis wrote to Fred Riccio:

Is your NetMail in *.MSG or Squish format?

he needs this to work at the PKT level so his tosser can then handle
them afterward...

After I hit the SEND button, I realised that was a stupid question. The utility does take the packet with the long message (renamed by squish to *.lng) as input, and creates a .pkt (with the long message split) as output so squish can give it another try. Message maximum size and input/output directories are all configurable by the user and stored in the registry.


Also after I wrote my last message, I dug out the program and tried it out under win10. No luck. It was written in VB4 in 2006, and requires vbrun300.dll to operate. regsvr32 complains that it is not a 32 or 64 bit .DLL and refuses to register it. Putting the DLL in the directory with the .Exe doesn't work either. It runs perfectly on older OS.
--- Msged/NT 6.0.1
* Origin: Somewhere in New Hampshire's White Mountains (1:132/174)

Hello Dallas!

05 Feb 22 17:28, Dallas Hinton wrote to All:

Hi, All!

I'm getting the ocassional message that squish won't toss (Netmail).
The log says "message too long, renamed to *.lng". Is there any solution, or any way to break up these big messages? Windows 11,
32bit here. Thanks!

One more thought...

Are you using the BUFFERS keyword in your squish.cfg or do you just let them default? See Squish.Doc pages 58 & 59.

Switching to SQ386 may help too.

--- Msged/NT 6.0.1
* Origin: Somewhere in New Hampshire's White Mountains (1:132/174)

Hello Dallas!

05 Feb 22 17:28, Dallas Hinton wrote to All:

Hi, All!

I'm getting the ocassional message that squish won't toss (Netmail).
The log says "message too long, renamed to *.lng". Is there any solution, or any way to break up these big messages? Windows 11,
32bit here. Thanks!

One more thought...

Are you using the BUFFERS keyword in your squish.cfg or do you just let them default? See Squish.Doc pages 58 & 59.

Switching to SQ386 may help too.
--- Msged/NT 6.0.1
* Origin: Somewhere in New Hampshire's White Mountains (1:132/174)

Hi, Fred -- on Feb 06 2022 at 05:45, you wrote:

Dallas, I wrote a quick little utility that takes those long
messages and splits them up into manageable pieces. I'm not sure
if it will run on Win11 or not. Do you want to give it a try?

I'd be delighted to try it, thanks!!

Is your NetMail in *.MSG or Squish format?

Netmail is *.msg, but the .lng messages never get tossed.

I'm at dallas.hinton @ gmail.com -- many thanks!


Cheers... Dallas
--- timEd/386 1.10.y2k+
* Origin: The BandMaster, Vancouver, CANADA (1:153/7715)

Hi, Oli -- on Feb 06 2022 at 12:35, you wrote:

How long are these messages?

64K, >256K?

Upwards of 100K -- maybe 125K

Which Squish version (for DOS or Windows)?

Using squish 32 bit -- sq386b.exe


Cheers... Dallas
--- timEd/386 1.10.y2k+
* Origin: The BandMaster, Vancouver, CANADA (1:153/7715)

Hi, mark -- on Feb 06 2022 at 06:39, you wrote:

there is/was a tool that could split/unsplit long messages in PKTs
before the tosser handled them... i do not know its status, any
more...

PSRT_14.ZIP 269257 Apr-27-1994

Perfect, thanks!! It's only netmail status reports from Nick that seem to be the problem. Apparently d'bridge won't limit outgoing message sizes so I have to cope! :-)

Cheers... Dallas
--- timEd/386 1.10.y2k+
* Origin: The BandMaster, Vancouver, CANADA (1:153/7715)

Hi, Fred -- on Feb 06 2022 at 10:13, you wrote:

Also after I wrote my last message, I dug out the program and tried
it out under win10. No luck. It was written in VB4 in 2006, and

Ah well -- I'll try packetsort -- thanks!!



Cheers... Dallas
--- timEd/386 1.10.y2k+
* Origin: The BandMaster, Vancouver, CANADA (1:153/7715)

Hi, Fred -- on Feb 06 2022 at 11:39, you wrote:

Are you using the BUFFERS keyword in your squish.cfg or do you just
let them default? See Squish.Doc pages 58 & 59.

Yes, buffers large

Switching to SQ386 may help too.

Already doing that. :-) But it never hurts to check!




Cheers... Dallas
--- timEd/386 1.10.y2k+
* Origin: The BandMaster, Vancouver, CANADA (1:153/7715)

Hi, mark -- on Feb 06 2022 at 06:39, you wrote:

PSRT_14.ZIP 269257 Apr-27-1994

Unfortunately, it won't run under w11 32bit. Good try, though!



Cheers... Dallas
--- timEd/386 1.10.y2k+
* Origin: The BandMaster, Vancouver, CANADA (1:153/7715)

Hello Dallas!

06 Feb 22 09:49, Dallas Hinton wrote to Oli:

How long are these messages?

Upwards of 100K -- maybe 125K

Using squish 32 bit -- sq386b.exe

According to the docs, SQ386 with BUFFERS LARGE should be able to handle a 256K message all by itself. Can your message reader/editor handle that?
--- Msged/NT 6.0.1
* Origin: Somewhere in New Hampshire's White Mountains (1:132/174)

Hi, Fred -- on Feb 06 2022 at 13:14, you wrote:

According to the docs, SQ386 with BUFFERS LARGE should be able to
handle a 256K message all by itself. Can your message
reader/editor handle that?

Yup -- the change to large seems to have solved things - at least for the current set of lng files I've saved. Thanks.

Cheers... Dallas
--- timEd/386 1.10.y2k+
* Origin: The BandMaster, Vancouver, CANADA (1:153/7715)

Hello Dallas!

06 Feb 22 11:36, Dallas Hinton wrote to Fred Riccio:

Yup -- the change to large seems to have solved things - at least for
the current set of lng files I've saved. Thanks.

+1 for RTFM :)
--- Msged/NT 6.0.1
* Origin: Somewhere in New Hampshire's White Mountains (1:132/174)

Hi, Fred -- on Feb 06 2022 at 15:47, you wrote:

+1 for RTFM :)

++1 for understanding it! :-)


Cheers... Dallas
--- timEd/386 1.10.y2k+
* Origin: The BandMaster, Vancouver, CANADA (1:153/7715)