[SOGo] Sogo update failed

2022-03-16 Thread Michael Lehner 

Hey there,

same issue here. Mismatch of file size.

apt clean (Ubuntu 20.04) replaced the Package.gz but now it tries all 
the time to install an older version of the nightly build which isn't on 
the server anymore:


Get:2 https://packages.inverse.ca/SOGo/nightly/5/debian 
bullseye/bullseye amd64 libsbjson2.3 amd64 4.9.r1664.20220311 [13.9 kB]
Get:3 https://packages.inverse.ca/SOGo/nightly/5/debian 
bullseye/bullseye amd64 libsope-xml4.9 amd64 4.9.r1664.20220311 [119 kB]
Get:5 https://packages.inverse.ca/SOGo/nightly/5/debian 
bullseye/bullseye amd64 libsope-core4.9 amd64 4.9.r1664.20220311 [289 kB]
Get:6 https://packages.inverse.ca/SOGo/nightly/5/debian 
bullseye/bullseye amd64 libsope-mime4.9 amd64 4.9.r1664.20220311 [262 kB]
Get:7 https://packages.inverse.ca/SOGo/nightly/5/debian 
bullseye/bullseye amd64 libsope-appserver4.9 amd64 4.9.r1664.20220311 
[782 kB]
Get:8 https://packages.inverse.ca/SOGo/nightly/5/debian 
bullseye/bullseye amd64 libsope-gdl1-4.9 amd64 4.9.r1664.20220311 [140 kB]
Get:9 https://packages.inverse.ca/SOGo/nightly/5/debian 
bullseye/bullseye amd64 libsope-ldap4.9 amd64 4.9.r1664.20220311 [44.0 kB]
Err:10 https://packages.inverse.ca/SOGo/nightly/5/debian 
bullseye/bullseye amd64 sogo-activesync amd64 5.5.1.20220315-1

  404  Not Found [IP: 184.86.103.212 443]
Get:11 https://packages.inverse.ca/SOGo/nightly/5/debian 
bullseye/bullseye amd64 sope4.9-libxmlsaxdriver amd64 4.9.r1664.20220311 
[31.7 kB]
Get:12 https://packages.inverse.ca/SOGo/nightly/5/debian 
bullseye/bullseye amd64 sope4.9-gdl1-mysql amd64 4.9.r1664.20220311 
[29.1 kB]
Err:13 https://packages.inverse.ca/SOGo/nightly/5/debian 
bullseye/bullseye amd64 sogo amd64 5.5.1.20220315-1

  404  Not Found [IP: 184.86.103.212 443]
Fetched 4,113 kB in 1s (5,518 kB/s)
E: Failed to fetch 
https://packages.inverse.ca/SOGo/nightly/5/debian/pool/bullseye/s/sogo/sogo-activesync_5.5.1.20220315-1_amd64.deb 
404  Not Found [IP: 184.86.103.212 443]
E: Failed to fetch 
https://packages.inverse.ca/SOGo/nightly/5/debian/pool/bullseye/s/sogo/sogo_5.5.1.20220315-1_amd64.deb 
404  Not Found [IP: 184.86.103.212 443]
E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?


Any hints on that.

Thx for any help!

mike

--
Haftungsausschluss

Dies ist eine vertrauliche Nachricht und nur für den Adressaten bestimmt.
Jedoch kann der Autor dieser Mail keinerlei Gewähr dafür übernehmen, dass
unberechtigte Dritte (NSA, GCHQ, BND usw.) nicht in illegaler Absicht mit
Hilfe automatisierter elektronischer Speicherung der Metadaten und
Mitschnitten (PRISM, XKeyscore  usw.) mitlesen, ihren Ursprung und ihr
Ziel nachverfolgen und entsprechende Querverbindungen herstellen.

Dies trifft inzwischen auch auf staatliche Behörden zu
(ePrivacy-Ausnahmeverordnung).

---

"Politiker verstehen unter mündigen Bürgern diejenigen, die zu allem
den Mund halten." Wolfram Weidner (*1925), dt. Journalist

--
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Exception Error: NSInvalidArgumentException REASON

2020-08-10 Thread Michael Lehner 
When I force the update e.g. fpr lisope I receive thos eror:

*> apt-get -y --force-yes install libsope-core4.9*
Reading package lists...
Building dependency tree...
Reading state information...
libsope-core4.9 is already the newest version (4.9.r1664.SHORTDATE).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Thx again 

Am 10.08.20 um 14:16 schrieb Ludovic Marcotte (lmarco...@inverse.ca):
> On 2020-08-10 8:05 a.m., Michael Lehner (mich...@virser.de) wrote:
>
>> Which seems to be the newest one when I look into the respository.
>>
> Force update the ons with the SORTDATE name in them.
>
-- 
Haftungsausschluss

Dies ist eine vertrauliche Nachricht und nur für den Adressaten bestimmt.
Jedoch kann der Autor dieser Mail keinerlei Gewähr dafür übernehmen, dass
unberechtigte Dritte (NSA, GCHQ, BND usw.) nicht in illegaler Absicht mit
Hilfe automatisierter elektronischer Speicherung der Metadaten und
Mitschnitten (PRISM, XKeyscore  usw.) mitlesen, ihren Ursprung und ihr
Ziel nachverfolgen und entsprechende Querverbindungen herstellen.

---

"Politiker verstehen unter mündigen Bürgern diejenigen, die zu allem den Mund 
halten."
Wolfram Weidner (*1925), dt. Journalist

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] Exception Error: NSInvalidArgumentException REASON

2020-08-10 Thread Michael Lehner 
Thanks for the reply.

I already removed the Sogo installation and did a reinstallation, so I
guess the SOPE packages should be updated, right?

This are the installed versions right  now:

 libsope-appserver4.9 4.9.r1664.20200806    
    libsope-core4.9 4.9.r1664.SHORTDATE    
    libsope-gdl1-4.9 4.9.r1664.SHORTDATE    
    libsope-ldap4.9 4.9.r1664.20200806    
    libsope-mime4.9 4.9.r1664.20200806    
    libsope-xml4.9 4.9.r1664.SHORTDATE        
    sope4.9-gdl1-mysql 4.9.r1664.20200806    
    sope4.9-libxmlsaxdriver 4.9.r1664.20200806

Which seems to be the newest one when I look into the respository.

Is there a specfic one which is maybe missing? Could you maybe point me
to the specific command for re-/installing ALL sope packages.

Thx again.

Mike


Am 10.08.20 um 13:58 schrieb Ludovic Marcotte (lmarco...@inverse.ca):
>
> On 2020-08-10 7:26 a.m., Michael Lehner (mich...@virser.de) wrote:
>
>> I have some issues with my Sogo-4-Installation (nighlty) running on a
>> Ubuntu 18.04 machine. I already reinstalled the nightly but the
>> errors I receive in the sogo.log isn't disappearing:
>>
>> 2020-08-10 12:47:52.230 sogod[11590:11590] EXCEPTION: > 0x55da6e0d6400> NAME:NSInvalidArgumentException REASON:NSURL(instance) does 
>> not recognize queryComponents INFO:(null)
>> Aug 10 12:47:52 sogod [11590]: [ERROR] <0x0x55da6e1dec20[WOHttpAdaptor]> 
>> http server caught:  
>> NAME:NSInvalidArgumentException REASON:_NSConcreteProcessInfo(instance) does 
>> not recognize fileDescriptorCount INFO:(null)
>> Aug 10 12:47:52 sogod [11590]: [ERROR] <0x0x55da6e1dec20[WOHttpAdaptor]> 
>> http server caught: (null)
>
> Upgrade *all* SOPE packages too.
>
> -- 
> Ludovic Marcotte
> lmarco...@inverse.ca  ::  +1.514.755.3630  ::  https://inverse.ca
> Inverse inc. :: Leaders behind SOGo (https://sogo.nu), PacketFence 
> (https://packetfence.org) and Fingerbank (https://fingerbank.org)
> -- 
> users@sogo.nu
> https://inverse.ca/sogo/lists

-- 
Haftungsausschluss

Dies ist eine vertrauliche Nachricht und nur für den Adressaten bestimmt.
Jedoch kann der Autor dieser Mail keinerlei Gewähr dafür übernehmen, dass
unberechtigte Dritte (NSA, GCHQ, BND usw.) nicht in illegaler Absicht mit
Hilfe automatisierter elektronischer Speicherung der Metadaten und
Mitschnitten (PRISM, XKeyscore  usw.) mitlesen, ihren Ursprung und ihr
Ziel nachverfolgen und entsprechende Querverbindungen herstellen.

---

"Politiker verstehen unter mündigen Bürgern diejenigen, die zu allem den Mund 
halten."
Wolfram Weidner (*1925), dt. Journalist

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

[SOGo] Exception Error: NSInvalidArgumentException REASON

2020-08-10 Thread Michael Lehner 
Hey there,

I have some issues with my Sogo-4-Installation (nighlty) running on a
Ubuntu 18.04 machine. I already reinstalled the nightly but the errors I
receive in the sogo.log isn't disappearing:

2020-08-10 12:47:52.230 sogod[11590:11590] EXCEPTION:  NAME:NSInvalidArgumentException REASON:NSURL(instance) does not 
recognize queryComponents INFO:(null)
Aug 10 12:47:52 sogod [11590]: [ERROR] <0x0x55da6e1dec20[WOHttpAdaptor]> http 
server caught:  NAME:NSInvalidArgumentException 
REASON:_NSConcreteProcessInfo(instance) does not recognize fileDescriptorCount 
INFO:(null)
Aug 10 12:47:52 sogod [11590]: [ERROR] <0x0x55da6e1dec20[WOHttpAdaptor]> http 
server caught: (null)

Whenever I log in to the WUI I only Receive a blank page. Also has the sync 
with my Android device stopped and I cant send or receive mails. I am using a 
Nginx Webserver. 

MY sogo.conf is right now:

{
//
//  - Official SOGo document: 
http://sogo.nu/support/index.html#/documentation
//  - Mailing list: http://sogo.nu/support/index.html#/community
//

// Daemon address and port
WOPort = 127.0.0.1:2;

// PID file
//WOPidFile = /var/run/sogo/sogo.pid;

// Log file
//WOLogFile = /var/log/sogo/sogo.log;

// Enable verbose logging. Reference:
// 
http://www.sogo.nu/nc/support/faq/article/how-to-enable-more-verbose-logging-in-sogo.html
//SOGoDebugRequests = YES;
//SOGoEASDebugEnabled = YES;
//ImapDebugEnabled = YES;
//LDAPDebugEnabled = YES;
//MySQL4DebugEnabled = YES;
//PGDebugEnabled = YES;

// Define the URL to online help for SOGo. When set, an additional icon
// will appear near the logout button in SOGo's web interface. The URL
// will always be open in a blank target.
//SOGoHelpURL = '';

// set the maximum allowed size for content being sent to SOGo, this can
// also limit the file attachment size being uploaded to SOGo when
// composing a mail.
// The value is in kilobyte. Default is 0 or disabled (unlimit).
WOMaxUploadSize = 15360;

// Parameter used to set the maximum allowed email message size when
// composing a mail.
// The value is in kilobytes. By default, the value is 0, or disabled so
// no limit will be set.
SOGoMaximumMessageSizeLimit = 15360;

// Performance Tuning
//
// The amount of instances of SOGo that will be spawned to handle multiple
// requests simultaneously. When started from the init script, that amount
// is overriden by the `PREFORK=` setting in /etc/sysconfig/sogo or
// /etc/default/sogo. A value of 3 is a reasonable default for low usage.
// The maximum value depends on the CPU and IO power provided by your
// machine: a value set too high will actually decrease performances under
// high load.
//
// You should have at least one child per EAS device configured to use
// "push". You must also have more children than you have EAS devices
// configured to use "push" - in order to handle normal SOGo requests to
// its Web or DAV interfaces.
//
// Defaults to 1 when unset, increase it if you see below error message in
// sogo log file: 'No child available to handle incoming request'
//
// WARNING:
//  - on RHEL/CentOS, this setting is controlled by parameter
//'PREFORK=' defined in /etc/sysconfig/sogo.
//  - on Debian/Ubuntu, this setting is controlled by parameter
//'PREFORK=' defined in /etc/default/sogo.
WOWorkersCount = 10;

// Parameter used to set the maximum amount of time, in seconds, SOGo will
// wait before replying to a Ping command.
// If not set, it defaults to 10 seconds.
SOGoMaximumPingInterval = 3540;

// Parameter used to set the maximum amount of time, in seconds, SOGo will
// wait before replying to a Sync command.
// If not set, it defaults to 30 seconds.
SOGoMaximumSyncInterval = 3540;

// Parameter used to set the maximum amount of time, in seconds, SOGo will
// wait before doing an internal check for data changes (add, delete, and
// update). This parameter must be lower than SOGoMaximumSyncInterval and
// SOGoMaximumPingInterval.
// If not set, it defaults to 10 seconds.
SOGoInternalSyncInterval = 30;

// Specifies the number of minutes after which a busy child process will be
// killed by the parent process.
// Defaults to 10 (minutes).
WOWatchDogRequestTimeout = 61;

// Overwrite the maximum number of items returned during a Sync operation.
// Defaults to 0, which means no overwrite is performed.
// Setting this parameter to a value greater than 512 will have unexpected
// behaviour with various ActiveSync clients.
//SOGoMaximumSyncWindowSize = 100;

// Overwrite the maximum response size during a Sync operation.
// The value is in kilobytes. Setting this to 512 means the response size
// will be of 524288 bytes or less (or a bit

[SOGo] [WOHttpAdaptor]> http server caught:

2020-06-19 Thread Michael Lehner 
Hey there,

I try to connect an iPhone via Exchange with my Sogo instance. But I
receive always the error in my Nginx-Log:

2020/06/18 09:38:53 [error] 936#936: *973173 upstream prematurely closed
connection while reading response header from upstream, client:
3.227.182.193, server: virmai.de, request: "HEAD /SOGo/ HTTP/1.1",
upstream: "http://127.0.0.1:2/SOGo/;, host: "mbox.virmai.de"

The Sogo config part is

// Parameter used to set the maximum amount of time, in seconds, SOGo will
    // wait before replying to a Ping command.
    // If not set, it defaults to 10 seconds.
    SOGoMaximumPingInterval = 3540;

    // Parameter used to set the maximum amount of time, in seconds,
SOGo will
    // wait before replying to a Sync command.
    // If not set, it defaults to 30 seconds.
    SOGoMaximumSyncInterval = 3540;

The same error appears when I try to connect my Calender with Calendly
(https://calendly.com) - an webapp that can be be used in Wordpress to
schedule events.

So I activated debugging in the Sogo-Conf:

    // Log file
    WOLogFile = /var/log/sogo/sogo.log;

    // Enable verbose logging. Reference:
    // http://www.sogo.nu/nc/support/faq/artic … -sogo.html

    SOGoDebugRequests = YES;
    SOGoEASDebugEnabled = YES;
    //ImapDebugEnabled = YES;
    //LDAPDebugEnabled = YES;
    //MySQL4DebugEnabled = YES;
    //PGDebugEnabled = YES;

And the only error when I tried to connect to Sogo with Calendly was
this line in the sogo-log:

Jun 19 08:18:18 sogod [3291]: [ERROR] <0x0x55f96b329b00[WOHttpAdaptor]>
http server caught: 
NAME:NSInvalidArgumentException REASON:[NGHttpCredentials-userName]
should be overridden by subclass INFO:(null)

And as i mentioned in the nginx-log this one:

2020/06/19 08:19:02 [error] 936#936: *1058977 upstream prematurely
closed connection while reading response header from upstream, client:
3.227.182.193, server: virmai.de, request: "HEAD /SOGo/ HTTP/1.1",
upstream: "http://127.0.0.1:2/SOGo/;, host: "mbox.virmai.de"


Thx for any help.

Greets mike

-- 
Haftungsausschluss

Dies ist eine vertrauliche Nachricht und nur für den Adressaten bestimmt.
Jedoch kann der Autor dieser Mail keinerlei Gewähr dafür übernehmen, dass
unberechtigte Dritte (NSA, GCHQ, BND usw.) nicht in illegaler Absicht mit
Hilfe automatisierter elektronischer Speicherung der Metadaten und
Mitschnitten (PRISM, XKeyscore  usw.) mitlesen, ihren Ursprung und ihr
Ziel nachverfolgen und entsprechende Querverbindungen herstellen.

---

"Politiker verstehen unter mündigen Bürgern diejenigen, die zu allem den Mund 
halten."
Wolfram Weidner (*1925), dt. Journalist

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

[SOGo] Second Mail-Account within SoGo

2020-02-27 Thread Michael Lehner 



Hey there,

is it possible to call two different mail-accounts within SoGo?

In the configuration of the user under Configuration/Settings => Mail  
=>IMAP-Accounts it is only possible to change some settings of the  
logged in account, but no feature to add another account that should  
appear within SoGo.


I already checked the Installation and Config guide on the wiki of  
SoGo: https://sogo.nu/files/docs/SOGoInstalla … iguration.


But I did not find any solution.

Is it possible after all to call two different mail-accounts within  
one instance of SoGo like in e.g. Horde? I used Horde for a long time,  
but the user interface is so outdated that I switched to iRedMail with  
SoGo as a whole.


Any help is appreciated on that.

Thx and Greets mike
--

Haftungsausschluss

Dies ist eine vertrauliche Nachricht und nur für den Adressaten bestimmt.
Jedoch kann der Autor dieser Mail keinerlei Gewähr dafür übernehmen, dass
unberechtigte Dritte (NSA, GCHQ, BND usw.) nicht in illegaler Absicht mit
Hilfe automatisierter elektronischer Speicherung der Metadaten und
Mitschnitten (PRISM, XKeyscore  usw.) mitlesen, ihren Ursprung und ihr
Ziel nachverfolgen und entsprechende Querverbindungen herstellen.

--
users@sogo.nu
https://inverse.ca/sogo/lists