Closed Bug 1104897 Opened 10 years ago Closed 9 years ago

Get email working on Thunderbird blog (change main email address)

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rkent, Unassigned)

References

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/150] [] )

+++ This bug was initially created as a clone of Bug #1101801 +++

My admin access to the Thunderbird blog is working, but I was unable to change the main email contact from the current jb@mozilla.org to kent@caspia.com  This is needed so that I can get email to moderate comments. As a workaround, I disabled emails for moderation so that I will need to check the site regularly to moderate comments.

The WP part seemed to work, in that I could change the field, then it claims that it needs to verify the address kent@caspia.com  But that email is never received.

I suspect that the SMTP settings are incorrect in the configuration for the blog.
Whiteboard: [kanban:webops:https://kanbanize.com/ctrl_board/4/1891]
Whiteboard: [kanban:webops:https://kanbanize.com/ctrl_board/4/1920]
Summary: Give Kent James access to the Thunderbird blog → Please add the Mozilla Thunderbird blog to Mozilla Planet
Summary: Please add the Mozilla Thunderbird blog to Mozilla Planet → Get email working on Thunderbird blog (change main email address)
can you provide the URL to the blog?

Thanks
Here is the admin page:

https://blog.mozilla.org/thunderbird/wp-admin/
:rkent - i can confirm that the account has been linked to kent@caspia.com. with regards to outbound email, i know for certain that works on the blog.mo platform since i receive messages from it frequently.

i do see that your account authentication type is still set to LDAP - is this new account a valid mozilla community LDAP account? if not, we'll want to change that to (wordpress) local authentication.
Flags: needinfo?(kent)
OS: Windows 8.1 → All
Hardware: x86_64 → All
On the admin page (Settings/General Settings/E-mail address) it still says:

E-mail address: jb@mozilla.com  ... There is a pending change of the admin e-mail to kent@caspia.com.

So what exactly did you confirm to be kent@caspia.com?

kent@caspia.com is a Mozilla LDAP account, not sure which kinds there are. The password that I use to login in an LDAP account password, and as far as I know it is valid as an LDAP account.

I can turn back on moderation emails and see what happens.
Flags: needinfo?(kent)
@rkent - I've tried re-setting the admin e-mail address for the blog to kent@caspia.com.  Please let me know if you received the email message that needs to be confirmed before the change will take effect.

Looking in the mail logs, I see three messages sent to kent@caspia.com:
   Dec  8 18:22:40
   Dec 15 13:39:30
   Jan  6 23:40:31 (right after I tried re-setting the admin email address)

I don't see any error messages associated with trying to send the message (e.g. it says 'status=sent').  I'm wondering if something is dropping the message / marking it as spam between our mail server and yours.
Thanks for confirming status in your email logs.

In the next week or so I'll be changing the MX records for caspia.com to a different account, eliminating one email hop in the process. The most likely issue right now is some sort of interaction issue involving the first hop (either with mozilla or with the final email repository). Rather than try to fix something that is likely to change, let's wait a week or so after I have changed the MX record for caspia.com, then I'll try again.
Whiteboard: [kanban:webops:https://kanbanize.com/ctrl_board/4/1920] → [kanban:https://webops.kanbanize.com/ctrl_board/2/150] []
@rkent: 

  1) Were you able to make the MX record changes for caspia.com and
  2) Have there been any changes in your ability to get the admin email confirmation message?
I did that MX change yesterday. Just now I tried again to change the admin email address and this time it went through. Not sure what was blocking the email before, but as I hoped changing the email infrastructure fixed the issue.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.