after checking my emails I would expect to be able to send a message
right away, without giving my password again. I left the fields in the
sent preferences dialog empty, but checked the box for SMTP AUTH.
Sylpheed did it with the same configuration, more exact: claws converted
the Sylpheed settings. I am using a secured imap server and a secured
smtp server.

tags 510798 moreinfo
thanks

Hi,

If you don't provide passwords in config I think it's expectable to be
asked for them.
I don't understand where the bug is... or maybe I did'n understand
anything else.

Anyway since version 3.6.0 session-wide passwords have been
implemented, you may try latest version from experimental (requires
libetpan from there too), which is 3.7.0 and see if that improves your
experience regarding this.

regards,

Hi,

This is not a bug. Passwords are cached per account and server type.

Hi Eric,

[Please, don't remove Cc, it helps me to track bugs better]

As Colin commented previously [0] this is not a bug, servers can be
completely different, there's no reason to assume they use the same
password if you didn't provide one explicitly for it in the
configuration.

Reusing the POP password for SMTP AUTH would be a feature request, if
you want, you may file it as a separate bug (severity wishlist) or
reshape this one (I can do it for you if you want). Anyway the use
case seems a bit rare IMHO, not sure if deserves another option
(though maybe a hidden preference can solve it easily).

[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510798#17

Hi Ricardo,
I thought about this is not a bug but a feature. My point is, that the dialog explanation tells you, if you leave it blank in sent, the POP or IMAP values are taken.
This is how sylpheed behaves.
Claws does not.
The preferences dialog does not point out the server, but a user issue.
I see it can be useful, but I don't think the majority of people are using different passwords for sending and recieving emails. And there is already a way for such persons, to handle it by another account.

On Mon, 5 Jan 2009 14:59:57 +0100 "Ricardo Mones" <mones@debian.org> wrote:

I second that request. Moreover, I think this is how it *should* behave,
because the following text is written under the 'SMTP authentication'/user ID
field:

  "If you leave these entries empty, the same user ID and password as receiving
  will be used".

and this is how claws behave if I set a password directly in the receiving
settings. If I have both fields empty, the password I entered for the session
should *also* apply to the SMTP server. It shouldn't behave differently!

If I really wanted to enter a different password, I would simply enter an
username here (and leave the password field empty).

The current behavior is unexpected for me.