Hello all\!

I'm trying to send mail to my point, in basic form, ie *.pkt. It's important for the mail to be in *.pkt form in huis inbound. How can
I do this with squish? Thanks.

Have a nice day!
Phil

--- timEd 1.10.y2k+
* Origin: Think Outside the Policy (1:229/3000)

Hello, Phil...

Dec 24, 2006 at 17:29, Phil Simpson wrote to all\:

I'm trying to send mail to my point, in basic form, ie *.pkt. It's important for the mail to be in *.pkt form in huis inbound. How can
I do this with squish? Thanks.

It's done in ROUTE.CFG, with the SEND NOARC command. It's best if you use either SEND NOARC HOLD or SEND NOARC CRASH to make sure that a subsequent command doesn't accidentally bundle it up.

Regards,

Jerry Schwartz

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

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

On Dec 24 2006 Jerry Schwartz wrote to Phil Simpson:

Hello, Phil...

Dec 24, 2006 at 17:29, Phil Simpson wrote to all\:

I'm trying to send mail to my point, in basic form, ie *.pkt. It's important for the mail to be in *.pkt form in huis inbound. How can
I do this with squish? Thanks.

It's done in ROUTE.CFG, with the SEND NOARC command. It's best if
you use either SEND NOARC HOLD or SEND NOARC CRASH to make sure
that a subsequent command doesn't accidentally bundle it up.

Tried that, doesn't compress the file, but it is in cut format not *.pkt
Tosser doesn't seem to like anything but *.pkt files.

Have a nice day!
Phil

--- timEd 1.10.y2k+
* Origin: Think Outside the Policy (1:229/3000)

Hi Phil,

I'm trying to send mail to my point, in basic form, ie *.pkt. It's important for the mail to be in *.pkt form in huis inbound. How can
I do this with squish? Thanks.

It's done in ROUTE.CFG, with the SEND NOARC command. It's best if
you use either SEND NOARC HOLD or SEND NOARC CRASH to make sure
that a subsequent command doesn't accidentally bundle it up.

Tried that, doesn't compress the file, but it is in cut format not *.pkt Tosser doesn't seem to like anything but *.pkt files.

.CUT files ARE .PKT files, but with a ROUTING file extension.

Squish packs mail into .PKT format files, and then the ROUTE.CFG section tells Squish what you wish to DO with those files. The .CUT extension is simply a .PKT format file that has been RENAMED into a format for sending to a node. If you want to use .PKT files "au natural" (natively) then use the LEAVE command in ROUTE.CFG to tell Squish to NOT touch the created .PKT file.

Cheers..............pk.


--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)

Hello, Peter...

Dec 26, 2006 at 11:03, Peter Knapper wrote to Phil Simpson:

I'm trying to send mail to my point, in basic form, ie *.pkt. It's
important for the mail to be in *.pkt form in huis inbound. How can
I do this with squish? Thanks.

It's done in ROUTE.CFG, with the SEND NOARC command. It's best if
you use either SEND NOARC HOLD or SEND NOARC CRASH to make sure
that a subsequent command doesn't accidentally bundle it up.

Tried that, doesn't compress the file, but it is in cut format not
*.pkt Tosser doesn't seem to like anything but *.pkt files.

.CUT files ARE .PKT files, but with a ROUTING file extension.

Squish packs mail into .PKT format files, and then the ROUTE.CFG
section tells Squish what you wish to DO with those files. The .CUT extension is simply a .PKT format file that has been RENAMED into a format for sending to a node. If you want to use .PKT files "au
natural" (natively) then use the LEAVE command in ROUTE.CFG to tell Squish to NOT touch the created .PKT file.

Doesn't the mailer rename the .?UT files as .PKT files when they are sent? That's my vague and possibly incorrect memory.

Regards,

Jerry Schwartz

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

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

Hi Jerry,

Squish packs mail into .PKT format files, and then the ROUTE.CFG
section tells Squish what you wish to DO with those files. The .CUT extension is simply a .PKT format file that has been RENAMED into a format for sending to a node. If you want to use .PKT files "au
natural" (natively) then use the LEAVE command in ROUTE.CFG to tell Squish to NOT touch the created .PKT file.

Doesn't the mailer rename the .?UT files as .PKT files
when they are sent? That's my vague and possibly incorrect memory.

Its been a long time since I looked into this and you may be correct, however as I understand it the original poster wanted the .PKT format BEFORE BinkD got its hands on them.

Cheers.............pk.


--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)

Doesn't the mailer rename the .?UT files as .PKT files
when they are sent? That's my vague and possibly
incorrect memory.

That's what's supposed to happen :)

"The Outside World" section in Squish.doc explains the entire process.

Those .Pkt files being sent could be either compressed or uncompressed (but not
both), and contain bundled or unbundled messages (but not both).

--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

Tried that, doesn't compress the file, but it is
in cut format not *.pkt
Tosser doesn't seem to like anything but *.pkt files.

.CUT files ARE .PKT files, but with a ROUTING file extension.

Squish packs mail into .PKT format files, and then the
ROUTE.CFG section tells Squish what you wish to DO with
those files. The .CUT extension is simply a .PKT format
file that has been RENAMED into a format for sending to
a node. If you want to use .PKT files "au natural"
(natively) then use the LEAVE command in ROUTE.CFG to
tell Squish to NOT touch the created .PKT file.

According to Squish.doc, the Leave command makes mail inaccessible to polling systems. Thus nothing gets sent because their file extensions change to *.N?T.

--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

I'm trying to send mail to my point, in basic form, ie *.pkt. It's important for the mail to be in *.pkt form in huis inbound. How can
I do this with squish? Thanks.

It's done in ROUTE.CFG, with the SEND NOARC command. It's best if
you use either SEND NOARC HOLD or SEND NOARC CRASH to make sure
that a subsequent command doesn't accidentally bundle it up.

Tried that, doesn't compress the file, but it is in cut format not *.pkt Tosser doesn't seem to like anything but *.pkt files.

It sounds like your point node's tosser isn't decompressing compressed mail bundles properly, perhaps because you're both using an incompatible archiver; or they have a misconfigured Compress.Cfg/Tosser.

SEND NOARC's only a band-aid fix because everybody Zip-pack's mail these days, so your point node will encounter problems when other systems outside your zone:net/node address mail to them.

--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

Hi Mvan,

According to Squish.doc, the Leave command makes mail
inaccessible to polling systems.

Yes, I agree with this part...

Thus nothing gets sent because their file extensions change to *.N?T.

However not EVERYTHING gets renamed, only the .FLO type files that already exist, and only those files in OUTBOUND areas...

Here is the full text of the Squish V3 docs about the LEAVE command -

Leave <node> [<nodes>...]

The Leave command modifies outbound mail so that it won't be
sent by BinkleyTerm. Squish will rename both *.?UT and
*.?LO to an extension which is not recognized by
BinkleyTerm, thereby preventing the mail from being sent or
picked up.

Leaving mail is useful for mail hubs and NECs, since it
stops all mail from being given to the specified nodes. If
your system has a crucial polling window and you want to
stop others from receiving mail when they call in, the Leave
command can be used to make that mail inaccessible.

To convert mail back to its original form after using
"Leave", see the documentation for the Unleave command.

As many nodes can be specified for the Leave command as
necessary. Wildcards are permitted.

In the BinkleyTerm outbound area, using Leave has the
following result:

xxxxyyyy.?UT --> xxxxyyyy.N?T
xxxxyyyy.?LO --> xxxxyyyy.N?O


It may also pay to look at the Squish docs for the UNLEAVE command...

So Squish renames .FLO files, but not any OTHER files. This means that it does not touch files in \Outbound.Sq, so THOSE files should be .PKT files, but probably bearing a Squish Extn (probably .SQ). These files could be renamed to .PKT, moved to the appropriate directory and then sent, which I think is what the original poster wanted, however he would also have to do that himself, as Squish would process them according to its configuration, and not move them to the required outbound area.

I still wonder exactly why the original user wants to do it this way, its like he is mixing and matching an AMA Style Mailer, but using BinkD and BSO, but one
would have to wonder why. Perhaps if he is using Squish, then he would be better off using Sqush in AMA mode and Fileboxes in BinkD, however I have never
played with either of those so I dont know the quirks one might find.

Cheers............pk.


--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)

It sounds like your point node's tosser isn't
decompressing compressed mail bundles properly, perhaps
because you're both using an incompatible archiver; or
they have a misconfigured Compress.Cfg/Tosser.

SEND NOARC's only a band-aid fix because everybody Zip-
pack's mail these days, so your point node will
encounter problems when other systems outside your
zone:net/node address mail to them.

There is a nodelist flag that can be on an entry that requires that all mail sent to the node from someone else in fidonet must be non-compressed. I fly that flag on my entry. While I do allow compressed mail, it is for only nodes that have made some arragements with me.....

And *officially* the only compression that is legal without prior negotiation is a very old ARC standard..... Yes, I could do that if I wanted to, but I opt
to say no compresses mail....

Take care,

Bob Jones, 1:343/41



--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

Hello all!

I send mail to my point, 1:229/3000.1 and all compressed crash mail gets sent as 0000ffff.th0 depending on date. This is likely the problem, what can I do to
fix this?

Have a nice day!
Phil

--- timEd 1.10.y2k+
* Origin: Think Outside the Policy (1:229/3000)

Hi Phil,

I send mail to my point, 1:229/3000.1 and all
compressed crash mail gets sent as 0000ffff.th0
depending on date. This is likely the problem, what can I do to fix this?

This is absolutely NORMAL. ALL Mail addressed to a 4D point off YOUR node will use the 0000ffff.??? filename format. Its a "special" number that all Fidonet Mailers should recognise because the packet naming scheme does not allow for Points within the forming of the 8.3 file name. the 0000ffff part means "My node Number - 1", and as negative node numbers are not allowed this means the point node is handled appropriately.

However if you were using 3D Point addressing (where a "Fakenet" number is used), then the Filenames should be normal.

Cheers.............pk.


--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)

Hello all!

I send mail to my point, 1:229/3000.1 and all
compressed crash mail gets sent as 0000ffff.th0
depending on date. This is likely the problem, what can I do to fix this?

That looks right to me.

Your default outbound directory should look like this after you run SQUISH OUT (or SQUASH if only netmail was created):

<outbound>\00E50BB8.PNT\00000001.CLO <-- initiate crash mail to 229/3000.1
<outbound>\00E50BB8.PNT\0000ffff.th0 <-- compressed mail bundle (or unbundled
if just 1 message. heh.)

where 00000001.CLO contains

#<outbound>\00E50BB8.PNT\0000ffff.th0

If you were sending to 229/3000.2,.3,.4 etc. it would look like

<outbound>\00E50BB8.PNT\00000002.CLO
<outbound>\00E50BB8.PNT\00000003.CLO
<outbound>\00E50BB8.PNT\00000004.CLO
...
...
...

where each file contains what it needs to send to the remote system.

Btw; Hex 00E5 equals 229 in decimal (your net number) and 0BB8 equals 3000 (your node number).

During the mail session with your point node, your mailer sends the file "0000ffff.th0" which is then saved to some other file name on your point's machine's inbound directory eg. <inbound>\<random_letters>.th0. Their tosser determines if <random_letters>.th0 is a compressed or uncompressed file and proceeds to extract/import accordingly.

We need to look at your point's tosser log file, and maybe their mailer's log file to see if the above sequence of events takes place.

I hope you guys are using BinkD and Squish on both ends. Heh.


--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

MSGID: 1:229/3000.0 58effcf0
Hello all\!

I'm trying to send mail to my point, in basic form, ie *.pkt. It's important for the mail to be in *.pkt form in huis inbound. How can
I do this with squish? Thanks.

Have a nice day!
Phil

--- timEd 1.10.y2k+
* Origin: Think Outside the Policy (1:229/3000)

MSGID: 1:142/928 458eec1b
TZUTC: -0500
REPLY: 1:229/3000.0 58effcf0
Hello, Phil...

Dec 24, 2006 at 17:29, Phil Simpson wrote to all\:

I'm trying to send mail to my point, in basic form, ie *.pkt. It's important for the mail to be in *.pkt form in huis inbound. How can
I do this with squish? Thanks.

It's done in ROUTE.CFG, with the SEND NOARC command. It's best if you use either SEND NOARC HOLD or SEND NOARC CRASH to make sure that a subsequent command doesn't accidentally bundle it up.

Regards,

Jerry Schwartz

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

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

MSGID: 1:229/3000.0 58fdf970
REPLY: 1:142/928 458eec1b
On Dec 24 2006 Jerry Schwartz wrote to Phil Simpson:

Hello, Phil...

Dec 24, 2006 at 17:29, Phil Simpson wrote to all\:

I'm trying to send mail to my point, in basic form, ie *.pkt. It's important for the mail to be in *.pkt form in huis inbound. How can
I do this with squish? Thanks.

It's done in ROUTE.CFG, with the SEND NOARC command. It's best if
you use either SEND NOARC HOLD or SEND NOARC CRASH to make sure
that a subsequent command doesn't accidentally bundle it up.

Tried that, doesn't compress the file, but it is in cut format not *.pkt
Tosser doesn't seem to like anything but *.pkt files.

Have a nice day!
Phil

--- timEd 1.10.y2k+
* Origin: Think Outside the Policy (1:229/3000)

MSGID: 1:142/928 45916d80
TZUTC: -0500
REPLY: 3:772/1.10 459058aa
Hello, Peter...

Dec 26, 2006 at 11:03, Peter Knapper wrote to Phil Simpson:

I'm trying to send mail to my point, in basic form, ie *.pkt. It's
important for the mail to be in *.pkt form in huis inbound. How can
I do this with squish? Thanks.

It's done in ROUTE.CFG, with the SEND NOARC command. It's best if
you use either SEND NOARC HOLD or SEND NOARC CRASH to make sure
that a subsequent command doesn't accidentally bundle it up.

Tried that, doesn't compress the file, but it is in cut format not
*.pkt Tosser doesn't seem to like anything but *.pkt files.

.CUT files ARE .PKT files, but with a ROUTING file extension.

Squish packs mail into .PKT format files, and then the ROUTE.CFG
section tells Squish what you wish to DO with those files. The .CUT extension is simply a .PKT format file that has been RENAMED into a format for sending to a node. If you want to use .PKT files "au
natural" (natively) then use the LEAVE command in ROUTE.CFG to tell Squish to NOT touch the created .PKT file.

Doesn't the mailer rename the .?UT files as .PKT files when they are sent? That's my vague and possibly incorrect memory.

Regards,

Jerry Schwartz

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

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

REPLY: 1:142/928 45916d80
MSGID: 1:343/41.0 4592fd86

Doesn't the mailer rename the .?UT files as .PKT files
when they are sent? That's my vague and possibly
incorrect memory.

That's what's supposed to happen :)

"The Outside World" section in Squish.doc explains the entire process.

Those .Pkt files being sent could be either compressed or uncompressed (but not both), and contain bundled or unbundled messages (but not both).

--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

REPLY: 3:772/1.10 459058aa
MSGID: 1:343/41.0 4592fe7e

Tried that, doesn't compress the file, but it is
in cut format not *.pkt
Tosser doesn't seem to like anything but *.pkt files.

.CUT files ARE .PKT files, but with a ROUTING file extension.

Squish packs mail into .PKT format files, and then the
ROUTE.CFG section tells Squish what you wish to DO with
those files. The .CUT extension is simply a .PKT format
file that has been RENAMED into a format for sending to
a node. If you want to use .PKT files "au natural"
(natively) then use the LEAVE command in ROUTE.CFG to
tell Squish to NOT touch the created .PKT file.

According to Squish.doc, the Leave command makes mail inaccessible to polling systems. Thus nothing gets sent because their file extensions change to *.N?T.

--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

REPLY: 1:229/3000.0 58fdf970
MSGID: 1:343/41.0 4592ff18

I'm trying to send mail to my point, in basic form, ie *.pkt. It's important for the mail to be in *.pkt form in huis inbound. How can
I do this with squish? Thanks.

It's done in ROUTE.CFG, with the SEND NOARC command. It's best if
you use either SEND NOARC HOLD or SEND NOARC CRASH to make sure
that a subsequent command doesn't accidentally bundle it up.

Tried that, doesn't compress the file, but it is in cut format not *.pkt Tosser doesn't seem to like anything but *.pkt files.

It sounds like your point node's tosser isn't decompressing compressed mail bundles properly, perhaps because you're both using an incompatible archiver; or they have a misconfigured Compress.Cfg/Tosser.

SEND NOARC's only a band-aid fix because everybody Zip-pack's mail these days, so your point node will encounter problems when other systems outside your zone:net/node address mail to them.

--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

MSGID: 1:343/41.0 4593191c
REPLY: 1:343/41.0 4592ff18

It sounds like your point node's tosser isn't
decompressing compressed mail bundles properly, perhaps
because you're both using an incompatible archiver; or
they have a misconfigured Compress.Cfg/Tosser.

SEND NOARC's only a band-aid fix because everybody Zip-
pack's mail these days, so your point node will
encounter problems when other systems outside your
zone:net/node address mail to them.

There is a nodelist flag that can be on an entry that requires that all mail sent to the node from someone else in fidonet must be non-compressed. I fly that flag on my entry. While I do allow compressed mail, it is for only nodes that have made some arragements with me.....

And *officially* the only compression that is legal without prior negotiation is a very old ARC standard..... Yes, I could do that if I wanted to, but I opt to say no compresses mail....

Take care,

Bob Jones, 1:343/41



--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)

MSGID: 1:229/3000.0 593dd330
Hello all!

I send mail to my point, 1:229/3000.1 and all compressed crash mail gets sent as 0000ffff.th0 depending on date. This is likely the problem, what can I do to fix this?

Have a nice day!
Phil

--- timEd 1.10.y2k+
* Origin: Think Outside the Policy (1:229/3000)

REPLY: 1:229/3000.0 593dd330
MSGID: 1:343/41.0 4594510c

Hello all!

I send mail to my point, 1:229/3000.1 and all
compressed crash mail gets sent as 0000ffff.th0
depending on date. This is likely the problem, what can I do to fix this?

That looks right to me.

Your default outbound directory should look like this after you run SQUISH OUT (or SQUASH if only netmail was created):

<outbound>\00E50BB8.PNT\00000001.CLO <-- initiate crash mail to 229/3000.1
<outbound>\00E50BB8.PNT\0000ffff.th0 <-- compressed mail bundle (or unbundled if just 1 message. heh.)

where 00000001.CLO contains

#<outbound>\00E50BB8.PNT\0000ffff.th0

If you were sending to 229/3000.2,.3,.4 etc. it would look like

<outbound>\00E50BB8.PNT\00000002.CLO
<outbound>\00E50BB8.PNT\00000003.CLO
<outbound>\00E50BB8.PNT\00000004.CLO
...
...
...

where each file contains what it needs to send to the remote system.

Btw; Hex 00E5 equals 229 in decimal (your net number) and 0BB8 equals 3000 (your node number).

During the mail session with your point node, your mailer sends the file "0000ffff.th0" which is then saved to some other file name on your point's machine's inbound directory eg. <inbound>\<random_letters>.th0. Their tosser determines if <random_letters>.th0 is a compressed or uncompressed file and proceeds to extract/import accordingly.

We need to look at your point's tosser log file, and maybe their mailer's log file to see if the above sequence of events takes place.

I hope you guys are using BinkD and Squish on both ends. Heh.


--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)