similar to: res_calendar & LetsEncrypt

Hi, I try to use res_calendar with ownCloud. While it works with google/ics, I've some difficulties with caldav and ownCloud[1]. According to the logs and tcpdump the calendar entries have been fetched but they are not available in Asterisk. 'calendar show calendars' doesn't show the status busy, 'calendar show calendar owncloud' doesn't show the current events.

dear lists trying to integrate google calendar with asterisk 1.8.20.1. but 'calendar show calendars' not showing anything. when i run 'show modules' on asterisk prompt. it is not showing res_calendar_caldav.so module, only showing res_calendar.so module . is there anything wrong with google API. plz help. abhi -------------- next part -------------- An HTML attachment was

Hi I'm using asterisk 1.8.25.0 on CentOS 6. I have compiled it with all the calendar modules: *CLI> module show like calendar Module Description Use Count res_calendar.so Asterisk Calendar integration 4 res_calendar_ews.so Asterisk MS Exchange Web Service Calenda 0 res_calendar_caldav.so

Hello I have changed type 'caldav' to 'ical', but still no succes : [Oct 27 10:30:38] WARNING[23388]: res_calendar_icalendar.c:117 auth_credentials: Invalid username or password for iCalendar 'cal1' [Oct 27 10:30:38] WARNING[23388]: res_calendar_icalendar.c:150 fetch_icalendar: Unable to retrieve iCalendar 'cal1' from

Hello I find very little feedback on the following warning/error when trying to connect to Google calendar : [Oct 26 12:11:14] WARNING[24926]: res_calendar_caldav.c:118 auth_credentials: Invalid username or password for CalDAV calendar 'cal1' [Oct 26 12:11:14] WARNING[24926]: res_calendar_caldav.c:157 caldav_request: Unknown response to CalDAV calendar cal1, request REPORT to

Asterisk-11.9.0, Fedora 20: res_calendar_caldav.so => (Asterisk CalDAV Calendar Integration) [Apr 27 10:49:13] ERROR[4255]: res_calendar_ews.c:911 load_module: Exchange Web Service calendar module require neon >= 0.29.1, but neon 0.30.0: Library build, IPv6, Expat 2.1.0, zlib 1.2.8, GNU TLS 3.1.13. is installed. Is this a bug, or do I need to downgrade to 0.29? sean

On Tue, 19 Jun 2018, tech wrote: > Jun 19 16:34:55 REDACTED upsmon[7389]: Can not initialize SSL context > I am lost. Comments and Help welcome. It's only a comment, but, this message comes from NUT program netssl.c status = NSS_NoDB_Init(NULL); if (status != SECSuccess) { upslogx(LOG_ERR, "Can not initialize SSL context"); nss_error("upscli_init /

On Wed, 27 Jun 2018, tech wrote: > It was a access right violation on /etc.../letsencrypt/....cert . The folder was own by root:root   > Had to create a group nutusers including root and my nut users. After that, had to change the chmod for the folder from 755 to 775 > > Now, running upsc -l > > Init SSL without certificate database > 850PRO > > Witch is better. But

I have DNS setup as my auth, and use nsupdate to let it get the token. On 3/3/17, 12:07 PM, "dovecot on behalf of David Mehler" <dovecot-bounces at dovecot.org on behalf of dave.mehler at gmail.com> wrote: Hello, I know some users here are using letsencrypt for their CA. If this is to off topic write me privately. I'm wanting letsencrypt to take

On 2017-03-03 19:07, David Mehler wrote: > Hello, > > I know some users here are using letsencrypt for their CA. If this is > to off topic write me privately. > > I'm wanting letsencrypt to take over as my CA, replacing existing self > signed certificates. I've got web working, a certificate for https > sites and one for webmail as they have different names. What

David Mehler <dave.mehler at gmail.com> writes: > I'm wanting letsencrypt to take over as my CA, replacing existing self > signed certificates. I've got web working, a certificate for https > sites and one for webmail as they have different names. What I'm now > wanting to do is get letsencrypt going for my email setup, the smtp > handled by postfix, but mail, and

> Thanks. Is there another way of doing this? I've got a web server > running on 80 and 443. Are there any other options? I'm getting this list in digest mode, so it's possible by the time this gets to you, I will have repeated someone else' suggestion. In this situation, where your dovecot server lives on the same host as a web server (wembail?), and this web server is

On Fri, Sep 08, 2017 at 06:47:25AM -0600, @lbutlr wrote: >So this morning at 4am I was awoken to my mail clients getting certificate errors for an expired certificate. > >I hopped on to the server and checked and? no, the LE certs renewed last month and are valid until November. > >After some moments of confusion I noticed that dovecot had been running since before the renewal, so I

"I think it?s probably easier to just kick dovecot once a month." - that's not good from system administration's point of view. You can get into trouble when certificate is renewed but dovecot isn't reloaded yet. And, doing something via cron just by-guess, once a month - is a no no logic. "it seems like checking the certs is something that dovecot should be doing on its

On 08.09.2017 16:20, LuKreme wrote: > That is a great solution, but I think it?s probably easier to just > kick dovecot once a month. Certbot hooks are very easy to write, and are only executed when the certificate is updated. In that light, I can see no advantage in "kick dovecot once a month". ;-) > However, it seems like checking the certs is something that dovecot >

On 08 Sep 2017, at 10:08, Ralph Seichter <m16+dovecot at monksofcool.net> wrote: > What is Dovecot supposed to do? Keep track of the certificate expiry > date? And if that is passed, then what? Automatically shutdown/restart? > What if the certificate has not been updated in between? I think that > handling certificates is better left to the administrator. How I would do it is

On 08.09.2017 19:51, @lbutlr wrote: > How I would do it is IF the certificate is expired, the dovecot should > check if there is a new cert and if so, load it. New cert as in file modification date or checksum changed? Might work. Still, from what I seem to remember, Dovecot loads certificate data before dropping privileges, which is why reloading the data might be problematic without some

On 08 Sep 2017, at 12:21, Ralph Seichter <m16+dovecot at monksofcool.net> wrote: > On 08.09.2017 19:51, @lbutlr wrote: >> How I would do it is IF the certificate is expired, the dovecot should >> check if there is a new cert and if so, load it. > New cert as in file modification date or checksum changed? Either one, but checksum is going to be more reliable. > Might

<master at remort.net> writes: > "writing a script to check the certs" - there is no need to write any > scripts. As one mentioned, it's done by a hook to certbot. Please read > the manuals for LE or certbot. The issue you have is quite common and > of course certbot designed to do it for you. Won't work, of course, if you employ the least-privilege security

On Tue, 12 Sep 2017, dovecot-request at dovecot.org wrote: > What's wrong with using a certbot "post-hook" script such as: > > #!/bin/bash > echo "Letsencrypt renewal hook running..." > echo "RENEWED_DOMAINS=$RENEWED_DOMAINS" > echo "RENEWED_LINEAGE=$RENEWED_LINEAGE" > > if grep --quiet "your.email.domain" <<<