Menu

#150 Lightning 1.0b1 not able to connect to DavMail

v3.6.5
closed-fixed
nobody
Caldav (160)
5
2010-07-20
2010-04-23
No

Hello,

I just upgraded Thunderbird and lightning and it is no longer able to connect to DavMail. The versions I have are:
Thunderbird 3.0.4
Lightning 1.0b1
DavMail 3.6.5-1000

Is this known? Please let me know what I can do to help.

Thanks!

Discussion

  • Mickael Guessant

    As usual, a log file would help !

     
  • Daniel Castro

    Daniel Castro - 2010-04-23

    What kind of logs do you want?
    At the moment it is set to:
    Default:WARN HttpClient:WARN
    DavMail:DEBUG Wire: DEBUG

    And there is nothing on the logs, it looks like lightning is not even trying to connect to 127.0.0.1.
    I have tried this on a few different machines with the same versions.

    Have you successfully used lightning 1.0b1?
    Maybe the configuration for 1.0b1 is different?

    Thanks!

     
  • Mickael Guessant

    I use 1.0b1 daily, and had a few issues with inbox handling but overall it' working.

    You should probably have a look at Lightning logs (see http://davmail.sourceforge.net/faq.html\)

     
  • Daniel Castro

    Daniel Castro - 2010-04-26

    Ok. Lightning logs say:

    Warning: There has been an error reading data for calendar: Work. However, this error is believed to be minor, so the program will attempt to continue. Error code: DAV_NOT_DAV. Description: The resource at http://127.0.0.1:1080/users/username@domain.com/calendar is either not a DAV collection or not available

    Warning: There has been an error reading data for calendar: Work. However, this error is believed to be minor, so the program will attempt to continue. Error code: READ_FAILED. Description:

    Any ideas? If I revert to Thunderbird 2.0.0.24 and lightning 0.9 it works.

     
  • Daniel Castro

    Daniel Castro - 2010-06-03

    I came across this issues again. After a while I figured that for some reason it had to do with my global proxy configuration.
    The strange thing is that using the old lightning plugin this wouldn't happen. Disabling the system-wide plugin or adding the exchange server to the bypass list fixed the issue.

     
  • Mickael Guessant

    • status: open --> closed-fixed
     

Log in to post a comment.