| |
I0OJJ > JNOS 05.06.20 04:12l 122 Lines 3901 Bytes #-1779 (0) @ WW
BID : 362A5_I0OJJ
Read: DF7EAV DJ6UX GUEST DG8NGN
Subj: Re: wierdness of mailmsg command
Path: DB0FHN<OE2XZR<OE5XBL<F1OYP<IZ3LSV<I3XTY<I0OJJ
Sent: 200605/0211z @:I0OJJ.ITA.EU [Rome] #:14757 $:362a5_I0OJJ
>From i0ojj@i0ojj.ampr.org Fri Jun 5 04:11:25 2020
Received: from [44.134.32.240] by i0ojj.ampr.org (JNOS2.0n) with SMTP
id AA114757 ; Fri, 05 Jun 2020 04:11:25 +0200
>From: Gustavo <i0ojj@i0ojj.ampr.org>
Organization: SICD Rome
Message-ID: <bf71413c-9e73-2715-6140-21825c9362a5@i0ojj.ampr.org>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:68.0) Gecko/20100101
Thunderbird/68.8.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Hi Maiko and all,
since I have gained 'no access' to the ML, just reply by using
the packet-radio.
> Langelaar maiko at xxxxxxxx.yy
> Thu Jun 4 15:20:59 EDT 2020
> Subject: wierdness of mailmsg command
>
> _______________________________________________________________________
>
> something I have never noticed with mailmsg till now ?
>
> mailmsg ve4klm TEST
>
> sends me a mail, no subject line, and body TEST
>
> mailmsg ve4klm TEST "testing blah"
>
> sends me a mail, subject TEST, and body testing blah
>
> I didn't write that :)
>
> Maiko
>
> _______________________________________________________________________
Now, issuing the 'mailmsg' command, the JNOS reply:
Usage: mailmsg <to> [<subj>] <msg|/pathname>
but this results as a wrong/incomplete indication, so, since many
many years ago, I dropped the following note to explain to me
about this (discrepance) command; as follows:
-----------------------
1.11x1 (960422) [update 'for sysop only'] (i0ojj)
To make it easier to queue smtp messages from the console, I added a
"mailmsg" command, that is compiled in when MAILMSG is #define'd.
The syntax is: mailmsg <to_addr> ["<subject>"] "<msg|/pathname>"
and serves to send email to <to_addr> with an optional subject
header.
The <msg> string becomes the body of the message.
If <msg> begins with a forward or backward slash, or begins with a
DOS drive specification, it is taken as the path to a file to be
sent as the message body.
N.B.: the '"' sign *must* be placed to both the 'subject' and to the
'message/pathname' fields:
i.e.: mailmsg jnos@ww "JNOS-2.0k.2 is running here!" "/jnos/info"
that's all!
-----------------------
Then, the better setup of 'log trigger' was that found as below:
# Mon 11 May 2020 06:41:52 PM CEST
log on
# 18Apr2020, Maiko (VE4KLM), NEW log (action) triggers
log trigger "fwd failed&" "mailmsg i0ojj FBBFWD fwd_failure"
log trigger "lzhuf&error&" "mailmsg i0ojj FBBCOMP lzhuf_error"
# log trigger "adding mbox|" "sh ./adding.sh"
log timer 300
#
Not fully understood the following command line and the conntent
of 'shell' command:
log trigger "adding mbox|" "sh ./adding.sh"
---------------
Found also that the 'FBBFWD Proposals checksum err (ff)' as below
is actually not recognized/reported by the 'log trigger'
---------------
21:00:59 - privs [8192] directory [/jnos/public 8192]
21:00:59 - i3xty perms 2000 (8192)
21:00:59 I3XTY-3 @ IQ3BLX - MBOX (i3xty) open
21:01:01 I3XTY-3 @ IQ3BLX - MBOX (i3xty) forwarding
21:01:01 I3XTY-3 @ IQ3BLX - MBOX (i3xty) incoming proposal FA B NS2B
USA ALL 53092_NS2B 1660
21:01:01 I3XTY-3 @ IQ3BLX - MBOX (i3xty) incoming proposal FB B DL0BN
DL DISTRI QA25IJDB0BLO 2547
21:01:01 I3XTY-3 @ IQ3BLX - MBOX (i3xty) incoming proposal FB B G4APL
WW PACKET 55705_GB7CIP 4045
21:01:01 I3XTY-3 @ IQ3BLX - MBOX (i3xty) incoming proposal FB B JN1VSI
JPN CONDX 95UJH4XSY007 3903
21:01:01 I3XTY-3 @ IQ3BLX - MBOX (i3xty) incoming proposal FB B LW3DBH
LATNET MSWIN 64610_LW3DBH 4341
21:01:01 I3XTY-3 @ IQ3BLX - MBOX (i3xty) FBBFWD Proposals checksum err (ff)
21:01:01 I3XTY-3 @ IQ3BLX - MBOX (i3xty) FBB error, last read : F> EA
21:01:01 I3XTY-3 @ IQ3BLX - MBOX (i3xty) exit
--
73 and ciao, gustavo i0ojj/ir0aab/ir0eq
A proud member of linux team
Quidquid latine dictum sit, altum videtur
Read previous mail | Read next mail
| |
