• Support

  • Problems when mail driver down

Hi! I am new to the community although running a flarum forum for more than 2 years now. I couldn't find, however, a place to post Issues on github and hopefully this is a good place to get visibility.

I think there is a design flaw in the current Flarum iteration. When your email API provider (Mailgun in my case) is down, o misconfigured, users get an error when posting an answer in a thread. And then they retry and they get duplicates. Also when they quote, the quote disappears.

It seems to me this is a design error, the action of actually checking to send a notification should not block the posting of new answers in a thread. It should be an async call and if it fails, well, it fails and you throw an error. But it should not break the posting feature which is more important.

Maybe I am misunderstanding it (worked with Laravel years ago, but not the best one), but I think it could be a better solution than the current one.

Thank you! I really like Flarum, although I would really like to understand it better so i can customise the front-end and the SEO, which I am quite used to in Nuxt and Next.

    DaniBerlanga first it would be great if you could provide more information on your issue and setup as described in our troubleshooting guide. Besides that I asume you don't have any form of queue running? If so - then it's clear that you receive issues when your mails can't go out as likely there is a notification being sent out on most posts. You can easily solve this by using redis or a db queue extension/setup.

        GreXXL

        Thank you for such a fast answer. No my forum is small, and I don't have Redis or any queuing system. We used to have IronMQ back in the day for our laravel SaaS, but for this small scale (it is almost like a private forum) it is absolutely overkill.

        I think the problem resides in a timeout of Mailgun (first time it was due to wrong configuration of the SMTP keys, second time it was actually a massive downtime of all Mailgun services) and the front-end keeps on waiting for an answer and it never arrives. So the new post dialog never closes, and the new posts never display. Only on page refresh you see that the post is already stored, but then it is too late. People are used to being able to post, close the dialog and the new entry is already there at the end.

        I cannot debug more than this. Took me quite a lot of log diving to understand that the issue was related to notifications and mailgun.

            Flarum 1.8.5 all of this confirmed. I didnt meet a notice about new discussion and I am start with "FoF Subscribed" and "FoF Follow Tags", but emails quantity going over limits of my hosting and I meet warnings. So, I decided to disable this extensions. However, some tests showing that I can disable notice to emails in profiles (in mass way from database) and all will be fine. But I am still didnt write a script for this.

            DaniBerlanga any results?