On Sun, 16 Nov 2014, Björn Felten wrote to Paul Quinn:

 BF> Now, if only you could add a CM flag to your nodelist entry, so
 BF> that the mail to you get sent immediately without having to wait
 BF> for your ZMH, all would be back to normal.

 BF>    I don't remember how I fixed this in Argus... :(

there's like three or four ways to get to the overrides for each node... i use
the CTRL-T -> NODES tab override grid to place the overrides i need... 

3:640/384    "quinnspost.nodelist.net",CM,IBN

the only problem with the above is if/when that FQDN changes... BUT i think i
found a way to handle that in the taurus docs for the overrides section... if
i am reading the following correctly, one can use the FTN address in the
override field...

3:640/384    3:640/384,CM,IBN

i just tested this override and it works fine... it takes the FQDN from the
nodlist as it should and then overrides the flags so that the CM is used... i
haven't checked (yet) if this 2009 v5.101 taurus handles the ICM flag...
before i was using the 2006 v5.001 taurus... and then just today i've found
out that there's a v5.114 2013 version of taurus out there some where... i'm
on the hunt for that now...

anyway, see the "or indirectly" example in the 6th paragraph below... this
whole section is everything needed to know for node overrides ;)

[quote google translate of taurus docs]
Nodes
Grid overrides TCP / IP nodes, which can be overridden for a node, one or more
IP-Adros, ports or protocols. You can also override the flags and runtime
node, instead of the listed IP - nodes.

Table overrides TCP / IP nodes is similar to the table overrides modem nodes.

You can work with the Taurus without a list IP-nodes, pointing here
IP-addresses of nodes on which you usually call.

Format override the node address, flags. One redefinition can contain multiple
nodes, listed by a space.

Node operating on IP, must contain one of the dedicated TCP / IP-flags. In
this Taurus will produce a connection attempt on all of the flags of protocols
in the following order: BinkP, Raw, Telnet.

Address to override can be set both in digital and in character (DNS) form,
that is, as the name of an Internet host. To specify the address in symbolic
form it must be enclosed in quotation marks: "fido.ritlabs.com",CM,IFC. The
address can be specified directly (eg 193.219.215.111,CM,IFC) or indirectly
(for example, 5:133/555,CM,IFC), in the latter case the number is removed from
the current list of nodes. To override the IP-port value specified after his
address through an underscore: "fido.ritlabs.com"_23,CM,IFC or "
93.219.215.111"_23,CM,IFC

The line input Auxiliary Nodes File, you can specify the path to the
additional overrides TCP / IP-nodes that will be used in addition to these in
the grid. The file format is as follows (the override one node per line):


Address | Overrides

Additional file overrides loaded into memory at startup Taurus, as well as
detecting flag file IPOVR.OK in Home Directory. The results are reflected in
the download file prozvonok chronology.

Consider the case where a node is not in the list of nodes, or in the DNS, but
you asked the address of its host without flags indicating the work. The
implication is that a node can only receive calls in ZMH (a point at all).
Therefore, the appearance package with priority Crash or Direct to send buffer
will serve Taurus signal to establish outgoing connections to the node only in
its ZMH. Point C in this case Taurus generally will not try to establish an
outgoing connection. Continuity can not also occur due to the fact that flags
the node is not fully spelled out, and / or can not comply with the conditions
limiting prozvonok.
[/quote]



)\/(ark

If you think it's expensive to hire a professional to do the job, wait until
you hire an amateur.

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