Using another email about selfmailbot

[grepto]

I think we should add another command to reset the email and re-confirm the user, so i will reopen this issue.

What is the point of having two different commands to change the e-mail address depending on whether or not the user has received any messages? It's a modality.

I suggest we use one command to change the address.

[f213]

Currently there is no option to reset the email. I think we should implement a command for that, like /reset — it should completely drop the user record from the db.

Feel free to make a PR for this :-)

[f213]

@fash1k
The command is implemented.

Just type /reset and the bot will ask you for the new email

[f213]

Unfortunately, reset command works only for non-confirmed users, e.g. when you did not received any email from the bot.

I think we should add another command to reset the email and re-confirm the user, so i will reopen this issue.

[f213]

@grepto This issue might be a challenge for you :-)

[f213]

I suggest we use one command to change the address.

I completely agree with you

[grepto]

I broke my head thinking why it should be challenge. Issue look simple. I guess we'll just have to add one more command handler for /reset. This handler should not have any filters.

Something like this

dispatcher.add_handler(CommandHandler('reset', reset_email))

Maybe there's some other reason why we can't reset email for users to whom bot has already sent mail?

[f213]

Maybe there's some other reason why we can't reset email for users to whom bot has already sent mail?

We should reset user's confirmation status during email reset — otherwise there will be an ability to confirm an email, change it, and send emails to the new, unconfirmed, one.

[grepto]

We should reset user's confirmation status during email reset

Agree. That's why I made a reset confirmation status for user when he use /reset

[f213]

The /reset command is usable in production now. Thank you @grepto!