locked Subject Tags #GeneralGroupInfo


John, K9MM
 

I thought it was OK to use a new subject tag if the subject didn't already have an appropriate one at the end of the digest. I had some questions about FST4 so I sent a message with the subject line
"JT9 vs FST4 #FST4". It would have been OK if the message had gone to a moderator for review, but it actually bounced.
======================================================
This is an automatically generated Delivery Status Notification.


Delivery to the following recipients failed permanently:

* main@wsjtx.groups.io

Reason: Permanent Error


Reporting-MTA: dns; resqmta-ch2-04v.sys.comcast.net [69.252.207.36]
Received-From-MTA: dns; resomta-ch2-03v.sys.comcast.net [69.252.207.99]
Arrival-Date: Mon, 15 Feb 2021 21:14:23 +0000


Final-recipient: rfc822; main@wsjtx.groups.io
Diagnostic-Code: smtp; 500 Members are not allowed to create new hashtags. Please resend your message using only approved hashtags in the subject.
========================================================
So I resent the message with this subject line and it went through
"JT9 vs FST4 vs Q65 #Q65"

The original message DID address Q65 tangentially, but it mainly was about JT9 and FST4. There are no APPROVED tags for either FST4 or JT9.

I don't want to start a long discussion about this, but just suggesting perhaps the tag process needs to be massaged a bit. Thanks!

73,

John, K9MM


Bob Cutter <ki0g@...>
 

I had some issue, sent one to config#?  No response, yet. 

Bob KI0G




On Wednesday, February 17, 2021, 8:01 AM, John, K9MM <johnb3030@...> wrote:

I thought it was OK to use a new subject tag if the subject didn't
already have an appropriate one at the end of the digest. I had some
questions about FST4 so I sent a message with the subject line
"JT9 vs FST4 #FST4". It would have been OK if the message had gone to a
moderator for review, but it actually bounced.
======================================================
      This is an automatically generated Delivery Status Notification.


Delivery to the following recipients failed permanently:


Reason: Permanent Error


Reporting-MTA: dns; resqmta-ch2-04v.sys.comcast.net [69.252.207.36]
Received-From-MTA: dns; resomta-ch2-03v.sys.comcast.net [69.252.207.99]
Arrival-Date: Mon, 15 Feb 2021 21:14:23 +0000


Final-recipient: rfc822; main@wsjtx.groups.io
Diagnostic-Code: smtp; 500 Members are not allowed to create new
hashtags. Please resend your message using only approved hashtags in the
subject.
========================================================
So I resent the message with this subject line and it went through
"JT9 vs FST4 vs Q65 #Q65"

The original message DID address Q65 tangentially, but it mainly was
about JT9 and FST4. There are no APPROVED tags for either FST4 or JT9.

I don't want to start a long discussion about this, but just suggesting
perhaps the tag process needs to be massaged a bit. Thanks!

73,

John, K9MM




Roger
 

On 17/02/2021 15:01, John, K9MM wrote:
I thought it was OK to use a new subject tag if the subject didn't already have an appropriate one at the end of the digest. I had some questions about FST4 so I sent a message with the subject line
"JT9 vs FST4 #FST4". It would have been OK if the message had gone to a moderator for review, but it actually bounced.
Hi John

That hashtag now exists and I've created others to ensure they exist for every mode.

We're bound by what is possible on groups.io and I don't think it's possible to create a hashtag in that manner.


73
Roger
G#4HZA
moderator