In the Postfix world this feature is called "always bcc", but it does not look like something like this exists out of the box in Haraka.

@micmc said in Configure Haraka for Mailman3:

https://www.phplist.org/

Thanks for the recommendation. PHPList looks like a "campaign" mailing list to send to external people. This is definitely useful but not quite what we were after.

More we are looking for mailing lists for internal people that maintains nice archives and people inside our group can subscribe to our de-subscribe to. Eg sales@ourconmpany.com, devops@ourcompany.com, expenses@ourcompany.com, design@ourcompany.com, marketing@ourcompany.com, etc. And so as people our interested in some of these topics they get naturally filtered to the different email lists... and we have internal archives of these lists. It works quite well as we currently have it. I just want to bring this sort of thing over to a cloudron server!

@girish Yes there are definitely more than 20 events, and the Next page still works to load more, it's just that dropdown to change how many records are shown at once which has an issue. I just updated to 7.0.3 so will try soon, unfortunately it seems the email logs were cleared after update, so there's no records in there at all now.

@girish Ah that's perfect! Thanks Girish! 🙂

@eddowding If you like you can patch the file in /home/yellowtent/box/src/mail.js and systemctl restart box.

@luckow Yes, similar view to the aliases ones where all are listed for the mailbox user.

I didn't know Argo tunnels were free. So one can hide the mail service and put it thru an Argo tunnel on a subdomain to the world.

https://docs.ibracorp.io/all-guides-in-order/documentation/cloudflare-tunnel

Similarly one can have another domain and IP handle the incoming, which is tunneled to you via Tailscale.

https://docs.ibracorp.io/all-guides-in-order/documentation/tailscale

@murgero re-read, my response remains the same, sorry.

You know the way security scanners (or script-kiddies) works, it's to scan the network (Internet), get hosts and they software; if there is zero-day on CloudRon or other not disclosed vulnerability, apply it across the hosts.
Having DNS records showing that there is CloudRon here means you don't even need to scan for the ports, which just simplify things.

Hope that helps to understand my response here.

I have also added Service events in the event log for the next release. So, this way, we can know if the service was automatically restarted after cert update.

@marcusquinn as @robi said, there is no such limitation of having a single app on that domain.

@murgero thank you!

@girish ah alright, that sent me down the right path. needed to switch from encoded body to raw JSON and that cleared it up. thank you!

@austinsonger

Regarding Linode and Mail - default is blocked by Linode:
https://www.linode.com/docs/guides/running-a-mail-server/

Sending Email on Linode

In an effort to fight spam, Linode restricts outbound connections on ports 25, 465, and 587 on all Linodes for new accounts created after November 5th, 2019.

If you have a need to send mail from your Linode, we ask that you first configure (1) valid DNS A records and (2) rDNS records for any Linodes that you plan to use to send mail. Then, open a Support ticket from the Linode Manager – we’ll ask you to provide the name of the Linode(s) that will be used for mailing.

Once you’ve completed those steps and provided that information, our Support team will be happy to review your request.

@nebulon Thanks 👍

@scooke we have traced this down to a nodejs bug apparently with the domain in question.
The upstream issue is at https://github.com/nodejs/node/issues/39397

Good notes to follow up when we look into email in the next release.

IIRC, whitelist setting is a bit dangerous because it allows "spoofed" emails as it pretty much bypasses all the SPF/DMARC/DKIM checks. Meaning, Cloudron does not reject mail if those checks do not pass because there are too many misconfigured mail servers out there. Instead we tag the failures and allow spamassassin to score the rules. whitelisting makes spamassassin bypass the checks altogether.

@d19dotca Ah good point about editing those files. In the next release, I am hoping to make the filemanager be able to edit mail data (so admins can setup sieve rules etc for a mailbox), so this will atleast partly fix that issue.

@eddowding ah, great you managed to figure this out. indeed, cloudflare can only proxy http(s) and not email.

@micmc Can you share one of the domains so I can have a look?

@jegillikin-0 mm, that shouldn't be the reason. But something for me to ask future users who hit the same problem.

@nj Use this: https://omm.ovh.net/ , very fast and no any data amount limitations.

@msbt yes, thanks for reaching out, will take a look.

@girish WHOOP!!! Thank you!!

@d19dotca Okay, that is a bit confusing, but I will only be able to figure it out once I try it.

I appreciate everyone's help and responses.

@timconsidine Also good to point out is if the plan is to just use a personal google account's SMTP settings it will be severely rate limited.

@humptydumpty Yes, correct. Server restart won't fix the issue, have to restart the service explicitly (since it copies over certs).

I end this thread because I now have a more specific one going.

Mystery solved; The server i was hosting Afterlogic on turns out is just too slow. Checking the logs it would always time out, which is 15 seconds.
I ran Afterlogic on a much faster server and now it sends emails just fine.
Thanks all for your efforts to help me, it was much appreciated.

Not 100% sure but are there any files under /home/yellowtent/boxdata/mail/spamd/<mailboxname> ? Those are the per mailbox spamassassin bayes databases. Maybe it's picking up something from there?

@girish WOW that greatly simplifies the process, that's great, still always amazed at how CR makes sysadmin soooo much easier 🙂