Auto-configure email for iPhone
Completed
The current auto-configure for email clients seems to work fine in most cases and has cut down on our support costs per client. The one still killing us though is iPhone email configuration for IMAP and POP3!!
We take calls daily with people needing help setting up their iPhones to work with cPanel email servers. If you google it, quite a few hosting companies even had to put together how-to videos, it's that challenging.
cPanel needs to work on making it MUCH easier to setup an iPhone to work with the cPanel email system.
This is scheduled for inclusion in 11.48 as part of case 121309
This is now available in 11.48+
This is scheduled for inclusion in 11.48 as part of case 121309
This is now available in 11.48+
It would appear that this would be feasible by generating and providing an installable IOS Profile for the user to download/send to their phone.
It would appear that this would be feasible by generating and providing an installable IOS Profile for the user to download/send to their phone.
GREAT!! We get calls daily and this can tie up an hour or more of support time per client.. iPhones are a REAL pita on standard POP/IMAP accounts..
GREAT!! We get calls daily and this can tie up an hour or more of support time per client.. iPhones are a REAL pita on standard POP/IMAP accounts..
Seems like the guys from https://iphoneconfig.com/ worked a solution,
however I don´t feel well asking my customers to go to a third party website
and have them to type in their passwords.
Seems like the guys from https://iphoneconfig.com/ worked a solution,
however I don´t feel well asking my customers to go to a third party website
and have them to type in their passwords.
BTW I guess that there should an Android equivalent of this application.
BTW I guess that there should an Android equivalent of this application.
The problems with the profiles are that you cannot change all config fields by hand afterwards. A profile is not autoconfig, where you still be able to change all values afterwards.
The problems with the profiles are that you cannot change all config fields by hand afterwards. A profile is not autoconfig, where you still be able to change all values afterwards.
http://features.cpanel.net/responses/unify-imap-folder-usage-between-webmail-clients-and-popular-desktop-clients
I though it was a missing INBOX path. The assignment of all default folders to enable user to sent emails is a pain. Dovecot is supporting special folders.
namespace inbox {
#mailbox name {
# auto=create will automatically create this mailbox.
# auto=subscribe will both create and subscribe to the mailbox.
#auto = no
# Space separated list of IMAP SPECIAL-USE attributes as specified by
# RFC 6154: \All \Archive \Drafts \Flagged \Junk \Sent \Trash
#special_use =
#}
# These mailboxes are widely used and could perhaps be created automatically:
mailbox Drafts {
special_use = \Drafts
# Tachtler
auto = subscribe
}
mailbox Junk {
special_use = \Junk
# Tachtler
auto = subscribe
}
mailbox Trash {
special_use = \Trash
# Tachtler
auto = subscribe
}
# For \Sent mailboxes there are two widely used names. We'll mark both of
# them as \Sent. User typically deletes one of them if duplicates are created.
mailbox Sent {
special_use = \Sent
# Tachtler
auto = subscribe
}
mailbox "Sent Messages" {
special_use = \Sent
}
# If you have a virtual "All messages" mailbox:
#mailbox virtual/All {
# special_use = \All
#}
# If you have a virtual "Flagged" mailbox:
#mailbox virtual/Flagged {
# special_use = \Flagged
#}
}
http://features.cpanel.net/responses/unify-imap-folder-usage-between-webmail-clients-and-popular-desktop-clients
I though it was a missing INBOX path. The assignment of all default folders to enable user to sent emails is a pain. Dovecot is supporting special folders.
namespace inbox {
#mailbox name {
# auto=create will automatically create this mailbox.
# auto=subscribe will both create and subscribe to the mailbox.
#auto = no
# Space separated list of IMAP SPECIAL-USE attributes as specified by
# RFC 6154: \All \Archive \Drafts \Flagged \Junk \Sent \Trash
#special_use =
#}
# These mailboxes are widely used and could perhaps be created automatically:
mailbox Drafts {
special_use = \Drafts
# Tachtler
auto = subscribe
}
mailbox Junk {
special_use = \Junk
# Tachtler
auto = subscribe
}
mailbox Trash {
special_use = \Trash
# Tachtler
auto = subscribe
}
# For \Sent mailboxes there are two widely used names. We'll mark both of
# them as \Sent. User typically deletes one of them if duplicates are created.
mailbox Sent {
special_use = \Sent
# Tachtler
auto = subscribe
}
mailbox "Sent Messages" {
special_use = \Sent
}
# If you have a virtual "All messages" mailbox:
#mailbox virtual/All {
# special_use = \All
#}
# If you have a virtual "Flagged" mailbox:
#mailbox virtual/Flagged {
# special_use = \Flagged
#}
}
The last post fixes the situation with iOS, OSX, Thunderbird and most intelligent email clients! However Microsoft Outlook is still far from working fine.
Thank you!
The last post fixes the situation with iOS, OSX, Thunderbird and most intelligent email clients! However Microsoft Outlook is still far from working fine.
Thank you!
IT'S URGENT!!! also for Android and Windows Phone.
IT'S URGENT!!! also for Android and Windows Phone.
This is scheduled for inclusion in 11.48 as part of case 121309
This is now available in 11.48+
This is scheduled for inclusion in 11.48 as part of case 121309
This is now available in 11.48+
When is 11.48 going to be released? We're running stable and its still at 11.46
When is 11.48 going to be released? We're running stable and its still at 11.46
BTW, this is STILL broken in 11.48.. We have tested this and it's only half working and putting in a ticket has yielded ZERO fixes or work-arounds. Also, autodiscover for Outlook is half-baked because you can't disable it on a per-domain basis which causes MAJOR issues with remote Exchange and Outlook clients.
BTW, this is STILL broken in 11.48.. We have tested this and it's only half working and putting in a ticket has yielded ZERO fixes or work-arounds. Also, autodiscover for Outlook is half-baked because you can't disable it on a per-domain basis which causes MAJOR issues with remote Exchange and Outlook clients.
Replies have been locked on this page!