Project

General

Profile

Actions

tickets #112016

closed

Still Can't Verify E-mail Address when challenged by lists.opensuse.org

Added by drankinatty@suddenlinkmail.com over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Email
Target version:
-
Start date:
2022-06-04
Due date:
% Done:

100%

Estimated time:

Description

Henne, Per, all,

In the last ticket I described this problem where my ISP
(suddenlinkmail.com) rejects mail from lists.opensuse.org. This happens
randomly depending on which mail-host the incoming message hits. Per had a
work-around and I got most mail for a while, but I'm still stuck when I try
and login at the mailing lists archive because the challenge verification
e-mail never makes it to me. This is from:

https://lists.opensuse.org/accounts/confirm-email/

Verify Your E-mail Address

We have sent an e-mail to you for verification. Follow the link provided to
finalize the signup process. Please contact us if you do not receive it within
a few minutes.

The problem is my registered e-mail is:

drankinatty@suddenlinkmail.com (which randomly bounces)

I set up another e-mail on gmail

drankinatty@gmail.com

Which is where I asked that the challenge verification go (that may mean
having to add an e-mail or change my primary for the lists mails) If at all
possible, I would like to keep the suddenlinkmail.com mail address as gmail
doesn't show posts I send to the list. But for now:

What can we do so I can pass the challenge verification?

Thanks for any help you can give. (you may want to also send replies to
drankinatty@gmail.com to make sure I see them)

--
David C. Rankin, J.D.,P.E.

Actions #1

Updated by drankinatty@suddenlinkmail.com over 2 years ago

On 6/4/22 16:39, redmine@opensuse.org wrote:

[openSUSE Tracker]
Issue #112016 has been reported bydrankinatty@suddenlinkmail.com.


tickets #112016: Still Can't Verify E-mail Address when challenged by lists.opensuse.org
https://progress.opensuse.org/issues/112016

* Target version:

This message came through no problem. Thanks for looking into it.

--
David C. Rankin, J.D.,P.E.

Actions #2

Updated by pjessen over 2 years ago

  • Category set to Email
  • Private changed from Yes to No

drankinatty@suddenlinkmail.com wrote:

randomly depending on which mail-host the incoming message hits. Per had a
work-around and I got most mail for a while,

Yeah, it was at most a quick kludge based on some guess-work. I can re-instate it, but it will not work in the long run. We can't fix the incompetence of your provider :-(

But for now:
What can we do so I can pass the challenge verification?

I have re-enabled the kludge, so "mx2.mx-altice.prod.cloud.synchronoss.net" (mx for suddenlinkmail.com) always resolves to 65.20.48.3.
The kludge is an update to /etc/hosts plus forcing postfix to read /etc/hosts.

Actions #3

Updated by drankinatty@suddenlinkmail.com over 2 years ago

On 6/5/22 07:09, redmine@opensuse.org wrote:

[openSUSE Tracker]
Issue #112016 has been updated by pjessen.

Category set to Email
Private changed from Yes to No

drankinatty@suddenlinkmail.com wrote:

randomly depending on which mail-host the incoming message hits. Per had a
work-around and I got most mail for a while,

Yeah, it was at most a quick kludge based on some guess-work. I can re-instate it, but it will not work in the long run. We can't fix the incompetence of your provider :-(

But for now:
What can we do so I can pass the challenge verification?

I have re-enabled my band-aid, so mails "mx2.mx-altice.prod.cloud.synchronoss.net" (mx for suddenlinkmail.com) always resolves to 65.20.48.3.

Bandaid working great. Let's hope this hack works for a while longer. Thank
you for your help!

--
David C. Rankin, J.D.,P.E.

Actions #4

Updated by pjessen over 2 years ago

drankinatty@suddenlinkmail.com wrote:

Bandaid working great. Let's hope this hack works for a while longer. Thank
you for your help!

Well, I'm not really keen on maintaining such workarounds, but I guess it doesn't hurt. It will however be dropped again, at some point. Or it'll break when your provider changes something. From my perspective, there are really just two options -

  • fix your provider
  • change email address.
Actions #5

Updated by pjessen over 2 years ago

  • Status changed from New to Resolved
  • Assignee set to pjessen
  • % Done changed from 0 to 100

pjessen wrote:

From my perspective, there are really just two options -

  • fix your provider
  • change email address.

I'm closing this - my 'fix' will get dropped at some point, maybe your provider will have seen fit to fix the issue by then.

Actions

Also available in: Atom PDF