TIP: Click on subject to list as thread! ANSI
echo: maximus
to: DALE SHIPP
from: JACK SMITH
date: 1997-05-05 09:21:00
subject: Re: Boss in SEENBY

On May 03, 1997, Dale Shipp wrote:
 JS> ; For a point at 2:201/506.3, the following configuration would be
 JS> used: ; Address 2:201/506.3
 DS>  The problem that I had was that when I only put my Boss
 DS> node on the configuration line for the echos, Squish
 DS> refused to pack the outgoing  mail for him, because it saw
 DS> that his node was already in the SEEN-BY  (when in fact it
 DS> was really mine that was there).  To over come that,  what I
 DS> have had to do as a work around is to tell SQUISH that I
 DS> want to distribute the echo to one of his other node
 DS> numbers (and allow receipt  from his first node number).
 DS>  I.e. here are a few lines from my config file:
 DS>  EchoArea  COOKING   E:\IM\MAIL\SQ\COOKING  -$d45  1:261/1137 1180
 DS>  EchoArea  MUFFIN    E:\IM\MAIL\SQ\MUFFIN   -$d7   1:261/1137 1180
 DS> Why didn't what you say work for me? (i.e. having only
 DS> 261/1137 on the distribution for the echos?)
Well... I stand corrected, Dale.  I mistakenly assumed that if one followed 
the docs for Max 3.01/Squish 1.11 and set both up as specified for a 4D 
point, all would work fine.  It doesn't and what you say is true.  Max puts 
the boss node's 2D address in the seen-by (seen-by addresses are always 2D 
(FTS-4)) and Squish will not scan out the messages to the boss because of 
this.
I don't know if this is true of older versions of Max.  At one time I had a 
point who was running a full BBS (using Max) but it was an older version, 
probably 2.01wb.  I don't remember him having problems with getting the mail 
scanned out but that was several years ago.  The reason why my other points 
have no problems is simple: they use sysop message editors that don't put 
anything in the seen-by so Squish just does its thing.
While trying various config methods I discovered what looks like a good 
workaround-- especially if your boss only has one node number.
In MAX.CTL:
  Address 1:116/30.1
  Address 1:30226/1
In SQUISH.CFG:
  Address 1:116/30.1
  Pointnet     30226
If set up this way, Squish will scan and archive to 1:116/30 (.0) with a 
correct packet format.  The "30226" is a fakenet number that was assigned to 
me back in the late 80s by the Fido IC but you could use it or (better) one 
of your own to accomplish the end result you're looking for.  55555 would 
work just as well.
Max puts 30226/1 in the seen-by instead of 116/30.  When Squish sees it, it 
recognizes that it is a "fakenet" address (because of the Pointnet verb) and 
strips it out when doing the "Out Squash".  Then, 116/30 is added to the 
seen-by when the outbound packet is constructed.  The 30226/1 address is 
never seen outside of the originating system so all is as it should be.  I 
checked the packets made in this manner and they had the correct originating 
address (1:116/30.1) in the packet header and 116/30 in the seen-by.
Sorry about the misinformed post.
 -Jack
  ogre@nashville.com
--- Squish/386 v1.11
---------------
* Origin: UltraTech - Nashville, TN * PRIVATE * {V.34/V.FC} (1:116/30)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.