Email sending issue again (Was: URGENT)

[mmtrade]

@joseph It happened again and i have to restart it again

[joseph]

@mmtrade maybe you can create a copy of the files in the mail queue when it dies like this and send it to us?

[mmtrade]

@joseph i sent it to your email. you can check. when you restart it starts woking and you just test with 50emails and it will stop.

there seems to be a problem and i do not know why it keep crashing

[mmtrade]

@joseph any update on this?

[mmtrade]

@joseph I had to restart it again

once i do restart it it will start working fine.. can you check what and why the bug is affecting this?

[nebulon]

@mmtrade we only provide best-effort support through the forum. If you need more timely and direct support, we have a subscription plan for this.

[scooke]

@nebulon said in Email sending issue again (Was: URGENT):

we only provide best-effort support through the forum. If you need more timely and direct support, we have a subscription plan for this.

SERIOUSLY.

[girish]

@mmtrade We found the issue. I have raised an issue and submitted a PR to haraka - https://github.com/haraka/Haraka/issues/3455

[mmtrade]

@girish OK. good to know. I have seen it and i even commented on this on github

[girish]

@mmtrade once upstream merges, we will make a new mail container image that should fix the problem. I think haraka maintainers are in US timezone..

[mmtrade]

@girish @joseph @nebulon this issue is still here

maybe what you sent was not worked on

the buy is very bad and nothing is working on this cloudrron

[d19dotca]

@mmtrade The fix was just merged less than 8 hours ago by the Haraka maintainers (outside of Cloudron's control). Give everyone a reasonable amount of time, and I'm sure it will be ready soon.

[girish]

I have made a new build of mail container.

IMPORTANT: Do not apply this fix unless you are affected by this . The new mail container passes tests but it also contains a new Haraka release.

• Edit /home/yellowtent/box/src/infra_version.js . Change the mail container image to registry.docker.com/cloudron/mail:3.16.1@sha256:900b7f55a74a289568c501cd873c24738d424e24f005c3c49cf76a26c296ec22
• systemctl restart box

[mmtrade]

@girish Is it not commendable that i actually saw a problem that was there that nobody saw and noticed?

People thought i was crazy sending a lot of posts

[necrevistonnezr]

It’s not what you communicated but how.

And I believe it‘s far more commendable that @girish kept his patience, analyzed your particular problem (no one else reported something similar), reported it upstream, and merged the fix himself, all within hours. And all without an SLA.

So credit where credit is due.

[mmtrade]

@necrevistonnezr who the hell are you? all this ass licking... well i was never referring to you.

@girish i actually did not understand what the problem was but you helped track it down.

meanwhile is the update currently running on the cloudron?

[joseph]

@mmtrade I am afraid such language is just unacceptable . worse, you seem just unaware, intentionally or not about your tone. the update is not running on Cloudron, but you need to make the change as suggested by @girish . I will lock this thread but we are having none of this tone here.