OTRS don't put a Return-path: header into the agent notification mails
Closed, DeclinedPublic
Actions

Edit Task
Edit Related Tasks...
Create Subtask
Edit Parent Tasks
Edit Subtasks
Merge Duplicates In
Close As Duplicate
Edit Related Objects...
Edit Commits
Edit Mocks
Mute Notifications
Protect as security issue
Award Token
Flag For Later

Assigned To

None

Authored By

	• bzimport
	Nov 1 2005, 10:26 AM

Description

Author: wikipedia

Description:
In the "There is a new ticket" mails from OTRS there is no adress in the
Return-path: header. (Perhaps this is the cause for Exim filtering failing).

Version: unspecified
Severity: normal

Details

Reference: bz3853

Event Timeline

• bzimport raised the priority of this task from to Lowest.Nov 21 2014, 8:54 PM

• bzimport added a project: Wikimedia-Mailing-lists.

• bzimport set Reference to bz3853.

• bzimport added a subscriber: Unknown Object (MLST).

• bzimport created this task.Nov 1 2005, 10:26 AM

jeluf wrote:

According to RFC822, the Return-path header is set by the final transport, which
is your MTA, not ours.

See http://www.freesoft.org/CIE/RFC/822/28.htm

OTRS don't put a Return-path: header into the agent notification mailsClosed, DeclinedPublicActions

Description

Details

Event Timeline

OTRS don't put a Return-path: header into the agent notification mails
Closed, DeclinedPublic
Actions