• Resolved jorgitobg

    (@jorgitobg)


    Hi,

    How can I customize “Return-Path:” for notifications sended from formidableforms?

    Right now im using Reply-to but gmail filters doesnt seems to recognize this header… only working with “Return-Path:”.

    Also I tried to hardcode Return-Path: on phpmailer_init but doesnt achieve nothing yet…. any advice on how to use reply-to header for customizing Return-Path?

    Maybe you have some function/hook to achieve this?

    Regards

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter jorgitobg

    (@jorgitobg)

    I forgot to specify that Im hosting my mail servers on gmail servers…..

    Plugin Support Njones35

    (@njones35)

    Hi @jorgitobg,

    We’ve seen this issue pop up with Gmail a couple of times.

    There are a couple of scenarios where the new Gmail interface will ignore the reply-to address in the email header.

    It seems that if the From and To addresses are the same, this issue pops up.
    Also if the From address is saved as a Gmail sending account.

    Does this sound like what you’re running into?

    Thread Starter jorgitobg

    (@jorgitobg)

    Hi @njones35, thanks for your answer!

    The From and To addresses are not the same, only the same domain. So…. if I need to send the notification to my domain, then: From:[email protected] To:[email protected]… ReplyTo:[email protected]. Still Gmail ignoring reply-to headers, only works with return-path header.

    After many hours debugging I get return-path customized on phpmailer_init by extracting the email I want from email body and sending to $phpmailer->Sender.

    Also I see formidableforms send the subject on base64, why?

    Regards

    Plugin Support Njones35

    (@njones35)

    Hi @jorgitobg,

    Could you please open a ticket in our helpdesk about this? It may be more complex than I initially expected: https://formidableforms.com/new-topic/

    Thread Starter jorgitobg

    (@jorgitobg)

    Done!

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Return-Path: instead Reply-to:’ is closed to new replies.