When testing email-in to a category, I get Discourse::InvalidAccess in the rejected emails tab. The category is set to receive emails from any address. The security of the category does not include everyone, but this is on purpose. Is that the cause of the error?

Changing min_topic_title_length solved the issue: the default is 15 characters, but incoming emails had shorter subject lines.

Uh is that with discoursemail or different server system? There will be an error if you are trying to reply to e-mail with different address than what notification mail was sent to. If you are trying to start a new topic there may be some other problem.

Yes this is supposed to create a new topic…

That is supposed to work regardless of if security of category is not open to everyone, e-mails will create a new topic post.

It would be useful to test and reproduce this issue to verify there is no bug… I’m going to reset the setting and retry… Duh… The default was 15 characters, not 10. (Edited solution above.)

Email-in Discourse::InvalidAccess [min_topic_title_length]

Product Support

Heliosurge (Dan DeMontmorency) December 23, 2023, 11:42pm 2

@anon36555649 has some recent XP with reply/post by email.

Topic		Replies	Views
Private sub-category email-in Discourse::InvalidAccess Product Support email	10	617	January 18, 2024
"Email in allowed groups" setting is too permissive Product Support email , mailing-list	4	528	January 30, 2024
Category not accepting "anonymous email" from known users Bug	29	4242	June 12, 2026
Creating a topic via email without write access to the category? Product Support	3	1809	January 11, 2019
Title character limit exception Product Support	2	445	July 10, 2020

Email-in Discourse::InvalidAccess [min_topic_title_length]

Related topics