[SOGo] BTS activities for Wednesday, February 23 2022

[SOGo reporter]

Title: BTS activities for Wednesday, February 23 2022





  
BTS Activities

  Home page: https://sogo.nu/bugs
  Project: SOGo
  For the period covering: Wednesday, February 23 2022

  
  
idlast updatestatus (resolution)categorysummary
	
	
	  
	
5439
	2022-02-23 23:54:32
	updated (open)
	Backend General
	Endless invitation emails sent
	
	  
	
5428
	2022-02-23 07:47:37
	closed (not a bug)
	Web Mail
	Webmail redirecty me every few minutes back to SSO.
	
	  
	
  
  


-- users@sogo.nuhttps://inverse.ca/sogo/lists

Re: [SOGo] ActiveSync from Android not working, SOGO 5.5.1

[Philipp Kuehne]

Hello Tomaž and Thomas,

we also just upgraded to SOGo 5.5.1 and today experienced the same error.

Our setup:

* OS debian10

* installed with apt

* libexpat1 (2.2.6-2+deb10u3)

After a couple hours of searching we figured out, that there was an
update to the libexpat1 library (see
https://tracker.debian.org/news/1305688/accepted-expat-226-2deb10u3-source-into-oldstable-embargoed-oldstable/).

Since libwbxml depends on expat1 this error occurs.

After we downgraded libexpat1 from 2.2.6-2+deb10u3 to 2.2.6-2+deb10u1
the error was gone.

I hope this helps you.

Kind regards

Philipp

Am 23.02.22 um 18:54 schrieb "Thomas Fuehrer" (t...@aon.at):
> Hi Tomaž,
> please provide more infos about your environment.
>
> OS/install procedure/installed packages (e.g.
> sog/sope/sogo-activesysnc/libwbxml/...)
>
> Regards
> Thomas
>
> -Ursprüngliche Nachricht-
> Von: users-requ...@sogo.nu  Im Auftrag von NOVAK
> TOMAR
> Gesendet: Mittwoch, 23. Februar 2022 08:54
> An: users@sogo.nu
> Betreff: [SOGo] ActiveSync from Android not working, SOGO 5.5.1
>
> Hi!
>
> I can not sync mail to my Android device or Outlook.
> I keep seeing errors in sogo.log:
>
> Feb 23 08:32:04 sogod [3497]: <0x0x5566de7c7d10[SOGoActiveSyncDispatcher]>
> EAS - request for device androidc1012178084: 
>  "http://www.microsoft.com/;>
> 
>  0
> 
>
> Feb 23 08:32:04 sogod [3497]: [ERROR] <0x0x5566deeadc40[NSDataMalloc]>
> xml2wbxmlFromContent: failed: Parsing of XML Document Failed
>
> Feb 23 08:32:04 sogod [3497]: [ERROR] <0x0x5566deeadc40[NSDataMalloc]>
> Original data written to: /tmp/mail_da9_27c619a8_2f.data
> Feb 23 08:32:04 sogod [3497]: |SOGo| request took 0.236170 seconds to
> execute
>
> If i do xmllint --format /tmp/mail_da9_27c619a8_2f.data it parses file
> correctly and no errors are given.
>
> What can i do to fix this or figure out what is wrong ?
>
> * email account i try to sync has 0 emails in its account, since i emptied
> account, because i thought problem was with some mail.
> * also no account works, tried to create 5 accounts, on every account i get
> same sync errors and not even initial sync completes
>
> With regards,
>
> Tomaž
>
>
>
-- 
___

Philipp Kühne | IT Administrator


indurad GmbH| the industrial radar company

Belvedereallee 5 | 52070 Aachen | Germany
phone: +49 241 538070-103 | front desk: +49 241 538070-0
email: philipp.kue...@indurad.com | web: www.indurad.com


OpenPGP_signature
Description: OpenPGP digital signature

AW: [SOGo] ActiveSync from Android not working, SOGO 5.5.1

["Thomas Fuehrer"]

Hi Tomaž,
please provide more infos about your environment.

OS/install procedure/installed packages (e.g.
sog/sope/sogo-activesysnc/libwbxml/...)

Regards
Thomas

-Ursprüngliche Nachricht-
Von: users-requ...@sogo.nu  Im Auftrag von NOVAK
TOMAR
Gesendet: Mittwoch, 23. Februar 2022 08:54
An: users@sogo.nu
Betreff: [SOGo] ActiveSync from Android not working, SOGO 5.5.1

Hi!

I can not sync mail to my Android device or Outlook.
I keep seeing errors in sogo.log:

Feb 23 08:32:04 sogod [3497]: <0x0x5566de7c7d10[SOGoActiveSyncDispatcher]>
EAS - request for device androidc1012178084: 
http://www.microsoft.com/;>

 0


Feb 23 08:32:04 sogod [3497]: [ERROR] <0x0x5566deeadc40[NSDataMalloc]>
xml2wbxmlFromContent: failed: Parsing of XML Document Failed

Feb 23 08:32:04 sogod [3497]: [ERROR] <0x0x5566deeadc40[NSDataMalloc]>
Original data written to: /tmp/mail_da9_27c619a8_2f.data
Feb 23 08:32:04 sogod [3497]: |SOGo| request took 0.236170 seconds to
execute

If i do xmllint --format /tmp/mail_da9_27c619a8_2f.data it parses file
correctly and no errors are given.

What can i do to fix this or figure out what is wrong ?

* email account i try to sync has 0 emails in its account, since i emptied
account, because i thought problem was with some mail.
* also no account works, tried to create 5 accounts, on every account i get
same sync errors and not even initial sync completes

With regards,

Tomaž



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

Re: [SOGo] WebMail: Embedded links always in lower case

["H.Plett"]

OK, will do, thanks for the quick reply.

Heinrich

Am Mittwoch, Februar 23, 2022 15:54 CET, schrieb "Francis Lachapelle" 
(flachape...@inverse.ca) :
  Hi Heinrich On Feb 23, 2022, at 09:51, H.Plett  wrote:
When receiving a (valid) link in an inbound mail (e.g. dhl tracking), it does 
not work, if there is an Upper Case letter included in the original link. So, I 
receive the mail, open it in the WebMail (in Firefox or Edge) and try to click 
the embedded link. This does not work, most cases a Code 404 "not found" is 
returned. I checked a lttle deeper and found, that the entire Link has been 
changed into lower case characters, even when in the original Link there were 
uppercase letters.
E.g. DHL sends a tracking number with the link 
https://mailing3.dhl.de/Go/dfm4d45v7hv3szfhhtave5pptfkpzbaudrdsk8w845ht/7?t_ID=1715824557=00340434462072375354
 (not a real link), then my Browser tries to open this: 
https://mailing3.dhl.de/go/dfm4d45v7hv3szfhhtave5pptfkpzbaudrdsk8w845ht/7?t_id=1715824557=00340434462072375354
 (so, "Go" has been turned to "go" and "ID" has been changed to "id"). This 
issue happens in Firefox and likewise in Chrome.
If I open the very link on the mobile (Android), there is no problem.
So the problem is clearly on the SOGo WebMail Frontend.
I am using SOGo Version 5.3.0 (@shiva2.inverse 202111250126)

Any Idea what could be the reason, why the uppercase charakters are swapped to 
lowercase? And which instance could be responsible, Postfix or Sogo or anything 
else?This is an old bug (https://www.sogo.nu/bugs/view.php?id=5434). Please 
take the time to visit the BTS prior to ask questions on the mailing list.  
Francis --
users@sogo.nu
https://inverse.ca/sogo/lists


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

Re: [SOGo] WebMail: Embedded links always in lower case

[Francis Lachapelle]

Hi Heinrich

> On Feb 23, 2022, at 09:51, H.Plett  wrote:
> 
> When receiving a (valid) link in an inbound mail (e.g. dhl tracking), it does 
> not work, if there is an Upper Case letter included in the original link. So, 
> I receive the mail, open it in the WebMail (in Firefox or Edge) and try to 
> click the embedded link. This does not work, most cases a Code 404 "not 
> found" is returned. I checked a lttle deeper and found, that the entire Link 
> has been changed into lower case characters, even when in the original Link 
> there were uppercase letters.
> E.g. DHL sends a tracking number with the link 
> https://mailing3.dhl.de/Go/dfm4d45v7hv3szfhhtave5pptfkpzbaudrdsk8w845ht/7?t_ID=1715824557=00340434462072375354
>  (not a real link), then my Browser tries to open this: 
> https://mailing3.dhl.de/go/dfm4d45v7hv3szfhhtave5pptfkpzbaudrdsk8w845ht/7?t_id=1715824557=00340434462072375354
>  (so, "Go" has been turned to "go" and "ID" has been changed to "id"). This 
> issue happens in Firefox and likewise in Chrome.
> If I open the very link on the mobile (Android), there is no problem.
> So the problem is clearly on the SOGo WebMail Frontend.
> I am using SOGo Version 5.3.0 (@shiva2.inverse 202111250126)
> 
> Any Idea what could be the reason, why the uppercase charakters are swapped 
> to lowercase? And which instance could be responsible, Postfix or Sogo or 
> anything else?

This is an old bug (https://www.sogo.nu/bugs/view.php?id=5434 
).

Please take the time to visit the BTS prior to ask questions on the mailing 
list.


Francis

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

[SOGo] WebMail: Embedded links always in lower case

["H.Plett"]

Hello, Team,
hope someone can advise / help with the following issue:

When receiving a (valid) link in an inbound mail (e.g. dhl tracking), it does 
not work, if there is an Upper Case letter included in the original link. So, I 
receive the mail, open it in the WebMail (in Firefox or Edge) and try to click 
the embedded link. This does not work, most cases a Code 404 "not found" is 
returned. I checked a lttle deeper and found, that the entire Link has been 
changed into lower case characters, even when in the original Link there were 
uppercase letters.
E.g. DHL sends a tracking number with the link 
https://mailing3.dhl.de/Go/dfm4d45v7hv3szfhhtave5pptfkpzbaudrdsk8w845ht/7?t_ID=1715824557=00340434462072375354
 (not a real link), then my Browser tries to open this: 
https://mailing3.dhl.de/go/dfm4d45v7hv3szfhhtave5pptfkpzbaudrdsk8w845ht/7?t_id=1715824557=00340434462072375354
 (so, "Go" has been turned to "go" and "ID" has been changed to "id"). This 
issue happens in Firefox and likewise in Chrome.
If I open the very link on the mobile (Android), there is no problem.
So the problem is clearly on the SOGo WebMail Frontend.
I am using SOGo Version 5.3.0 (@shiva2.inverse 202111250126)

Any Idea what could be the reason, why the uppercase charakters are swapped to 
lowercase? And which instance could be responsible, Postfix or Sogo or anything 
else?

Thanks!

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

Re: [SOGo] Fwd: sogo webclient - send signed email error - sender address not in certificate

["Frank Schmirler"]

Hi Christian,

I'm also running 5.5.1 and have no problems sending signed messages, provided 
the sender address is really part of the  certificate. Please double check 
that. I Tried with both, a certificate with the email address in SAN only (like 
yours) and a certificate with the email address in DN and SAN.

I can confirm that email addresses in the SAN are not visible in Preferences > 
Mail > IMAP Accounts > Edit > Security.
With the fix for issue #5440 SAN email addresses became visible only when 
viewing signed messages.

Best regards,
Frank

Am Mittwoch, 23. Februar 2022 10:57 CET, schrieb "Christian Setzer | Hochschule 
Augsburg" (christian.set...@hs-augsburg.de) :

> sorry ...
>
> hereby with the attachments ...
>
> :P
>
> ChriS.
>
>
>  Forwarded Message 
> Subject:  sogo webclient - send signed email error - sender address not
> in certificate
> Date: Wed, 23 Feb 2022 10:41:12 +0100
> From: Christian Setzer | Hochschule Augsburg
> 
> Organization: Hochschule für angewandte Wissenschaften Augsburg
> To:   users@sogo.nu
>
>
>
> Hello all together!
>
> As i am not sure if it is or was a reported bug already, i will try this
> channel first, although i couldn't find anything on the same topic.
>
> It seems to me that it could be related to the issues #5407 and #5440 in
> the SOGo BTS and the "fix(mail): check if smime certificate matches
> sender address".
>
>
> Currently, we cannot send signed messages using the sogo web client. 
> (actually using version 5.5.1)
>
> Before sending, there appears to be a check of the valid certificate and
> it runs into an error:
>
> "The message can't be signed because the sender address is not included
> in the certificate associated to the mail account."
>
> See attachment: "SogoWebErrorMessageSignedSenderAddressNotInCert.jpg"
>
>
> If i recall it correctly, we had no issues sending signed email until
> version 5.2, before the change in version 5.3 where the check was added.
>
> Then, we had the issue with the warning when receiving signed messages
> as shown in bug #5440, which disappeared with the upgrade on 5.4.
>
> "Message is signed but the certificate (name surname) doesn't match the
> sender email address"
>
> Finally, we upgraded to 5.5.1 and hoped the sending signed error would
> disappear, but it didn't.
>
>
> When i go to Preferences > Mail > IMAP Accounts > Edit > Security and
> open the view of the certificate, i can only see the parts Subject Name
> and Issuer.
>
> But the SAN / E-Mail-Address is not shown / visible.
>
> See attachment: "SogoWebSecurityViewCertDetails.jpg"
>
>
> My questions would be:
>
> Could anyone observe the same issue?
>
> What could be the origin, if it is likely to be a more personal issue?
>
> If others can observe it to, should i place it in the SOGo BTS?
>
>
> Thanks and greetings,
>
> ChriS.
>
> --
> Christian Setzer
> Rechenzentrum (Computer Center & IT Services)
> HOCHSCHULE für angewandte Wissenschaften AUGSBURG (University of Applied 
> Sciences)
> --

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

[SOGo] sogo webclient - send signed email error - sender address not in certificate

[Christian Setzer | Hochschule Augsburg]

On 23.02.22 10:41, Christian Setzer | Hochschule Augsburg wrote:


Hello all together!

As i am not sure if it is or was a reported bug already, i will try 
this channel first, although i couldn't find anything on the same topic.


It seems to me that it could be related to the issues #5407 and #5440 
in the SOGo BTS and the "fix(mail): check if smime certificate matches 
sender address".



Currently, we cannot send signed messages using the sogo web client. 
(actually using version 5.5.1)


Before sending, there appears to be a check of the valid certificate 
and it runs into an error:


"The message can't be signed because the sender address is not 
included in the certificate associated to the mail account."


See attachment: "SogoWebErrorMessageSignedSenderAddressNotInCert.jpg"


If i recall it correctly, we had no issues sending signed email until 
version 5.2, before the change in version 5.3 where the check was added.


Then, we had the issue with the warning when receiving signed messages 
as shown in bug #5440, which disappeared with the upgrade on 5.4.


"Message is signed but the certificate (name surname) doesn't match 
the sender email address"


Finally, we upgraded to 5.5.1 and hoped the sending signed error would 
disappear, but it didn't.



When i go to Preferences > Mail > IMAP Accounts > Edit > Security and 
open the view of the certificate, i can only see the parts Subject 
Name and Issuer.


But the SAN / E-Mail-Address is not shown / visible.

See attachment: "SogoWebSecurityViewCertDetails.jpg"


My questions would be:

Could anyone observe the same issue?

What could be the origin, if it is likely to be a more personal issue?

If others can observe it to, should i place it in the SOGo BTS?


Thanks and greetings,

ChriS.

--
Christian Setzer
Rechenzentrum (Computer Center & IT Services)
HOCHSCHULE für angewandte Wissenschaften AUGSBURG (University of Applied 
Sciences)
--BEGIN:VCARD
VERSION:4.0
EMAIL;PREF=1:christian.set...@hs-augsburg.de
FN:Christian Setzer
ORG:Hochschule (für angewandte Wissenschaften) Augsburg;Rechenzentrum
N:Setzer;Christian;;;
ADR:;;An der Hochschule 1;Augsburg;Bayern;86161;Deutschland
TEL;VALUE=TEXT:+4982155863544
URL;TYPE=work;VALUE=URL:www.hs-augsburg.de
UID:16a4aa8f-83db-459d-9b1a-c8161d40b8ce
END:VCARD


smime.p7s
Description: S/MIME Cryptographic Signature

[SOGo] ActiveSync from Android not working, SOGO 5.5.1

[novak.to...@adria-mobil.si]

Hi!

I can not sync mail to my Android device or Outlook.
I keep seeing errors in sogo.log:

Feb 23 08:32:04 sogod [3497]: <0x0x5566de7c7d10[SOGoActiveSyncDispatcher]>
EAS - request for device androidc1012178084: 
http://www.microsoft.com/;>

 0


Feb 23 08:32:04 sogod [3497]: [ERROR] <0x0x5566deeadc40[NSDataMalloc]>
xml2wbxmlFromContent: failed: Parsing of XML Document Failed

Feb 23 08:32:04 sogod [3497]: [ERROR] <0x0x5566deeadc40[NSDataMalloc]>
Original data written to: /tmp/mail_da9_27c619a8_2f.data
Feb 23 08:32:04 sogod [3497]: |SOGo| request took 0.236170 seconds to
execute

If i do xmllint --format /tmp/mail_da9_27c619a8_2f.data it parses file
correctly and no errors are given.

What can i do to fix this or figure out what is wrong ?

* email account i try to sync has 0 emails in its account, since i emptied
account, because i thought problem was with some mail.
* also no account works, tried to create 5 accounts, on every account i get
same sync errors and not even initial sync completes

With regards,

Tomaž




smime.p7s
Description: S/MIME cryptographic signature