Hello All !

Atm the only way I can readdress mail is manually via BinkleyTerm.

How do I get Squish to re-address mail in the outbound directory after it has been packed and compressed ? eg. There are Held packets destined for 1:222/333 which I want to reroute to 4:555/666.

--- Msged/386 4.30
* Origin: ypan.dyndns.org loves Msged... (3:712/104)

Hello Minh!

03 Feb 08 06:05, Minh Van Le wrote to All:

Atm the only way I can readdress mail is manually via BinkleyTerm.

How do I get Squish to re-address mail in the outbound directory after
it has been packed and compressed ? eg. There are Held packets
destined for 1:222/333 which I want to reroute to 4:555/666.

Netmail is routable, echomail is not. Bundles (and PKTs) can contain either or
both, so the Squish needs to know in advance (via ROUTE.CFG) in order to build the PKTs and bundles correctly for the correct destination address (intermediate or final), based on message type of individual messages.

If 4:555/666 receives packets with echomail that were built for 1:222/333, it is likely that there will be a horrible mess at 4:555/666 when he tries to toss
it, that dies right there...even if you do it manually in BT. Squish will either toss it all to his own netmail area, or rename the PKTs to BADs depending on security settings.

.\\ike

--- GoldED/2 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hello Mike !

On 07-Feb'08 13:30, Mike Tripp wrote to Minh Van Le:

How do I get Squish to re-address mail in the outbound
directory after it has been packed and compressed ? eg. There
are Held packets destined for 1:222/333 which I want to
reroute to 4:555/666.

Netmail is routable, echomail is not. Bundles (and PKTs)
can contain either or both, so the Squish needs to know in
advance (via ROUTE.CFG) in order to build the PKTs and
bundles correctly for the correct destination address
(intermediate or final), based on message type of
individual messages.

Ok. How do I reroute netmail after it has been packed and compressed ? can Squish do it ? or do I have to start using shell scripts.

--- Msged/386 4.30
* Origin: ypan.dyndns.org loves Msged... (3:712/104)

Hello, Minh...

Feb 09, 2008 at 16:48, Minh Van Le wrote to Mike Tripp:

Ok. How do I reroute netmail after it has been packed and compressed
? can Squish do it ? or do I have to start using shell scripts.

Squish can't do it. I have done it by hand, in the past. You have to uncompress
the archive into a .PKT file, then recompress it into the properly named archive and file attach it to the intended node.

At least I think that's what I did.

Regards,

Jerry Schwartz

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

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

Hello Minh!

09 Feb 08 16:48, Minh Van Le wrote to Mike Tripp:

Ok. How do I reroute netmail after it has been packed and compressed ?
can Squish do it ? or do I have to start using shell scripts.

I don't know of any way to convince Squish to extract anything from the outbound directory. If it is only netmail, then you might be able to update ROUTE.CFG with the appropriate statement for the addresses involved and then move the bundle from your outbound to your own inbound and toss it. If this method works, simple batch could handle it.

I have only done it manually myself...cutting the appropriate line for the bundlename in question from original .?LO file for the original address and pasting it into the new one. You may be able to get away with simply renaming the ?LO...assuming that everything in the original needs to be rerouted and there isn't anything already pending for the new address.

.\\ike

--- GoldED/2 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hello Jerry !

On 09-Feb'08 13:49, Jerry Schwartz wrote to Minh Van Le:

Ok. How do I reroute netmail after it has been packed and
compressed ? can Squish do it ? or do I have to start using
shell scripts.

Squish can't do it. I have done it by hand, in the past.
You have to uncompress the archive into a .PKT file, then
recompress it into the properly named archive and file
attach it to the intended node.

Ok.

Is there a tool to perform these actions non interactively ?

--- Msged/386 4.30
* Origin: ypan.dyndns.org loves Msged... (3:712/104)

HI MInh,

Minh Van Le wrote in a message to Jerry Schwartz:

Ok. How do I reroute netmail after it has been packed and
compressed ? can Squish do it ? or do I have to start using
shell scripts.

Squish can't do it. I have done it by hand, in the past.
You have to uncompress the archive into a .PKT file, then
recompress it into the properly named archive and file
attach it to the intended node.

Is there a tool to perform these actions non interactively ?

SOunds to me like you need to do some careful reworking of your route.cfg, which should be in the same directory as the squish executable and config file.

Regards,
Richard
--- timEd 1.10.y2k+
* Origin: Radio REscue net operations BBS (1:116/901)

Hello Richard !

On 12-Feb'08 18:18, Richard Webb wrote to Minh Van Le:

Minh Van Le wrote in a message to Jerry Schwartz:

Ok. How do I reroute netmail after it has been packed and
compressed ? can Squish do it ? or do I have to start using
shell scripts.

Squish can't do it. I have done it by hand, in the past.
You have to uncompress the archive into a .PKT file, then
recompress it into the properly named archive and file
attach it to the intended node.

Is there a tool to perform these actions non interactively
?

SOunds to me like you need to do some careful reworking of
your route.cfg, which should be in the same directory as
the squish executable and config file.

Yeah but I wanna readdress mail -after- it has been placed in outbound, because
I want to view a summary of all interzone netmail before they're sent eg. in the nifty BinklyTerm outbound zoom window.

The problem is those interzone netmails can be addressed to any random address eg. 5:111/123, 6:222/456, 7:444/789. Usually this isn't a problem because they would be routed through a single uplink which is performed by Squish at SQUASH time. However for my purposes, I don't want the PKTs bundled into 1 uplink address -until- ZMH so that I can inspect my outbound directory during daytime.
eg,

┌ Pending Outbound Mail ────────┐
│ Node Files Size Status │
│ 3:712/0 1 325b H ! │
│ 5:111/123 1 315b H │
│ 6:222/456 1 167b H │
│ 7:444/789 1 230b H │
└───────────────────────────────┘

This way I can see what interzone mail I got pending.

In other words I don't want to group all netmail straightaway for my uplink (3:712/0). If I did, all I would see in my outbound would be a big bundle for 3:712/0.

Node: 3:712/104@fidonet.org ypan.dyndns.org
┌ Zoomed Pending Outbound Mail ───────────────────────────────────────── ─
│ Node Files Bytes Age Calls Bad Status
│ 3:111/222@fidonet.org 1 325 1 0 0 H
│ 5:111/123@fidonet.org 1 315 1 0 0 H
│ 6:222/456@fidonet.org 1 167 1 0 0 H
7:444/789@fidonet.org 1 230 1 0 0 H │
│
│
│
│
│
│A Readdress mail [Alt/] G Get (request) File(s) │C/D/H/N Crash/Direct/Hold/Normal [Alt/] S Send File(s)
│I Reset Dial Tries [Alt/] P Poll a node
│R Kill requests T Stop mail
│K Kill all mail to node
│Page UP/DN Scroll Up/Down 1 Page UP/DN Arrow Move Up/Down 1 Line
│HOME Move to top of list END Move to end of list └─────────────────────────────────────────────────────────────────────── ─
BinkleyTerm Version 2.60-uSoft8.0(Unregistered) Press Alt-F10 For Help

Even if I used HostRoute or arranged an uplink in each zone (which is one stupid way to do it ...), I still can't achieve what I want because Squish can only perform addressing and/or bundling actions once.

Once the .flo's are created, you can't change or readdress anything with Squish. To my current knowledge you have to do it manually in BinkleyTerm or other mailer.

I was hoping for a clean way to readdress bundled mail using Squish.

But it sounds like I have to use shell scripts / batch files.

For example to reroute interzone (netmail) mail to 3:712/0:

merge.bat:
================================================
:: combine everything into 02c80000.hlo (3:712/0)
copy ftn\02c80000.hlo
ftn.1\*.hlo ftn.2\*.hlo ftn.4\*.hlo
ftn.5\*.hlo ftn.6\*.hlo ftn.7\*.hlo
ftn\02c80000.tmp

:: overwrite the old .hlo file
copy ftn\02c80000.tmp ftn\02c80000.hlo

del ftn.?\*.hlo
;
; poll NC here
;
================================================

or something crap like that.

--- Msged/386 4.30
* Origin: ypan.dyndns.org loves Msged... (3:712/104)

Hello Minh!

14 Feb 08 09:26, Minh Van Le wrote to Richard Webb:

The problem is those interzone netmails can be addressed to any random address eg. 5:111/123, 6:222/456, 7:444/789. Usually this isn't a
problem because they would be routed through a single uplink which is performed by Squish at SQUASH time. However for my purposes, I don't
want the PKTs bundled into 1 uplink address -until- ZMH so that I can inspect my outbound directory during daytime. eg,

The trick is not to bundle them for the destination that you never intend to connect with, so that you're not trying to "re-bundle" them for their actual destination later.

If you really are willing to sit on the netmails until ZMH, then you could initially send them as unrouted/HOLD/uncompressed PKTs throughout the day. This
allows you to view them individually in the outbound window without originating
connection attempts. Then add a Sched block for ZMH which actually CHANGEs them from HOLD to NORMAL and then ROUTEs them to the single uplink with whatever compression and flavor you like for that node. Squish can do that for
raw uncompressed PKTs already in the outbound.

Of course, you would have to rethink your default archiving setup in SQUISH.CFG
and global routing statements in ROUTE.CFG to make sure they don't collide with
or contradict this scheme and get the extra -s switch for SQUISH invocations to
tell Squish how/when to use the new schedule block.

.\\ike

--- GoldED/2 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hello Mike !

On 16-Feb'08 13:20, Mike Tripp wrote to Minh Van Le:

The trick is not to bundle them for the destination that
you never intend to connect with, so that you're not trying
to "re-bundle" them for their actual destination later.

If you really are willing to sit on the netmails until ZMH,
then you could initially send them as
unrouted/HOLD/uncompressed PKTs throughout the day. This
allows you to view them individually in the outbound window
without originating connection attempts. Then add a Sched
block for ZMH which actually CHANGEs them from HOLD to
NORMAL and then ROUTEs them to the single uplink with
whatever compression and flavor you like for that node.
Squish can do that for raw uncompressed PKTs already in the
outbound.

Of course, you would have to rethink your default archiving
setup in SQUISH.CFG and global routing statements in
ROUTE.CFG to make sure they don't collide with or
contradict this scheme and get the extra -s switch for
SQUISH invocations to tell Squish how/when to use the new
schedule block.

Yeah I already have a sched block

Sched RouteInterZone
Route Hold 3:712/0 World

and -s in BinkleyTerm batch ... just haven't figured out how to leave interzone
packets untouched.

I probably have to change

Send Hold World

in the global section to limit holds to zone 3.

Will experiment some time in future.

--- Msged/386 4.30
* Origin: ypan.dyndns.org loves Msged... (3:712/104)

Minh Van Le wrote in a message to Mike Tripp:

Yeah I already have a sched block

Sched RouteInterZone
Route Hold 3:712/0 World

and -s in BinkleyTerm batch ... just haven't figured out how to
leave interzone packets untouched.

I probably have to change

Send Hold World

What about using the "leave" command in route.cfg to not touch those messages, or let binkley or any other mailer see them until zmh?

For example: My feed is not available via pots mailer certain hours of the day. I use the leave command to hide mail destined for his system from the mailer until such time as he's up and running again.

Also, my system polls our zc twice daily for files and mail. YEt even if I have routed mail which goes through her system I don't want it tying up her system during zmh. SHe might have files on hold for me, and I'd just as soon not have her pots line tied up sending them then. Hence, I "leave" mail destined to her system, which is all interzone netmail etc.

Immediately after zmh I use "unleave" to process that mail and let my mailer see it.

Just "leave" mail destined to your routing target for all interzone mail until zmh. OR use the all and world wildcards. FOr example, during other periods of
the day you could leave all mail not for your zone as follows:

leave 1:all 2:all 4:all 5:all

Then during zmh:

unleave 1:all 2:all 4:all 5:all

THis way you can view them in whatever manner you usually use.

Hope that helps.


Regards,
Richard
--- timEd 1.10.y2k+
* Origin: Radio REscue net operations BBS (1:116/901)

Hello Richard!

20 Feb 08 02:35, Richard Webb wrote to Minh Van Le:

What about using the "leave" command in route.cfg to not touch those messages, or let binkley or any other mailer see them until zmh?

[...]

THis way you can view them in whatever manner you usually use.

Unfortunately, he wants to see them through the internal functionality of the mailer itself. "Leave" renames the ?LO files to extensions that the mailer doesn't recognize, so they "disappear" from the outbound window display.

.\\ike

--- GoldED/2 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

HI MIke,

Mike Tripp wrote in a message to Richard Webb:

What about using the "leave" command in route.cfg to not touch those messages, or let binkley or any other mailer see them until zmh?

THis way you can view them in whatever manner you usually use.

Unfortunately, he wants to see them through the internal
functionality of the mailer itself. "Leave" renames the ?LO files
to extensions that the mailer doesn't recognize, so they "disappear"
from the outbound window display.

Yah that wouldn't work. I just have a single keystroke from binkleyterm which gets me to the outbound directory and calls up inspect from DAvid Nugent. I can move around to other directories than my primary outbound if I so choose.


Regards,
Richard
--- timEd 1.10.y2k+
* Origin: Radio REscue net operations BBS (1:116/901)

Hello Minh!

18 Feb 08 13:30, Minh Van Le wrote to Mike Tripp:

Yeah I already have a sched block

Sched RouteInterZone
Route Hold 3:712/0 World

and -s in BinkleyTerm batch ... just haven't figured out how to leave interzone packets untouched.

How/why do you want the interzone mail handled differently than the intrazone? It appears that they're all routed to the same place at the same time currently?

Also, keep in mind that ROUTE will be looking for NORMAL mail. So if you are keeping them NoArc and HOLD until ZMH for viewing, you will need a CHANGE statement to make them NORMAL again before you get to the ROUTE command.

I probably have to change

Send Hold World

in the global section to limit holds to zone 3.

Probably not what you're really after, but:

Send Hold 3:All

is the wildcard method of limiting the command just to normal mail destined for
Zone 3.

.\\ike

--- GoldED/2 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hello Richard !

On 20-Feb'08 02:35, Richard Webb wrote to Minh Van Le:

I probably have to change

Send Hold World

What about using the "leave" command in route.cfg to not
touch those messages, or let binkley or any other mailer
see them until zmh?

I thought about the 'leave' command, and read it over a couple of times. I don't think it will work the way I want because it won't generate outbound until 'unleave' :)

I want to see any interzone mail queued until ZMH.

I will test it when I have time. But I'm sure 'leave' prevents Squish from scanning out particular mail, which means no .hlo is created to view using BinkleyTerm Outbound Zoom window.

--- Msged/386 4.30
* Origin: ypan.dyndns.org loves Msged... (3:712/104)