Page MenuHomePhabricator

User:Ymblanter is continually having their email address unsubscribed
Closed, DeclinedPublic

Event Timeline

Legoktm raised the priority of this task from to Needs Triage.
Legoktm updated the task description. (Show Details)
Legoktm added subscribers: Legoktm, Ymblanter.

All the entries in the bounce_records table have a reason similar to Warning: message 1ZpQtM-0006IC-G5 delayed 48 hours (some say 24 hours).

First bounce I see was on 20151016043132.

@Ymblanter and you do actually receive emails when you expect to?

I wonder if this is just BounceHandler being over sensitive? It's not actually a bounce. delayed != undeliver(ed|able)

If someone is around, we will have to check the logs. We are not saving the entire bounce message as of now, so we might not be able to figure out which header in the bounced email caused bouncehandler to get confused, and mark it as bounce. Delayed emails are considered as soft-bounces, which Bouncehandler should never process, according to our regexp ( we have it for almost all standard mail servers )

Once a user re-verify his/her email address after getting email un-verified, the user gets un-subscribed when just '1' more bounce arrives from his email id, causing the user to confirm it frequently unlike waiting for a $threshold. The bouncehandler db is un-aware that the user has verified his email address, and the next time a bounce form his id come, it finds that there is a collection of bounces already existing back here ( > $threshold ) and immediately takes action.This is a bug/feature ?

If someone is around, we will have to check the logs. We are not saving the entire bounce message as of now, so we might not be able to figure out which header in the bounced email caused bouncehandler to get confused, and mark it as bounce. Delayed emails are considered as soft-bounces, which Bouncehandler should never process, according to our regexp ( we have it for almost all standard mail servers )

Mailserver logs? Not MW logs specifically?

reedy@fluorine:/a/mw-log/archive$ zgrep mccme.ru BounceHandler.log-2015*
BounceHandler.log-20151104.gz:2015-11-03 19:51:54 mw1002 enwiki BounceHandler INFO: Un-subscribed global user EMAILHERE for exceeding Bounce Limit 5  
BounceHandler.log-20151104.gz:2015-11-04 02:22:12 mw1002 enwiki BounceHandler INFO: Un-subscribed global user EMAILHERE for exceeding Bounce Limit 5  
BounceHandler.log-20151113.gz:2015-11-12 20:17:13 mw1016 enwiki BounceHandler INFO: Un-subscribed global user EMAILHERE for exceeding Bounce Limit 5  
BounceHandler.log-20151113.gz:2015-11-13 01:38:50 mw1011 enwiki BounceHandler INFO: Un-subscribed global user EMAILHERE for exceeding Bounce Limit 5  
BounceHandler.log-20151113.gz:2015-11-13 04:05:44 mw1006 enwiki BounceHandler INFO: Un-subscribed global user EMAILHERE for exceeding Bounce Limit 5  
BounceHandler.log-20151114.gz:2015-11-13 20:30:26 mw1015 enwiki BounceHandler INFO: Un-subscribed global user EMAILHERE for exceeding Bounce Limit 5  
BounceHandler.log-20151114.gz:2015-11-14 01:49:05 mw1007 enwiki BounceHandler INFO: Un-subscribed global user EMAILHERE for exceeding Bounce Limit 5  
BounceHandler.log-20151114.gz:2015-11-14 04:31:14 mw1006 enwiki BounceHandler INFO: Un-subscribed global user EMAILHERE for exceeding Bounce Limit 5  
reedy@fluorine:/a/mw-log/archive$ cd ..
reedy@fluorine:/a/mw-log$ grep mccme.ru BounceHandler.log 
2015-11-14 15:19:19 mw1010 enwiki BounceHandler INFO: Un-subscribed global user EMAILHERE for exceeding Bounce Limit 5  
reedy@fluorine:/a/mw-log$

For example, I have just got three test e-mails from Reedy (which are labeled as 1, 2, and 4).

For example, I have just got three test e-mails from Reedy (which are labeled as 1, 2, and 4).

I wonder where 3 went... We'll see

You seem to be having a few emails being sent (based on the number of bounce records in the db for your email).

Guess we need to wait until your get unsubscribed again... Will check the logs in the morning etc. Certainly if you get an Echo notification that you have been, please let us know ASAP :)

Reedy changed the task status from Open to Stalled.Nov 14 2015, 9:14 PM

Got unsubscribed again a few minutes ago. I did not connect my mail back yet, waiting for possible feedback from this task.

Got unsubscribed again a few minutes ago. I did not connect my mail back yet, waiting for possible feedback from this task.

Thanks for the heads up. I'll go have a look

Reedy changed the task status from Stalled to Open.EditedNov 15 2015, 4:26 PM
2015-11-15 16:07:35 mw1006 enwiki BounceHandler INFO: Un-subscribed global user <REMOVED>@mccme.ru for exceeding Bounce Limit 5.
Headers:
to: wiki-enwiki-8ouzf-nxqzx1-q4PCSychUsR+ieu/@wikimedia.org
subject: Warning: message 1ZxBCA-0002m5-72 delayed 48 hours
date: Sun, 15 Nov 2015 16:07:34 +0000
smtp-code: 550

http://www.serversmtp.com/en/error-550

Simply put, a 550 error code means that your SMTP server isn't able to deliver the sent email to the user because his mailbox does not exist: either the customer has entered it wrong (a typical example is something like mail@otmail.com instead of mail@hotmail.com), or the account has been deactivated and replaced with a new one (but you didn't know it).

@Ymblanter you might want to try also speaking to your mail provider as to why they're giving an error 550 for emails sent to you...

Yeah @Reedy. Its strange for the Mail server to return 550 for this case.

Reedy changed the task status from Open to Stalled.Nov 15 2015, 8:30 PM

Thanks, I will do it.

@Ymblanter: What was the result? Is this still a problem nowadays?

@Aklapper : Yes, I asked, and they did something. Now I am getting reminders from wikidata-bureaucrats-owner@lists.wikimedia.org (I am one of the maintainers of this list) but no messages from any list I am subscribed on. Trying to get a new password via the webmail interface (for example, to wikimedia-l) fails as well: I do not receive any mail with temporary password. I am not quite sure how to proceed.

Anyone knows if we still see smtp-code 550s for this user (assuming this is still a problem)?

I had to move to a different e-mail address since I could not do anything more on my side. Thanks for looking into it.

Understandable, and sorry that we could not track down the exact issue here.
Closing this task as declined as the "test case" is gone.