Skip to main content

Creating no-reply@domain.com account in Postfix

If you wanted to send emails to users but did not want to receive any replies to the email, you would need to setup a no-reply@domain.com email account. These kind of email ids are useful when sending emails containing forgotten passwords or activation code. Below are the steps for creating such account in Postfix.

1. Identify the file containing alias for Postfix

First, make sure the following line in the ALIAS DATABASE section of the /etc/postfix/main.cf is NOT commented out:

alias_maps = hash:/etc/aliases

2. Create an alias that redirects messages to /dev/null

Edit /etc/aliases and add following entry

devnull: /dev/null

3. Create a virtual email id

Edit /etc/postfix/virtual and add following entry

no-reply@domain.com devnull

4. refresh postfix alias and postfix cache

Execute following commands. (You may require root privileges)

> newaliases

> postfix reload

Comments

darkstar said…
Your procedure works for postfix mail server.
How do I make it work for the postfix relay on MX server?
Thanks in advance.
El Fercho said…
Great tip man!
You will also need to set up, in /etc/postfix/main.cf:
virtual_alias_maps = hash:/etc/postfix/virtual

And remember to run postmap /etc/postfix/virtual, once you entered the aliases on the file.
carlos aya said…
For the record, as a fix to the above, I had to put in /etc/postfix/virtual

no-reply@domain.com devnull@localhost


in my relay only postfix setup. Thanks, great resource.
Nelson Castillo said…
I had to add:

virtual_alias_maps = hash:/etc/postfix/virtual

And also run:

postmap virtual

Thanks a lot.

Popular posts from this blog

jupyter notebook execution error: "http://localhost:8889/tree?token=xxx" doesn’t understand the “open location” message

I got this error when I tried to launch jupyter notebook on a mac. It is not a fatal error. I could still go to browser directly and copy/paste the url manually. The error indicates that when the command automatically tried to launch a browser, it couldn't find the default browser in jupyter configuration file. The easy fix is to specify the browser. Here are the steps to do so; 1.   Open ~/.jupyter/jupyter_notebook_config.py in an editor.       If the file does not exist then you can create a default config file by typing the following command;       jupyter notebook --generate-config 2. Search for a word "browser" to locate a following line.     #c.NotebookApp.browser = ''     By default it is commented. You can uncomment it and use one of the following values depending on your browser preference.     # set default browser to chrome     c.NotebookApp.browser = 'chrome'     ...

.ssh/config: “Bad configuration option: UseKeychain” on Mac OS

After upgrading Mac OS to Mojave I started seeing this error when doing "git pull". I was able to follow the steps below as described here ; 1. open ssh config vi ~/.ssh/config 2. Add the following lines to ssh config to keep your configuration compatible with both new and old versions of openssh. IgnoreUnknown UseKeychain UseKeychain yes That fixed the issue for me. Try running git pull again.    More details about the issue are available here .