On Tue, 14 May 2013, Paul Quinn wrote to Mark Lewis:


 ml> i just wish i could figure out how to delay Taurus from sending 
 ml> normal netmails as soon as it sees them... "normal" as in not 
 ml> CRAsh or IMMediate... normal mail bundles wait until poll time 
 ml> before they are sent but netmails don't :?

 PQ> I'd say 'quit using the netmail routing table thing', and rely on
 PQ> the Cron/Outbound managers.  :)

the cron/outbound managers don't automatically pack netmail... that requires
another tool and i'd rather not go that way... frontdoor and db don't need
them and i'd rather not be stuck with blackhole routing if i don't have to
be... binkleyterm and most mailers that use BSO require that netmail be packed
externally... Taurus seems to be the first of the ART family that doesn't ;)

 PQ> I have two mail bundles holding at present: one to a 
 PQ> cron-configured node; the other depends on outbound mail.  One is 
 PQ> a direct-flavoured bundle to the cron-ed node and the other is 
 PQ> crash but the node is limited to ",U,THv"(!), which Radius 
 PQ> respects (clue: there can be multiple Tyz periods set for a node). 

i understand... if we can locate the source code for radius, that 'U'
requirement can easily be removed... if it is how i think it is, it would only
take commenting out two items in the code... a variable and the boolean
operator tying it to the Txy flag ;)

 PQ> Check your Config->Polls->Options(tab) dialogue.  Look for the two 
 PQ> tick-box options, particularly the "Prevent 'Direct' from 
 PQ> initiating a poll" option (it only has effect on the 
 PQ> cron-configured node).  Both options are ticked here.  You may 
 PQ> find more in Taurus[shrug].

other than the connection attempts counters and stand-off minutes for each,
the only other options are

  Transmit hold on outgoing (unchecked)
  Prevent 'Direct' from initiating a poll (unchecked)
  Force 'Normal' to initiate a poll (unchecked)

what i need is a way to schedule "events" as in mailer events which qualify
mail to be sent during that event... then a way to qualify that mail... what i
have right now is no way to specify that 'Normal' is held until a specific
mailer event... here is what the roughly google translated from russian to
english help section says about events...

[/quote]
Events

The event serves to change the line of the mail system. Such parameters may
be, for example, command-line modems, access file requests, minimum allowed
speed of the connection, etc.

In contrast to the periodic run applications and periodic calls, events in
themselves do not perform in a global system, and only affect the parameters
of the lines to which they are attached.

After the creation of the event do not forget to tie him to the lines (modem
or TCP / IP), for which it is intended!

Events tied to the line in the configuration dialog line Config / Dialup /
Line on the page Events.

The event has a periodicity, described in the format of cron, the duration of
exposure to the line, and a list of atoms. Duration of the event or can be
specified in days, hours and minutes, or event is determined by permanent.
Periodicity (ie the start of the event action) is given by either local time
(default) or in UTC.

Atom - a particle events affecting a particular line of argument, to which the
event is attached to.

For example, an event that changes the modem initialization string and a
string of necessary conditions continuity, contains two atoms - atom
replacement modem initialization string and replace the string atom conditions
necessary continuity.

See also:

Description of the format Cron,

A flag indicating whether the work site,

List of atoms.
[/quote]

i really do wish that i could find the taurusen hlp or chm file that was
available... translation from decompiled chm is extremely slow and cumbersome
as one has to translate each text section in the html code and then save the
page for viewing in a browser...

)\/(ark

--- FMail/Win32 1.60
 * Origin:  (1:3634/12.71)