Sending email using Gmail SMTPS from SMTP

[Julian Tree]

Hi Helma Community, 

I just want to get a clear idea on where we should submit the code change to the helma 1.x core to in the future.  I know there is Helma NG/RingoJS now, but I am launch a site for a company that require stable production release. So I'm still using Helma 1.7.0.  

I recently came across an issue while sending email using the GMAIL SMTP using helma.Mail that required me to modified the source code at helma.Mail.js

Everything is fine if you are sending email using port 25, all you have you do is to enable 

smtp.tls = true 

in the server.properties

However, if you for some reason your service provider (GoGrid) decided to block your outgoing port 25 and you are forced to use port 465

 to communicate with Gmail, then helma.Mail just hang when using the helma.Mail.send() 

I finally was able to get it to work by modifying the helma.Mail.js by changing:

 "mail.transport.protocol" to "smtps", you need to set the other properties as "mail.smtps." properties, not "mail.smtp." properties.

( http://stackoverflow.com/questions/10409517/trouble-sending-via-gmails-smtp-server-with-java )

This seems to work for me at least for now, however, it leaves out the SMTP protocol. I feel like some revision to the smtp setup is need to allow smtps. 

Any recommendations and where should the new code be submitted to?  On github and which repository? 

https://github.com/helma-org/helma
https://github.com/oberhamsi/helma/tree/helma-1.8

Julian

[Daniel Ruthardt]

Hi Julian,

to quickly answer your main question without having read the actual SMTP details (short lunch break):

http://github.com/helma-org/helma is and was meant to be a github mirror of the SVN repository in order to create forks on GitHub.

https://github.com/helma-next/helma-next is and was meant to be my forked version which ultimately should have been a complete rewrite from the inside. The issue list on this fork also represents what was in Bugzilla and lots of issues have been fixed already and some things have already been re-written and improved. But to be honest, I also didn't find a lot of time lately to continue, although it is still my plan to do so. So I would be happy to see your bugfix also in my fork.

But, feel free to commit it to any other fork like http://github.com/oberhamsi/helma.

Greets,

Daniel

--
You received this message because you are subscribed to the Google Groups "Helma" group.
To post to this group, send email to he...@googlegroups.com.
To unsubscribe from this group, send email to helma+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/helma?hl=en.

[Tobi Schäfer]

hi julian

as the oberhamsi fork at github seems to be the only helma codebase which has advanced reasonably and (afaik) is the base for orf.at’s production code i suggest you direct your pull requests to there.

https://groups.google.com/forum/?fromgroups#!topic/helma/E0i-M_n4j3s

cheers,
tobi

[Simon Oberhammer]

Hi Julian,

I just want to get a clear idea on where we should submit the code change to the helma 1.x core to in the future. 

I finally updated the "official" helma-org/helma repository and would recommend you base your patch on <https://github.com/helma-org/helma>.

Because - important for your patch - I merged the formerly separate repositories "manage" and "modules" into this helma repo.

So even if you yourself use 1.7.0... the current helma-org/helma repository is the most likely candidate for a future release (it only has two patches on top of 1.7.1, both of which have been extensively used in production).

 simon

[Daniel Ruthardt]

Hi all,

forget my last post.

What I haven't seen is, that the helma-org/helma repository on GitHub now became the only repository and as such is not anymore just a readonly mirror of the SVN repository, what I thought it still is.

So in this case helma-org/helma definitely is the place to send pull requests to.

Greets,

Daniel