Getting E-Mails from inactive users

support
1

I’m using incoming mail support for group messaging with staged users.

This works fine if the address the message is coming from is new. However, I am re-purposing a Discourse installation for a yearly event, and some old users are stuck with an inactive accounts they can no longer log in to.

When such a user sends a mail to Discourse, they are rejected with Email::Receiver::InactiveUserError.
What’s the best method to prevent this issue? Would replacing the mail address of the inactive accounts work?

1 Like
2

Any thoughts here @zogstrip?

1 Like
3

The InactiveUserError happens only when the user is not activated and not staged. If you want your users to be able to send emails in, you will have to either activate their account or mark them as staged.

2 Likes
4

Can I mark existing, inactive users as staged? Would that have any side effects?

5

Other than enabling them to send emails in, none :wink:

1 Like
6

How can I do that, then? The admin UI does not offer this option.

Will they return to normal if they ever log in?

7

You’ll have to use the rails console or run a SQL query.

Yes.

1 Like
8

Hm, it looks like this doesn’t work.

I had a non-active, staged user (that had been disabled via the interface and staged via Rails). After the user logged in (via SSO), he had to confirm has address, became active and could log in, but is still staged:

Pasted image1425×609 43.7 KB

1 Like
9

Hmm, it might not unstage when using SSO. Having a look.

2 Likes
10

Thanks a lot!

In the meantime, for anyone who wants to try the same approach, here’s what I ran on the rails console (rails c inside the container):

User.where({ active: false }).update_all({ staged: true })
1 Like
11

You can do slightly shorter :wink:

User.where(active: false).update_all(staged: true)
2 Likes
12

I’ve given up understanding Ruby’s syntax a long time ago – even my version took many tries to be correct. Thanks for the shorter version :wink:

13

Just pushed a fix :helicopter:

https://github.com/discourse/discourse/commit/874c18cbc1c4768412cfe9ca08f416295f112c8b

4 Likes
14

After a journey into tests-passed lands, I can confirm this is fixed. Thanks a lot!

3 Likes