Hi! > Am 24.06.2012 01:27, schrieb Pyrokar: > > My question was: are there 2 passwords in icedove for receive and send? > > Since sending mail works, the username+password configuration for this > > is correct. > > What makes you shure? Sending and receiving are different parts!
Since sending mail worked, the username+password configuration for this (sending mails) was correct. I'm sure of this, because it *worked*. > For > receiving mails icedove uses the POP protocol (or IMAP), for sending > SMTP. This are different protocols with diffrent ports! Icedove is > makeing a separate entry for the two different parts. This is the answer to my original question: are there 2 distinct credentials for send and receive. > So you have to check your settings if the username for both things is > the same, as, you know you have to use for sending and receiving the > same username. > Also the passwords of course. > > >> You will find your passwords in 'Edit - Preferences - Security - > >> Passwords -> Saved passwords...'. > >> And the used username in 'Edit -> Account Settings -> Outgoing SMTP > >> Server'. These to different locations for credentials I hadn't found, therefore the question regarding seperate credential for send and receive. > > I have found several bug-reports with same error-message and problem > > description posted over the last few years without any solution posted. > > I've switched to kmail and won't give icedove another try in the next > > few years. > > Without any hints to this bug messages we are unable to reproduce this > behavior. My last testing with mail getting via POP and gmx works fine, > so I don't now there your problem is from. At first receiving mail via pop from gmx had worked fine. After I had decided to use icedove, I populated my adressbook with 15-20 contacts. After this action receiving failed with the error-message I wrote into the bug-report: Error: this._mostRecentActivityForFolder[aFolder.URI] is undefined Source File: file:///usr/lib/icedove/modules/activity/pop3Download.js Line: 127 > You wrote that you are not using icedove anymore and don't wanne do > this. So I think it is better to close this bug and open a new one if > there are new problems. This was obviously not a new problem. After days without response I searched a bit and found several reports of the same bug. The only "solution" found was: clear profile and restart fresh. I don't intent to enter adressbook after adressbook to "solve" a years old and always ignored bug. Pyrokar -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
