[GH-ISSUE #1001] Support IMAP username separate from email address #798

New issue

Open

opened 2026-02-26 01:31:55 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 01:31:55 +03:00

Owner

Originally created by @kurahaupo on GitHub (Dec 20, 2019).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1001

As a security measure, some services use a random token as the IMAP username, rather than the associated email address.
Currently the IMAP username is also used as the user's own email address, as noted in #999.

I suggest that the form for entering IMAP details should have a field for email address, which is then used as the default for the IMAP username.
For backwards compatibility, the IMAP username should continue to be used where no email address is provided.

Originally created by @kurahaupo on GitHub (Dec 20, 2019). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1001 As a security measure, some services use a random token as the IMAP username, rather than the associated email address. Currently the IMAP username is also used as the user's own email address, as noted in #999. I suggest that the form for entering IMAP details should have a field for email address, which is then used as the default for the IMAP username. For backwards compatibility, the IMAP username should continue to be used where no email address is provided.

kerem added the

feature-request

label

2026-02-26 01:31:55 +03:00

kerem commented

2026-02-26 01:31:56 +03:00

Author

Owner

@kurahaupo commented on GitHub (Dec 21, 2019):

Starting from the email address, it should also be possible to suggest an IMAP server name, as s/.*@/imap./.

Not sure we'd want to go the whole hog with autodiscovery (probing DNS for various domainnames, then probing connections on various ports)

@kurahaupo commented on GitHub (Dec 21, 2019): Starting from the email address, it should also be possible to suggest an IMAP server name, as `s/.*@/imap./`. Not sure we'd want to go the whole hog with autodiscovery (probing DNS for various domainnames, then probing connections on various ports)