Closed
Bug 1054342
Opened 11 years ago
Closed 9 years ago
Message for the password reset is received too late
Categories
(Cloud Services :: Server: Firefox Accounts, defect)
Cloud Services
Server: Firefox Accounts
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: mstanke, Unassigned)
References
()
Details
On the Czech support forum, we have received some complaints about too late delivered e-mails for the Firefox Sync registration or password reset. Here is a header of one of those e-mails (for password reset). The user stated, this occurs repeatedly even when he tried to resend the e-mail.
> Delivered-To: xxxxx@volny.cz
> Received: from mail-g1.snat.cent (mail-g1.snat.cent [10.32.3.100])
> by gmmr2.centrum.cz (Postfix) with QMQP id DA7376000315
> for <xxxxx@volny.cz>; Sat, 9 Aug 2014 15:10:16 +0200 (CEST)
> Received: from a27-128.smtp-out.us-west-2.amazonses.com by bq (envelope-from <00000147b9752c82-ac52cb20-45e5-44c6-936f-0508ab7b7172-000000@us-west-2.amazonses.com>, uid 201) with VF-scanner
> (bq.virusfree.cz
> Clear:RC:0(54.240.27.128):SA:0(2.9/5.0):.
> Processed in 0.495853 secs); 09 Aug 2014 13:10:16 -0000
> X-Spam-Status: No, hits=2.9 required=5.0
> X-Spam-Level: **
> X-VF-Scanner-Mail-From: 00000147b9752c82-ac52cb20-45e5-44c6-936f-0508ab7b7172-000000@us-west-2.amazonses.com via bq
> X-VF-Scanner-Rcpt-To: xxxxx@volny.cz
> X-VF-Scanner: (RC:0(54.240.27.128):SA:0(2.9/5.0):. Processed in 0.495853 secs Process 29073)
> Received: from a27-128.smtp-out.us-west-2.amazonses.com (54.240.27.128)
> by bx.virusfree.cz with ESMTPS (AES128-SHA encrypted); 9 Aug 2014 15:10:15 +0200
> Received-SPF: pass (bq: domain of us-west-2.amazonses.com designates 54.240.27.128 as permitted sender) client-ip=54.240.27.128; envelope-from=00000147b9752c82-ac52cb20-45e5-44c6-936f-0508ab7b7172-000000@us-west-2.amazonses.com; helo=a27-128.smtp-out.us-west-2.amazonses.com;
> DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
> s=hsbnp7p3ensaochzwyq5wwmceodymuwv; d=amazonses.com; t=1407565769;
> h=Date:Message-Id:From:To:Subject:Content-Type:MIME-Version:Feedback-ID;
> bh=xkgo3/SXr1GIf8Hfcbv/Uay0hY6d/KttZ1HnGOGfNFs=;
> b=OVtmKCwllGyx+zLnZgEPylT4cwrNm4SjWBQlIACKTZ+h0i4MtAHTUCI1tjCj/uPV
> 9HCVBswF0wrxVU4MWFqBSvoD+sTFvMhU3fzQqzX6rsP/P0ovB6ZhUFyLw9nTUgR87lV
> mBcwExQI5YF7y1uIpPFLgwsuQKGcsHzZ4zic2emc=
> DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
> s=dd4gchik5xsqzclqaslfwpn6hdfiawc2; d=accounts.firefox.com;
> t=1407565769;
> h=Date:Message-Id:From:To:Subject:Content-Type:MIME-Version;
> bh=xkgo3/SXr1GIf8Hfcbv/Uay0hY6d/KttZ1HnGOGfNFs=;
> b=W7ZNpE2ublA6UUodJsh/Z9cQp5ZD6IOTkqYPDD7NokklV2f9UbrQCaTcOXbLitl4
> EwHDENWfhcZeCJXPrnY0bwBnoCjdtHwJP2E2ymYLTwhf9pjf2RZMBIMZDLi8GISD/rs
> OGBr7/ea0vCCYfm7OihNAz59i9uamW4xn0Tcy91g=
> X-Mailer: Nodemailer (0.6.5; +http://github.com/andris9/nodemailer;
> smtp/0.3.32)
> Date: Sat, 9 Aug 2014 06:29:29 +0000
> Message-ID: <00000147b9752c82-ac52cb20-45e5-44c6-936f-0508ab7b7172-000000@us-west-2.amazonses.com>
> X-Recovery-Code: 381367b0e2fb07320b156bb4673804cf
> X-Link: https://accounts.firefox.com/v1/complete_reset_password?token=2fe3693fa2427e9ac17b8f734246bb38007d129c70daf7d1e1b75af27d3a2488&code=381367b0e2fb07320b156bb4673804cf&email=xxxxx%40volny.cz&service=sync
> Content-Language: cs
> From: "Firefox Accounts" <verification@accounts.firefox.com>
> To: xxxxx@volny.cz
> Subject: Obnovit heslo
> Content-Type: multipart/alternative;
> boundary="----Nodemailer-0.6.5-?=_1-1407565769716"
> MIME-Version: 1.0
> X-SES-Outgoing: 2014.08.09-54.240.27.128
> Feedback-ID: us-west-2.dmVyaWZpY2F0aW9uQGFjY291bnRzLmZpcmVmb3guY29t:AmazonSES
Reporter | ||
Comment 1•10 years ago
|
||
I know this issue is quite old, but does anybody know, why this happened? Just want to know in case it occurs again in the future.
Comment 2•9 years ago
|
||
Unfortunately I can't add anything useful here, and the issue is old enough now that I doubt we can do any useful debugging. Email deliverability continues to be an interesting and challenging problem...
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•