SMTP Email delivery method
投稿日時:2016年2月04日
This topic is sticking around for many years. I'm personally surprised how high level of ignorance is presented by Zendesk developer.
Sending emails over authorized SMTP is only CORRECT and SAFE option for most companies that are concerned about data safety. SPF method works only to some level and then becomes a liability.
Can't understand what kind of issue Zendesk have with SMTP approach but this doesn't build trust to the whole system. Should you care more about data safety and end-user comfort??
You can be surprised but adding SPF records in many cases is far more complicated that setting up email account and password for it ;-)
Hope you can reconsider ability to sending messages over SMTP. It's biggest disadvantage I can find at the moment if I compare Zendesk to competitors. Rest pass this test with flying colors.
Best Regards
Konrad
55
60件のコメント
公式
Kristal Lam
Hi everyone!
Thanks for taking the time to provide feedback around SMTP Email Delivery! This is something that we have on our roadmap, we’re going to be starting discovery for this early next year.
Once we start discovery, we would love to reach out to everyone who has shared feedback for requirements.You can expect us to reach out to you to gather more information in (Quarter/Year). We’ll continue to collect feedback around why this is important to our customers today and the use cases it will solve through this post as well and reach out when we’re ready to start discovery.
Thank you!
0
Sean Cusick
Thank-you everybody for your interest and feedback. Here is the EAP Intro and Signup Form doc. All of the currently available information we have is contained within that page.
0
Johnathan Kulow
The following link outlines the changes I mentioned as described by Proofpoint, but it requires a login so I'll also attach a screenshot to read: Proofpoint's Response on CIDR Range 40.95.0.0/16 Giving Relay Deny errors
Here is the link to the Microsoft documentation.
0
Johnathan Kulow
Hi 1263082333209
On March 2, 2023, you mentioned this was on the 2023 roadmap. On December 1, 2023 you mentioned this feature was under development.
As of the first quarter of 2024 Microsoft has started a slow roll-out of some mail handling processes to ensure their IP's don't end up on blacklists due to open relays forwarding too much spam. This now affects the consistent delivery from our internal support address relaying to our Zendesk support address to create tickets, and I'm sure we're not the only Zendesk customer having issues. We have SPF and DKIM setup properly but that's not the solution, and never should have been the solution to begin with, any longer. We NEED the ability to setup authenticated SMTP leveraging an o365 account in order to maintain brand consistency with our support.
Could you provide any sort of update? I saw reference that this type of functionality exists within Zendesk Sell, so it's not like the knowledge to implement the solution is missing from Zendesk's internal development team. We're just all curious why it's been 8 years since this thread was first opened expressing similar concerns to today, and still not having a solution in place to address things.
Thank you.
1
Creed
Hello Sean Cusick
Can I get a share of the development schedule?
I wonder when it will be released.
We are very interested in this feature.
It's a must-have feature.
0
Sean Cusick
We are currently in development for an Authenticated SMTP Connector. We do not have an ETA for when that feature will be released. We will update this thread once we have more information.
0
Anton Kikels
Should be implemented early last year... Now it's time to implement this feature. As Jarrad Richards told the signature Management is something important but also Mail signing and encryption... We all getting closer to use Mailrelay's for automatically sign and encrypt emails and this is at the moment not possible...
0
Permanently deleted user
Sean Cusick We're at the end of November now, any ETA available please?
Would love to see if it's possible to retain features such as CodeTwo (signature manager), to stop double handling of signatures in multiple locations (Zendesk & CodeTwo).
2
Mark Evans
Adding a voice, here. This is something our IT department requires so that there is a record of all emails in and out of the organization - something I'm sure many others can relate to. The increased delivery reliability would be a bonus. Eager to learn when this feature will be available.
Last status update was in March, so we're another half-year on now. Any sign?
0
Mehd Raza
Planning to move from FreshDesk to ZenDesk & testing different optons of ZenDesk, but found this SMTP option is not available. Will move on to this platform once this option is properly available.
Also Sean Cusick, one option which I have complaint to FreshDesk and they have not resolve it yet. Option is that when sending emails from custom domain SMTP (not gmail or yahoo), it just sent email from our server but does not save in SentBox of the email address. In programming, we have to use SMTP for sending email and must add few lines of extra codes (like imap_append in PHP) to save sent email in SentBox. So please must provide this option or add some checkbox "to save emails in SentBox".
Just followed the thread and also upvoted. Keep us posted.
0
Sean Cusick
I can confirm that this feature is on our 2023 roadmap. We have no ETA at this time, though we will update this thread once we are ready to roll the feature out.
1
サインインしてコメントを残してください。