Also, of course, your experiences. Mainly in /advanced/ e-mail handling, but also other stuff that isn't straight forward using a "plain" HTTP component (like LDAP, OAUTH and such). TIA!
Darian Miller, checked that some 1/2 yr ago. Looks really nice - except for the cost :) ended up using streamsec for the foreseeable future. When and if I'll have the turnaround to pay 5k euro a year I think it's an excellent solution.
Well, i'm experimenting with Synapse. I must say to send e-mails plain/html in different languages and with different encodings is MUCH easier than using Indy.
Dany Marmur I use Indy to send HTML emails, but I wrote a wrapper unit to do it. My unit loads HTML templates, replaces any macros found in the template text and sends the email out to multiple recipients. Works great.
That is why I wrote my unit and Email classes. You figure out Indy once, and reuse it on multiple projects. I can send complex mail-merged HTML emails with about 10 lines of (non-messy) code.
It's what i am about to do. I already have a good wrapper for /sending/ emails. Now i'm writing one for receiving them. Since writing the one for sending was messy IMHO - i took the chance to look at alternatives. Rewriting the wrapper for /sending/ was minutes with Synapse (but then i knew what i wanted). The wrapper for receiving is almost done :)
Did you exclude Indy on purpose?
ReplyDeleteYup, i'm interested in what else is out there.
ReplyDeleteAlso, of course, your experiences. Mainly in /advanced/ e-mail handling, but also other stuff that isn't straight forward using a "plain" HTTP component (like LDAP, OAUTH and such). TIA!
ReplyDeleteSecureBlackBox by Eldos is good.
ReplyDeleteI write a lot of TCP/IP apps. Indy works fine. It supports all the major protocols and you can easily design your own if need be.
ReplyDeleteDarian Miller, checked that some 1/2 yr ago. Looks really nice - except for the cost :) ended up using streamsec for the foreseeable future. When and if I'll have the turnaround to pay 5k euro a year I think it's an excellent solution.
ReplyDeleteKevin, sure. But there's some quirks that I have lost time on. That's the reason I'm asking.
ReplyDeleteI use IP works. Non blocking makes them easy to work with
ReplyDeleteWell, i'm experimenting with Synapse. I must say to send e-mails plain/html in different languages and with different encodings is MUCH easier than using Indy.
ReplyDeleteDany Marmur I use Indy to send HTML emails, but I wrote a wrapper unit to do it. My unit loads HTML templates, replaces any macros found in the template text and sends the email out to multiple recipients. Works great.
ReplyDeleteThat is why I wrote my unit and Email classes. You figure out Indy once, and reuse it on multiple projects. I can send complex mail-merged HTML emails with about 10 lines of (non-messy) code.
ReplyDeleteIt's what i am about to do. I already have a good wrapper for /sending/ emails. Now i'm writing one for receiving them. Since writing the one for sending was messy IMHO - i took the chance to look at alternatives. Rewriting the wrapper for /sending/ was minutes with Synapse (but then i knew what i wanted). The wrapper for receiving is almost done :)
ReplyDelete