* bare minimum SMTP implementation
@ 2009-10-30 13:53 darshan.ghumare
2009-10-30 14:53 ` FunkyChunkyMunky
2009-10-30 20:45 ` Glynn Clements
0 siblings, 2 replies; 3+ messages in thread
From: darshan.ghumare @ 2009-10-30 13:53 UTC (permalink / raw)
To: linux-c-programming
In my project one thread will have a task to send mail. It can be send to say gmail also.
But if you try to connect smtp.gmail.cm@25 then after greeting gmail ask you to setup SSL.
I have search a lot for SMTP implementation that support STARTTLS, many of them consume about 800+kb. As my project is run on embedded system this is not feasible to me.
If anybody knows any implementation that support above STARTTLS still consume less memory?
Many of them ask for OpenSSL but that consume 800kb+ memory hence not feasible for me.
Thank you very much
Regards
Darshan
--
This message was sent on behalf of darshan.ghumare@gmail.com at openSubscriber.com
http://www.opensubscriber.com/messages/linux-c-programming@vger.kernel.org/topic.html
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: bare minimum SMTP implementation
2009-10-30 13:53 bare minimum SMTP implementation darshan.ghumare
@ 2009-10-30 14:53 ` FunkyChunkyMunky
2009-10-30 20:45 ` Glynn Clements
1 sibling, 0 replies; 3+ messages in thread
From: FunkyChunkyMunky @ 2009-10-30 14:53 UTC (permalink / raw)
Cc: linux-c-programming
darshan.ghumare@gmail.com wrote:
> In my project one thread will have a task to send mail. It can be send to say gmail also.
> But if you try to connect smtp.gmail.cm@25 then after greeting gmail ask you to setup SSL.
> I have search a lot for SMTP implementation that support STARTTLS, many of them consume about 800+kb. As my project is run on embedded system this is not feasible to me.
> If anybody knows any implementation that support above STARTTLS still consume less memory?
> Many of them ask for OpenSSL but that consume 800kb+ memory hence not feasible for me.
>
> Thank you very much
>
> Regards
> Darshan
>
>
>
> --
> This message was sent on behalf of darshan.ghumare@gmail.com at openSubscriber.com
> http://www.opensubscriber.com/messages/linux-c-programming@vger.kernel.org/topic.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
why deliver directly from the embedded device?
setup a relaying mta and have all the devices forward to that server
which will deliver the mail
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: bare minimum SMTP implementation
2009-10-30 13:53 bare minimum SMTP implementation darshan.ghumare
2009-10-30 14:53 ` FunkyChunkyMunky
@ 2009-10-30 20:45 ` Glynn Clements
1 sibling, 0 replies; 3+ messages in thread
From: Glynn Clements @ 2009-10-30 20:45 UTC (permalink / raw)
To: darshan.ghumare; +Cc: linux-c-programming
darshan.ghumare@gmail.com wrote:
> In my project one thread will have a task to send mail. It can be
> send to say gmail also.
> But if you try to connect smtp.gmail.cm@25 then after greeting gmail
> ask you to setup SSL.
> I have search a lot for SMTP implementation that support STARTTLS,
> many of them consume about 800+kb. As my project is run on embedded
> system this is not feasible to me.
> If anybody knows any implementation that support above STARTTLS
> still consume less memory?
> Many of them ask for OpenSSL but that consume 800kb+ memory hence
> not feasible for me.
http://www.google.com/search?q=embedded%20SSL
--
Glynn Clements <glynn@gclements.plus.com>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-10-30 20:45 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-30 13:53 bare minimum SMTP implementation darshan.ghumare
2009-10-30 14:53 ` FunkyChunkyMunky
2009-10-30 20:45 ` Glynn Clements
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).