Is there a way to take the Sieve rules and normalize them? A quick search for sieve parser got me to this: https://github.com/python-sifter/sifter

Thanks to everyone who gave me suggestions. I finally found a solution. ChatGPT provided misleading information—actually, the 'From' field can be modified. Here is the Sieve filter I ultimately used. require ["editheader", "variables", "copy"]; if true { if header :matches "From" "*" { set "original_from" "${0}"; } else { set "original_from" "unknown@domain.com"; } deleteheader "Reply-To"; addheader "Reply-To" "${original_from}"; deleteheader "From"; deleteheader "DKIM-Signature"; addheader "From" "Forwarder <forwarder@mydomain.com>"; addheader "X-Original-From" "${original_from}"; redirect "myemail@gmail.com"; keep; }

If anyone else is getting mildly annoyed by this I've just discovered that if you actually enter something into the Name field and save it then it stops happening (even if you then go and delete what is in that field and save again).

@mihailaks no, SnappyMail is not indexing mails itself. It searches via IMAP and the mail server has to index attachments.

@LoudLemur I think for admin the TOTP has to be set in the ini file (https://github.com/the-djmaze/snappymail/issues/84#issuecomment-885181768) . For users, the 2FA extension is used. The 2fa is shown in admin login page, all the time for me as well. But if you can identify the bug, maybe you can report this upstream since 2FA auth comes from snappy and not from Cloudron.

@luckow s/mime has been broken so many times, I don't think total privacy can be expected anyways

@LoudLemur yeah, there is no way around user not knowing about Cloudron dashboard to change the email password. The alternative is to create a web app which does this and uses Cloudron API (which is out of scope for us). Unless Cloudron develops it's own webmail ui , this is hard to solve (for the reasons you pointed out).

Resolved, it was an incorrectly entered IP address on the OVH side, and they have corrected the error. Thank you all for your contributions.

2.31.0 fixed the problem

Thank you, gentlemen! This worked. I hope that a summary of this explanation is included in the documentation.

@robi said in SnappyMail on Cloudron: How to setup your domain name's email with SnappyMail: @jdaviescoates Cool, what recording extension did you use? Also love the Bitwarden workflow, didn't know it was so slick now. VokoscreenNG is good: https://linuxecke.volkoh.de/vokoscreen/vokoscreen.html

Just in case you like mystery stories, there is a bit more to this tale. It might be connected to time. Restoring to a backup works ok, until the next day/midnight... Also, the account was also setup on Nextcloud and remains accessible there. I think it might be due to a OTTP token corruption problem. There is no OTTP used for access via Nextcloud.

@robi me stupid. I had two entries with allow_admin_panel, one was "On", one was "Off"

@girish Indeed, that was the case! Thanks I'd installed the plugins, but didn't check them yet. The plugin had a placeholder (invalid) value set as the default.

@nebulon @girish Thanks for the details!

I did it! Thank God for that! You have no idea how glad I am to get out of that rabbit hole! Thank God! Thank you everybody who looked and tried to help. In particular, thank you to @humptydumpty for that last post. The key thing I was missing was that I needed to go into the Cloudron's email settings and create a mailbox for my email. I will try and add some comments later but right now I am just delighted and have to do so many other things that were blocked. I love Cloudron!

@artd2019 Have to test with SnappyMail! Will get back on whether it uses the indexed search.

@girish for me this message has stopped popping up after the 7.4.1 update.

My NC and mail server are on two different Cloudrons. I had to go into the NC Admin Settings --> Administration --> Additional Settings, and log in as SnappyMail admin through the link on the page and did the following: Domains: add your domain(s) to the list Click on your newly added domain and enter your mail server under IMAP and SMTP. Go to Security and change the default admin password. You should be able to log in now.