• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Mails for system users

archer2000

New Pleskian
I created a new customer with a subscription. As far as I see, this user will be the linux user as well. Now, I would like to be able to send (system) mails to that user. I tried:

(1) .forward-file in the home directory of the user
(2) Adding the user to /etc/aliases
(3) Adding the user to /var/spool/postfix/plesk

(2) and (3) with

- postmap -s aliases > aliases
- newaliases / postmap hash:aliases

Always I am getting such an error (I used mail test as root-user):

Oct 8 23:07:11 servername postfix/pickup[4994]: 05B8C1AE64C8: uid=0 from=<root>
Oct 8 23:07:11 servername postfix/cleanup[5002]: 05B8C1AE64C8: message-id=<[email protected]>
Oct 8 23:07:11 servername postfix/qmgr[4995]: 05B8C1AE64C8: from=<[email protected]>, size=374, nrcpt=1 (queue active)
Oct 8 23:07:11 servername postfix/error[5256]: 05B8C1AE64C8: to=<[email protected]>, orig_to=<test>, relay=none, delay=0.41, delays=0.34/0/0/0.07, dsn=5.0.0, status=bounced (User unknown in virtual alias table)


Where I have to add the user?
 
I'm also very interested in how to do this.

I've been wondering about handling email for these system users since I set up Plesk last week, but didn't put much thought into it because I didn't see where it mattered, until today.

If a user schedules a task without changing the default notification settings, output from cron goes to user (at) myserver.net and root receives a bounce message. Consider the scenario where user is testing something and sets cron for every minute. While user wonders where the output is going, my inbox fills up.

Ideally, this would be handled automatically by Plesk and mail for these system users would forward to the subscriber's email address (like how root email forwards to the email address in admin profile).

An alternative solution, though not ideal, that would work for this scenario is changing the default notification setting to off.
 
Last edited:

My root mailbox was not full. Plesk automatically sets up an alias for root. Mail to root@localhost comes to the email address I set as the admin address in the Plesk control panel.

Problem is that I *do* want legit root mail, but not hundreds/thousands of bounces from a user's cron job. There should be a way to forward system users' mail to their "real" accounts.

For example, I create a customer with the user name cc-panel and there is an email address associated with this account which either I or the customer can change. Then I add a subscription to this customer with the system user name contactc. This user name is their SSH/FTP login. If they create a cron job, the default is to send output to contactc (at) myserver.net which has no entry in the virtual alias table.

I figured out how to manually add entries to the virtual alias table, but I have no idea how to make that permanent. I assume that this file will be overwritten any time an email address is added/changed on the server.

What I'd like to see is automatic additions to the virtual alias table, when a subscription is added, to forward the sys_user (at) myserver.net to the client email. This entry would then need to be updated whenever client/server admin email address was changed.

At the very least, the default notification setting should not be to send email to a non-existent address.
 
Back
Top