Just as to clarify:

No other adjustment were made to the system (e.g. changes of certificates or postfix / dovecot settings)

Hi war,

i also stated the same problem since sunday (as I do a autoupdate every sunday at 4:00am).

As workaround I hence this method:
/etc/dovecot/conf.d/99-local-imap.conf:
service imap-login {
inet_listener imap {
address = 127.0.0.1
port = 143
}

service_count = 1
process_min_avail = 2
process_limit = 100
}

/var/lib/sogo/GNUstep/Defaults/sogod.plist:
<key>SOGoIMAPServer</key>
<string>imap://127.0.0.1:143</string>

I also tried to reduce the TLS version to 1.0 in dovecot but without any success.

Your Update log:
sogo:amd64 (4.3.2.20200703-1, 4.3.2.20200706-1)
libsope-core4.9:amd64 (4.9.r1664.20200703, 4.9.r1664.20200704)

My Update log:
sogo:amd64 (4.3.2.20200627-1, 4.3.2.20200704-1)
libsope-core4.9:amd64 (4.9.r1664.20200624, 4.9.r1664.20200704)

So it must have something to do with sope 4.9.r1664.20200704 because you had previously 4.9.r1664.20200703 installed and it was working?
Or since sogo 4.3.2.20200704-1 because 4.3.2.20200705-1, 4.3.2.20200706-1, 4.3.2.20200707-1 od not resolve the problem!

On thuesday I am in holiday now I am facing this problem what a nice deal.
Also there's no archive we can deal with. :(

best regards
realizelol

I can try your workaround.

However, I have not changed anything in dovecot. The issue has to attributed to SOGo and not require me to open other ports.

Hi war,

don't understand me wrongly. Inverse inc. should solve the problem as soon as possible because I also don't like the transport unencrypted even it's just locally.
But let me tell you that you "only" have to listen on port 143 locally (127.0.0.1) so even if you would open port 143 to the internet it shouldn't give a repsonse if you really disabled imap protocol
as I've done.

What I forget to tell you: You may have the need to reboot the system. Restarting just dovecot & sogo wasn't working for me.

best regards
realizelol

PS: I am running on OS: Ubuntu 20.04 Focal Fossa

Hi,
thanks for the workaround, I faced nearly the same problem, logs were a little bit different:

Jul 07 16:19:00 sogod [5212]: [ERROR] <0x0F2B2970[SOGoMailAccount]:0> Could not connect IMAP4
Jul 07 16:19:00 sogod [5212]: [ERROR] <0x0x55f50e974620[WOHttpAdaptor]> http server caught: <NSException: 0x55f50f118870> NAME:NSInvalidArgumentException REASON:-[_NSConcreteProcessInfo fileDescriptorCount]: unrecognized selector sent to instance 0x55f50e9d6c90 INFO:(null)
Jul 07 16:19:00 sogod [5212]: [ERROR] <0x0x55f50f03da50[NGImap4ConnectionManager]> IMAP4 login failed:
host=193.50.5.57, user=user, pwd=yes
url=imaps://user@xxx.xx.x.xx/
base=(null)
base-class=(null))
= <0x0x55f50f2fc7e0[NGImap4Client]: login=user(pwd) address=<0x0x55f50f308b80[NGInternetSocketAddress]: host=xxx.xx.x.xx not-filled>>

modifying sogo.conf was sufficient as imap was allowed on my mail server.

Best regards,

Laurent

Thanks for your support and hints.

One can easily change the connection in sogo.conf
from
SOGoIMAPServer = imaps://127.0.0.1:993;
to
SOGoIMAPServer = imap://127.0.0.1:143;

and restart with
sudo systemctl restart sogo.service && sudo systemctl restart apache2.service

(mind the protocol: imaps -> 993, imap -> 143)

I would not recommend changing files in /var/lib/SOGo... as these are overwritten by updates.

Further investigation, the error is exactly the same on sogo 2 and Sogo 4, the only error I can see now is :

Jul 07 17:24:29 sogod [5808]: [ERROR] <0x0x558ec23b58d0[WOHttpAdaptor]> http server caught: <NSException: 0x558ec39a5370> NAME:NSInvalidArgumentException REASON:-[_NSConcreteProcessInfo fileDescriptorCount]: unrecognized selector sent to instance 0x558ec2417c90 INFO:(null)

Best regards

Laurent

Upgrade SOPE.

SOPE is already the newest version available in nightly repo "4.9.r1664.20200704". Or should this mean you're actually updating SOPE?

As I can see there was a big update to openssl/gnutls and hostname detection in github commit 9138e79:
https://github.com/inverse-inc/sope/commit/9138e796f091756b13a4836610c05ccd8d4ca50f

maybe a hint?:
I don't really know much about CPP but maybe this has to be #include ?:
https://github.com/inverse-inc/sope/commit/9138e796f091756b13a4836610c05ccd8d4ca50f#diff-92d6f641cf1b1cafceece900cd04f3e7R26
as of https://docs.microsoft.com/de-de/cpp/preprocessor/hash-import-directive-cpp?view=vs-2019 it has to: #import "filename" [attributes] or #import <filename> [attributes]
or otherwise there is a attribute missing?

best regards
realizelol

4.9.r1664.20200704 is NOT the latest version - 4.9.r1664.20200707 is.

Maybe you're using Xenial, builds have been broken for a few days on that distro - the others are OK.

Hi ludovic,

on my server:

apt update && apt-cache policy sope4.9*
Hit:1 http://mirror.hetzner.de/ubuntu/packages focal InRelease
Hit:2 http://mirror.hetzner.de/ubuntu/packages focal-updates InRelease                                                                                                                                                                                             
Hit:3 http://mirror.hetzner.de/ubuntu/packages focal-backports InRelease                                                                                                                                                                                           
Hit:4 http://mirror.hetzner.de/ubuntu/packages focal-security InRelease                                                                                                                                                                                            
Hit:5 http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease                                                                                                                                                                                                   
Hit:6 https://rspamd.com/apt-stable bionic InRelease                                                                                                                                                      
Hit:7 http://archive.ubuntu.com/ubuntu focal InRelease                                                                                                           
Hit:8 http://security.ubuntu.com/ubuntu focal-security InRelease                                                                           
Hit:9 http://archive.ubuntu.com/ubuntu focal-updates InRelease                                                                             
Hit:10 http://nginx.org/packages/ubuntu focal InRelease                                                              
Hit:11 http://archive.ubuntu.com/ubuntu focal-backports InRelease                                 
Hit:12 http://nginx.org/packages/mainline/ubuntu focal InRelease                                  
Hit:13 http://packages.inverse.ca/SOGo/nightly/4/ubuntu focal InRelease     
Reading package lists... Done                         
Building dependency tree       
Reading state information... Done
All packages are up to date.
sope4.9-stxsaxdriver:
  Installed: (none)
  Candidate: 4.9.r1664.20200704
  Version table:
     4.9.r1664.20200704 500
        500 http://packages.inverse.ca/SOGo/nightly/4/ubuntu focal/focal amd64 Packages
sope4.9-dbg:
  Installed: (none)
  Candidate: 4.9.r1664.20200704
  Version table:
     4.9.r1664.20200704 500
        500 http://packages.inverse.ca/SOGo/nightly/4/ubuntu focal/focal amd64 Packages
sope4.9-appserver:
  Installed: (none)
  Candidate: 4.9.r1664.20200704
  Version table:
     4.9.r1664.20200704 500
        500 http://packages.inverse.ca/SOGo/nightly/4/ubuntu focal/focal amd64 Packages
sope4.9-gdl1-postgresql:
  Installed: (none)
  Candidate: 4.9.r1664.20200704
  Version table:
     4.9.r1664.20200704 500
        500 http://packages.inverse.ca/SOGo/nightly/4/ubuntu focal/focal amd64 Packages
sope4.9-gdl1-mysql:
  Installed: 4.9.r1664.20200704
  Candidate: 4.9.r1664.20200704
  Version table:
 *** 4.9.r1664.20200704 500
        500 http://packages.inverse.ca/SOGo/nightly/4/ubuntu focal/focal amd64 Packages
        100 /var/lib/dpkg/status
sope4.9-db-connector:
  Installed: (none)
  Candidate: (none)
  Version table:
sope4.9-libxmlsaxdriver:
  Installed: 4.9.r1664.20200704
  Candidate: 4.9.r1664.20200704
  Version table:
 *** 4.9.r1664.20200704 500
        500 http://packages.inverse.ca/SOGo/nightly/4/ubuntu focal/focal amd64 Packages
        100 /var/lib/dpkg/status

and also on https://packages.inverse.ca/SOGo/nightly/4/ubuntu/pool/focal/s/sope/
or even on https://packages.inverse.ca/SOGo/nightly/4/debian/pool/buster/s/sope/
or https://packages.inverse.ca/SOGo/nightly/4/rhel/8/x86_64/RPMS/ there's no 4.9.r1664.20200707.

Isn't it published yet?

best regards
realizelol

Long time listener, first time caller.

I auto-update at 5am on Sundays, have had issues since. All the errors listed above i've seen. Difference - our IMAP never had TLS enabled. imap is on the same server, and per their comment "// Local connection is considered as secure by Dovecot, so 'imap://' is fine." i've left it alone.

I changed these last night:

SOGoMaximumPingInterval = 3540;
SOGoMaximumSyncInterval = 3540;
SOGoInternalSyncInterval = 60;
WOWatchDogRequestTimeout = 15;

from the defaults, and it started running smoother. Most of the complaints i've had are from users with boxes >=3 gb.

I think I'm going to change the update from Sunday's to Wednesday's or Thursday's. I think this is the 3rd time this year we've had issues post update. (been running since 3/2017)

From the logs it seems your configuration/certificate is invalid. If you are using tls you have to specify the fqdn, not 127.0.0.1, otherwise the certificate validation will of course fail. If you localhost is fine for you, disable tls. Otherwise use imaps://mail.example.org (adjusted accordingly).
Certificates failing validation will not accepted anymore!

@the_nic: I presume that your message addressed my post.

If the certificate is the problem, how could SOGo work ever since 4.0 was launched? The certificate is valid and was not changed on 6th of July.

@war Because you're using a nightly build and that code was merged a few days ago.

@the_nic: Just reread your post.

Did you mean that the code was modified in such a way that TLS issues that previously were resolved quietly are now turned down and the software stops working?

If so, it would be nice to give users notice in the post upgrade script (which notifies me about how to upgrade databases - totally useless in most cases).

Could have helped.

I can confirm that this was the issue.
After I changed to the FQDN defined in the certificate it works perfectly.
I would also like that such changes should be more visible...

Remember that you are running a nightly build - don't expect us to do fancy announcements every time we make a commit. Those are reserved for a release.

I fully agree, but in such cases it would really save us and you a lot of time ;-)
Cheers
Alex

You can already read the commit messages before upgrading if you want to save time.

@war yes, that is correct. Before the merge, any certificate was accepted by sogo when using tls. This was actually a severe security issue and undermined the purpose of tls and the certificate chain.

That is why now misconfigured installations will fail to work. Allowing admins to disable peer validation could be an option, but that could take a bit of time, and is of course discouraged; fixing your setup/config is the better option as you will immediately notice any failures.

@the_nic: After understanding the purpose and intention behind the change, I fully agree with you and support this move.

Please bear in mind that nightly users contribute to the stability of your commercial package. Totally ignoring their needs (for stability) might reduce acceptance and positive feedback. So I think that a brief mention in the post-installation notice would have been benefitial. If I ignore those, it's completely my fault (as happened to me after upgrading from 2 to 3).

btw: I replaced IP to fqdn and it worked well. - Thanks for the hint

As for me, this issue can be closed. Please update the online and PDF documentation as there is still the IP address as an option.

D SOGoIMAPServer Parameter used to set the DNS name or IP address of the IMAP server used by SOGo. You can also use SSL or TLS by providing a value using an URL, such as:

• imaps://127.0.0.1:993
• imap://127.0.0.1:143/?tls=YES

As I understand, the first line is not possible

There's no point in enabling TLS/SSL if you don't want the certificate to be verified. Read comments in related tickets.