Open GoogleCodeExporter opened 8 years ago
It's true that in theory it is possible to support other IMAP servers too. The
problem is that it introduces a lot of
special cases for all the different kinds of connection modes and edge cases.
I'll assign low priority to this
request as I'd rather keep SMS Backup simple (and robust). Patches are, of
course, very welcome!
Original comment by chstu...@gmail.com
on 2 Aug 2009 at 10:13
I patched latest svn SMS Backup to include prefs for using a different IMAP
server
than gmail.
Works flawlessly with my Cyrus 2.2 so far. Label name has to be "Inbox.SMS" in
that case.
Original comment by felix.kn...@googlemail.com
on 16 Aug 2009 at 3:56
Attachments:
Today I manually inserted felix' patch into the source code of the svn-version
of SMS
Backup.
The app displayed everything fine and tried to connect the right way. I checked
that
via "logcat", but as SMS Backup / Imapstore seems to only work with IMAP-SSL, I
couldn't test it with my IMAP-server (which is TLS).
Anyways the patch looks very clean and therefore I _highly_ recommend to work
this
patch into the original source as soon as possible.
Original comment by madc...@gmail.com
on 6 Oct 2009 at 2:45
Original comment by chstu...@gmail.com
on 17 Nov 2009 at 1:08
I really appreciate the work done for this patch, thank you! However, I'm still
hesitating
to include it as this setting would be confusing to >90% of the users. It also
adds many
more possible configurations which are very hard to debug.
The easiest would be to hide this setting for normal users and make it hard to
uncover
it. In order to properly support all kinds of IMAP servers for end-users, a lot
of work
would've to go into testing and UI (see the stock Email app of Android).
Original comment by chstu...@gmail.com
on 19 Nov 2009 at 9:26
How about something as simple as an additional menu option that required the
user to
enter a password/code that could only be found in the wiki that would enable
configuration of 'self supported' servers. The wiki page could make it quite
clear
that the use of the function is ill advised and that if you really, really
wanted to
use it you would be on your own?
Original comment by Fuzzy...@gmail.com
on 19 Nov 2009 at 10:01
Ok, I went and updated my patch.
I moved the server address to a sub category inside the advanced category. I
also
added the text "Do not change unless you know what you are doing!" to the
category
description. I didn't add any passcode, because I think that users are not THAT
stupid ;)
For those tinkering around anyway, I added the default values for gmail into the
property descriptions. So no "Reset to default" button, but I guess the default
in
the description should suffice.
I also added the option madcrax requested. In that same category you can now
choose
which security protocol to use. There is SSL (Required), SSL (Optional), TLS
(Required), TLS (Optional) and none. The "(Optional)" means that any certificate
errors are ignored. E.g. for self-signed certs etc.
Hope this makes the patch acceptable for integration into the next version. Let
me
know if there need to be more changes.
Original comment by felix.kn...@googlemail.com
on 12 Dec 2009 at 8:51
Attachments:
Hey,
great work @Felix.
Could somebody sent me a compiled copy for testing the new feature???
I'm new to android by the way don't sue me. :-)
Thx
dschoerdi@googlemail.com
Original comment by Dschoe...@gmail.com
on 21 Jan 2010 at 1:20
I've reviewed the patch and it looks really good, thanks a lot! Sorry for the
long
delay... :-/
Are okay with me including this under the Apache License 2.0?
Original comment by chstu...@gmail.com
on 22 Jan 2010 at 8:50
Ups, I totally missed that comment by you. Sorry! Of course the APL 2.0 is okay
for me!
Original comment by felix.kn...@googlemail.com
on 21 Apr 2010 at 5:16
Hi guys,
I'd love to get my hands on this patch. Was just wondering if there's any
progress on getting it integrated into the main release?
Thanks to all concerned on the good work!
Cheers!
Mark.
Original comment by mark.tu...@gmail.com
on 16 Jun 2010 at 11:50
This patch (or equivalent functionality) is incorporated in the sms-backup-plus
fork at https://github.com/jberkel/sms-backup-plus/#readme
Original comment by dav...@j5int.com
on 20 Jul 2011 at 9:27
Original issue reported on code.google.com by
Fuzzy...@gmail.com
on 22 May 2009 at 4:00