Hi,
can anybody tell me why the Reply-To header is parsed
before the From header to get the ticket requestor in
RT::Interface::ParseSenderAddressFromHead ?
Thanks!
Chris
Hi,
can anybody tell me why the Reply-To header is parsed
before the From header to get the ticket requestor in
RT::Interface::ParseSenderAddressFromHead ?
Thanks!
Chris
Hi,
can anybody tell me why the Reply-To header is parsed
before the From header to get the ticket requestor in
RT::Interface::ParseSenderAddressFromHead ?
History. May be a comment in a RFC. Developer’s mood
Thanks!
Chris
List info: The rt-devel Archives
Best regards, Ruslan.
Hi,
can anybody tell me why the Reply-To header is parsed
before the From header to get the ticket requestor in
RT::Interface::ParseSenderAddressFromHead ?
Because it seems more right to have RT pick up the Reply-To rather than
the From if they’re different.
We have an monitoring system that send notifications with
so the ticket requestor is nobody.
If you would have more systems that send mail in this way I thought it
would be better to use the From instead of the Reply-To header to
distinguish the different ticket creators.
But the RFC says that a Reply-To header supersedes a From header so you
are right with the current parse order.
ChrisAm 21.05.2011 05:53, schrieb Jesse Vincent:
On Fri 20.May’11 at 11:43:00 +0200, Loos, Christian wrote:
Hi,
can anybody tell me why the Reply-To header is parsed
before the From header to get the ticket requestor in
RT::Interface::ParseSenderAddressFromHead ?Because it seems more right to have RT pick up the Reply-To rather than
the From if they’re different.Thanks!
Chris