In a support thread titled ‘Email-in Discourse::InvalidAccess [min_topic_title_length]’, hellekin reports receiving Discourse::InvalidAccess errors when testing email-in to a restricted category, despite allowing emails from any address. Heliosurge directs them to anon36555649, who clarifies that email replies must match the original sender’s address, but new topics via email should work regardless of category security settings. hellekin confirms they’re trying to create new topics. anon36555649 affirms this should be allowed. Eventually, hellekin identifies the root cause: the default min_topic_title_length is 15 characters, but incoming emails had shorter subject lines. After correcting this, the issue resolved. hellekin suggests testing and reproducing the issue to confirm no underlying bug, noting they had initially misstated the default as 10 instead of 15 characters.
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?
@anon36555649 has some recent XP with reply/post by email.
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.
Changing min_topic_title_length solved the issue: the default is 15 characters, but incoming emails had shorter subject lines.
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.)