Closed
Bug 602057
Opened 14 years ago
Closed 13 years ago
[tracker] SMTPRecipientsRefused errors
Categories
(support.mozilla.org :: Code Quality, task, P3)
support.mozilla.org
Code Quality
Tracking
(Not tracked)
VERIFIED
FIXED
2.6
People
(Reporter: jsocol, Assigned: paulc)
References
Details
(Whiteboard: [qa-])
I've seen a couple SMTPRecipientsRefused stack traces trickle through. They all appear to have come from questions.tasks.send_confirmation_email, which uses send_mail instead of send_mass_mail, fortunately. I don't think we need the whole stack trace every time someone types in an invalid email address, though. We should be fine to log it and move on.
Reporter | ||
Updated•14 years ago
|
Target Milestone: 2.3 → 2.4
Reporter | ||
Updated•14 years ago
|
Target Milestone: 2.4 → Future
Reporter | ||
Comment 1•13 years ago
|
||
There are a lot of these, in different places, with different solutions. For registration we should show an error and (probably) delete the user to free up the name and let the user try again. For anonymous notifications we should seriously consider removing the watch. For authenticated notifications we should follow Twitter's example of marking the user, not trying to send notifications, and telling them that recent attempts to email them have failed. Etc. So I'm turning this into a tracker and going to file blockers against it.
Priority: P5 → P3
Summary: Investigate SMTPRecipientsRefused errors → [tracker] SMTPRecipientsRefused errors
Reporter | ||
Comment 2•13 years ago
|
||
Info, courtesy of Wil: http://support.socketlabs.com/index.php/Knowledgebase/Article/View/65/
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → paulc
Whiteboard: [qa-]
Assignee | ||
Comment 3•13 years ago
|
||
Closing this. We can go beyond what we do now and use the suppression list in comment 2, if it's worth it. However, we delete users upon registration if we can't email them, and we only get a handful of stack traces periodically. So I doubt it's a huge problem. I say file separate bug if/once it's an issue. Atm, all blocking bugs are closed!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: Future → 2.6
You need to log in
before you can comment on or make changes to this bug.
Description
•