I have not explicitly enabled ssl lockdown for 127.0.0.1 recently. However, I did recently switch from an old OpenSuSE server system to new hardware running Ubuntu server 16.04.

I changed $type from 1 to 2, as you suggested and got a little farther. The cal.log file had a complaint that "mail is not in the sudoers file.” I fixed that, and authentication is successful now:

01/09/18 23:32:22 [1414] ----
01/09/18 23:32:22 [1414] Sabre CAL
01/09/18 23:32:22 [1414] need auth beforeMethod [REPORT-calendars/john@wilkes.com/SW837404-556F-0373-393D-4516F4034383]
01/09/18 23:32:22 [1414] NWAUTH user=john@wilkes.com pass={hidden} hash=1c74855d13c34eb9421fcbc4d47a1192
01/09/18 23:32:22 [1414] NWAUTH Cached login valid (john@wilkes.com) age=0/1800
01/09/18 23:32:22 [1414] Sabre CAL END

It’s still not working though.

In SurgeWeb I see my four calendars in the panel on the left side of the page, but no calendar entries.

An error message is displayed: SabreDAV REPORT failed: 500 Internal Server Error

No error is reported in the cal.log file.

A little closer, one step at a time…

--
John Wilkes
john@wilkes.com

On Jan 9, 2018, at 2:35 PM, Surgemail Support (Marijn) <surgemail-support@netwinsite.com> wrote:

That login looks like it fails due to SSL restrictions.

The calendaring checks with imap on 127.0.0.1 for authentication. This does not support SSL so looks like you may have enabled the ssl lockdown for 127.0.0.1 recently?

Alternatively the calendaring can be configured to use nwauth directly (provided you are using nwauth that is!). So maybe that is what you did in the past?? To do that edit the following line in surgemail\phplib\netwin\Nwauth_sabre.php:

       // change $type to 2 for nwauth direct authentication!
         $type = 1;

and change it to:
       // change $type to 2 for nwauth direct authentication!
         $type = 2;

Marijn





On Tuesday 09/01/2018 at 5:46 pm, John Wilkes wrote:

The calendar worked for years before my server disk drive died and I replaced it with the mirror system. Is some of the calendar configuration not being sent to the mirror?

$ telnet 127.0.0.1 143
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
* OK IMAP (C) wilkes.com (Version 7.3c3-3)
A001 CAPABILITY
* CAPABILITY IMAP4 IMAP4REV1 NAMESPACE QUOTA UIDPLUS IDLE SORT SURGEMAIL STARTTLS LOGINDISABLED
A001 OK Capability completed
A002 LOGIN john@wilkes.com password_redacted
A002 BAD login failed SSL required for ip (127.0.0.1)

--
John Wilkes
john@wilkes.com

On Jan 8, 2018, at 3:48 PM, Surgemail Support (Marijn) <surgemail-support@netwinsite.com> wrote:

Looks like you have surgemail set not to answer imap on 127.0.0.1, try manually checking imap connectivity (to 127.0.0.1) on the server using telnet as per:

         http://netwinsite.com/surgemail/help/telnet.htm

Let us know results thanks.

Marijn




On Tuesday 09/01/2018 at 12:00 pm, John Wilkes wrote:

I renamed caldb.sqlite.bak to caldb.sqlite, and I made the system the master.

I still get an error message when I click the calendar button in SurgeWeb:

Cal Request Failed: 401 Unauthorized


I have port 80 blocked and always used port 7443 on the (now dead) master.

When I try https://myserver.com:7443/cal my login is not accepted and I get this error message when I leave the login window:

Sabre_DAV_Exception_NotAuthenticated No basic authentication headers were found 1.6.2


In the cal.log file:

01/08/18 22:44:02 [27148] NETWIN NetWin Info Test BEGIN
01/08/18 22:44:02 [27148] NETWIN NetWin Info Test END
01/08/18 22:45:53 [27160] ----
01/08/18 22:45:53 [27160] Sabre CAL
01/08/18 22:45:53 [27160] need auth beforeMethod [GET-]
01/08/18 22:45:53 [27160] Sabre CAL END
01/08/18 22:45:53 [27162] ----
01/08/18 22:45:53 [27162] Sabre CAL
01/08/18 22:45:53 [27162] need auth beforeMethod [GET-]
01/08/18 22:45:53 [27162] Sabre CAL END
01/08/18 22:46:17 [27167] ----
01/08/18 22:46:17 [27167] Sabre CAL
01/08/18 22:46:17 [27167] need auth beforeMethod [GET-]
01/08/18 22:46:17 [27167] Sabre CAL END
01/08/18 22:46:33 [27169] ----
01/08/18 22:46:33 [27169] Sabre CAL
01/08/18 22:46:33 [27169] need auth beforeMethod [GET-]
01/08/18 22:46:33 [27169] NWAUTH user=john@wilkes.com pass={hidden} hash=1c74855d13c34eb9421fcbc4d47a1192
01/08/18 22:46:33 [27169] NWAUTH Cached login expired (john@wilkes.com) age=399607/1800
01/08/18 22:46:33 [27169] No cached login, trying IMAP
01/08/18 22:46:33 [27169] Imap login exception imap_open(): Couldn't open stream {127.0.0.1:143/notls}INBOX
01/08/18 22:46:33 [27169] NWAUTH authorised=[NO]
01/08/18 22:46:33 [27169] Sabre CAL END
01/08/18 22:46:38 [27172] ----
01/08/18 22:46:38 [27172] Sabre CAL
01/08/18 22:46:38 [27172] need auth beforeMethod [GET-]
01/08/18 22:46:38 [27172] Sabre CAL END



--
John Wilkes
john@wilkes.com

On Jan 8, 2018, at 1:04 PM, Surgemail Support (Marijn) <surgemail-support@netwinsite.com> wrote:

X-SpamDetect-Info: ------------- Start ASpam results ---------------
X-SpamDetect-Info: This message may be spam. This message BODY has been altered to show you the spam information
X-SpamDetect: ****: 4.1 sd=4.1 0.68(X-Verify-Helo:-ERR) 0.40(X-myrbl:Color=orange) [nnot=0,ng=0,nsum=0,nb=0,nw=0,0.13]
X-SpamDetect-Info: ------------- End ASpam results -----------------


Calendaring data is not "live mirrorred" but copied once per day from the master to the slave for backup puposes as caldb.sqlite.bak. This is the reason calendaring is normally disabled on the slave. In order to enable calendaring on on the mirror:

1) copy / rename surgemail/scripts/data/caldb.sqlite.bak to surgemail/scripts/data/caldb.sqlite

2) either make the system the master, OR comment out this check in surgemail/scripts/cal.php

//if(getenv("CLUSTER_MASTER")!='TRUE'){
// print("ERROR: calendaring can only be used on the MASTER of a mirrorred cluster");
// return;
//}

Marijn



On Tuesday 09/01/2018 at 5:36 am, John Wilkes wrote:

I installed the php modules that CalDAV needs and when I tried to “verify authentication integration” I got an error message that calendaring is available on the master only.

I changed g_mirror_mode to “MASTER” in the (former) mirror’s surgemail.ini, shutdown the mirror and restarted.

Now when I verify authentication integration I get the login popup, but it does not accept my password.

If I try to see my calendar in SurgeWeb, I get an error message: Cal Request Failed: 401 Unauthorized

What do I need to do to fix this?

Thanks,
John

—
john@wilkes.com

On Jan 7, 2018, at 5:11 PM, John Wilkes <john@wilkes.com> wrote:

I have a mirror setup, and I use the caldav and carddav on my server. Are calendar and contacts mirrored?

My server disk drive failed, and I am currently running on the mirror (still as a “slave”) while I organize a new server system, but I don’t see my calendar in SurgeWeb, just a blank blue page, and the only contacts are those to whom I have sent email while running on the mirror.

Thanks,
John

—
john@wilkes.com