OpenBCM V1.07b11 (WIN32)

Packet Radio Mailbox

DBO595

[LAU JN59RM]

 Login: GAST





  

NL2ZTM > BPQ32    13.01.16 18:30l 106 Lines 3770 Bytes #999 (0) @ WW
BID : 6178_NL3ZTM
Read: GAST
Subj: Fwd: Re: [BPQ32] killing NTS messages
Path: DBO595<BX0RBL<FRA199<FRA485<FRB001<NL3WAM<NL3ZZE<NL3ZTM
Sent: 160110/0022Z 6178@NL3ZTM.ZH.NLD.EU BPQ1.4.65




-------- Doorgestuurd bericht --------
Onderwerp: 	Re: [BPQ32] killing NTS messages
Datum: 	Sat, 9 Jan 2016 09:15:31 -0500
Van: 	Dave druliefw@gmail.com [BPQ32] <BPQ32@yahoogroups.com>
Antwoord-naar: 	BPQ32@yahoogroups.com
Aan: 	BPQ32@yahoogroups.com



It seems to me that any NTS type messages need to be kept on file for a 
specific period of time.
Once an NTS message is killed, it probably should not be purged for at 
least that time, keeping the message available but with a K status. NO? 
John, could that be set up as an option to set the time to keep killed 
NTS Traffic. I keep my MARS traffic for one year.
73
Dave
AFA2HV


On 1/9/2016 8:13 AM, 'John Wiseman' john.wiseman@cantab.net [BPQ32] wrote:
>
> It seems there is a disagreement between NTS operators. I was asked 
> towards
> the end of 2014 to allow any user to kill NTS messages. Unfortunately I
> can’t remember who it was who asked. Perhaps whoever it was could join 
> this
> discussion.
>
> 73,
> John
>
> ________________________________________
> From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com]
> Sent: 09 January 2016 12:31
> To: BPQ32@yahoogroups.com
> Subject: RE: [BPQ32] killing NTS messages
>
>
> I agree
> Grant WB6OTS
> NTS 12th Regional Digital Hub
>
> From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com]
> Sent: 9 January, 2016 2:21 AM
> To: BPQ32@yahoogroups.com
> Subject: [BPQ32] killing NTS messages
>
>
> Hi all,
>
> it seems to me that a normal user (not sysop) is
> allowed to kill NTS message with any status (except
> for already killed messages).
>
> >From my perspective only a sysop should be allowed
> to kill NTS messages. Any thoughts?
>
> Best regards, Peter
>
> This email has been sent from a virus-free computer protected by Avast.
> www.avast.com
>

__._,_.___
------------------------------------------------------------------------
Posted by: Dave <druliefw@gmail.com>
------------------------------------------------------------------------
Reply via web post 
<https://groups.yahoo.com/neo/groups/BPQ32/conversations/messages/18542;_ylc=X3oDMTJyYWwzNnZiBF9TAzk3MzU5NzE0BGdycElkAzE1Njk5MTI3BGdycHNwSWQDMTcwNTA2MzEwOARtc2dJZAMxODU0MgRzZWMDZnRyBHNsawNycGx5BHN0aW1lAzE0NTIzNDg5MzU-?act=reply&messageNum=18542> 
	• 	Reply to sender 
<mailto:druliefw@gmail.com?subject=Re%3A%20%5BBPQ32%5D%20killing%20NTS%20messages> 
	• 	Reply to group 
<mailto:BPQ32@yahoogroups.com?subject=Re%3A%20%5BBPQ32%5D%20killing%20NTS%20messages> 
	• 	Start a New Topic 
<https://groups.yahoo.com/neo/groups/BPQ32/conversations/newtopic;_ylc=X3oDMTJma2RmMTlhBF9TAzk3MzU5NzE0BGdycElkAzE1Njk5MTI3BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNudHBjBHN0aW1lAzE0NTIzNDg5MzU-> 
	• 	Messages in this topic 
<https://groups.yahoo.com/neo/groups/BPQ32/conversations/topics/18538;_ylc=X3oDMTM3cnFxNThyBF9TAzk3MzU5NzE0BGdycElkAzE1Njk5MTI3BGdycHNwSWQDMTcwNTA2MzEwOARtc2dJZAMxODU0MgRzZWMDZnRyBHNsawN2dHBjBHN0aW1lAzE0NTIzNDg5MzUEdHBjSWQDMTg1Mzg-> 
(4)

Visit Your Group 
<https://groups.yahoo.com/neo/groups/BPQ32/info;_ylc=X3oDMTJmZTNxYzRiBF9TAzk3MzU5NzE0BGdycElkAzE1Njk5MTI3BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDdnRsBHNsawN2Z2hwBHN0aW1lAzE0NTIzNDg5MzU-> 


  * New Members
    <https://groups.yahoo.com/neo/groups/BPQ32/members/all;_ylc=X3oDMTJnN3R2aDFvBF9TAzk3MzU5NzE0BGdycElkAzE1Njk5MTI3BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDdnRsBHNsawN2bWJycwRzdGltZQMxNDUyMzQ4OTM1>
    3

Yahoo! Groups 
<https://groups.yahoo.com/neo;_ylc=X3oDMTJlc2VxamNiBF9TAzk3NDc2NTkwBGdycElkAzE1Njk5MTI3BGdycHNwSWQDMTcwNTA2MzEwOARzZWMDZnRyBHNsawNnZnAEc3RpbWUDMTQ1MjM0ODkzNQ--> 

• Privacy <https://info.yahoo.com/privacy/us/yahoo/groups/details.html> 
• Unsubscribe 
<mailto:BPQ32-unsubscribe@yahoogroups.com?subject=Unsubscribe> • Terms 
of Use <https://info.yahoo.com/legal/us/yahoo/utos/terms/>

..

__,_._,___





Lese vorherige Mail | Lese naechste Mail


 22.03.2026 17:45:22lZurueck Nach oben