Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This is related to this question:

linux - Ways to get a bounceback report for my newsletter application? - Server Fault

Let's say I'm generating email addresses like this when I send out newsletters to identify bounces and unsubscribe them from my newsletter:

I assume I'd use this in the return-path, right?

Then how would I set it up in postfix to collect all these addresses prefixed with "bounce-" into one mailbox?

Finally, I've heard people mention a soft bounce vs. a hard bounce. Can someone explain the different and how they should be counted to know when to permanently remove someone from an email newsletter?

share|improve this question
Note that an email address that includes the word "bounce" may also be viewed as "yuck"... (spam)—that being said, if you can stick your own Message-Id in your header, it has to be sent back and that would be enough to check who's who. – Alexis Wilke Nov 11 '15 at 3:43
up vote 12 down vote accepted

The exact answer to your question (handling the address) depends on how your server is configured to receive mail. If is the virtual domain the best you can do is collect the messages in the mailbox (assuming recipient_delimiter = -).

If is the locally delivered domain for the server (mail is delivered to actual system accounts) then you can add a .forward file to the home directory of the bounce user, which delivers to a program that parses the bounce information and records it in a database or file. See man local for more info on the .forward format and how to deliver to a program.

What we do, since we send messages for a large number of domains, is use as our VERP domain. This domain needs to be added to relay_domains. Create /etc/postfix/transport_maps with this content:             bulkbounce:

Then append a line similar to this to /etc/postfix/

bulkbounce   unix  -       n       n       -       -       pipe
  user=nobody argv=/usr/local/bin/ ${recipient}

The script accepts the VERP address as its command line option, parses it and makes the necessary database updates to record the bounce.

share|improve this answer
Ooh, I like the idea of using the recipient delimeter to group them. Typically a + is used right? I think that will work great, thanks! – Brian Armstrong Jul 31 '09 at 21:40

Most modern mailing list software already knows how to handle VERP messages if the MTA is properly configured to pass them back to the mailing list software. In the case of GNU Mailman you should checkout the FAQ page aptly named "How do I use VERP with a - delimiter (Postfix recipient_delimiter)?".

If you're making your own custom newsletter software to handle this you should ask yourself why you're re-inventing the wheel instead of using existing applications that can handle the task simply and easily for you already.

share|improve this answer
Yep, I'm making my own newsletter software. There is a good reason! – Brian Armstrong Jul 31 '09 at 3:23
Then you should look at having it use VERP to handle bounces properly. – Jeremy Bouse Jul 31 '09 at 10:48
Hi Jeremy, I think you're right VERP is the standard solution here, although it appears it's only useful to identify the sender and recipient. In this case we need to also identify the particular message which went out that caused the bounce, so I believe we'll have to do a custom solution with our own ID in the address. I think the solution mentioned below using a recipient delimeter will let us group them together in one bounce account. Thanks for the response though I appreciate the help! – Brian Armstrong Jul 31 '09 at 21:39
Insyte's solution is just a modified VERP at it's core. You just need to make sure that it provides enough of a unique identifier for your bounce handler to identify it. In most mailing list software that is the email address, but could be anything since you're designing your own. – Jeremy Bouse Aug 1 '09 at 0:25

Actually, Instyle's answer is very difficult to implement if you want to support many different domains and it is wrong because:

a) With his example of transport_maps, all the emails sent to that domain are sent to that specific service without any regard to whether the emails are bounced emails or not. Since it uses a specific domain name, it should indeed only be bounced emails... but it cannot be guaranteed that way.

b) The data sent to your script is the email itself and not the bounce message. In other words, your code may have no idea why the email was bounced (i.e. local bounce will send you the original email only.)

The correct way to do that setup in postfix is to use the bounce notification class.

1) In /etc/postfix/

notify_classes = bounce
bounce_notice_recipient =
transport_maps = hash:/etc/postfix/transport_maps

2) In /etc/postfix/transport_maps

# when you make changes to this file, run:
#   sudo postmap /etc/postfix/transport_maps bulkbounce:

As you can see, we now tell postfix to use whenever an email gets bounced. Then in the transport map, to use bulkbounce as the service to handle any email address to

Finally you can define bulkbounce with your script:

3) In /etc/postfix/

bulkbounce unix -       n       n       -       -       pipe
  flags=FRq user=bounce argv=/home/bounce/bin/snapbounce --sender ${sender} --recipient ${recipient}

This script requires you to have a user. nobody is a good choice too. If you want to have a specific user, you can create it with:

useradd bounce

Without the script in, the emails are sent to the bulkbounce account. So if you have a script that parses emails from files, this would work without the transport_maps and changes.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.