Continuing the discussion from Email-in Discourse::InvalidAccess : The Discourse::InvalidAccess hit again. This time, the length of Subject is not in cause. I’m suspecting that it has to do with the category being a restricted sub-category. But the category is set to receive email from addresses wit…

I think people use emailing into a group as an alternative, if that could be useful?

I rebuilt after a (noop) git pull, and now it seems to be working with the second domain added to Postfix’s relay_domains. Before these series of tests, and with the change, I had no more error, but emails did not appear at all, neither in the category nor in the error logs. In containers/mail-rece…

Somehow the failure returned. This is a bit ridiculous, because previous tests were OK. Now after another rebuild, incoming email is refused again. I resorted to repeat the git pull then rebuild dance but this time it did not seem to work. I suspect the sub-category situation may be playing, unless…

[이미지] hellekin: But the category is set to receive email from addresses without an account, so I would expect the email to go through and create a new topic. Are these rejected emails from users who do already have an account?

Some yes. Emails from people with no accounts are rejected (but the category is set to receive email from addresses without an account). Emails from people in the authorized groups seem to get through fine. Emails from people with an account but no access to the category are rejected. It seems t…

For the ones who do have an account but don’t have access to the category, it’s expected that those would be rejected. The Accept emails from anonymous users with no accounts only applies to staged users, and those with an existing account have the category permissions applied. It’s odd that people…

So apparently the rejection is handled by the endpoint at /admin/email/smtp_should_reject.json. [이미지] JammyDodger: It’s odd that people with no accounts are being rejected. Could this be because of the changes you made to the mail receiver? I made the change because emails were bouncing. I f…

I think you’re right @JammyDodger , staged users go through, existing users with normal access to the category go through, but existing accounts without access cannot send email to the category. I guess a workaround would be to create a CFP group without any notification for the category that compri…

That could… Probably this is what should be done. Do you know whether a group with a muted category will have precedence over another group with the same category set to watching?

So, to summarize: Given a private category with email-in authorized for unknown email addresses (i.e., belonging to no existing account, AKA staged user) → if an email comes in from an unknown address: it is delivered to the private category → if an email comes in from a known address: it is d…

비공개 하위 카테고리 email-in: Discourse::InvalidAccess

지원

JammyDodger 1월 18, 2024, 12:08오후 9

그것이 유용할 수 있다면, 사람들은 그룹으로 이메일을 보내는 것을 대안으로 사용하는 것 같아요.

글		댓글	조회수
Category not accepting "anonymous email" from known users Bug	29	4100	6월 12, 2026
Private support categories: staged users can email in, but not registered users Support	4	1669	3월 27, 2019
Mail address per category Feature	7	2565	3월 20, 2017
"Email in allowed groups" setting is too permissive Support email , mailing-list	4	495	1월 30, 2024
Creating a topic via email without write access to the category? Support	3	1791	1월 11, 2019

비공개 하위 카테고리 email-in: Discourse::InvalidAccess

Related topics