There is no status update, per se’

 

We struggle with downstream post offices along the way all the time marking us as spam creators given what is being aliased through arrl.net.

 

With the one example Dick provided we are having an in-depth conversation with the vendor to see what the deal is with this particular account.  Jim will also broaden the discussion to other potential error causes such as server timeouts and non-deliverable messages which again are sourced at the server level.

 

Frankly, arrl.net is a remarkable time sink for this organization that shows very little benefit compared to what its original intent was.  And when it was created, there was little to no anti-spam engines on mail servers auto blacklisting sites or domain alias servers.  It was simple to implement and move on from.

 

Stay tuned.

 

David

 

From: arrl-odv <arrl-odv-bounces@reflector.arrl.org> On Behalf Of Kristen McIntyre
Sent: Monday, April 18, 2022 3:11 PM
To: arrl-odv <arrl-odv@arrl.org>
Subject: [arrl-odv:33655] Re: Problem With ARRL.net Forwarding

 

I’m getting a number of emails about this.  Can we get a status update?



On Apr 16, 2022, at 5:29 PM, Richard Norton via arrl-odv <arrl-odv@reflector.arrl.org> wrote:

 

There is a problem with ARRL.net forwarding.

 

See below.

 

73,

 

Dick, N6AA

 

 

----- Forwarded Message -----

Cc:

Sent: Sat, Apr 16, 2022 at 4:33 PM

Subject: Failure Notice

Sorry, we were unable to deliver your message to the following address.

 

550: 5.1.1 <n6tv@arrl.net>: Recipient address rejected: User unknown

 

---------- Forwarded message ----------

_______________________________________________
arrl-odv mailing list
arrl-odv@reflector.arrl.org
https://reflector.arrl.org/mailman/listinfo/arrl-odv

 

                                    -Kristen (K6WX)

"Your eyes ... it's a day's work just looking into them" 
                                       Laurie Anderson

(--... ...--  -.. .  -.- -.... .-- -..-)