Closed Bug 377313 Opened 17 years ago Closed 17 years ago

wiki.mozilla.org password reset emails not going out

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Type:
task
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nelson, Assigned: oremj)

References

(
URL
)

Details

After having succesfully logged in to wiki.mozilla.org in the past,
and having succesfully edited and created pages there in the past,
I tried to login there today, at
http://wiki.mozilla.org/index.php?title=Special:Userlogin
but it told me my password was wrong.

So, I pressed the "E-mail password" button, and it replied:

> A new password has been sent to the e-mail address registered for "Nelsonb". 
> Please log in again after you receive it.

But I never received any such email.  I have tried this repeatedly.
I never receive any email from wiki.  

Consequently, I cannot edit any more pages on wiki.mozilla.org. :-(

This same problem was reported to me yesterday by another user, 
Alexei Volkov.  Alexei and I have mail accounts with different mail 
service providers, so this is not simply a problem with a single shared
mailbox provider.
This works for me.  Please check you spam filters.  The e-mail is coming from sysadmins@mozilla.org.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
No problem with spam filters.  
Again, problem is seen by multiple users.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
This is what I see in the mail logs:

Apr 12 10:11:25 mrapp04 sendmail[28879]: l3CHBNTt028879: to=Nelsonb <nelson@bolyard.com>, ctladdr=apache (48/48), delay=00:00:02, xdelay=00:00:00, mailer=relay, pri=30633, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (l3CHBPbY028880 Message accepted for delivery)
Apr 12 10:11:26 mrapp04 sendmail[28882]: l3CHBPbY028880: to=<nelson@bolyard.com>, ctladdr=<apache@mrapp04.mozilla.org> (48/48), delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=120866, relay=inbound.netidentit...rehostedemail.com. [64.97.139.1], dsn=5.0.0, stat=Service unavailable
Apr 12 10:31:39 mrapp04 sendmail[29267]: l3CHVa2G029267: to=Nelsonb <nelson@bolyard.com>, ctladdr=apache (48/48), delay=00:00:03, xdelay=00:00:00, mailer=relay, pri=30633, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (l3CHVdlX029268 Message accepted for delivery)
Apr 12 10:31:39 mrapp04 sendmail[29270]: l3CHVdlX029268: to=<nelson@bolyard.com>, ctladdr=<apache@mrapp04.mozilla.org> (48/48), delay=00:00:00, xdelay=00:00:00, mailer=esmtp, pri=120866, relay=inbound.netidentit...rehostedemail.com. [64.97.139.1], dsn=5.0.0, stat=Service unavailable

Please look in your logs for mails for alexei.volkov sent yesterday, also.

Question regarding this string from comment 3:
> relay=inbound.netidentit...rehostedemail.com.
                          ^^^
Do you really see that ellipsis?  or is there a longer string there?
If the longer/full string in available, please paste it in here.

So, are those emails queued up somewhere due to the "service unavaailable" 
statuses??
Add me to the list.

I'm using a different provider than Nelson (gmx.de) and the confirmation mail doesn't arrive here either.

I've tried with my both sun.com and gmail.com addresses. Non of them is working.  
Note if you are using gmail: the email confirmation is flagged as spam, check that folder.
Note this:

ctladdr=<apache@mrapp04.mozilla.org>

It should not be using mrapp04.mozilla.org as the domain name, that domain doesn't exist outside our firewall.  Is this machine one of the recent redeploys?  If so it sounds like the MTA config for the cluster never got pushed to it.  Try rsyncing /etc/mail to it off mrapp01
Severity: critical → major
Would you all mind trying again.

Thanks.
It works now, but here is the full story:


Earlier today I tried again to confirm using an address at the gmx.de domain. No message arrived.

Then I updated my wiki profile to use an address at the redhat.com domain. Still no email.

But then, with an delay of about 1-2 hours, I received two messages to the redhat.com address, sent at the same minute.

I clicked the link latter  and I was told I had to log in.
So I logged in first. Nothing happened.

I went back to the email and clicked the link again.

NOW IT WORKS.

Thanks


I believe this is fixed on the app side.  Thanks for the bug, sorry for the inconvenience.
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Assignee: server-ops → oremj
Well, it may be  better now, but I still am not receiving any of these 
mails, and so still cannot login to wiki.m.o.  I've tried several more
times today.  

Jeremy, 
please paste the log lines from my most recent attempts here as a comment, 
so that I can pass them on to my mail service provider for investigation.  
I expect them to tell me that wiki.m.o is now on some RBL thing.

Alexei, what results are you getting?
Yes, it works now. I found the email in the spam folder of gmail account.
Apr 13 08:32:04 mrapp04 sendmail[13638]: l3DFW2lY013638: to=Nelsonb <nelson@bolyard.com>, ctladdr=apache (48/48), delay=00:00:02, xdelay=00:00:00, mailer=relay, pri=30633, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (l3DFW4gP013639 Message accepted for delivery)
Apr 13 08:32:05 mrapp04 sendmail[13641]: l3DFW4gP013639: to=<nelson@bolyard.com>, ctladdr=<apache@mrapp04.mozilla.org> (48/48), delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=120866, relay=inbound.netidentit...rehostedemail.com. [64.97.139.1], dsn=5.0.0, stat=Service unavailable
Apr 13 11:21:52 mrapp04 sendmail[15709]: l3DILoAo015709: to=Nelsonb <nelson@bolyard.com>, ctladdr=apache (48/48), delay=00:00:02, xdelay=00:00:00, mailer=relay, pri=30633, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (l3DILqIY015710 Message accepted for delivery)
Apr 13 11:21:52 mrapp04 sendmail[15712]: l3DILqIY015710: to=<nelson@bolyard.com>, ctladdr=<apache@mrapp04.mozilla.org> (48/48), delay=00:00:00, xdelay=00:00:00, mailer=esmtp, pri=120866, relay=inbound.netidentit...rehostedemail.com. [64.97.139.1], dsn=5.0.0, stat=Service unavailable


Dave do you have any idea why this is happening?
The mail server is not accepting mail from our hosts - you'll need to fix the mail server listed as the mx for your domain:

bolyard.com.            1800    IN      MX      10 inbound.netidentity.com.cust.securehostedemail.com.
bolyard.com.            1800    IN      MX      20 inbound.netidentity.com.cust.securehostedemail.com.
(In comment #8, dave miller wrote)
> Note this:
> 
> ctladdr=<apache@mrapp04.mozilla.org>
> 
> It should not be using mrapp04.mozilla.org as the domain name, that domain
> doesn't exist outside our firewall.  

I believe that is the issue.  And as shown in the latest log lines, it is
still this way, this is unchanged.  

> Is this machine one of the recent
> redeploys?  If so it sounds like the MTA config for the cluster never got
> pushed to it.  Try rsyncing /etc/mail to it off mrapp01

Yes, please try that.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
> Is this machine one of the recent
> redeploys?  If so it sounds like the MTA config for the cluster never got
> pushed to it.  Try rsyncing /etc/mail to it off mrapp01

It wasn't a redeploy and is already using the config off of mrapp01
ok, so resyncing is NOT the solution for the problem Dave described.
Please find another solution.
Looks like your mail provider is overly aggressive - can you talk to them about whitelisting Mozilla?

[root@mrapp04 ~]# telnet inbound.netidentity.com.cust.securehostedemail.com 25
Trying 64.97.139.1...
Connected to inbound.netidentity.com.cust.securehostedemail.com (64.97.139.1).
Escape character is '^]'.
220 n107.sc1.cp.net ESMTP Service (7.2.069.1) ready
helo mrapp04.mozilla.org
250 n107.sc1.cp.net
mail from: <apache@mrapp04.mozilla.org>
550 mail not accepted from blacklisted IP address [63.245.208.146]

IIRC, the recent bot attack caused wiki to send out zillions of bogus emails.
I think the blacklisting was done as an act of self-preservation.
I'll see if I can get them to undo it.
no more action from IT - closing.
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.