I know this is an old thread, but has anyone had success with getting the reply-to address to work? We also get emails where we need to use the reply-to address instead of the from address. I am using IMAP and have edited class.mailfetch.php (at line 14) from this:

function getHeaderInfo($mid) {

$headerinfo=imap_headerinfo($this->mbox,$mid);

$sender=$headerinfo->from;

to say:

function getHeaderInfo($mid) {

$headerinfo=imap_headerinfo($this->mbox,$mid);

$sender=$headerinfo->reply-to;

and the program stops retrieving emails when I know there are emails on the server. This is the only issue holding me back from using OSTicket. Any help would be appreciated!

Thanks in advance,

Tim

Don't have time to test this right now, but off the top of my head, it should be reply_to not reply-to

4 months later

Piping Method

Anybody know how to get email piping to honor reply to?

3 months later

Can anyone else has more effective way to deal with trouble ?

a month later

I just added this little bit of code so that if the reply-to address is set it uses it otherwise it will use the from email address.

Before...

function getHeaderInfo($mid) {

$headerinfo=imap_headerinfo($this->mbox,$mid);

$sender=$headerinfo->from;

After...

function getHeaderInfo($mid) {

$headerinfo=imap_headerinfo($this->mbox,$mid);

if (isset($headerinfo->reply_to)){

$sender=$headerinfo->reply_to;

} else {

$sender=$headerinfo->from;

}

Hope this helps.

10 months later

I just added this little bit of code so that if the reply-to address is set it uses it otherwise it will use the from email address.

Before...

function getHeaderInfo($mid) {

$headerinfo=imap_headerinfo($this->mbox,$mid);

$sender=$headerinfo->from;

After...

function getHeaderInfo($mid) {

$headerinfo=imap_headerinfo($this->mbox,$mid);

if (isset($headerinfo->reply_to)){

$sender=$headerinfo->reply_to;

} else {

$sender=$headerinfo->from;

}

Hope this helps.

THANKS... This definitely works...

9 years later

hi all - I had auto-reply rules that were using the reply-to header and all of it was working until i upgraded to ....
osTicket Version 1.14-git

its not working now.

Looks like somethign has broken wrt the detection of reply-to header in incoming emails

@DA7276727

Tested this using latest develop (v1.14.2 + latest commits) with PHP 7.4 and MySQL 8.0 and see no issues.

Cheers.

    Thanks Kevin. i'll try upgrading to the latest and let you know if that fixes it.

    @DA7276727

    Post a screenshot of the entire filter (ie. the config, the rules, and the actions). There could be many reasons the system isn’t using the Reply-To header: the email in question doesn’t match certain criteria, another filter is taking precedence, the target channel isn’t right, etc.

    Cheers.

      2 months later

      Kevin, What I have found is the following...

      Our email goes from
      (A)Sender > (B) intermediate server > forwarded to > (C) recipient mailbox on different server

      C is where Osticket is installed and running.
      Our configuration has been this way from 5 years but we have just moved Osticket to a new server C2 whereas previously we were using a server C1 ...
      In inspecting email headers, C1 did not add a return-path header but C2 is adding a return-path header.
      Since this new server (C2) is adding return path....

      Looks to me that The autoreply from OSticket is ignoring the reply-to if a return-path exists. <<< Is this a correct assumption

      In the emails we send
      (A) Sender has put a reply-to header into the email
      The recipient mailbox's server (C2) > adds a return-path header saying email originally received from.

      Is there a way to configure OSticket to ignore return-path and use reply-to if reply-to exists (because the filters are setup to use reply-to) and it was working when C1 wasnt adding a return-path.

      KevinTheJedi Since it was already working and nothing has changed I think its not the filter. I found another point that could be it, appreciate your advice on my previous message.

        Write a Reply...