Hello @hlfh,
I hope this message finds you well.
Thank you for reaching out to our Support team.
The Return-Path is not a standard header that can be reliably set manually. It is automatically determined by the receiving mail server based on the SMTP MAIL FROM (also known as the envelope sender), and the server typically writes this value into the Return-Path header.
That said, if your goal is to control where replies are sent, you can configure a Reply-To address in Post SMTP> Settings> Messages tab.
If you have a specific use case in mind or need help configuring this, feel free to let me know.
Thread Starter
HLFH
(@hlfh)
@aqibkhan9 Hi, I am using “The Newsletter Plugin” (TNP) for Email Marketing, I am using it for a blog newsletter with 3200+ subscribers. This plugin allows to set the return-path header, and bounces were going to my postmaster email address, let’s say “[email protected]”. I have never had any issue despite their warning: “Some providers ignore it or block all emails if set“, considering it a FUD could be an exaggeration, it is though a bit my feeling on this. I was also using the “SMTP Addon” of TNP but I needed a few more features: logging and resend. Currently, because their “Bounces Addon” is looking at “[email protected]”, it is no longer working, and your plugin seems to remove or ignore the return-path configuration and set it to the from email address. Being able to set the return-path header would be very reliable for my use case. My current point of view is the from and reply-to headers are often the same, but the return-path is a technical one that is only used for mailing list optimization, so the end client that is in the from and reply-to email addresses does not have to see the bounces: it is not the client’s job. The return-path header has always worked for me. It would be great if you integrate the ability to set the return-path header in your plugin. If I look at the raw email, return-path header was correctly set before switching to your great SMTP plugin.
-
This reply was modified 4 months ago by
HLFH.
-
This reply was modified 4 months ago by HLFH.
Thread Starter
HLFH
(@hlfh)
Another question. In my TNP plugin, I have also set the max emails per hour to 3000.
Since I use your SMTP capability, does the free version have a default for it as it seems slow and seems below 3000 per hour.
Do I need the premium version (Postman SMTP Pro) and the Advance Delivery feature? https://postmansmtp.com/docs/advance-functionality/advance-delivery-logs/
I want to set the Email Quota value to 3000 per hour.
What is the default quota per hour for the free version?
-
This reply was modified 4 months ago by HLFH.
Hey @hlfh,
Thank you so much for sharing your use case. I really appreciate the context.
I’ll discuss this with our Development team to see whether it’s feasible to implement a setup that allows explicitly defining the Return-Path header. At the moment, you can customize headers via Post SMTP> Settings> Messages> Custom Headers, which may help depending on your requirements.
Please note that discussions related to the Pro plugin aren’t permitted on public threads. For anything related to Pro features or licensing, feel free to reach out to us directly through our official website.
Regarding the free plugin: it sends emails one by one, so there’s no quota set by Post SMTP itself. Instead, it typically relies on the sending rate or limits imposed by the triggering plugin or your mail provider.
Thread Starter
HLFH
(@hlfh)
Hi, with the former SMTP Addon I was using, I was set to unlimited (“0”) for the “max emails per second” and set to “3000” (now set to “3500”) for the “max emails per hour” setting. It sounds like I may have a capacity of 4468 emails per hour according to this addon. With your plugin, instead of maximum one hour and a half, it took about 8 to 10 hours to send the 3200+ emails to the subscribers of the newsletter. It means I would definitely need your “Advance Email Delivery and Logs extension” to make the switch from my former SMTP plugin. Might be good to announce this feature at the top of your plugin homepage within this paragraph: “you can unlock even more advanced features, such as […] and much more. I will reach out directly as advised.
Regarding the return-path header, customizing headers via Post SMTP> Settings> Messages> Custom Headers might help, I also have read some of your code that seems to willingly ignore the return-path header, so I don’t know. Might be related to RFC 5321 compliance (section 4.4), in particular:
“A message-originating SMTP system SHOULD NOT send a message that already contains a Return-path header field”
But what if allowing the Postman SMTP users to choose whether they want to comply with RFC 5321 or not is better? It will definitely increase the reach of Postman SMTP for the Email Marketing use-case if you have the return-path header option in the GUI.
Tu summarize, I need:
Feature requests:
- Return-path header direct support for the postmaster to handle non-delivery reports.
- EML archives of sent emails to share them with the postmaster service of ESPs, and therefore reduce false-positives and increase deliverability.
Issues / Bugs:
- Fix the resend function: in the free version, when you click “Resend” on an email, you risk to click and resend twice because nothing happens for a few seconds when you hit the button
Already available but not well featured in the plugin homepage:
- Advance email delivery (being able to optimize the email sending speed)
I will consider this issue as solved as we are talking about developments which may happen or not in the future.
