Search results

Why not use php-fpm's chroot directive for this? That's already built into php-fpm. You have bubblewrap already. You'd just have to build a chroot'd directory environment for every user and then set each user's php-fpm pool to their respective chroot'd directory. I haven't had a chance to...

I love how much DirectAdmin can be customized. But the lack of documentation and just everything scattered every where is the part that just REALLY gets on my nerves. Like... Why can some things be turned off with a commands.deny or never_command list but other things can't? Where do we...

Am I crazy or did you used to be able to put CMD_EMAIL_VACATION in either /usr/local/directadmin/data/users/%user%/commands.deny or add it to a colon separated list in the never_commands option in /usr/local/directadmin/conf/directadmin.conf and that would prevent Vacation Messages from showing...

As far as giving the message a better appearance of who it is coming from - it's important to note that the message sent out includes a Reply-To header. That Reply-To header is always going to be set to the reseller or admin's Contact E-Mail Address - that part does not change. So even if the...

I think a lot of this thread is just over complicating things - I suppose a lot of that could be my doing, since I posted multiple solutions with sendmail_pre.sh scripts. I would just go back to the very simple solution. Replace the From Header with diradmin@${HOSTNAME} and call it a day...

I suppose if you have a reseller that is using a local-to-the-server email address as their Contact E-Mail Address (not a yahoo.com, gmail.com, outlook.com, etc email address), then that address can be used to send messages From. Presumably, the account would have SPF and DKIM set up to match...

Well... not try to sound condescending... but this ain't 2005 any more. Maybe in 2005 you could use your yahoo.com email address as the From address from any server and any message you sent. But it wasn't proper then. Now there are measures the dictate that it's not proper. If you - the...

Your SPF and DKIM are both failing: Authentication-Results: spf=none (sender IP is 5.9.XX.XX) smtp.mailfrom=v9.my-domain.co.uk; dkim=none (message not signed) header.d=none;dmarc=fail action=quarantine header.from=v9.my-domain.co.uk;compauth=fail reason=000 I would guess that there is no...

You can use the hostnamectl utility on the command-line to set the server's hostname. No clue what DirectAdmin's setting of the server's hostname actually does. To use hostnamectl, you would do: hostnamectl set-hostname your.fully.qualified.domain.name.for.the.server.tld or sudo hostnamectl...

I suppose one bit I left out, this assumes your server's hostname is a Fully Qualified Domain Name (FQDN). To put this simply, if you go to your server's shell (SSH) and type: echo ${HOSTNAME} What is displayed? If this just says: server Or just a single word, that's not a FQDN. An FQDN...

To a degree, you are correct to wonder this. BUT... a reseller setting their Contact E-Mail Address has a reasonable assumption that this is the email address that notices are going to go TO. Not necessarily the email address messages are sent FROM. Any time you send an email message to an...

Is %%%%%%%%%.co.uk a domain that is setup on the same server you are creating accounts on? I'm guessing that is the case and even though SPF alignment isn't passing with DMARC, DKIM alignment is. It's when the From header is using a foreign domain name - one that does not exist and resolve to...

All of this rears it's head when you Add a New User and have the checkbox for Send E-Mail Notification checked. I suspect this is done in other emails sent out by DirectAdmin as well. I suspect this is the case when an account reaches it's disk quota limit or bandwidth limit. I see some...

That's what I thought, but wasn't what I was seeing. Then I found the documentation for this hook: https://docs.directadmin.com/developer/hooks/miscellaneous.html#sendmail-pre-sh And according to that documentation, "This script will allow you to override the sendmail call and handle the...

You can hackify your way to a solution to this by using the sendmail_pre custom hook. Create the file /usr/local/directadmin/scripts/custom/sendmail_pre.sh with the contents: #!/bin/bash full_message=$(echo "${full_message}" | sed -E...

Meh, I'd just settle for the correct usage of the From header right now. If a reseller doesn't like the From header being from a generic name, then they can uncheck the checkbox that sends an email. The problem right now is that resellers are oblivious to the fact that this From header is...

This would seem to ultimately be the issue you are having from the post you linked to. For the longest time, sender spoofing was allowed. And technically there's nothing in the SMTP RFCs that prevent sender spoofing. When using SMTP, you can use a From address (envelope-sender or header from)...

That appears to be the template for the message. But it doesn't include any of the header information, which is what needs to be modified. That's why I don't think the header information is customizable. And this would need to be fixed by the actual DirectAdmin developers. But I'm also a...

I don't think those are message templates. Those look to be more configuration templates (i.e. what actually gets added as a VirtualHost when you create a new account). Nothing comes up when I search specifically for this new account message: # grep -lr 'is now ready for use'...

From what I can tell, DirectAdmin is incorrectly setting a From Header address in it's system outgoing email messages. Specifically I am seeing this in the messages when a new account is created, i.e. the ones with subjects of: Your account for example.tld is now ready for use. and Creator...