Recent content by jigster

Strange, on my servers all emails from CSF, DirectAdmin messaging system etc. are all signed correctly and pass DKIM, SPF and DMARC! I have root emails forwarded to an external email address using /etc/aliases. I have a separate DNS zone for the server hostname (e.g. server.hostname.com) and the...

Did you create a DKIM entry for your server hostname? I did this: /usr/local/directadmin/scripts/dkim_create.sh $(hostname -f) I had to do this first in order for the above to work because I don't have the server hostname set up as a domain on the server: mkdir -p /etc/virtual/$(hostname -f)...

Yes, here's what I did: mkdir -p /usr/local/directadmin/custombuild/custom/exim; cp /usr/local/directadmin/custombuild/configure/exim/exim.dkim.conf /usr/local/directadmin/custombuild/custom/exim/; Then edit /usr/local/directadmin/custombuild/custom/exim/exim.dkim.conf to replace the...

The solution posted above by @Stije worked for us and now autoresponders are correctly passing DMARC. Thanks a million @Stije - it was driving me nuts for days!

Thanks @Stije, I will try it next week and see if it works for us.

Yes I've got those, and both SPF and DKIM pass when an autoresponder is sent, so that's all working correctly. What doesn't pass is the DMARC alignment check which needs either the SPF or DKIM to be using the user domain (not the server hostname) so one of them matches the 'From:' header...

That solution didn't work for me because it sets the envelope-sender to [email protected] (the sieve script owner) which still doesn't match the user's domain which is what is in the header-from of the autoresponder and what needs to match for DMARC to pass alignment checks. Strange...

Since the upgrade from DirectAdmin 1.659 to 1.660 we can no longer access the Login Keys page as the admin user. It says the feature has been disabled. I have checked Login Keys are turned on: # /usr/local/directadmin/directadmin config | grep login_keys login_keys=1...

Yes that seems to be a major issue with DMARC - with it set to 'p=none' autoresponders work without bounces, but then DMARC is essentially doing nothing other than notifications. With DMARC set to quarantine or reject, autoresponders bounce or go to spam. Catch 22!

How does everyone else handle autoresponders and DMARC? Not use DMARC quarantine/reject and set the DMARC policy to 'none' instead? Not use DMARC at all? Or just not worry about a lot of autoresponders bouncing? Thanks - just trying to gauge the best approach. We've come from cPanel where...

Thanks a lot, but I'm not sure that would work because the header-from has to match the domain used for SPF (from the envelope-sender) or DKIM, both of which are the server hostname. I think the only options are: Change the autoresponder's header-from to use the server hostname so it matches...

Yes, and both pass. It's the alignment that's causing the problem because the header-from domain is different to the SPF/DKIM domain. Unless DMARC is set to 'none' all the big providers bounce the messages due to the failure.

When an autoresponder/out-of-office reply is sent (with DirectAdmin Vacation or with a sieve rule in Roundcube), DMARC fails. Even with the solution posted here, DMARC still fails because the header-from domain is that of the actual user but DKIM/SPF both use the server hostname, so DMARC fails...

Great, I've just created a subdomain using the legacy mode to link it to the the folder and it's now showing in Wordpress Manager. Thanks a lot for the info @ericosman

Hi, I've just transferred a customer from cPanel to our DirectAdmin server. They have a Wordpress installation in a subfolder of public_html and although the Wordpress site is still working and active, it is not listed in 'Wordpress Manager' in the user's Directadmin. Upon further investigation...