| |
N1URO > JNOS 19.10.19 19:49l 28 Lines 1239 Bytes #999 (0) @ WW
BID : 12208_N1URO
Read: GUEST
Subj: Mail on hold
Path: IW8PGT<IR2UBX<DB0RES<DB0OVN<DB0GOS<ON0AR<OZ5BBS<CX2SA<GB7CIP<ED1ZAC<
IZ3LSV<I3XTY<I0OJJ<N1URO
Sent: 191008/1033z @:N1URO.#JNOS.CT.USA.NOAM [Unionville] #:12210 $:12208_N1URO
>From n1uro%n1uro.#jnos.ct.usa.noam@i0ojj.ampr.org Tue Oct 8 12:35:39 2019
Received: from i0ojj.ampr.org by i0ojj.ampr.org (JNOS2.0k.3b2) with SMTP
id AA28460 ; Tue, 08 Oct 2019 12:35:39 +0200
Message-Id: <12208_N1URO@n1uro.bbs>
>From: n1uro@n1uro.#jnos.ct.usa.noam
X-JNOS-User-Port: Circuit (CTJNOS:N1URO-7 N1URO-7) -> Sending message
Greetings;
I've figured out how to unhold mail in JNOS and have approached Maiko with an
idea on how to handle this. Hopefully he'll be able to oblige us who run JNOS.
Hopefully it'll be a very simple add-on to the code. It only requires a one
line deletion in the message header to unhold mail in JNOS and it does not
affect the area spool file (area.txt).
My idea for Maiko was to add a prompt after reading held mail with the RH
command to allow the sysop to either release it as good or allow the sysop
to kill the message. In some cases JNOS actually does bag dupe mails so it
should be fairly simple for the sysop to determine what to do with held mail.
I was going to write a script to handle this via cron BUT it would risk more
dupes being sent out in the case where JNOS did infact flag a message held
because of a possible dupe.
Hopefully Maiko will embrace my mail :)
73 de N1URO
Read previous mail | Read next mail
| |
