-
OK, after a little more investigation, it seems that smtplib.py indeed does support TLS, but a couple of things might be in the way of getting this to work.
1) StormSiren does not tell smtplib.py to use TLS in this case
2) As shown in this example (though possibly outdated):
http://bit.ly/2VNXn
there may be a problem with the Gmail server.
2009-04-21 16:37:28 UTC by jphillips
-
I'm trying to get 2.0RC3 working. Finally got it to ise the correct StormSiren.conf file.
I am wanting to use Gmail as my SMTP server as I do not run my own SMTP server, and have configured it to do so, but Gmail requires that TLS is used as part of the authentication. It seems that smtplib.py does not support TLS?.
2009-04-20 21:20:43 UTC by jphillips
-
I loved the original StormSiren, but I was even happier to know that 2.0 handles the new XML CAP info. I just wish it was as easy to set up and get running as the original. *sigh*.
2009-03-23 02:24:29 UTC by jphillips
-
No--it's one county, but it's split into two NWS forecast zones. This is very common in some parts of the country, especially where elevation changes over a short distance or the county is adjacent to a large body of water.
So: http://www.weather.gov/wwarss-tst/ct.php?x=2
Meanwhile, do you know about this:
"It is expected these CAP 1.1 feeds will replace the current feeds by...
2008-11-09 18:24:21 UTC by ctwxman
-
Unsure how the username/password example became corrupted... A clean example should be:
proxy = USERNAME:PASSWORD@proxy.example.com:3128.
2008-11-09 17:11:56 UTC by cfreeze
-
Ok, I didn't realize that there was actually two different counties with the same name. You can take a look at the wiki for how to configure a MythTv device.
http://www.cfreeze.com/trac/stormsiren/wiki/MythTvDevice.
2008-11-09 17:09:21 UTC by cfreeze
-
It does seem to want Northern and Southern, since it sent the Litchfield forecast as soon as I added that. There are two Litchfield County entries in the CAP file.
currently: [1]
device = email
to = me@geofffox.com
alert = forecast,statement,advisory, watch,warning
areas = Litchfield,CT:Hartford,CT:Windham,CT:Tolland,CT:Fairfield,CT:New Haven,CT:Middlesex,CT:New London,CT:Southern...
2008-11-09 07:47:41 UTC by ctwxman
-
The extra alert could have come from me. Check the email headers as I was using your configuration file for testing. I would not expect you to have to do anything other than specify the "Location,State" in your 'areas' defintion. The current ct.cap file from weather.gov does not include any alerts for Litchfield,CT. Have you been able to use the MythTV alert device yet? The...
2008-11-09 07:39:02 UTC by cfreeze
-
Got on Trac--finally. Have not posted my probs because of this ongoing conversation. Took email forever to reach me. Your site is somewhat sluggish to me in normal ops as well.
Geoff.
2008-11-09 07:36:26 UTC by ctwxman
-
OK -
Got the Hartford, Tolland and Windham forecasts twice - 2:13 and 2:21 am. The cron is running every minute and the forecasts didn't change (I think).
Did not get Litchfield County--and I assume I have to split it (and te other four counties) into north and south as per NWS zones.
Not sure how to get you the terminal dump you need. Was running the GUI to unpack the .deb.
I only...
2008-11-09 07:34:54 UTC by ctwxman
