OTRS 6 Feature: Default Headers for Outgoing Emails

Martin Gruner13. Dec 2016 | Development


The practical examples presented in our technical blog (blog.otrs.com) and now in the expert category in our FAQ blog section serve as a source of ideas and documentation to show what is theoretically possible with OTRS in concrete scenarios or sometimes even for more exotic configurations. All configurations presented here were developed under laboratory conditions as a proof of concept. 

We can only guarantee testing and implementation of these concepts to be error-free and productive if implemented in a workshop with one of our OTRS consultants. Without this, the responsibility lies with the customer himself. Please note that configurations from older OTRS versions may not work in the newer ones.

This is the first article in a series about smaller and bigger features of the major version, OTRS 6.

We’ll start with a nice contribution by Renée Bäcker. He added the possibility to define default headers for outgoing emails, which can be necessary for certain network infrastructures. All emails that OTRS generates will automatically include these headers.

This behavior can be configured with the new configuration setting Sendmail::DefaultHeaders. Here you can add custom headers such as Precedence: bulk to suppress any automatic responses from external systems.

Thanks to Renée for the contribution!

Did you know? Contributing to OTRS has never been that easy. Just head over to otrs.github.io to find all you need to get started. We’re looking forward to receiving your great ideas!

Jens Bothe at 19.11.2018, 20:42

No, there is no such feature

Oleg at 15.11.2018, 15:52

Is there and option to set Reply-To: header per queue? Use case is huge: all emails from OTRS must have one FROM email that collects bounces, but cannot be reached outside of MTA, while customers should REPLY-TO.

Your email address will not be published. Required fields are marked *