Cloudron Forum

@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 🙂

@imc67 nevermind, I found it - https://docs.espocrm.com/user-guide/mass-email/#settings

I will move this to feature request. But we haven't really analyzed what work this involves.

Just found the solution here: https://forum.cloudron.io/topic/1279/receive-email/4

The problem was that AWS EC2 instances close port 25 by default. As soon as I opened it in the AWS console, I was able to receive emails.

This problem is not reproducible anymore.

@girish said in Anyone else see many connections denied due to "Mail from domain <domain> is not allowed from your host" repeatedly from spammy IPs?:

@necrevistonnezr Ah, sorry! I misread. In my case, the sender is just spamming the hell out of me for video content. Sender is not trying to spoof. I guess you have to block by IP in the network firewall.

Yeah, well, those IPs are never the same (see above) and even ranges are difficult to ascertain. Maybe an easy way to subscribe to a blocklist would help? 🙂 (as suggested in my old topic linked above…)

@ccfu That's a good point. Probably one for their forum but I think I'd like that too so may help develop.

@d19dotca it's not a problem. Just the natue of any service being exposed to the internet. There a bots, misconfigured services, compromised iot devices doing all sorts of things. Nothing to worry.

@d19dotca This looks pretty good. I am testing it now 🙂

how embarrassing. You're absolutely right. I was searching after ghosts.

@necrevistonnezr excellent catch! I think I searched “email” when I should have just searched “mail”. 😇 There may be a couple others I missed.

@gobenizzle unfortunately, no. I was just re-reading this thread. What is your use case for this (sorry, if I missed this).

@tamayers you said use case is "A reason for this (such as my use case) is that you might have inboxes for employees using Google Workplace, Microsoft Exchange, or Cloudron email for user account and then support inboxes for customer inquires or sales that you do not want handled on the same system." I am not sure why this is done, is this to save money because exchange/workspace charges per mailbox?

Okay... I may be on the side of this working properly again. lol. Maybe I've been wrong this whole time in thinking it wasn't working correctly.

So coincidentally I was checking the mail server logs and saw another example of the same message go through to the same recipient from the same mail server, it was listed in the logs as "just now" so I quickly checked mxtoolbox and found that only 4 at that time had been listed, none of which were ones I was using.

Here is how it looked at the very moment I checked when it was "just now" in the logs:

69bc5a02-12ca-420e-958a-27405c21f7ed-image.png

07b937c4-4840-4c14-887b-7513acc87251-image.png

Edit: Checking about 6 minutes later, I see the blocklists have aleady been updated for more (Spamhaus Zen in this case would have caught it if it were about 5 minutes earlier):

4522d168-dc21-498f-845b-885cfe0a73a1-image.png

So I guess we can probably mark this as resolved, as I now see conclusive evidence that the various blocklists used just didn't have it listed until a few minutes after the message was received. I guess in order for it to adapt so quickly this spam attack on one of my users from those mail servers must be right at the beginning of a spam wave. Kind of neat actually to see how real-time these lists are. haha.

@d19dotca since the email is forwarded , this info is probably lost. One idea is to look into the bounce mail headers. Maybe there is some message I'd or something we can match.

@mdreira said in Lightmeter - Mail server delivery monitoring:

What mail server does Cloudron use? Exim?

This is what Cloudron uses for smpt: https://haraka.github.io/

Nevermind, I did not realize sendgrid setup was only for sending email, I see the other parts to setup for receiving email now. Please disregard.