| Summary: | BCC addresses functionality not implemented | ||
|---|---|---|---|
| Product: | [Unmaintained] KMail Mobile | Reporter: | Sabine Faure <sabine> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | CLOSED FIXED | ||
| Severity: | normal | CC: | tokoe |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Sabine Faure
2010-09-08 21:18:02 UTC
Hej Sabine, works fine here on desktop with current trunk version. Can you retest please with current packages? Ciao, Tobias I retested this on the N900 today using 3 differents email addresses just like in my description above (A: work address, B: personal address and C: Imap testing address on the N900). I can still reproduce this bug: When I click on 'Reply' and go to the recipient's tab in the Composer I can see that 'To:' displays address A as it should but underneath the second line edit is empty and instead of displaying 'BBC:' it shows 'To:'. As a result recipient B never receives a copy of the reply whereas it should so I am reopening this bug. N900, 4:4.6~20101128.1201814-1maemo1.1200957 Hej Sabine, I guess you mix up BCC and Reply-To here. As the "What's This" information of the 'BCC addresses' fields in the identity dialog says, the BCC address is added automatically to the composer if Recipient A is sending an email. This feature is used to archive all mails Recipient A sends to a second account. The feature you are referring to is the Reply-To field, which is used by Recipient C's mail client to send back the message to an altenative email address of Recipient A. Can you confirm that? Ciao, Tobias Indeed I was not testing this functionality correctly! Thx Tobias ;o) Here are the correct steps to test it: - Launch Kmail-mobile - Open the 'Actions' tab - Click on 'Identities' - Select an already existing identity (ex: Recipient A) - Click on 'Modify' button - Click on the 'Advanced' tab - Enter an email address (Recipient B) in the 'BCC addresses' line edit - Click on 'Ok' twice and close the 'Actions' tab - Click on 'Write new Email' - In the composer, select the identity you've modified as the sender (Recipient A) - Enter a subject, a few words and a recipient (Recipient C) - Click on 'Send' - The email is sent and received properly by Recipient C However, Recipient B never receives a copy of the email whereas he should so I am reopening this bug. Note: I retested this on the N900 today using 3 differents email addresses (A: personal address, B: work address and C: Imap testing address on the N900). N900, 4:4.6~20101215.1206727-1maemo1.1206430 Also I forgot to mention that if you show the source of the email sent (Action tab - View - Show source) there is no mention of a BCC address in it. N900, 4:4.6~20101215.1206727-1maemo1.1206430 SVN commit 1206971 by tokoe: Use the identity BCC addresses when composing mails. Now the BCC addresses are applied initially on the new message and updated whenever the user changes the identity via the identity combobox in the composer. BUG: 250602 M +16 -1 composerview.cpp M +2 -0 composerview.h M +16 -9 mainview.cpp M +1 -1 mainview.h WebSVN link: http://websvn.kde.org/?view=rev&revision=1206971 Hej Sabine, last time I only tested with KMail and not kmail-mobile while under the impression that both use the same code for sending mails. However the code differs, so this last patch should fix it for kmail-mobile as well. This also brought up another bug with using multiple addresses in the identity's BCC field, which is fixed now as well. So thanks for insisting on the existence of this bug :) Ciao, Tobias Thx Tobias! ;o) It is corrected now Recipient B, now receives a copy of the email as he should so I am closing this bug. N900, 4:4.6~20101220.1208001-1maemo1.1206430 |