In a message to Anthony about areafix, Paul said:

PE> I thought the squish routing commands might have
PE> automatically attempted to dial out straight away when you
PE> next get into Binkley.  Next time you do the run, just

I does work.

PE> DON'T make any other changes to the batch file!!!

Too late!

There's one last line I would like to either unrem or delete:

del binkley.scd

the binkley schedule file.  Is there any point in deleting it?

PE> I wouldn't have thought you got them in the QWK packets,
PE> but maybe you are complaining about them being in your
PE> messagebase?

Both.  But I thought I saw a config statement somewhere that lets me
turn them off?  Anyway, it's fine the way it is now, thanks.

Also, since modifying msgareas.ctl to limit the messagebase to a
certain number of days rather than a certain number of messages, Max
now complains when its processing .rep uploads, that I specified an
invalid area number and asks me to select a new area.  All the areas
are tagged in the QWK section, so it isnt that.  It seems to be
happening to messages bound for any and all echos.  Here's a bit of my
msgareas.ctl file that is typical.

Area 4

        MsgAccess       Disgrace

        Type            Squish
        MsgInfo         AUST_AVTECH
        MsgName         AUST_AVTECH

        EchoMail        MSG\AVTECH\

        Public Only
        MsgOverride Enter Normal
        MsgOverride Reply Normal
        MsgOverride Kill  Normal
        MsgOverride Upload Normal
        Renum Days 21

End Area

Also, the Public Only line - is that the one that stops echomail
messages with the PVT flag set from being seen?  What do I do to
be able to see messages with PVT set.  (occasionally/accidentally
people set the PVT flag...)

Lastly, when polling for mail, Binkley says that the outbound packet
(replies) is truncated after its finished.  It also leaves the file in
the outbound directory, albeit zero bytes in length.  Is this
"normal"?  A part of a typical binkley.log file:

: 11 Nov 21:31:52 BINK Dialing 436-1785
# 11 Nov 21:32:11 BINK Connect 14400/Arq/V32/Lapm/V42Bis
* 11 Nov 21:32:17 BINK Intro: * Address 3:711/934{at}fidonet Using
BinkleyTerm-OS/2
* 11 Nov 21:32:18 BINK Ten Minute Limit (3:711/934{at}fidonet)
* 11 Nov 21:32:18 BINK Remote Uses BinkleyTerm Version 2.50
: 11 Nov 21:32:19 BINK Sysop: Paul Edwards
* 11 Nov 21:32:19 BINK Password-protected session
: 11 Nov 21:32:19 BINK Session method: ZedZap
+ 11 Nov 21:32:25 BINK CPS: 1332 (7994 bytes)  Efficiency: 92%
+ 11 Nov 21:32:25 BINK Sent-Z/32 Outbound\00000000.th1
  11 Nov 21:32:25 BINK File Outbound\00000000.th1 truncated
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Well, almost lastly, I've noticed that after polling early in the
evening, and then polling to send the replies back later that night,
that there is sometimes another inbound packet sent.  How often does a
packet get made for me?  And at what time/s?  I thought outbound point
packets would only be processed once, and after your early morning
poll?

'tnt, Amfony.


--- Maximus/2 2.01wb