Email sending issue (was: URGENT)

[mmtrade]

see attached i changed host names

[d19dotca]

@mmtrade said in URGENT:

Now it started working and sending mails. When i started my campaign, I noticed i could not send up to 1000 emails before this issue started again. I am being blocked and my emails will not receive or send. when i try to do a test it does not work and it still keeps showing me the attached. Everything just worked fine when i started the process again but i do not know why after some time i am being blocked....

This definitely sounds like rate limiting being done somewhere if you get up to 1000 emails and then suddenly you can't send any more. But I'm not sure why you can't receive emails either. This feels like something to do with the host you're running with, but if they say they don't do that then I'm not so sure where else it could come from.

What do the mail service logs show? Does the issue happen even after you restart the server or restart the mail service? If yes, then that would seem like something outside of Cloudron, but if the issue is then resolved after restarting then perhaps something else within Cloudron that's affecting things. Best bet to help narrow it down is to show the logs from the mail server (redact sensitive info like email addresses though of course). You may feel safer sending those logs into Cloudron Support email instead from an alternative address.

[mmtrade]

My bad it sent more than 1000 but it was just an odd number. I think about 5436 emails to be precise. the last one sent around 10k plus.

the random changes in sending emails makes it suspicious.

However at first it was the IP spamhous block issue which got resolved and still it did not work moving forward before i reinstalled it and set another host to it.

Does it mean that cloudrun has detected the IP? what do you need from me to test and know cloudrun is not associated with this issue?

What do the mail service logs show? I cannot send emails out to know this. If you know how to get this let me know. I will post what you need me to on forum.

Even when i restart the server.. the issue is still there.

Tell me what to do

[mmtrade]

@d19dotca @BrutalBirdie @jdaviescoates

My bad it sent more than 1000 but it was just an odd number. I think about 5436 emails to be precise. the last one sent around 10k plus.

the random changes in sending emails makes it suspicious.

However at first it was the IP spamhous block issue which got resolved and still it did not work moving forward before i reinstalled it and set another host to it.

Does it mean that cloudrun has detected the IP? what do you need from me to test and know cloudrun is not associated with this issue?

What do the mail service logs show? I cannot send emails out to know this. If you know how to get this let me know. I will post what you need me to on forum.

Even when i restart the server.. the issue is still there.

Tell me what to do

[d19dotca]

@mmtrade said in URGENT:

What do the mail service logs show? I cannot send emails out to know this. If you know how to get this let me know. I will post what you need me to on forum.

In Cloudron, you click on Services page and then the log icon for the mail container. Then export the logs (in case the issue isn't most recently seen in the logs).

[nebulon]

@mmtrade since you are sending out lots of emails and probably within a very short time, you pretty much have to use some external email relay, otherwise your Cloudron's IP will end up in blocklists and gets flagged, at which point it is hard to build up trust with other email providers for that IP again. All kinds of issues will come up once the IP of the sending email server (your Cloudron) gets a bad reputation and the errors other mail providers give aren't always too helpful, dependin gon their spam protection strategy.

This is bound to your IP btw, so restart a server or so won't help.

Basically for non-transaction emails you want to use one of the supported relays https://docs.cloudron.io/email/#relay-outbound-mails there is nothing we can do much on the platform code side unfortunately.

[mmtrade]

@d19dotca

you mean this??

[jdaviescoates]

@mmtrade said in Email sending issue (was: URGENT):

I deleted my whole server and started the reinstallation process again with a different host. Now it started working and sending mails. When i started my campaign, I noticed i could not send up to 1000 emails before this issue started again. I am being blocked and my emails will not receive or send. when i try to do a test it does not work and it still keeps showing me the attached. Everything just worked fine when i started the process again but i do not know why after some time i am being blocked....

Please i need answers to this urgently because I am loosing my mind.

From what you've said here, it sounds to me like this has nothing to do with Cloudron.

It's likely because your hosts are blocking port 25, either because they do that by default (lots do - e.g. these days Hetzner does that with new customers), or because you're trying to send 1000s emails quickly and that's triggering anti spamming protection and the block is getting enabled.

If you need to send lots of emails you're much better off outsourcing that to a specialist email sending service like https://postmarkapp.com/ etc (I'm using mailgun.com just because that's what Ghost requires but lot of people here have had good experiences with Post Mark)

[jdaviescoates]

@mmtrade no @d19dotca means here:

But this clearly isn't anything to do with Cloudron imho. You need to use an email relay if you're going to be sending out 1000s of emails, otherwise you'll get blocked by your host and/ or added to blacklists. There isn't anything Cloudron can do about that, it's just the way the email world works.

[mmtrade]

@nebulon This is from cloudron server

I cannot run telnet on it

i changed service providers and same thing and same issue

[mmtrade]

@jdaviescoates this is 100% cloudrun issue

i changed servers just to be sure and i still have thesame error messsage assame as last VPS server

i tried connecting to telnet not working

this messed my email campaign up.. i also put it some triggers to make sure it does not come into spam and send emails at the rate off 200 per 30 mins.

see attached

the problem is from cloudron and you need to fix this. This is no server issue. Since you made your upgrade it has messed our servers up.Check this internally because this same issue cannot happen with a different VPS provider

[d19dotca]

@mmtrade Again, you’ll want to check the mail container status and logs, as that will likely be the most telling if the issue is in Cloudron or not. Maybe include a screenshot of the services list, and include a snippet of the latest log lines before and after restarting the mail container. That will probably be helpful.

[mmtrade]

@d19dotca can you tell me how to check this?

[d19dotca]

@mmtrade @jdaviescoates showed how to do that above. Go to Services page and click the log icon next to the mail line.

[mmtrade]

@d19dotca can you give me a SC on this

[mmtrade]

I mean can you give me Screeshots for this review? Do you think this problem can come from the OS?

[scooke]

Are you being purposefully obtuse and difficult @mmtrade? Several times you've been asked to check something by someone trying to help you, and you don't do it. You either reinstall the entire server or just ignore the posted help. You're wasting everyone's time if you won't follow the suggestions.

Something is off here.

[mmtrade]

@scooke thats not a nice thing to say... wasting someones time? I asked to give me directions to check this.

@d19dotca thanks for all your help but i actually want to check the logs part if i can get help with it

I tried reinstalling the whole thing and it will start working after some time this error will come up again

i have tried that several times

[mmtrade]

it is not fun coming to this review forum to keep talking about a particular problem. I have tried with 2 different server VPS and all give same result.

After some time they stop working. The first was the spamHouse now i actually do not know if it is the domain or what but am now sure it is not the service VPS provider.

I am trying to eliminate these issues one after the other for me to find the cause off the problem.

I really need help

[BrutalBirdie]

I just tried accessing your domain my.miritz.bio but got a refused to connect error.
Also I can see that you only have an A records and no AAAA record:

dig A my.miritz.bio +short
213.232.235.195
dig AAAA my.miritz.bio +short

And your PTR is:

dig -x 213.232.235.195 +short
miritz.bio.

But I can't verify the AAAA PTR Record.

Using the bare domain as the mail server domain can lead to many issues like DNS propagation times.
But your choice.

At least the IMCP Ping is working:

ping my.miritz.bio
PING my.miritz.bio (213.232.235.195) 56(84) bytes of data.
64 bytes from miritz.bio (213.232.235.195): icmp_seq=1 ttl=119 time=78.7 ms

Also I just run nmap -T Aggressive -A 213.232.235.195 also the following might be false but:

nmap -T Aggressive -A 213.232.235.195
Starting Nmap 7.95 ( https://nmap.org ) at 2025-03-26 09:20 W. Europe Standard Time
Nmap scan report for miritz.bio (213.232.235.195)
Host is up (0.063s latency).
Not shown: 993 closed tcp ports (reset)
PORT     STATE    SERVICE       VERSION
135/tcp  filtered msrpc
139/tcp  filtered netbios-ssn
445/tcp  filtered microsoft-ds
3389/tcp open     ms-wbt-server Microsoft Terminal Services
|_ssl-date: 2025-03-26T08:21:55+00:00; 0s from scanner time.
| ssl-cert: Subject: commonName=opal-labs
| Not valid before: 2025-03-24T15:14:12
|_Not valid after:  2025-09-23T15:14:12
| rdp-ntlm-info:
|   Target_Name: OPAL-LABS
|   NetBIOS_Domain_Name: OPAL-LABS
|   NetBIOS_Computer_Name: OPAL-LABS
|   DNS_Domain_Name: opal-labs
|   DNS_Computer_Name: opal-labs
|   Product_Version: 10.0.17763
|_  System_Time: 2025-03-26T08:21:53+00:00
5357/tcp open     http          Microsoft HTTPAPI httpd 2.0 (SSDP/UPnP)
|_http-title: Service Unavailable
|_http-server-header: Microsoft-HTTPAPI/2.0
5985/tcp open     http          Microsoft HTTPAPI httpd 2.0 (SSDP/UPnP)
|_http-title: Not Found
|_http-server-header: Microsoft-HTTPAPI/2.0
5986/tcp open     ssl/http      Microsoft HTTPAPI httpd 2.0 (SSDP/UPnP)
|_http-title: Not Found
|_http-server-header: Microsoft-HTTPAPI/2.0
| tls-alpn:
|_  http/1.1
| ssl-cert: Subject: commonName=Cloudbase-Init WinRM
| Not valid before: 2025-03-24T15:14:30
|_Not valid after:  2035-03-23T15:14:30
|_ssl-date: 2025-03-26T08:21:55+00:00; 0s from scanner time.
Device type: general purpose
Running (JUST GUESSING): Microsoft Windows 10|2019|2016 (89%)
OS CPE: cpe:/o:microsoft:windows_10 cpe:/o:microsoft:windows_server_2019 cpe:/o:microsoft:windows_server_2016
Aggressive OS guesses: Microsoft Windows 10 1607 (89%), Windows Server 2019 (88%), Microsoft Windows 10 1903 - 21H1 (85%), Microsoft Windows Server 2016 (85%)
No exact OS matches for host (test conditions non-ideal).
Network Distance: 10 hops
Service Info: OS: Windows; CPE: cpe:/o:microsoft:windows

Windows? Maybe a Windows Virtualized Setup?

Your posted putty screenshots connecting to root@host are you really using a VPS and not a home server setup?

You were requested several times, by several different people to provide the mail service logs which you did not provide.