[kmailtransport] [Bug 435354] Sending SMTP mail doesn't work
https://bugs.kde.org/show_bug.cgi?id=435354 Harry Sinclair changed: What|Removed |Added CC||shadw...@hls3.com --- Comment #2 from Harry Sinclair --- I am experiencing the same issue on Ubuntu 21.04 with KMAIL 20.12.3. The SMTP commands never attempt to authenticate after the ELHO and STARTTLS commands. Here is the ksmtp log file output. - S: 220 mail2.domain.com ESMTP Postfix C: EHLO pop-os.localnet S: 250-mail2.domain.com S: 250-PIPELINING S: 250-SIZE 15728640 S: 250-ETRN S: 250-STARTTLS S: 250-ENHANCEDSTATUSCODES S: 250-8BITMIME S: 250-DSN S: 250 SMTPUTF8 C: STARTTLS S: 220 2.0.0 Ready to start TLS C: EHLO pop-os.localnet S: 250-mail2.domain.com S: 250-PIPELINING S: 250-SIZE 15728640 S: 250-ETRN S: 250-AUTH PLAIN LOGIN S: 250-ENHANCEDSTATUSCODES S: 250-8BITMIME S: 250-DSN S: 250 SMTPUTF8 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 303861] Can't write CalDav items from korganizer
https://bugs.kde.org/show_bug.cgi?id=303861 --- Comment #27 from Harry Sinclair --- Can you send those wireshark instructions to me as well? (In reply to comment #26) > (In reply to comment #25) > > Thanks for fixing that - I will test 4.9.3 as soon as it is available. > > Nevertheless, there was a different behavior between access rights of > > calendar and contact items. Contacts allway worked with davmail. > > As CalDav and CardDav share a lot of code, including the access rights > management, my best guess would be that DavMail replies differently. The > only way to be sure would be with a network capture. > > > For me it > > seems, that there might be an underlying bug in carddav ignoring the access > > rights at all. > > Full access can be granted if the CardDav answer does not contain any > privileges specification or explicitly states that all privileges are > granted. Without the XML of the exchange it's impossible to tell which is > happening. > > I'll insist heavily on that: a network capture speeds up the debugging > drastically. It only took a couple of minutes to find the problem once Hans > sent me one. If you need the process (with Wireshark) I have it at hand :) > > Cheers, > Grégory -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 303861] Can't write CalDav items from korganizer
https://bugs.kde.org/show_bug.cgi?id=303861 --- Comment #19 from Harry Sinclair --- My daily workaround is to bring up akonadiconsole and remove the blank AccessRights attribute from the Calendar folder under the DavMail agent. (In reply to comment #18) > Hi, > > Without access to an Exchange server this will be hard to debug > unfortunately :/ > > If any of you can do a network capture of a full exchange between the > resource and davmail, please send it to me. Try to anonymize it as much as > you can, especially the HTTP headers that will contain the authentication > data. I'm mostly interested in the XML exchanges, not that much in the > events data, so you can scrap it altogether. > > Cheers, > Grégory -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 303861] Can't write CalDav items from korganizer
https://bugs.kde.org/show_bug.cgi?id=303861 Harry Sinclair changed: What|Removed |Added CC||shadw...@hls3.com --- Comment #16 from Harry Sinclair --- I have this issue in KOrganizer 4.8.5 and DavMail 4.0.0-2016. This issues seems to be that when Akonadi (1.7.2) connects to the DavMail resources it creates the calendar directory with modification rights and it also creates a blank "AccessRights" attribute. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
