[GH-ISSUE #530] Select "SMS"; response: #6# [NO, [NONEXISTENT] error #450

New issue

Closed

opened 2026-02-26 01:30:37 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 01:30:37 +03:00

Owner

Originally created by @osubuckeyechick on GitHub (Jan 26, 2015).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/530

I got this error while backing up my texts. How do I fix this? The full error code is ;

Select "SMS"; response: #6# [NO, [NONEXISTENT], unknown mailbox: SMS (failure)]

Originally created by @osubuckeyechick on GitHub (Jan 26, 2015). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/530 I got this error while backing up my texts. How do I fix this? The full error code is ; Select "SMS"; response: #6# [NO, [NONEXISTENT], unknown mailbox: SMS (failure)]

kerem closed this issue

2026-02-26 01:30:37 +03:00

kerem commented

2026-02-26 01:30:37 +03:00

Author

Owner

@jberkel commented on GitHub (Jan 26, 2015):

it could be this:
https://github.com/jberkel/sms-backup-plus#i-get-the-one-of-following-errors-during-backuprestore-command-select-sms-response-6-no-unknown-mailbox-sms-failure-or-response-6-no-nonexistent-unknown-mailbox-sms-failure

@jberkel commented on GitHub (Jan 26, 2015): it could be this: https://github.com/jberkel/sms-backup-plus#i-get-the-one-of-following-errors-during-backuprestore-command-select-sms-response-6-no-unknown-mailbox-sms-failure-or-response-6-no-nonexistent-unknown-mailbox-sms-failure

kerem commented

2026-02-26 01:30:37 +03:00

Author

Owner

@osubuckeyechick commented on GitHub (Jan 27, 2015):

That was it. Thank you!

@osubuckeyechick commented on GitHub (Jan 27, 2015): That was it. Thank you!

kerem commented

2026-02-26 01:30:37 +03:00

Author

Owner

@comp9 commented on GitHub (Mar 3, 2015):

That was the issue for me as well. Thanks for the link, solved it for me as well! Hope they'll update the error message, wouldn't have guessed need to check imap based on that :D.

@comp9 commented on GitHub (Mar 3, 2015): That was the issue for me as well. Thanks for the link, solved it for me as well! Hope they'll update the error message, wouldn't have guessed need to check imap based on that :D.