On Dienstag 12 Mai 2009 Jonathan Feally wrote: > This could > pose a big problem with the fact that all messages in a mailbox would > have to be rewritten before a simple list command could be fulfilled > as the size of the messages would be different than what is stored > already in a column.
We are speaking about a mode which really breaks RFCs anyway. Will there be problems when you report the normal message size, say 5MB, to a client and then the mail is only 20KB received size? I guess the progress bar will get messed up, but the rest should be OK. > As an IT administrator, I > don't want to be the one who gets the call from the CEO when his > email on his blackberry is missing the very important forwarded as an > attachment email is replaced with a message - attachment(s) is/are > available on your non-mobile client. The CEO, or his techie, must explicitly configure #mobile mode. If you are afraid, don't do that. Use it only for people who you can explain the implications. And: the attachments are not only available on his PC, but he gets a https: link sent with the mail, replacing the attachment. A click on that link will download the attachment. After all, this mode helps saving time to receive a message, which is welcome to most mobile users. Blackberry gets mail pushed on it anyway, so maybe you don't want #mobile mode there, as you don't see the time it takes to receive a mail normally. mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0660 / 415 65 31 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
