1. Forum
  2. Fidonet
  3. HAM

  • Cox Blocking Mesages From ARRL.ORG

    From Al Kaiser@1:142/926 to All on Wed May 5 07:34:03 2021
    I am currenly having an issue with COX who is blocking any bulletins or Newletters coming from ARRL.ORG. I have two tickets open with them on the problem. But they don't take any action and close them after about a week.
    I keep reopening them to no avail.

    The Messages stopped sometime mid December. When I gave COX the approximate date they said that was about the time they updated their secuity software which blocks any messages they consider mass mailing spam.

    But even that does not stop REAL Spam from arriving but it does prevent ligitimate Bulletins and Newsletters.

    I'm guessing I'm not getting mail from other groups too. I just have not figureed out which ones.

    Anyone not receiving ARRL Bulletins and Newsletters and that has COX should call them and start a ticket on the problem. Maybe if they see a slew of complaints they will go back and fix their security software.

    GL to the DESERIVING like they say!

    Al Kaiser n1api@cox.net <=-

    Stay Healthy 'n Wealthy!

    Al Kaiser - Meriden, CT, 05-May-2021 at 7:34.
    Fido : 1:142/926 - Internet : n1api@cox.net

    .!. Sometimes I wake up grumpy... other times I let her sleep.
    --- Terminate 5.00/Pro
    * Origin: When did you last warm yourself with a Terminate! (1:142/926)
  • From Brian Rogers@1:142/103 to Al Kaiser on Wed May 5 12:01:00 2021
    Al et al;

    I am currenly having an issue with COX who is blocking any bulletins or Newletters coming from ARRL.ORG. I have two tickets open with them on the problem. But they don't take any action and close them after about
    a week. I keep reopening them to no avail.

    Many larger ISPs also block any IP beginning with 44. This is due to the fact that way back in the day it was listed as purely an "experimental" network
    so most of the big boys filtered it as potential spam when in fact most
    spam seems to come from those who filter out the hams such as Yahoo, AmazonAWS (where Winlink is hosted) and so on.

    Usually a nice note to postmaster@ clears the filters. Good luck.

    73 de Brian N1URO



    ... The number you have dailed...Nine-one-one...has been changed.
    --- MultiMail/Linux v0.52
    * Origin: Carnage - risen from the dead (1:142/103)
  • From Al Kaiser@1:142/926 to Brian Rogers on Tue May 18 09:27:44 2021
    Brian Rogers wrote to Al Kaiser Subject: Cox Blocking Mesages From

    Many larger ISPs also block any IP beginning with 44. This is
    due to the fact that way back in the day it was listed as purely an "experimental" network so most of the big boys filtered it as
    potential spam when in fact most spam seems to come from those who
    filter out the hams such as Yahoo, AmazonAWS (where Winlink is
    hosted) and so on.

    As I mentioned on the club's reflector I think they found the problem,
    I've seen a couple of things from the ARRL incduding the PFB which had not arrived since December.

    Hopefully they got it.

    Al Kaiser n1api@cox.net <=-

    Works for me!

    Al Kaiser - Meriden, CT, 18-May-2021 at 9:27.
    Fido : 1:142/926 - Internet : n1api@cox.net

    .!. Someday you might enjoy a little 7 of 9 and a half running around!
    --- Terminate 5.00/Pro
    * Origin: Life Sucks and then you die! (1:142/926)
  • From Brian Rogers@1:142/103 to Al Kaiser on Tue May 18 09:43:00 2021
    Al Kaiser wrote to Brian Rogers <=-

    As I mentioned on the club's reflector I think they found the problem, I've seen a couple of things from the ARRL incduding the PFB which had
    not arrived since December.

    Hopefully they got it.

    K1STM has issues with Frontier sending to me. Going through my logs there's
    not even a connection attempt from Frontier to me. Some of these larger ISPs think they can do whatever. What they don't realize is the S in iSp stands for "service". When you're providing mail services and don't send out mail to
    the remote destination but report false errors back to the customer, you're GOING TO GET CAUGHT.

    I've even caught Comcast deploying routers deliberately broke in Comcast's designs. They wanted to know who helped me with my detective work. I refused
    to rat out who it was. All they know is it was someone within Cisco... and
    I do have contacts there <G>. I reported them to Channel 8's consumer watch
    and they didn't want to know. Morale of the story: Rich get richer, poor get crapped on.

    ... Jim Beam up, Scotchy!
    --- MultiMail/Linux v0.52
    * Origin: SBBS - Carnage! 73 de N1URO in Hartford, Ct (1:142/103)