Subj : Compression question To : Peter Knapper From : Bo Simonsen Date : Tue Jul 22 2003 12:20 pm Mon 2003-07-21 20:00, Peter Knapper (3:772/1.10) wrote to Bo Simonsen: PK>> Note that Squish provides specific methods of handling PK>> Netmail and/or Echomail, or both. Unless something is broken in the PK>> version you are using. BS>> Okey, i haven't seen them in the documentation, would BS>> you be kind to show them? PK> Its really a combination of using the Squish control parameters in PK> the appropriate way. Ehh, people who doesn't eventbased/automatated tossing have no chance to do that. PK> Most people seem to forget that the PK> commandline parameters provide subtle control, and yet it is PK> possible to use them in conjunction with a control file that allows PK> very selective processing, as long as thats what you want to do. PK> Overall, you may need to perform multiple passes to do things PK> exactly as you want. Can you explain that a little bit more? PK> In addition, you can use the SEND and ROUTE commands to process PK> traffic for a specific set of nodes, and then the output of those PK> commands is NOT included in any other ROUTE statement processing PK> that encompass those nodes within a global statement (EG 4:ALL). Ehh, You can override the routing table in the commandline? PK> However note that this ALL must happen within ONE Squish operation PK> to work this way. Yes. BS>> Nearly zero nodes allows echomail routing! PK> Very true, few nodes will permit it, but it can certainly be done That's right. Today where nearly all the mail is transfered thru the internet, it wouldn't matter. PK>> What doesn't work about Zonegating (with unix), or more specficaly, PK>> what part of Zonegating is not working? BS>> The gateroute thing, it created a new message, whitch BS>> it marked sent, but it forgot to mark the original BS>> message sent too, to it keeps sending that message... PK> Hold on, Zonegating and GateRouting are 2 quite different things, PK> are you perhaps trying to mix them? Also note that "A ZoneGate" is PK> a specific system, but "ZoneGating" is the act of moving traffic PK> between Zones. The first is a Nodelisted system, whereas anyone can PK> perform the second. In brief - Well the GateRouting statement is routing mail to other zone to the zonegate, but still keep the original reciptent in the INTL line, and that does not work well, i try so late as yesterday to work out the problem, i did take some of it. PK> GateRouting was primarily used for non-3D aware systems where the PK> Zone info was not able to be understood and handled correctly. PK> Traffic could be routed via a Zonegate that ensured the Zone detail PK> was handled correctly between such systems. Are you SURE you really PK> need to use GateRoute these days, its highly unusual to find PK> someone using code that is not 3D aware these days... Most editors can make the Gating by their self, but fx. if a netmail is sent by maximus it can't. But yes i don't guess it matter if you use Zonegating or not. Sometimes i can be good to not use it. I should sent a netmail to 4:930/1, i sent it by zonegate but i got on Hold at his ZC, and he wasn't pollable, if i did sent it routed, it got catched up by another node. Whitch was a ip node, there put it on Hold. PK> I have never PK> had to use GateRoute so I can't be sure, but it sounds like you may PK> be generating your 2D output back into a 3D area and creating Dups PK> as a result. No? PK> Zonegating is simply used to trim Seen-by's for Echomail exporting PK> to another Zone, where Seen-by's can be duplicated and does not PK> necessarily relate to using "official" Zonegates at all. ZoneGating PK> reduces message sizes as well. It's _netmail_ zonegating. Regards, Bo --- timEd/Linux 1.11.b1 * Origin: The Night Express, Roennede Dk (2:236/100) .