maemo.org Bugzilla – Bug 2922
Want ability to delete POP mail from server
Last modified: 2011-01-16 23:59:51 UTC
You need to log in before you can comment on or make changes to this bug.
SOFTWARE VERSION: all STEPS TO REPRODUCE THE PROBLEM: Delete a POP3 message. Only deletes from tablet. EXPECTED OUTCOME: I would like an option to also delete from the POP3 server. (Current mail app already does this) ACTUAL OUTCOME: Only able to delete from tablet REPRODUCIBILITY: always EXTRA SOFTWARE INSTALLED: OTHER COMMENTS: In the current mail app, the radio buttons to select "delete from N810 and server" and "delete from N810 only" are also not optimal. It would be better to maybe have buttons for the different options.
from my understanding, this will be activated ones modest goes out of beta.
(In reply to comment #0) > SOFTWARE VERSION: all > > STEPS TO REPRODUCE THE PROBLEM: Delete a POP3 message. Only deletes from > tablet. > > EXPECTED OUTCOME: I would like an option to also delete from the POP3 server. > (Current mail app already does this) You can already delete POP3 mail from server. Just uncheck the "Leave on server" option in the account settings.
(In reply to comment #2) > (In reply to comment #0) > You can already delete POP3 mail from server. Just uncheck the "Leave on > server" option in the account settings. That is not what I want. I need to make myself clearer. When I check my email from the tablet, I WANT to leave the mail on the server, so that I can always download it to my Work PC. However, when I am traveling or away from the PC, I like to check emails from the tablet and maybe respond to a couple. I also would like to selectively delete some emails (usually junk) and so I don't need to see it again later and delete from my PC. In the orig email client, this was possible. In this new client there is only an option to delete from the tablet.
*** Bug 3338 has been marked as a duplicate of this bug. ***
Well, POP is a very simple protocol to download and delete email from the server. Any "Leave messages on server", "Delete after X days" options are just hacks. What you want to do is using IMAP.
Yes,(In reply to comment #5) > What you want to do is using IMAP. Yes, what I want is IMAP - please talk to my ISP about that who has no intention of implementing IMAP! :) In the meantime, I and many others are stuck with good old POP. I'm with the OP here in that I want to be able to download headers (over my Bluetooth/GSM connection) AND also delete selected messages from the server when I delete the message from the tablet. Heck, I even want the tablet to notice when a message has been deleted from my POP server because I've downloaded it through my desktop mail client (Thunderbird). If the tablet is downloading headers and I subsequently download the message on my desktop there is no point the tablet offering me the option to read the now deleted and non-existant server message - any attempts to read such a message will produces a Modest error message. I really like the idea of downloading just the headers when I'm mobile, so that I can then keep (ie. download) the important messages when I'm on my desktop. I'd also like to be able to delete the junk messages when I'm mobile so I don't have to download them when I'm on my desktop. The current Modest implementation doesn't handle this use case very well, but hopefully it will in future.
the funniest thing
sorry about that. anyways, the rfc allows for pr mail deletion from the server.
I also want the ability to delete emails from the POP3 server when the "Leave Message on Server" is set. This is not a new feature, the old email client before the Diablo update had the exact same feature. While you are looking at this, there is another bug. After the email is deleted from the inbox (not the server), the Modest is still keeping track of the deleted mail headers in the memory, so it knows which email has been downloaded. However, the headers are all kept in a list even after the actuall email is removed from the POP3 server (from another client), this causes incorrect email count on Modest. When you sync emails between inbox and POP3 server, you should also remove deleted email headers from all the list.
(In reply to comment #9) > > While you are looking at this, there is another bug. After the email is > deleted from the inbox (not the server), the Modest is still keeping track of > the deleted mail headers in the memory, so it knows which email has been > downloaded. However, the headers are all kept in a list even after the actuall > email is removed from the POP3 server (from another client), this causes > incorrect email count on Modest. When you sync emails between inbox and POP3 > server, you should also remove deleted email headers from all the list. > that would probably be this bug: https://bugs.maemo.org/show_bug.cgi?id=3081
*** Bug 3729 has been marked as a duplicate of this bug. ***
I would like to vote for this bug and confirm what the others have stated.. In the old chinook email client.. there was an option to download the email to the tablet and leave them on the POP server.. then after deleting them from the tablet, they would be deleted from the server as well.. Under diablo checking or unchecking "leave email on server" has no effect .. email is never deleted from the Pop server.. Under Chinook I would download full text of emails to the tablet (not just headers) so that I could read them offline.. then once I deleted them from the tablet they would be deleted from the server.. Under Diablo.. "leave email on server" does not download the body of the email to the tablet.. requiring a Wifi connection to read the email..
(In reply to comment #12) > I would like to vote for this bug But you didn't do yet. Please click on the "Vote for this bug" link then, this is how it works.
(In reply to comment #13) > (In reply to comment #12) > > I would like to vote for this bug > > But you didn't do yet. Please click on the "Vote for this bug" link then, this > is how it works. > Oh.. Now I have voted.. can I vote that the "vote for this bug" is confusing? Louis
(In reply to comment #14) > Oh.. Now I have voted.. > can I vote that the "vote for this bug" is confusing? Can you elaborate in a private email to me? I'm interested in that feedback.
What's the latest on this bug, will it be fixed? And if it's really considered an enhancement, will it be implemented? My Nokia phone can delete emails from a POP3 server, and it too only downloads the headers and leaves messages on the server... seems more of a bug/basic requirement than something we have to fight to get implemented as an enhancement.
(In reply to comment #16) > What's the latest on this bug, will it be fixed? And if it's really considered > an enhancement, will it be implemented? I don't know of any plans (yet) to implement this.
The plan is to provide the possibility to delete emails from the POP3 server in Fremantle.
(In reply to comment #17) > (In reply to comment #16) > > What's the latest on this bug, will it be fixed? And if it's really considered > > an enhancement, will it be implemented? > > I don't know of any plans (yet) to implement this. It's not an enhancement, it's actually a bug. After reviewing the code I have to say that it's not difficult to fix and we'll do that ASAP. If I understood correctly, you all want 2 delete options, one "delete email locally" and another "delete email in server". Well if it's a common use case we could think in how to add these options to the UI -any suggestion?- because the required code to do that is really small.
(In reply to comment #19) > It's not an enhancement, it's actually a bug. After reviewing the code I have > to say that it's not difficult to fix and we'll do that ASAP. > Excellent, thanks for doing the legwork Sergio. > If I understood correctly, you all want 2 delete options, one "delete email > locally" and another "delete email in server". Well if it's a common use case > we could think in how to add these options to the UI -any suggestion?- because > the required code to do that is really small. > Personally speaking, I only want the "delete email from server" option since if I'm reading an email on the tablet (that I don't want to download at home, ie. spam) then I will delete it from the tablet. I would have no objection if there were two delete options however, perhaps two icons in the toolbar or two delete options in the context menu though this might become confusing/dangerous. The only time I need to delete emails locally on the tablet is when I have already downloaded the emails from the server to my home PC/Thunderbird and the emails are left, abandoned, on the tablet - should I raise a seperate bug about "syncing" the tablet with the server (my S60 Nokia phone does this - any emails I download at home then automatically disappear from my phones inbox on the next refresh).
Sorry, a slight addendum as I missed off the final sentence to the last para in comment #20, above: "So, if the tablet can sync it's inbox with the server (as my phone does) then I would have no requirement to delete emails locally. My only requirement would be to delete emails from the server."
iirc, the mail client before modest asked, if one used the "leave mail on server" option, if one wanted to delete the message on the server when one deleted the message locally. however, having a mail suddenly vanish because its no longer on the server could be just as confusing as having multiple delete options. however, what if there was some way to mark if a mail was no longer on the server, like say applying strike-through (or whatever its called) on the title or something?
(In reply to comment #22) > iirc, the mail client before modest asked, if one used the "leave mail on > server" option, if one wanted to delete the message on the server when one > deleted the message locally. > That would work for me. If the system works correctly (ie. syncing with the server is implemented) then I won't object to being prompted on the few occasions when I manually delete an email. Obviously a checkbox "Don't ask this question again" would be icing on the cake! :) > however, having a mail suddenly vanish because its no longer on the server > could be just as confusing as having multiple delete options. > The problem is that if you are downloading only the headers once the email has been downloaded from the server by another email client any attempt to read the email on the tablet will result in an error informing you that the email is no longer available. Perhaps Modest should only "sync" with the server when it is set to download only headers, that would work for me. As I say, Nokia phones do this syncing trick already - I have my phone set to download only headers, not sure what it does when set to download the entire email, will check - so I can only assume it's not that confusing otherwise Nokia wouldn't support it in their S60 phones. > however, what if there was some way to mark if a mail was no longer on the > server, like say applying strike-through (or whatever its called) on the title > or something? > I can't see the point of this when downloading only the headers, however there could be some merit to this idea if Modest is configured to download the entire email (and not just the headers). Personally I have no desire to keep emails on the tablet that have been downloaded elsewhere and are no longer available to be read from the server. However if it is still possible to read an email, because it's been fully downloaded to the tablet, then adding an indication to inform the user it's been removed from the server might be of some benefit. The trouble is that if I'm downloading headers only, and I read an email which causes the whole email to be downloaded I would still want this email to be deleted automatically when it disappears from the server... so I guess for me this "retain but strike-through deleted emails" idea should only apply when Modest is *not* set to download headers - when it is set to download headers it should always remove from the tablet those emails that are no longer present on the server.
Results from a Nokia S60 (N85) phone - the S60 email client will always "sync" with the server whether it is downloading headers or the whole message & attachments. * I set the phone to download "Msgs. & attachs." (it was originally set to "Headers only") * I sent myself an email which was automatically downloaded to the phone (but left on the server) * I read the email on the phone * I downloaded the same email to my PC (Thunderbird), this deleted the message from the POP server * I refreshed the inbox on the phone and the inbox was left empty - the previously read message which was there prior to the refresh disappeared after the refresh.
ok, it looks like we may have to get our ducks in a row here. when i talk about downloaded mails, im talking about the whole thing, headers, content, attachments, all of it. if only headers are downloaded, i have no problem with the client auto-deleting headers that no longer have relation to a mail on the server (and modest do this already from what i recall). but what i don't want to see is modest deleting a mail that i have read on the tablet (thereby having it fully downloaded onto the tablet, but because of the "keep message on server" setting, can still be downloaded and deleted from server by a desktop client like thunderbird). however, if i then select one of those fully downloaded mails, and hit delete, it would be nice to get the question to delete the server-side copy, if modest thinks there still is one.
(In reply to comment #25) > if only headers are downloaded, i have no problem with the client auto-deleting > headers that no longer have relation to a mail on the server We agree here! :) > (and modest do this already from what i recall). > I've never seen modest do this - I wish it did! Maybe it's another bug? On my N810/5.2008 tablet I'm always left with a full inbox of non-existant emails, the blue LCD flashing away and the Home menu full of "new" emails long after these same emails have been downloaded to Thunderbird and removed from the server! :( I periodically have to go into Modest and remove all the old emails, remembering to perform a final refresh of the modest inbox before exiting due to bug 3081. > but what i don't want to see is modest deleting a mail that i have read on the > tablet (thereby having it fully downloaded onto the tablet, but because of the > "keep message on server" setting, can still be downloaded and deleted from > server by a desktop client like thunderbird). > > however, if i then select one of those fully downloaded mails, and hit delete, > it would be nice to get the question to delete the server-side copy, if modest > thinks there still is one. > OK, this is where we disagree! Hopefully a simple configuration option can give us both what we want. I typically download headers only, then read a selection of my emails on the tablet when I'm out and about, then later in the day I'll download all the emails for longer term storage on my desktop PC. At this point I don't want to then have to manually delete the same emails from the tablet that I just downloaded to my PC - I want modest to automatically "sync" with the server and if there are no emails on the server there should be no emails in my modest inbox (whether I downloaded them entirely, or just the headers). Since this isn't how you work (and there's no reason why it should be!) a "Sync downloaded emails with server" option appears necessary so that users can choose if downloaded emails should be removed from the tablet once they disappear from the server. Irresepective of the "sync downloaded emails with server" setting, any unread (and thus not yet downloaded) header-only emails should be automatically deleted from the tablet whenever the corresponding email is no longer available on the server. This exceeds the current functionality provided by Nokia S60 phones, as these devices sync always (downloaded or headers-only). Prompting the user delete the server-side email only when it exists is a nice touch. Should this requirement now be filed under another bug, or does it still fall within the boundaries of "email deletion"?
(In reply to comment #26) > (In reply to comment #25) > > if only headers are downloaded, i have no problem with the client auto-deleting > > headers that no longer have relation to a mail on the server > > We agree here! :) > > > (and modest do this already from what i recall). > > > > I've never seen modest do this - I wish it did! Maybe it's another bug? > > On my N810/5.2008 tablet I'm always left with a full inbox of non-existant > emails, the blue LCD flashing away and the Home menu full of "new" emails long > after these same emails have been downloaded to Thunderbird and removed from > the server! :( > > I periodically have to go into Modest and remove all the old emails, > remembering to perform a final refresh of the modest inbox before exiting due > to bug 3081. Well the reason why you still can see messages in Modest INBOX is because Modest caches the emails you read. This way you can always read them offline. Thunderbird does not cache your messages by default unless you explicitly ask it to do that. > > > but what i don't want to see is modest deleting a mail that i have read on the > > tablet (thereby having it fully downloaded onto the tablet, but because of the > > "keep message on server" setting, can still be downloaded and deleted from > > server by a desktop client like thunderbird). > > > > however, if i then select one of those fully downloaded mails, and hit delete, > > it would be nice to get the question to delete the server-side copy, if modest > > thinks there still is one. > > > > OK, this is where we disagree! Hopefully a simple configuration option can give > us both what we want. It seems that you're asking for different things indeed. > I typically download headers only, then read a selection of my emails on the > tablet when I'm out and about, then later in the day I'll download all the > emails for longer term storage on my desktop PC. At this point I don't want to > then have to manually delete the same emails from the tablet that I just > downloaded to my PC - I want modest to automatically "sync" with the server and > if there are no emails on the server there should be no emails in my modest > inbox (whether I downloaded them entirely, or just the headers). Well I understand that this is your typical workflow, but take into account that designing an email client we have always to follow the rule "never lose an email, never lose data". Some other user could complain about Modest deleting their emails when removing them from server. That's why I agree that the fairest solution could be some user setting.
(In reply to comment #27) > Well the reason why you still can see messages in Modest INBOX is because > Modest caches the emails you read. This way you can always read them offline. > Thunderbird does not cache your messages by default unless you explicitly ask > it to do that. > Caching is good, but when deleted messages come back from the dead that's not so good! Anyway I think you've pointed at a potential cause in your most recent comment on bug 3081. > Well I understand that this is your typical workflow, but take into account > that designing an email client we have always to follow the rule "never lose an > email, never lose data". Some other user could complain about Modest deleting > their emails when removing them from server. That's why I agree that the > fairest solution could be some user setting. > Although the way modest currently behaves is not consistent with other Nokia products, and judging from comments made in other bugs consistency seems to be a desirable objective, where possible. Adding the option discussed above would certainly be an improvement on existing Nokia behaviour. I'm going to open a new bug and mostly cut & paste from here!
(In reply to comment #27) > (In reply to comment #26) > > (In reply to comment #25) > > > if only headers are downloaded, i have no problem with the client auto-deleting > > > headers that no longer have relation to a mail on the server > > > > We agree here! :) > > > > > (and modest do this already from what i recall). > > > > > > > I've never seen modest do this - I wish it did! Maybe it's another bug? > > > > On my N810/5.2008 tablet I'm always left with a full inbox of non-existant > > emails, the blue LCD flashing away and the Home menu full of "new" emails long > > after these same emails have been downloaded to Thunderbird and removed from > > the server! :( > > > > I periodically have to go into Modest and remove all the old emails, > > remembering to perform a final refresh of the modest inbox before exiting due > > to bug 3081. > > Well the reason why you still can see messages in Modest INBOX is because > Modest caches the emails you read. This way you can always read them offline. > Thunderbird does not cache your messages by default unless you explicitly ask > it to do that. > i may be splitting hairs, but is caching really the right word to use in this context? remember, we are talking about POP3 here, not IMAP.
(In reply to comment #29) > i may be splitting hairs, but is caching really the right word to use in this > context? > > remember, we are talking about POP3 here, not IMAP. > I assume/believe Sergio means caching on the device (of headers, emails etc.) whereby POP3 information is retrieved and cached locally until the next refresh. There is a modest cache in ~/.modest/cache (which is mentioned in your bug 3949, which I think is a dupe of bug 3081!) :)
(In reply to comment #18) > The plan is to provide the possibility to delete emails from the POP3 server in > Fremantle. > Quim - considering Sergios follow on comment confirming this is a bug, should this report now be re-opened until we can confirm a fix has shipped?
(In reply to comment #19) > It's not an enhancement, it's actually a bug. I bet Sergio means that in his opinion this should be a piece functionality already implemented and without it there is something missing. > After reviewing the code I have > to say that it's not difficult to fix and we'll do that ASAP. > If I understood correctly, you all want 2 delete options, one "delete email > locally" and another "delete email in server". Well if it's a common use case > we could think in how to add these options to the UI -any suggestion?- because > the required code to do that is really small. This means that actually this "bug" is not specified in his project plan, some UI needs to be figured out and some code needs to be written, tested, etc. For these reasons I think that we are talking here about an enhancement request. Otherwise there is no specs or code to test against.
Bug 3975 created to track the syncing enhancement. (In reply to comment #19) > It's not an enhancement, it's actually a bug. After reviewing the code I have > to say that it's not difficult to fix and we'll do that ASAP. > > If I understood correctly, you all want 2 delete options, one "delete email > locally" and another "delete email in server". Well if it's a common use case > we could think in how to add these options to the UI -any suggestion?- because > the required code to do that is really small. > As a quick fix - perhaps even for Diablo - could we prompt the user "Do you also want to delete from the server?" (Yes/No) - obviously NO will only delete the local version, but YES will delete BOTH the local and (assuming it still exists as it may already have been deleted) the server version - if the server version no longer exists, just delete the local version and don't complain about the missing server version! Quim - enhancement or bug? I don't know, it's pretty basic functionality and seemingly it's a coding error and a quick fix to boot (GUI side permitting, with associated localisations etc.) Ideally this would be good for Diablo, but really does need to be in Freemantle at the very least (and if you target Freemantle, hopefully it can then be hooked up with bug 3975?) :)
(In reply to comment #33) > Quim - enhancement or bug? I don't know, it's pretty basic functionality and > seemingly it's a coding error and a quick fix to boot (GUI side permitting, > with associated localisations etc.) Ideally this would be good for Diablo, but > really does need to be in Freemantle at the very least (and if you target > Freemantle, hopefully it can then be hooked up with bug 3975?) :) UI spec, localization in several languages, code and testing is not pretty basic nor code error. FIXED + target milestone Fremantle means that we commit to have this functionality in Maemo 5.
(In reply to comment #26) > (In reply to comment #25) > > if only headers are downloaded, i have no problem with the client auto-deleting > > headers that no longer have relation to a mail on the server > > We agree here! :) > > > (and modest do this already from what i recall). > > > > I've never seen modest do this - I wish it did! Maybe it's another bug? > I must post an update to my statement here - and it's potentially another bug :( It appears that modest (5.2008.43-7) will auto delete header-only emails if they no longer exist on the server, but only if modest is restarted. I just sent myself a test POP email, refreshed the modest inbox and saw it appear, then deleted the email from the server wihtout reading it in modest. Upon refreshing the modest inbox perhaps 20 times the email continued to remain available for reading - it should have disappeared after the first refresh. I shut down modest and then started modest, and the email is shown as available in the inbox. If I now refresh the modest inbox the unread email disappears as it should have done prior to me shutting down modest. So this goes some way towards bug 3975, as it seems that modest will keep read (ie. downloaded) emails but delete unread header-only emails. I guess I should post this comment against bug 3975 too. I've never really seen this auto-deletion behaviour as I tend not to close down modest.
I am really happy to see the interset in this bug report. Also the good suggestions. What I am sad about is that it won't be implemented in Diablo. I reported this bug in February 2008 when Modest was in development. A perfect time to add in the delete from server option. Especially as it was already a feature of the previous email client. Quim - Was/Is there a better way to point out that a feature was missing from a beta piece of software? I thought the releases of Modest before it was added to the OS was for us to test and point out problems etc. I did the testing and reporting but was ignored. Now we have a situation where there is way too much development/testing/gui/language changes for the feature to be added :-(
(In reply to comment #36) > Was/Is there a better way to point out that a feature was missing from a > beta piece of software? What you've described are things that went wrong in the past when maemo.org Bugzilla was not embedded into Nokia's internal organization and hence mainly ignored. Times are changing/improving and maemo.org Bugzilla is still the correct place for such feature requests. (By voting for your favourite issues you can also make sure that reports get the attention they deserve.)
(In reply to comment #36) > Quim - Was/Is there a better way to point out that a feature was missing from a > beta piece of software? No. > I thought the releases of Modest before it was added > to the OS was for us to test and point out problems etc. That was the intention, yes. What happened in practice with these and other Modest reports I don't know. You could ask Dirk-Jan Binnema, the project manager at the time. Easy to find in maemo.org. > I did the testing and > reporting but was ignored. Now we have a situation where there is way too much > development/testing/gui/language changes for the feature to be added :-( This happens because we have a lot to improve in our open development, and simply in gathering user feedback. It's improving but there is still a way to go. About Modest, I will propose to the team to move to pure open development by the Fremantle beta SDK release. This might help getting a community Diablo backport, by the way.
(In reply to comment #36) > I am really happy to see the interset in this bug report. Also the good > suggestions. > What I am sad about is that it won't be implemented in Diablo. > I reported this bug in February 2008 when Modest was in development. A perfect > time to add in the delete from server option. Especially as it was already a > feature of the previous email client. Don't be so sad Andrew :-) We're really pushing hard for a more open development as Quim said. Don't worry too much about Diablo, because we're developing Modest for Fremantle, but because of its design/architecture, most of the code is shared between the different supported UIs (GNOME, Diablo, Fremantle), so this kind of problems that do not depend on UI things will be fixed for one and all different versions. The current code under development still builds perfectly for Diablo so it would depend more on the releasing policy of Nokia, maybe we could have future releases for Diablo, don't know.
(In reply to comment #30) > (In reply to comment #29) > > i may be splitting hairs, but is caching really the right word to use in this > > context? > > > > remember, we are talking about POP3 here, not IMAP. > > > > I assume/believe Sergio means caching on the device (of headers, emails etc.) > whereby POP3 information is retrieved and cached locally until the next > refresh. There is a modest cache in ~/.modest/cache (which is mentioned in your > bug 3949, which I think is a dupe of bug 3081!) :) > true, however, unless im mistaken, this is the expected behavior of POP3, the download of mails to local storage. mostly used in the days of analog dial-up connections, as they where often timed, and as such one would want to download, go offline and then read. this unlike IMAP where i understand the default behavior to be to basically act as a terminal to the server, and nothing is downloaded unless specified.
Setting Target Milestone to Fremantle SDK beta.
*** Bug 5567 has been marked as a duplicate of this bug. ***
According to bug 5567 this is not working yet in 1.2009.41-10. Reopening and setting TM according to comment 34.
*** Bug 7181 has been marked as a duplicate of this bug. ***
Have just set up a Yahoo POP3 account. Unchecked "leave Mail on Server" in the account settings. Deleting emails on the N900 removes the mail from the device. Perform a send and receive to see if it then removes from the server. Sadly it is still on the server. Restarted the web interface on the server as well as reboot of N900 to see if it changes, but no delete. Here is what the N900 user manuals says. ================================ Delete mail messages To delete a mail message, select the message and . For POP3 accounts, if you have activated the Leave messages on server option in the incoming mail settings, the message is only deleted from your device. If you deactivate the option and want to delete the message from the server, select the message and Delete. For IMAP4 accounts, the messages you delete are always deleted from the server.
This is definatly a bug if Modest is supposed to support POP3 protocol. Please see RFC 1939 (http://tools.ietf.org/html/rfc1939) for reference, especially the DELE command. This is NOT an optional command to be supported but a core feature. This may already be issued correctly in which case the migration to UPDATE mode is not being handled. Either way this functionality is part of the POP version 3 protocol so either should be implimented or claims to support the protocol dropped.
I fixed this issue in the POP3 code a couple of weeks ago. Basically the DELE command was not issued properly.
(In reply to comment #47) > I fixed this issue in the POP3 code a couple of weeks ago. Basically the DELE > command was not issued properly. > Do you know if this made it into PR1.1/2.2009.51-1? I'm guessing not as it doesn't appear to be working in 51-1 (at least not with a Nokia Messaging/POP server).
(In reply to comment #47) > I fixed this issue in the POP3 code a couple of weeks ago. Basically the DELE > command was not issued properly. Sergio - thanks for the post on confirmation of this. Nice to know I wasn't too far off the problem. Glad all fixed and look forward to using a much better implimentation, thanks!
*** Bug 6722 has been marked as a duplicate of this bug. ***
Requested operation when "Leave on server" option selected. Mostly similar to current S60 operation on N95 or similar. - when send/receive esecuted only dowloads new messages from server - new messages means not previously downloaded by N900 email acct. Email already locally deleted on N900 should not be downloaded again. - Option to download only new + unread messages possible ? - unread means not accessed by another application such as webmail. - when deleting a message have the option to delete only locally or locally & from server - messages marked for deletion on server are deleted when next send/receive executed or when email application closed. - when send/receive executed any messages removed from server also deleted from N900 local account (e.g. messages downloaded by another email application such as Outlook and removed from server, or deleted by webmail access). - local account will auto disconnect after a few minutes of non-activity (selectble time?) in order to allow access by other applications. - This has potential conflict with the auto-update time interval when activated, so should always be less than the autoupdate interval. - This auto disconnect will delete marked messages from server (different behaviour from S60). - Non-activity open for interpretation, but example could be the account not opened from the the email main page, or no active keystrokes in an opened account. - Option for download header only, or with kb size setting, or full email+attachments. - When selecting specific message to open (when header only selected), do not download attachments unless separately selected, or configurable option. This is to allow control over data useage. - 0ption to set max. # of messages to download per send/receive. - Option for send message immediate or during next send/receive. - Option for send copy to self.
So what was the last comment about at all? Wishlist? Comparison? Something else?
Sorry if my posting was inappropriate. The intent was the requested user operation when using the delete function since I did not see a complete user case senario spelled out. The programmers I work with prefer this in my company where we do embedded systems. If my posting style is not correct for this community please steer me in the preferred direction since I an very excited about this platform and hope provide a great deal of feedback. Agree the last couple me items in my post probably belong in other bug tickets.
(In reply to comment #53) > Sorry if my posting was inappropriate. The intent was the requested user > operation when using the delete function since I did not see a complete user > case senario spelled out. > > The programmers I work with prefer this in my company where we do embedded > systems. If my posting style is not correct for this community please steer me > in the preferred direction since I an very excited about this platform and hope > provide a great deal of feedback. > > Agree the last couple me items in my post probably belong in other bug tickets. > Please a) Read the RFC regarding POP3 operation so you understand how POP3 is supposed to work and then b) the previous postings: you will see that the narrow scope of the request has already been addressed. Mixing up different sets of functionality makes bugs harder to track and show as complete, your posting covers multiple functionality (download & deletion). Is there good reason to leave this reopened? If not then can this eentry be reverted to previous state? I was under the impression that the DELE functionality was now corrected and awaiting release?
Closing as per comment 47.
can anybody confirm whether this is a two-way fix (phone to send delete to server (=DELETE) AND phone to pick up what has been deleted from server (=UPDATE)?
I installed already the thirth firmware update but this bug is still not solved! Why?
(In reply to comment #57) > I installed already the thirth firmware update but this bug is still not > solved! > Why? > That firmware updated didn't have any change in email application. Next time please check the list of changes.
Setting explicit PR1.2 milestone (so it's clearer in which public release the fix will be available to users). Sorry for the bugmail noise (you can filter on this message).
can anybody tell me whether there's a separate bug for emails that have been deleted from the pop3 server not being deleted from the N900 after a synch? I'm still having this problem in PR1.3
(In reply to comment #60) > can anybody tell me whether there's a separate bug for emails that have been > deleted from the pop3 server not being deleted from the N900 after a synch? It's unrelated to this ticket here, hence it is a separate issue (please avoid unrelated mail and use http://talk.maemo.org instead). Search or maybe file a request, though the latter for Maemo5 would result in a WONTFIX as no new features are planned for Maemo5 (again, http://talk.maemo.org).