Sulframus

Okay, I've finally figured it out. There were issues on top of issues. The actual working config with Active Directory using attributes proxyAddresses is following.

Has anybody been able to get AD LDAP working with dms? I've followed their documentation for AD, but keep getting dovecot auth issues. Reviewed dovecot forums and everything that I have tried still didn't get it to work. Usernames, passwords, IPs and domains have been changed to be redacted

I keep having issues where my activity on most torrents stops being announced. It's usually fixable by forcing recheck, but having to do a recheck for about 20TB of files every few weeks is extremely annoying. Anybody had this issue or would know about a way of to get this fixed? Just updating the tracker is not enough.

It looks like issue was with Thunderbird. When IMAP fills out the information, it puts the username as admin, not [email protected] and therefore the user is unknown. I now got mail receiving working. Sending e-mails to Gmail for example doesn't work. This looks to be an issue due to my ISP. I will try to call them up, hopefully they will be able to help out.

Not sure why it happens either, but thank you for your help and time. Your suggestions at least made me understand the way the subdomains work. I will open up an issue on DMS GitHub, hopefully they will be able to help.

I did have IPS on, disabled it now for testing, still no change. No firewall rules. This was done multiple times during testing. They show up when doing "setup email list", tried updating the passwords again to 123456, but still the same error message with unknown user appears.. Added it before, tried adding again. Tested with domain.com and mail.domain.com. Recreated the whole DMS docker, unfortunately still stuck on the same issue. Went through the "Troubleshooting" article on the DMS github page. The only part relevant is what is shown in docker logs in unraid anyway.

I think the response time is good for a forum, thank you! Unfortunately I am still having issues. I have decided to test with the least amount of security just for the testing purposes to see if I will be able to get access to the mail server from a VPN connection. I don't use NPM for actually port forwarding any of the ports used for DMS, this is done by the router instead, which points to Unraid, where the DMS is running. I have turned off the Cloudflare proxy for my A records and created them using the same way, that you mentioned. I have turned off SSL to avoid certificate issues. I have recreated the mail accounts. Thunderbird finds the IMAP configuration, but after trying to login it gets stuck on "checking password". Logs from DMS point to an account, that isn't created, which is weird, as I added both [email protected] and [email protected]

No warnings in Thunderbird, but even without sending anything I am being flooded in DMS logs with some connection and losing connection after EHLO from a Mexican domain, which I don't know at all. After blocking that IP in the firewall, the flood stopped. During the time when I send the mail I get the following logs: Certs in the template are setup followingly: This is where I store my CloudFlare provided Edge certificates, which are in use by NPM, so they are valid. Was not aware, that any subdomains were required, as I thought that an A record pointing to my public IP, MX record pointing to A record and TXT records with spf, dkim and dmarc were enough. I do however have my A record proxied through Cloudflare, wondering if this could cause any issues. Would you be able to tell me what the subdomains are required for and what would they need to point to? I thought, that the ports on the firewall had to be routed due to NPM taking only HTTP and HTTPS requests. I see, that you use the webmail.domain.com for the IMAP and SMTP information in Thunderbird? How do you point it in NPM? I have a single cert, which I believe is either for TLD or wildcard. I believe, that I already did the DKIM config before, but have done so once again now just in case. However, I don't receive e-mails even internally. The hostname in the docker template was setup correctly. Seems like the issue with the warning message in Thunderbird for Certificate error only appears the first time a mail is sent on the account. EDIT: Just tested using Thunderbird, that is not running on the same host and I get configuration issue.

To correct myself on the first part. Seems like F2B was disabled, as that's what is default to the template. Using the test account, I was able to connect to the account now in Thunderbird and same for the original mail account when I updated the password to something basic. Now I have a new problem, which seems quite stupid. In Thunderbird when sending the first mail I get a warning "Sending of the message failed. Peer's Certificate issuer is not recognized. The configuration related to mail.domain.com must be corrected". As mentioned in my previous comment, I am using manual certificates provided by Cloudflare. I have a MX record created with name domain.com to point to mail.domain.com. Sending mails between the two local accounts doesn't do anything and trying to send a mail from a different SMTP server, such as Gmail yields error that "mail.domain.com could not be found". I have also tried adding e-mail routing in Cloudflare, which I don't think should be necessary, but no change.

Thanks for the heads-up on the F2B, didn't decide to turn it off yet. Not sure if I may have gotten banned as the logs are not showing any alerts, what is the default duration for ban, or where would be the bans located, so I can clear them out? I have used [email protected] for the login in Thunderbird, which was already created prior in the console of the docker by going to the bin folder and running "setup email add [email protected] password". I did however use special characters during the setup. I will try later today again with a second account with basic password. Thank you.

Hi, I seem to be struggling with getting some parts right. I use Cloudflare as my DNS provider, where I already have my MX and TXT records setup and have the .pem and .key locations setup in template for manual. I have forwarded all the ports used by the docker at the moment for testing purposes onto the IP of the unraid server. Thunderbird does recognize these records, as it autofills the configuration with IMAP. However after this part it's when things starting falling apart - when trying to login, I get a message saying "Unable to log in at server. Probably wrong configuration, username or password." I have checked the username and password, which were correct. As there is not a specific error message, I am unsure what would be misconfigured. Would anybody happen to know what can be causing this issue and possibly the fix?

Hi, I have installed a Nvidia Quadro P2000 into the server. Everything was okay, but as soon as I have installed nvidia-driver the system kept working in a weird way. First of all, the nvidia-driver page was inaccessible as it just kept on loading forever. When opening up the terminal and trying to run nvidia-smi it looked like the terminal was trying to do something, but no output came out. I have decided to try to reboot the server after the install of the driver, but the system would not shutdown no matter how long I kept waiting for and I have to resort to forcefully shutting down the host. I have done some tests and this whole situation only happens when both the drivers and GPU are installed. There is no issue when only the drivers are installed and there is no issue when only the GPU is installed. myserver-diagnostics-20220605-0156.zip

Unfortunately I've moved my unraid server onto another hardware, so I wasn't able to do the GPU passthrough in the end.

So now I'm able to create a VM with the GPU and remote onto it with no problem, but the VM locks up after several minutes and goes back to the state of not being able to remote onto it/turn it off with a graceful shutdown.

After dumping the VBios of my own GPU and fully reinstalling the VM, I was able to get it working. But after some time, the VM froze up and now it's doing the same thing as before. I'll retry again tomorrow with a fresh new image, hopefully the results will be good.