Hi Paul,

On 11 Jun 17 14:24, Paul Hayton wrote to Wilfred van Velzen:
  about: "Re: Fmail":

 PH> OK I fixed it (of sorts)

Good! ;)

 PH> The import process I use each time I run a poll to the NNTP server
 PH> generates 4 netmails per poll (an hourly thing). The Hudson base has a
 PH> limit of around 606/607 messages so when that filled up I hit problems.
 PH> That happened a long time ago... in a galaxy.. well you get the idea :)

 PH> I checked the netmail dir I had defined and there were some 11,000+ *.MSG
 PH> files sitting there unable to be imported.

 PH> I found in the docs the hudson base was called #NETM in the docs so I ran

 PH> ftoolsw32 delete #NETM
 PH> ftoolsw32 maint /h /d /n /o /p

 PH> then I removed all the old *.msg files.

 PH> Now I can add the delete and maint switched to run as part of nightly
 PH> maint to keep the base clear. It's only ever (I hope) going to get netmail
 PH> from the gateway tool that I use.

 PH> Do areafix netmail get stored there or are they just processed and
 PH> removed?

There are these settings regarding AreaFix messages:

   3.3.4     Mgr options

   For a more extensive explanation of some of the options below, see
   also paragraph 3.8.

   Keep requests

          Do not delete AreaMgr requests after they have been
          processed.

   Keep receipts

          Do not set the KILL attribute on receipts created by
          AreaMgr.

Besides that, they are just netmails that should be treated as such. But I
don't use a hudson area for my netmail, I keep them all as *.msg's. So I
don't know how that would work out exactly, with a hudson netmail area. And
so I don't use the 'import' funciton of FMail:

   4.3       Import

   Imports netmail messages destined for your system into the message
   base. A netmail board should be defined in FConfig. Whether or not
   messages to the Sysop should be imported can also be defined in
   FConfig. The /A switch tells FMail to ignore AreaMgr requests.


Wilfred.

--- FMail-W32 2.0.1.4