FileZilla has a Site Manager (File -> Site Manager). You can create named sites. [image: 1632330490163-0cf9295b-7d1c-456b-bec6-64c9cb83bf06-image.png]

@nebulon got it, thank you!

Problem solved by install all three instances into one and bought a license from cloudron. Now it works

@brutalbirdie ok, thank you - I've got the idea!

@scuba9273 glad you figured it out and thanks for sharing the solution!

@setsuneh can you send a mail to support@cloudron.io with your dashboard domain and maybe the IP of the server you want to have your subscription reassigned to, then we can do this from our side most likely.

@seeker said in Testing Ensuring Email & Mailtrain is set up Properly: I have been working on exploring and setting up Cloudron. An important part of that for me is email and a mailing list. I am looking to make sure I have done everything I can to ensure people will get the emails I send out. I also have questions:) Questions: I am curious what steps I should be taking to make sure emails sent from both the regular imap email account, Cloudron/ Cloudron apps, and also the mailtrain account are received? Ometv chatroulette omegle bazoocam I am planning on using mailtrain to send out to a list of people of between 50 and 100 about 6 times a year. Is it the best solution here? Currently Mailtrain is set up to use Cloudron's email. I know it is possible to use a different server, but not sure what would be best or the cost? If people have other suggestions, please let me know. How is the Mail train's app email used? It does not look like it can receive emails (see below) What do I do to make sure email being sent has the best chance of arriving in recipient's inbox? Any steps I should take based on the test below? Any other tests I should do? Setting up email Enabled email/ set up email In order to do it properly I needed to change the name of the droplet so it matched. Then set up email client using IMAP and sent an email out to a couple of people and it worked. The password type was "normal" how secure that is. While doing this I was curious how one goes about backing up email. I am coming from a shared hosting environment, where I can ftp the mail folders. After sending and receiving a few test emails from the email client, I moved on to mailtrain. Setting up Mailtrain Installed the app. It looks lie mailtrain creates an admin email that is <install name.app.domain> That email address is also used by campaign defaults. I tried sending a test email to it however and it did not go anywhere. In testing sending some emails, it does not appear can just change this email to anything you want. It must match the app domain??? I created a list (of two people) and then sent an email to the two members on the list using mailtrain. 1 email went to a shared/self hosted email address and was received fine. The other went to an hotmail email address and went into the trash/spam folder. Testing Email Setting: Below I will show the test I ran, but if there are other test, let me know. I am new to this. The first thing I checked was the test within Cloudron. Really appreciate this test being included! One of the help docs mentioned checking your email server settings using Initially it did not work, but I tried entering the domain name with and without www.domain. I did not include my.domain. Below you will see that the Blacklist:4 and Failed:2 Here are the detailed results. I can include more of the test, but the rest was green. I am not positive what I should do to address the request failure above. I also used I ran the test three times. The first test email did not fair well. It "would not have seen the light of day" with a score of .8 out of 10. The email did not have a subject or contents. The second email where I included a subject and a little paragraph of text got 10.10 The thrid test, I used a little more text- it also got a 10/10 But there were some flags consistent among the second and third tests: Thank you thanks my issue has been fixed.

I have updated the vultr image. The DO image is also submitted for approval.

thanks for proving my point that one cannot have a discussion with you

@nebulon indeed, thank you! For the sake of future users, I guess it could make sense to add information about where to take token and full command line for cURL into the documentation, but it's not directly related to the case.

@humptydumpty said in Nextcloud is very slow on Linode: BTW, look into Syncthing (file sync), Wekan (kanban), Vikunja (kanban), and Matrix/Element (instead of Nextcloud Talk). All available on Cloudron. I certainly agree that Nextcloud can get bloated and even unstable when too many plugins are enabled. I use it heavily for file storage and shared folders, but for almost nothing outside of this. And definitely the other apps are worth exploring.

@girish That sounds great, if there was a way to access the content of what the app was trying to send that would be good enough for me, no specific need for it to be in a mail format, json, or any other specific data structure.

@jjhill Let us know when Cloudron has been installed correctly and is running well please.

@avatar1024 you can send the logs to support@cloudron.io Given that the backups are working fine on the hetzner instances, this indicates an issue during backup with the mountpoint. Maybe the connection to the storage box sees some hiccups. Those issues are generally quite hard to debug since they are often on the lower system levels Maybe you can also reach out to netcup/hetzner if they see any interruption between their networks during the time your backup failed last time.

@nebulon Thanks a lot for your quick support. It works now.

@sangroot this unfortunately means that your server got an IP with a bad reputation ending up in the blocklist. To explain, those IPs are constantly reused and it could just be that either this IP itself was used by a spammer in the past or that some other IPs in that IP block might have been spammer IPs. This is not unusual though and it takes a bit to get IP reputation up and manually removing it from blacklists by appealing is the first step in this case. If you need to deliver emails reliably from the start, you may consider using a mail relay configured through Cloudron for some time until you are off of all those blocklists.

Looks like we have to investigate again, but a similar issue was fixed in that version, apparently didn't fix all the cases.

@girish Belated marking as resolved for anybody looking in future. girish did some remote ssh support magic and solved the problem.

@nebulon great to hear that it was already reported and fixed! I didn't get any suggestions regarding similar topics, so I thought it wasn't reported yet.