https://wiki.xmission.com/api.php?action=feedcontributions&feedformat=atom&user=John 2026-04-11T08:56:28Z User contributions MediaWiki 1.43.1 https://wiki.xmission.com/index.php?title=Hosted_Email:MacMail_16.x&diff=11236 2022-07-22T22:01:08Z

<p>John: /* Adding a New Account */</p> <hr /> <div>== Mac Mail v. 16.x ==<br /> <br /> === Adding a New Account === <br /> <br /> On your mac you want to click on your apple and choose '''System Preferences'''<br /> <br /> NOTE: This shows configurations for customers with XMission's Zimbra Personal email accounts. Configuration is similar for hosted business domain email services, simply replace the username with your full business email address. <br /> <br /> {| <br /> |-<br /> |style=&quot;vertical-align: top; padding: 10px;&quot; | <br /> * Click on Internet Accounts <br /> |style=&quot;vertical-align: top; padding: 10px;&quot; | <br /> * Click on Add Other Account... <br /> |style=&quot;vertical-align: top; padding: 10px;&quot; | <br /> * Finally Click on Mail Account<br /> |-<br /> |style=&quot;vertical-align: top; padding: 10px;&quot; | [[File:SystemPreferences.jpg|300px]] <br /> |style=&quot;vertical-align: top; padding: 10px;&quot; | [[File:InternetAccounts-Add.jpg|300px]] <br /> |style=&quot;vertical-align: top; padding: 10px;&quot; | [[File:InternetAccount-Add-MailAccount.jpg|300px]] <br /> |-<br /> |style=&quot;vertical-align: top; padding: 10px;&quot; |<br /> * Fill in Name, Email Address and Password<br /> * Click on Sign In<br /> |style=&quot;vertical-align: top; padding: 10px;&quot; |<br /> * Make sure all fields are entered<br /> * Account Type: IMAP<br /> * Incoming Mail Server: '''zimbra.xmission.com'''<br /> * Outgoing Mail Server: '''zimbra.xmission.com'''<br /> * Click Sign in<br /> |style=&quot;vertical-align: top; padding: 10px;&quot; |<br /> * Finally make sure Mail is checked<br /> * Click on Done<br /> |-<br /> | style=&quot;vertical-align: top; padding: 10px;&quot; | [[File:EmailSetup-1.jpg|300px]] <br /> | style=&quot;vertical-align: top; padding: 10px;&quot; | [[File:ZPPEmailAdd.jpg|300px]] <br /> | style=&quot;vertical-align: top; padding: 10px;&quot; | [[File:EmailSetup-3.jpg|300px]]<br /> |}<br /> <br /> <br /> * Once you have filled out the information to add an account though Internet Accounts, you can then open your Mail application and your email will automatically setup.<br /> <br /> === Edit an Existing Account === <br /> <br /> * If you already have an email account setup on Mac Mail and you just need to update a password that you recently changed. Follow the steps below: <br /> * Be sure to close out of Mac Mail completely by clicking on the icon and choose Quit<br /> <br /> <br /> <br /> ==== Update Internet Accounts ====<br /> * We want to update your password in Internet Accounts first<br /> <br /> {|<br /> |-<br /> | style=&quot;vertical-align: top; padding: 10px;&quot; | <br /> * Click on your Apple and choose System Preferences<br /> * Then choose Internet Accounts<br /> | style=&quot;vertical-align: top; padding: 10px;&quot; | <br /> * Choose your XMission account on the Left<br /> * Update your Password on the right<br /> * Click on the red circle to save and close<br /> |-<br /> | style=&quot;vertical-align: top; padding: 10px;&quot; | [[File:SystemPreferences.jpg|300px]]<br /> | style=&quot;vertical-align: top; padding: 10px;&quot; | [[File:EditInternetAccounts.jpg|300px]]<br /> |}<br /> <br /> <br /> ==== Update Mac Mail Application ====<br /> * After you have updated Internet accounts we can then navigate to your Mac Mail application and update the password there.<br /> * Open your Mac Mail application by clicking on the mail envelope in your dock. <br /> <br /> {|<br /> | style=&quot;vertical-align: top; padding: 10px;&quot; | <br /> * With your Mail App Open Click on your Apple <br /> * Click on Preferences <br /> <br /> | style=&quot;vertical-align: top; padding: 10px;&quot; |<br /> * Next Make sure Accounts is highlighted at the top<br /> * Click on your XMission account on the left<br /> * Click on the '''Server Settings''' Tab<br /> * Update your Password in Incoming/Outgoing <br /> <br /> | style=&quot;vertical-align: top; padding: 10px;&quot; | <br /> * Uncheck the box that says: Automatically manage connection Settings<br /> * This will allow you to update the port information if needed <br /> * You can also make sure SSL is turned on<br /> <br /> |-<br /> | style=&quot;vertical-align: top; padding: 10px;&quot; | [[File:EditMail-1.jpg]] <br /> | style=&quot;vertical-align: top; padding: 10px;&quot; | [[File:ZPPEditMail-2.jpg|300px]] <br /> | style=&quot;vertical-align: top; padding: 10px;&quot; | [[File:ZPPEditMail-3.jpg|300px]]<br /> <br /> |}<br /> <br /> * Once you have updated all your settings you can click on the red circle to make sure your settings have taken effect.<br /> <br /> [[Category: Troubleshooting]]</div>

John https://wiki.xmission.com/index.php?title=Compromised&diff=11024 2022-05-26T19:57:52Z

<p>John: /* Password Criteria &amp; Guidelines */</p> <hr /> <div>XMission email and how to tell what is going on with your mailbox.<br /> <br /> ==Traditional XMission.com email==<br /> <br /> When you try to log into https://webmail.xmission.com do you get something like this?&lt;br&gt;<br /> [[File:Compromised-1.png]]<br /> <br /> If so, your account may have been compromised and you will need to call Technical Support. <br /> <br /> <br /> ==Hosted Zimbra business email==<br /> <br /> This area explains what happens to hosted Zimbra mailboxes that have been locked due to abuse: https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Mailbox_locked_for_abuse<br /> <br /> <br /> == How mailboxes are locked for abuse==<br /> <br /> Let's take a look and find out what how this may have happened.<br /> <br /> Hackers want access to anything they can get their hands on, including your email! Your account can be abused to send out spam email. <br /> <br /> This abuse can be due to any of the following reasons;<br /> * Successfully compromised by a phishing attempt and shared their password with someone they shouldn't have.<br /> * Use of a previously compromised password on another Internet site or service.<br /> * Malware on a computer or device.<br /> * Rootkit on the computer.<br /> <br /> ==Lets take a look at what makes a bad password==<br /> #Do not use only letters or numbers<br /> #Do not use names of your family members, significant others, or pets<br /> #Do not use your phone number, birthdates or Social Security numbers<br /> #Do not use incorporate your username or name of the service provider<br /> #Do not use any words that can easily be found in a dictionary<br /> <br /> <br /> ==Password Criteria &amp; Guidelines==<br /> <br /> #Passwords must be between 8 and 128 characters in length and are case-sensitive. <br /> #Passwords must contain a minimum of 1 upper case letter, 1 lower case letter, a number, and symbol.<br /> # Secure passwords are long and randomized. Visit https://passwordcard.org or https://ae7.st/g/index.html for random password generators<br /> #You cannot change your password to be the same as any of your past 10 passwords.<br /> #Never re-use old passwords from other Internet sites, especially those which may have been compromised. Check here: https://haveibeenpwned.com/<br /> <br /> ==Change your password often==<br /> We know it may be hard to keep track if you have multiple passwords. However it is suggested that you change your password at least once a year. Some companies require password updates every 90 days. This is a great habit to get into. Lastly, password managers like BitWarden, KeePass, and others, make keeping your online data easier. Many have free and paid options. <br /> <br /> <br /> <br /> [http://xmission.com/password Change your Password]<br /> <br /> [[Category: Security]]<br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=Hosted_Email:_Admin_Panel&diff=11023 2022-05-26T19:56:54Z

<p>John: /* Change Password */</p> <hr /> <div>==Overview/Logging In== <br /> The Zimbra domain administration console is the browser-based user interface used to centrally manage user accounts and most settings.<br /> <br /> As a domain administrator, you will be able to create and maintain the following:<br /> <br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_an_Email_Account Email accounts]<br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_an_Alias Mailbox aliases]<br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_a_Distribution_List Distribution lists]<br /> *Resources<br /> <br /> To login to the domain administration console, go to https://zimbraadmin.xmission.com/ and login with your administrative username and password. Domain administrators can also login from the dropdown menu next to your mailbox name in the top right corner of the webmail session. Click on 'Admin Console' to proceed.<br /> <br /> ==Domain Administrator Responsibilities==<br /> <br /> It is important to understand that as domain administrators you are responsible for changing passwords, creating distribution lists, setting email forwards, managing mailboxes, training on phishing, and etc. Our support policy for email is clearly outlined at: https://xmission.com/legal_policies#emlsup We require domain administrators be added as Technical contacts on your billing account in order to receive advanced assistance from our support staff. Please keep contacts up-to-date in the [https://xmission.com/control account management portal] or contact [https://xmission.com/contact XMission Billing] for assistance.<br /> <br /> Phishing and email scams are on the rise. It is important to educate yourself and your mailbox holders on how to avoid it. Reference this guide on <br /> [https://wiki.xmission.com/Phishing_and_Email_Scams understanding phishing].<br /> <br /> ==Email Domain Health==<br /> <br /> An important part of effective business email mean protecting your domain with some simple settings to improve delivery and reduce fraud.<br /> <br /> XMission advises implementing SPF and DKIM on domains. These are two simple methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf and prevent abuse. [https://wiki.xmission.com/SPF_and_DKIM How to configure SPF and DKIM]<br /> <br /> ==About the Administrative Console==<br /> <br /> The area above the '''Content''' pane includes the '''Search''' and '''Help''' functions.<br /> <br /> '''Search''' allows you to quickly find accounts, aliases, distribution lists and resources for editing. <br /> <br /> '''Help''' utilizes Zimbra’s wiki, forums, and documentation. This is a powerful unified search to quickly find answers to common questions.<br /> <br /> [[Image:1zimbraadminpanel.png]]<br /> <br /> <br /> <br /> The '''Navigation''' pane on the left includes the following sections:<br /> <br /> *'''Home:''' At any time, clicking here will return you to the administrative Home options. <br /> <br /> *'''Manage:''' Clicking here will permit you to create and edit any accounts, aliases, distribution lists, and resources for your domain(s). <br /> <br /> *'''Help:''' utilizes Zimbra’s wiki, forums, and documentation. This is a powerful unified search to quickly find answers to common questions. <br /> <br /> [[Image:4zimbraadminpanel.png]]<br /> <br /> <br /> <br /> Alternatively, you can also click on the arrow beside the &quot;Home&quot; button. This will give you the same options listed above, as well as recent searches and the options available under &quot;Manage.&quot; In this example, the recent search was for &quot;xdesign.com.&quot;<br /> <br /> [[Image:2zimbraadminpanel.png]]<br /> <br /> <br /> <br /> Clicking on &quot;Manage&quot; either way will permit you to make changes to your existing accounts, aliases, distribution lists, and resources.<br /> <br /> *'''Accounts:''' Lists all accounts. In the Accounts folder, you create and manage end-user accounts, setting options, class of service, passwords and aliases for an account.<br /> <br /> *'''Aliases:''' Lists all aliases that have been created in Accounts. You can use the Move Alias feature from the toolbar to move an alias from one account to another.<br /> <br /> *'''Distribution Lists:''' Lists all distribution lists. You can create new distribution lists and add or delete members of a distribution list.<br /> <br /> *'''Resources:''' This lists locations or equipment that can be scheduled from your Calendar. Here is where you can create new resources and set the scheduling policy for the resource.<br /> <br /> [[Image:3zimbraadminpanel.png]]<br /> <br /> <br /> ==Creating an Email Account== <br /> Select '''Manage''' and then '''Accounts''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the email mailbox you are about to create. Enter the following required information:<br /> <br /> * '''Account Name''': This will be the mailbox account that you are about to create. In this example, we are creating &quot;bobdobbs@xdesign.com.&quot;<br /> * '''First Name''': The first name of the email user. <br /> * '''Last Name''': The last name of the email user.<br /> [[Image:1zimbraaddaccount.png]]<br /> <br /> When creating a new mailbox account you will set the Class of Service (CoS) under '''General Information / Account Setup / Class of Service'''. Don't forget to deselect the &quot;[ ] auto&quot; box to enter the class type.<br /> <br /> You may mix and match Class of Service (CoS) for mailbox accounts in your domain to maximize benefits for your organization. Details below.<br /> <br /> Something to note, XMission identifies a billable Zimbra account as mailbox with a physical email Inbox and typically belonging to one person. So even if it is not &quot;active&quot; but still provisioned, it will count toward billing. Example, a mailbox set to &quot;closed&quot; or &quot;maintenance&quot; status remains billable.<br /> <br /> ==Class of Service==<br /> <br /> To '''upgrade''' an existing account, or to change existing accounts, simply log in to the admin interface, click on '''&quot;Manage&quot;''' and select the user by double-clicking on the name. Inside the '''&quot;General Information&quot;''' pane you will see '''&quot;Account Setup&quot;''' in the middle of the page. In this area you will find '''&quot;Class of Service&quot;''' with an input box next to it and the &quot;[x] auto&quot; box checked. Deselect the &quot;[ ] auto&quot; box and type '''&quot;xmpremium&quot;''' or '''&quot;xmbase&quot;''' in the field and then hit '''&quot;Save&quot;''' towards the top right of the window. Your account is now set to the selected service level with all the features and storage associated with the account type.<br /> <br /> Click the '''&quot;Finish&quot;''' button. You will be returned to the main admin screen, and the new account will have been created at the established service level.<br /> <br /> NOTE: If the &quot;Class of Service&quot; field is not available to you, you may need to add your admin account's email address to the &quot;admins&quot; distribution list on your domain and wait up to fifteen minutes. Some older accounts do not have this setup automatically. See [https://wiki.xmission.com/Zimbra_Hosting_Admin#Granting_Domain_Administrator_Access Granting Domain Administrator Access] for more details.<br /> <br /> ==Updating Account Information==<br /> To add, change, or remove information from an account, simply double-click the account you want to edit. Alternatively, you can right-click the account you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> ==Change Password==<br /> <br /> All Zimbra domain administrator should read this quick blog post on email security: https://xmission.com/blog/2017/10/17/best-practices-for-zimbra-email-security<br /> <br /> Changing your end-user mailbox password through the Zimbra [https://zimbraadmin.xmission.com domain admin control panel] is easy, but first let's review XMission password best practices.<br /> <br /> '''XMission Zimbra Password requirements:''' <br /> <br /> XMission recommends secure passphrases consisting of five to six words, with a few special characters and numbers, since they can be much easier to remember.<br /> <br /> * Ideally it is best to use longer, more complex passphrases to properly protect your mailboxes, and your company, from hackers. Our Zimbra system supports passwords up to 128 characters. We advise using a minimum passphrase length of 12-15 characters with 25-28 characters providing very reasonable security. <br /> * Shorter passwords require use of at least 1 of the following: UPPER CASE letter, lower case letter, special characters, and a numeral to meet minimum security requirements.<br /> * Passwords expire after 1 year and must be changed at that time. Changing more frequently is advised.<br /> * You cannot re-use your current password.<br /> * Please allow 15 minutes for the new password to propagate through the system.<br /> * Write credentials down in a secure place until you memorize it then destroy the note.<br /> * Here is a quick and easy to understand visual tutorial on password security: [https://xmission.com/blog/2017/10/17/best-practices-for-zimbra-email-security | https://xkcd.com/936/ ]<br /> <br /> '''Three ways to change passwords from domain admin control panel:'''<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column. Right-mouse click on the mailbox name to reveal a drop down menu, select &quot;Change password.&quot;<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column and highlight a mailbox. Now right-mouse click on the gear icon in the top right corner. Select &quot;Change password&quot;.<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column and double click on the desired mailbox. When it opens the settings page of the mailbox use the &quot;Password&quot; area to change the password.<br /> <br /> NOTE: XMission Zimbra servers will allow a password as short as 12 characters. Short passwords are poor security. Please take the time to protect your company email data buy using a passphrase in the 25-28 character length.<br /> <br /> ==Password Expiration and Failed Login Attempts==<br /> Please note the following details about XMission's email password expiration and failed login attempts policy.<br /> <br /> Should you ever have an end-user mailbox that is not allowing login there are two primary reasons for this. <br /> * The password has expired. <br /> * There have been too many failed login attempts to the account causing it to be temporarily suspended.<br /> <br /> ==== Expired Password ====<br /> <br /> All XMission email passwords must be changed once yearly. XMission sends email notices to the user mailbox 2 (two) weeks before expiration. Please ask your mailbox owners to change their password in a timely manner.<br /> <br /> Domain administrators are *not* emailed about the user mailbox need to change their password. Repeat, domain administrators are not emailed about password expirations.<br /> <br /> ==== Failed Login Attempt - Mailbox Access Suspension ====<br /> <br /> Failed login attempt account suspension practices are a way to safeguard mailboxes from brute force attacks where a bad actor is trying to access the sensitive information inside. XMission protects customer mailboxes by temporarily suspending mail accounts with too many failed login attempts. This prevents new logins and halts all access on active mail sessions. Incoming email is not restricted.<br /> <br /> If you, or another entity, are trying to access the account with too many failed password attempts within the monitoring cycle, the system blocks access for a short period of time, after which you can again attempt to authenticate with correct credentials.<br /> <br /> '''Failed login attempt definition:''' Improper entry of a password for a valid mailbox. <br /> <br /> '''How failed login attempts are measured and enforced:''' When the first failed login attempt occurs, the monitoring cycle begins. Thereafter, each time a unique wrong password fails, that adds to the count. <br /> <br /> It is important to note that when the ''same'' wrong password is used, from any number of IP addresses or devices, it only counts as one (1) failed login attempt.<br /> <br /> During the monitoring cycle, if additional failed login attempts are made using a different password from the original attempt, it add to the failed login attempt total. IE: Bad password &quot;A&quot; activates monitoring period. A second unique password &quot;B&quot; is used bringing the total to two (2) failed attempts. If password &quot;A&quot; is used again, it counts as another new unique password totaling three (3) failed attempts. <br /> <br /> Once the maximum number of failed attempts is reached, access to the mailbox is temporarily suspended.<br /> <br /> ==== Troubleshooting ====<br /> <br /> Mailbox accounts having failed login issues appear to have the same symptoms as an expired password. The way to test is to access webmail, https://zimbra.xmission.com, with your credentials. If the password is expired it will prompt you to set a new password immediately. If the account is locked out, it will simply not validate with the credentials until the suspension period ends.<br /> <br /> If an account is temporarily suspended for too many failed password attempts you need to either wait for the suspension period to pass, reset the mailbox status to active in the domain admin panel, or contact XMission Support to have the suspension manually removed.<br /> <br /> Domain administrators can change mailbox status and passwords via the domain admin interface.<br /> <br /> NOTE: Use of Two-Factor Authentication (2FA) does not prevent account suspension due to failed authentication attempts.<br /> <br /> ==Mailbox locked for abuse==<br /> <br /> A user mailbox can also be locked for abuse. This abuse can be due to any of the following reasons;<br /> * Successfully compromised by a phishing attempt and shared their password with someone they shouldn't have.<br /> * Use of a previously compromised password on another Internet site or service.<br /> * Malware on a computer or device.<br /> * Rootkit on the computer.<br /> <br /> ''Symptoms of abuse:''<br /> <br /> Domain administrators often ask why a mailbox was locked for a spam run when they do not see evidence of malicious messages in the Sent folder. The primary reason for this is because the spammers use SMTP mail applications that do not sync the Sent mail folder. Only messages sent via the Zimbra webmail interface, via Outlook with the Zimbra Connector, or sent via ActiveSync (Exchange) configuration on mobile devices, will sync Sent messages to the mail system. So a bad actor can send copious amounts of unwanted email quickly and with no trace the end user can see. However, XMission has logs for all messages sent which we use to identify and lock accounts as well as to train system rules to prevent future abuse. <br /> <br /> Determining why a mailbox has been locked for abuse can be difficult. XMission will do their best to provide data on what was compromised and how. In some cases this is possible, in others it is not. Most often phishing and re-used passwords are the primary attack vector resulting in a locked user mailbox.<br /> <br /> &quot;The remedy:&quot;<br /> <br /> Regardless of the &quot;how&quot; all compromised mailbox users are required to change their password immediately to continue using the service. It is imperative that domain administrators do not re-use passwords or set poor temporary passwords. <br /> <br /> We strongly advise in the use of long passwords (pass phrases) and password managers such as BitWarden, Keepass, and similar.<br /> <br /> Additional compromises of the same mailbox will result in a small fine which we hope is just enough to encourage proper mailbox security. You can read about this policy here: https://xmission.com/blog/2019/05/14/our-new-compromised-email-policy<br /> <br /> ==Creating an Alias==<br /> Select '''Manage''' and then '''Aliases''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the email alias you wish to create. Enter the following required information:<br /> <br /> *'''Alias''': This is the aliased address you will create. In this example, we are adding &quot;bob.dobbs@xdesign.com.&quot; <br /> *'''Target Account''': This is the actual email box that will receive any emails directed to the aliases address. <br /> [[Image:1zimbraaddalias.png]]<br /> <br /> <br /> Click &quot;Ok&quot; to add your new alias.<br /> <br /> <br /> ==Updating Alias Information==<br /> To add, change, or remove information from an alias, simply double-click the alias you want to edit. Alternatively, you can right-click the alias you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> <br /> ==Creating a Distribution List==<br /> Select '''Manage''' and then '''Distribution Lists''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the distribution list you wish to create. Enter the following required information:<br /> <br /> * '''List Name''': This will be the email address for the mailing list. <br /> * '''Display Name''': This can be a descriptive name for the list. <br /> <br /> [[Image:1zimbraaddlist.png]]<br /> <br /> <br /> To add email addresses to the list, scroll a bit to the right and you will see a &quot;Search&quot; button below the '''Add Members to this list''' section. If you want add email addresses that are withing your Zimbra package, search for the appropriate domain name(s). In this case, we searched for &quot;xdesign.com.&quot; Highlight any results you would like to be added to the list.<br /> <br /> [[Image:1zimbraaddmembers.png]]<br /> <br /> <br /> Using the scroll bar on the right, scroll down and click the &quot;Add Selected&quot; button. <br /> <br /> [[Image:2zimbraaddmembers.png]]<br /> <br /> <br /> If you want to manually add addresses or need to add addresses that are not within Zimbra's search function, you can type the email addresses in the box pictured below. In this case, we are adding two email addresses to the list -- &quot;bobdobbs@gmail.com&quot; and &quot;bigguyjake@xmission.com.&quot; Once you've typed in the email addresses you want added to your list, simply click the &quot;Add&quot; button below. <br /> <br /> [[Image:3zimbraaddmembers.png]]<br /> <br /> <br /> ''Notes:''<br /> <br /> You can make lists members of other lists. This is a handy way to create umbrella lists. For example, if you wanted a staff list, but had various departments, you could add your employees to the departmental list, and then subscribe the departmental lists to the staff lists. This way, an account is only entered once, rather than adding an account to each list individually.<br /> <br /> Distribution Lists can also be used to forward domain based emails. For example, you may need to forward ''project@yourdomain.com'' to ''address@someotherdomain.com''. This does not require a Zimbra account for the primary domain email address.<br /> <br /> <br /> ==Updating Distribution List information==<br /> To add, change, or remove information from a list, simply double-click the list you want to edit. Alternatively, you can right-click the list you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> <br /> ==Forwarding Email to Another Address==<br /> If you wish to forward emails sent to your hosted email to another email address, first select '''Manage''' and then '''Accounts.''' Double-click the account you wish to edit or right-click and choose '''Edit''' from the pop-up menu. <br /> <br /> To add a forward, click on the '''Forwarding''' section on the left-hand column. <br /> <br /> [[Image:1zimbraforward.png]]<br /> <br /> <br /> Enter the following required information:<br /> <br /> * '''User-specified forwarding address''': This will be the email account that emails are forwarded to that the account owner is aware of. In the example below, we will be forwarding emails to &quot;bob.dobbs@xmission.com.&quot; <br /> <br /> [[Image:2zimbraforward.png]]<br /> <br /> <br /> Don't forget to choose &quot;Save&quot; near the upper right hand corner after you've added the forwarding address!<br /> <br /> <br /> * '''Forwarding addresses hidden from the user''': This can be a list of email accounts that emails are forwarded to that the account owner is unaware of. To do this, first click the &quot;Add&quot; button located below the '''Forwarding addresses hidden from the user''' box. It will prompt you to enter an email address. After you've done so, simply click &quot;Ok.&quot; In the example below, we will be forwarding messages to &quot;bobdobbs@xmission.com.&quot;<br /> <br /> [[Image:3zimbraforward.png]]<br /> <br /> NOTE: You may also use Distribution Lists to forward domain based emails without needing an account for the specific address. For example, you may need to forward ''project@mydomain.com'' to ''johndoe@someotheremail.com''. The advantage of using a Distribution List is that you eliminate the costs associated with maintaining an account just for forwarding.<br /> <br /> ==Granting Domain Administrator Access==<br /> <br /> To grant an existing mailbox domain administrator privileges start by logging in to the admin interface. Next, select their account then double click to edit. Inside the General Information area, the second category down is &quot;Account Setup.&quot; Check the &quot;Administrator&quot; checkbox below &quot;Class of Service.&quot; Once checked, a field will appear below, &quot;Administrator role.&quot; Enter &quot;admins@yourdomain.com&quot;, replacing yourdomain.com with the domain you are granting access rights for. This will add the user to a distribution list, &quot;admins&quot;, on your domain, which grants the privileges.<br /> <br /> Click &quot;Save&quot; near top-right corner to complete the assignment of rights.<br /> <br /> Note that if the &quot;Administrator&quot; checkbox does not exist, you may need to add yourself to the &quot;admins&quot; distribution list manually and wait up to fifteen minutes.<br /> <br /> ==Importing Accounts from Exchange==<br /> <br /> This article has moved: https://wiki.xmission.com/Zimbra_Migration:_Exchange_Import_Wizard<br /> <br /> ==Deleting a Zimbra Mailbox==<br /> <br /> There are two fairly simple ways to properly delete a Zimbra mailbox from the XMission system. <br /> <br /> * Log into the Zimbra domain administration panel https://zimbraadmin.xmission.com and select the &quot;Manage&quot; area on the left. Once in the management area you simply highlight the mailbox and then right-mouse click to show the option menu. Select &quot;Delete&quot; and confirm the mailbox deletion request. <br /> <br /> * From inside the domain administration panel you may also highlight the mailbox name and then click on the gear wheel in the top right corner of the browser screen to display an options menu. Inside this menu select &quot;Delete&quot; and confirm the deletion request.<br /> <br /> Notes: <br /> * Changing mailbox status is not the same as deletion. All provisioned mailboxes are billable.<br /> * Deletion of a mail domain cannot be completed via the domain admin interface and requires contacting XMission billing department.<br /> * Be certain not to delete resource accounts such as galsync or distribution lists unless you know they are no longer needed. Doing so can impact mail performance.<br /> <br /> == Zimbra Themes ==<br /> <br /> You can see all the themes [https://wiki.xmission.com/Hosted_Email:_Admin_Panel/Zimbra_Themes here]<br /> <br /> <br /> [[Category:Zimbra|Admin Panel]]<br /> <br /> <br /> {{footer}}</div>

John https://wiki.xmission.com/index.php?title=Zimbra_Basics&diff=11022 2022-05-26T19:56:29Z

<p>John: /* Change Password */</p> <hr /> <div>==Overview/Logging In== <br /> The Zimbra user interface is a browser-based utility that allows you to manage not only your email but the many collaborative tools available for your use. <br /> <br /> To login to the Zimbra webmail interface, go to https://zimbra.xmission.com and login with your full email address and password. <br /> <br /> The application tabs near the top of your screen indicate what areas of Zimbra you will be working with. '''Please note that only customers who have purchased Premium Hosted Email will see and be able to utilize all the application tabs.''' If you find that one of these application tabs is missing and would like to have it available, consider upgrading to a higher level of service! For more information, please contact our sales team. <br /> <br /> The different application tabs have different features and tools available. They are as follows:<br /> <br /> *'''Mail''': Compose, delete, and manage your email.<br /> *'''Contacts''': Create, remove, share, and manage contacts for your email.<br /> *'''Calendar''': Create, remove, share, and manage deadlines, appointments, meetings, etc...(Only available in '''Standard''' and '''Premium''' packages)<br /> *'''Tasks''': Create, remove, share, and manage tasks, including task or project priorities and progress. (Only available in '''Standard''' and '''Premium''' packages)<br /> *'''Briefcase''': Create, remove, share, and manage items saved to your briefcase. (Only available in '''Standard''' and '''Premium''' packages)<br /> *'''Preferences''': Manage your user preferences.<br /> <br /> [[Image:1zimbratabs.png]]<br /> <br /> ==Change Password==<br /> <br /> Changing your password through the Zimbra webmail interface is easy and we will show you how below. First, take a few seconds to read about password best practices.<br /> <br /> <br /> '''Password requirements:''' <br /> <br /> This blog post on email and password security is extremely informational: https://xmission.com/blog/2017/10/17/best-practices-for-zimbra-email-security<br /> <br /> XMission recommends using secure passphrases consisting of multiple words and special characters since they can be much easier to remember.<br /> <br /> * Ideally it is best to use longer, more complex pass phrases to properly protect yourself, and your company, from hackers. Our Zimbra system supports passwords up to 128 characters. We request a minimum password length of 12-15 characters. <br /> * Shorter passwords require use of at least 1 of the following: UPPER CASE letter, lower case letter, special characters, and a numeral to meet minimum security requirements.<br /> * Passwords expire after 1 year and must be changed at that time. Changing more frequently is advised.<br /> * You can never re-use your current password.<br /> * Please allow 15 minutes for your new password to propagate through the system.<br /> * Write your password down in a secure location until you memorize it then destroy the note.<br /> <br /> <br /> XMission Personal Premium accounts must change their password here: https://xmission.com/password<br /> <br /> <br /> '''How to change your password in Zimbra webmail:'''<br /> <br /> * Click the ''Preferences'' tab.<br /> * Ensure ''General'' is selected in the left-hand column.<br /> * Click the ''Change Password'' button.<br /> <br /> [[Image:1zimbrachangepwd.png]]<br /> <br /> <br /> * Complete the fields in the pop-up window and click ''Change password'' to complete.<br /> <br /> Contact your Domain Administrator as they can perform password changes. XMission will not change end user mailbox passwords. <br /> [[File:Zimbra_changePassword_2.png]]<br /> <br /> ==Quota==<br /> <br /> Near the upper-right corner of your window and to the right of the '''Search''' field, you will see your &quot;Display Name&quot; and a bar beneath. This bar will fill up and change color as your storage increases. <br /> <br /> [[Image:1zimbraquota1.png]]<br /> <br /> For more detailed information on your quota, simply hover your mouse cursor over your name and a window will pop up with detailed information regarding your account quota. <br /> <br /> [[Image:1zimbraquota2.png]]<br /> <br /> Zimbra quota measured as follows: 1 GB = 1024 MB<br /> <br /> ==System Limits==<br /> <br /> XMission provide hosted Zimbra for business email needs. Certain limits apply per organization, domain, and user level.<br /> <br /> * Recipients addressed per hosted email domain per day <br /> ** 100,000 recipients external to the organization, with no hard quota on recipients internal to the organization <br /> ** XMission Hosted Zimbra business email service is not intended for bulk email services. <br /> <br /> * Maximum size of any hosted Zimbra mailbox<br /> ** 50 GB (51,200 MB)<br /> ** This is a hard quota and cannot be changed.<br /> <br /> * Maximum aliases <br /> ** 50 aliases per user level mailbox<br /> ** There is no limit to suffix-support mailbox aliases user+suffix@example.com<br /> ** 10 domain aliases per organization domain<br /> <br /> * Recipients addressed per user per day using on business domain <br /> ** 5,000 recipients external to the organization<br /> ** Internal domain email unlimited <br /> <br /> * Number of recipients per message<br /> ** 500 - hard coded limit<br /> ** Bulk mailing should use external service<br /> <br /> ==Dragging and Dropping==<br /> <br /> A powerful feature of the Zimbra user interface is the ability to &quot;drag and drop&quot; items. Not only can tags, contacts, and emails be dragged and dropped for easy organization, but you will find many features of Zimbra can be moved around via &quot;dragging&quot; and &quot;dropping.&quot; For example, you can drag-and-drop emails into different folders, drag tags onto emails or contacts for easy filtering, or even drag and drop folders into other folders. <br /> <br /> To drag an item, hold down the left mouse button on the item you wish to move. Then, move the mouse while continuing to hold down the left mouse button. When you wish to drop the item, release the left-mouse button. <br /> <br /> Another powerful feature of the Zimbra user interface worth mentioning is multiple selections. You can often select multiples of items you wish to move or be tagged by simply playing a checkmark beside each item you want in your selection. Alternatively, you can even select multiple items by holding down your shift key, using your arrow keys to select anything in the list, and releasing the shift key to complete your selection. These selections can then be moved in giant &quot;clumps,&quot; saving you time and energy and helping you to quickly organize items in exactly the way you want them. <br /> <br /> ==Mail==<br /> <br /> ===Managing your Inbox===<br /> Video about managing your Inbox: https://help.zimbra.com/videos/8x/Managing_Your_Inbox.mp4<br /> <br /> ===Compose email===<br /> <br /> It is very easy to create and compose a new email from within the Zimbra webmail interface. From within the Mail tab you can click on the &quot;'''New Message'''&quot; button in the left column. There are also several handy keyboard shortcuts that can be utilized to initiate a new email. The options are; ''''c'''' for compose new, ''''C'''' to compose in an external browser window, ''''nm'''' for new message, ''''r'''' for reply, and ''''a'''' for reply-all.<br /> <br /> Video on how to compose email from within Zimbra webmail: https://help.zimbra.com/videos/8x/Compose_an_Email.mp4<br /> <br /> ===Viewing===<br /> <br /> Zimbra webmail offers multiple viewing options. To access these, cllick the '''View''' pull-down menu near the upper-right corner of your window. <br /> <br /> You can choose to view '''By Conversation''' or '''By Message'''. Most prefer the conversation view as it groups email conversations together.<br /> <br /> Zimbra also provides options on how email appears in the web browser. Choose from '''Reading Pane At The Bottom''', '''Reading Pane On The Right''', or '''Reading Pane Off'''. We suggest you try all 3 to see which option best meets your needs. <br /> <br /> ''TIP'': '''Reading Pane On The Right''' gives the look and feel of the Outlook mail client.<br /> <br /> [[Image:1zimbramessageoptions.png]]<br /> <br /> Zimbra video on Message Views: https://help.zimbra.com/videos/8x/Conversation_View.mp4<br /> <br /> &lt;!-- ===Viewing External Email===<br /> <br /> Zimbra allows you to check all your email account through the web interface. Check them separately or create a &quot;universal inbox&quot; for all accounts.<br /> <br /> To set up your external account you need the following details:<br /> <br /> * '''Account type''' IMAP or POP - This is the type of email the service provider uses, IMAP is best.<br /> <br /> * &quot;''Username''' Typically the username is the part before the &quot;@&quot; or it can be the full email address. (example, &quot;sales&quot; or &quot;sales@xmission.com&quot;)<br /> <br /> * '''Email server''' This is the server name for your external account. (example, mroute01.xmission.com)<br /> <br /> * '''Advanced settings''' Your provider should let you know if they do not use standard IMAP (143) or POP (110) port. Please enable &quot;Use an encrypted connection ( SSL) when accessing this server&quot; to secure your email transactions with the external server. The port numbers will change.<br /> <br /> <br /> '''Receiving external messages to your account'''<br /> <br /> When you retrieve your external email messages, the messages and attachments are saved to the folder you specified when you configured your account information.<br /> <br /> Messages from your external accounts have to be checked manually. Messages are not automatically received in the Zimbra web client.<br /> <br /> If you configured the Inbox to be the folder to save the external account's messages, click Get Mail on the toolbar. Your Inbox folder is updated with all new messages including messages from your external accounts. NOTE: Only POP email accounts can be set for viewing in your Inbox folder.<br /> <br /> If you configured another folder for your external accounts, select that folder and click the Get Mail button from the toolbar. Messages are delivered to your folder. Click Refresh to see the latest messages.<br /> <br /> NOTE: If accessing a standard (ie non-Zimbra) xmisison.com mail account, use mroute01.xmission.com as the email server, rather than mail.xmission.com. --&gt;<br /> <br /> ===Tagging===<br /> <br /> Tagging allows you to quickly filter your mail, contacts, tasks, and documents according to your own parameters. <br /> <br /> You can create up to seven different colored tags to help you organize your email, contacts, tasks, and documents. To create a new tag, simply click on the '''gear icon''' [[Image:Gear_icon.png]] near the upper-right corner of '''Tags''' heading and then click '''New Tag'''. <br /> <br /> [[Image:1zimbratag1.png]]<br /> <br /> Alternatively, you can right-click in the '''Tags''' section in the left-hand column and select &lt;span class=&quot;button&quot;&gt;New Tag&lt;/span&gt; and then complete the following: <br /> <br /> *'''Tag Name''': This is a description of the tag.<br /> *'''Color''': Using the pull-down menu, select the color you want associated with this tag. <br /> <br /> [[Image:1zimbratag2.png]]<br /> <br /> To finish, click &lt;span class=&quot;button&quot;&gt;Ok&lt;/span&gt;.<br /> <br /> You will now see the named tag you created beneath the '''Tags''' section in the left-hand column. To tag an email, simply drag the tag from the '''Tags''' section and drop it on the email you would like to tag.<br /> <br /> You can even tag multiple messages at once. Just drag your selection of messages to the tag in the left-hand column, and the messages will be tagged accordingly. <br /> <br /> Alternatively, you can tag an email by selecting the tag icon from the mail application toolbar. <br /> <br /> Tagging is an extremely versatile tool for filtering your email. Once you have tagged a message or messages, you can filter to see only those tagged messages by clicking on the corresponding tag(s) under the '''Tags''' heading. This will show all messages you have tagged throughout all folders. You can even assign multiple tags to the same item! <br /> <br /> For example, you may wish to create a tag for &quot;Friends&quot; and a contact for &quot;Co-workers.&quot; Alternatively, you may wish to create a tag for &quot;High Priority&quot; and &quot;Low Priority.&quot; Ultimately, the possibilities of tagging are limitless and can be created to suit virtually any need.<br /> <br /> ===Searching===<br /> You can quickly search for an email or emails by typing in any text in the search field and clicking the '''Search''' icon [[Image:1search_icon.png]]. Be sure the pull-down menu beside the text field is set to '''Mail'''. <br /> <br /> [[Image:1zimbrasearch.png]]<br /> <br /> Simple searches can be done by just entering a word into the search field. <br /> <br /> More advanced searches can be done by specifying a search operator. A search operator is a special keyword followed by a colon, followed by some other parameter specific to that operator. For example:<br /> <br /> * '''in:inbox''': The operator is &quot;in&quot; and the parameter is &quot;inbox&quot; - this returns messages which are in the folder named &quot;inbox&quot;<br /> * '''from:someone''': The operator is &quot;from&quot; and the parameter is &quot;someone&quot; - this returns messages which have the word &quot;someone&quot; in their email address <br /> <br /> Let's say you wanted to find a particular image your grandmother sent you, but you can't find the email in your inbox. To run a search that would essentially &quot;find all messages from your grandmother that are in your inbox and have an attachment&quot; you would run a search like this: &quot;in:inbox from:grandma@internet.com has:attachment&quot;<br /> <br /> You can prefix any keyword with the word &quot;not&quot; to specify items that do not have that criterion -- for example not in:inbox. Search is case insensitive, meaning that &quot;in:inbox&quot; is the same as &quot;in:Inbox&quot;. <br /> <br /> The following is a list of common search operators:<br /> <br /> *'''content''': Specifies text that the message must contain. For example, content:bananas finds all items containing the word &quot;bananas&quot;.<br /> *'''from''': Specifies a sender name or email address that is in the From header. This can be text, as in &quot;John Smith III&quot;, an email address such as &quot;joe@acme.com&quot;, or a domain such as &quot;@zimbra.com&quot;.<br /> *'''to''': Same as from: except that it specifies one of the people to whom the email was addressed in the To: header.<br /> *'''cc''': Same as from: except that it specifies a recipient in the Cc: header of the message.<br /> *'''subject''': Specifies text that must appear in the subject header of the message. An example might be subject:&quot;new vacation policy&quot;. Use quotes to search for exact match.<br /> *'''in''': Specifies a folder. For example, in:sent would show all items in your 'Sent' folder.<br /> *'''has''': Specifies an attribute that the message must have. The types of object you can specify are &quot;attachment&quot;, &quot;phone&quot;, or &quot;url&quot;. For example, has:attachment would find all messages which contain one or more attachments of any type.<br /> *'''filename''': Specifies an attachment file name. For example, filename:query.txt would find messages with a file attachment named &quot;query.txt&quot;.<br /> *'''type''': Specifies a search within attachments of a specified type. The types of attachment you can specify are &quot;text&quot;, &quot;word&quot;, &quot;excel&quot;, and &quot;pdf&quot;. For example, type:word &quot;hello&quot; finds messages with attachments that are Microsoft Word documents and searches within those attachments for the word &quot;hello&quot;.<br /> *'''attachment''': Specifies any item with a certain type of attachment. For example, attachment:word would find all messages with Word attachments.<br /> *'''is''': Searches for messages with a certain status - for example, is: unread will find all unread messages. Allowable values are &quot;unread&quot;, &quot;read&quot;, &quot;flagged&quot;, &quot;unflagged&quot;, &quot;sent&quot;, &quot;draft&quot;, &quot;received&quot;, &quot;replied&quot;, &quot;unreplied&quot;, &quot;forwarded&quot;, unforwarded&quot;, &quot;anywhere&quot;, &quot;remote&quot; (in a shared folder), &quot;local&quot;, &quot;sent&quot;, &quot;invite&quot;, &quot;solo&quot; (no other messages in conversation), &quot;tome&quot;, &quot;fromme&quot;, &quot;ccme&quot;, &quot;tofromme&quot;. &quot;fromccme&quot;, &quot;tofromccme&quot; (to, from cc me, including my aliases)<br /> *'''date''': Use this keyword to specify a date, using the format that is default for your browser's locale (for US English the format is mm/dd/yyyy). For example, date:2/1/2007 would find messages dated February 1, 2007. The greater than (&gt;) or less than (&lt;) symbols can be used instead of after or before. &gt;= and &lt;= are also allowed.<br /> *'''after''': Specifies mail sent after a certain date. For example, after:2/1/2007 specifies mail sent after February 1, 2007.<br /> *'''before''': Same as after: except specifies mail sent before the specified date.<br /> *'''size''': Specifies messages whose total size, including attachments, is a specified number of bytes, kilobytes, or megabytes For example, size:12 kb would find messages that are exactly 12K in size. The greater than (&gt;) or less than (&lt;) symbols can be used instead of bigger or smaller.<br /> *'''larger''': Similar to size: except specifies greater than the specified size.<br /> *'''smaller''': Similar to size: except specifies smaller than the specified size.<br /> *'''tag''': Finds messages which have been tagged with a specified tag. For example, tag:amber will find message that have a tag called &quot;amber&quot; applied. <br /> <br /> The asterisk (*) can be used as a wildcard in a search to find content that contains words that have similar spellings.<br /> <br /> Use the asterisk * as a wildcard after a prefix. For example, the search string '''do*''' returns items such as do, dog, door, etc....<br /> <br /> Your searches can even be saved! To save a search, first run your search and then simply click &lt;span class=&quot;button&quot;&gt;Save&lt;/span&gt; on the search bar. <br /> <br /> [[Image:1zimbrasearch2.png]]<br /> <br /> You will be prompted to give your search a name. Once you've named your search, you can look up saved searches in the advanced search mode and quickly run them. For example, let's say you often need to find emails you've exchanged with your grandmother. You would type &quot;from:grandma@internet.com&quot; in the search field, and click &lt;span class=&quot;button&quot;&gt;Save&lt;/span&gt;. You could name your search &quot;Grandma's Emails&quot; and quickly run that search whenever you like from the Advanced Search menu!<br /> <br /> Video on Zimbra Search: https://help.zimbra.com/videos/8x/Searching_in_Zimbra.mp4<br /> <br /> ===Folders===<br /> Creating new folders with the Zimbra user interface is easy. If you wish to create a a folder, simply click on the '''gear icon''' [[Image:Gear_icon.png]] near the upper-right corner of the left-hand column and then click '''New Folder'''. <br /> <br /> [[Image:1zimbrafolder1.png]]<br /> <br /> Alternatively, you can right click on the folder heading or any folder and choose '''New Folder'''. You will then be prompted to name your new folder. Once named, the folder will now be displayed along with your other folders in the left-hand column. <br /> <br /> [[Image:1zimbrafolder2.png]]<br /> <br /> Once you have created a new folder, you may move the folder around by simply dragging and dropping it on the location you'd like it to be. <br /> <br /> If you would like to rename, delete, or share a folder, simply right-click on that folder and choose the appropriate option from the pop-up menu.<br /> <br /> ==Address Book==<br /> ===Adding Contacts===<br /> There are a few ways to add a new contact to your Contacts. <br /> <br /> If you receive an email from someone you'd like to add as a contact, simply right-click on the email and choose &lt;span class=&quot;button&quot;&gt;Add to Contacts&lt;/span&gt; from the pop-up menu. <br /> <br /> [[Image:1zimbracontact1.png]]<br /> <br /> This will automatically bring you to the contact creation screen, where you can define more information for the contact if you wish. Once you are happy with the contact info you've entered, click &lt;span class=&quot;button&quot;&gt;Save&lt;/span&gt; near the upper left corner of the window. You will see a box that says '''Contact Created'''. <br /> <br /> If you'd like to create a contact from scratch, click on the '''Contacts''' tab near the top of your screen and click &lt;span class=&quot;button&quot;&gt;New Contact&lt;/span&gt;. <br /> <br /> [[Image:1zimbracontact2.png]]<br /> <br /> This will also present you with the contact creation screen. Enter all the information you would like, and then choose &lt;span class=&quot;button&quot;&gt;Save&lt;/span&gt; near the upper left corner of the window. You will see a box that says '''Contact Created'''.<br /> <br /> Video on creating and managing Contacts in Zimbra: http://help.zimbra.com/videos/8x/Contacts.mp4<br /> <br /> ====Contact Groups====<br /> <br /> Within your Contacts, you're not limited to single contacts. You can create multiple '''Contact Groups''' to help you keep organized. <br /> <br /> For example, suppose some fellow coworkers and/or friends wanted to form a Book Club. These people are all in your Contacts, but you want to more easily find and email them. You would create a new '''Contact Group.'''<br /> <br /> To create a new '''Contact Group''', ensure you have selected the '''Contacts''' tab and click the arrow beside '''New Contact''' to open a new menu. Then, simply click '''New Contact Group'''. <br /> <br /> [[Image:1zimbracontgroup1.png]]<br /> <br /> Simply complete the following:<br /> <br /> *'''Group Name''': The name of your new contact group. In this example, our Contact Group would be named &quot;Book Club.&quot; <br /> *'''Group Members''': You can search for individuals to add in the right-hand column Search field or add members immediately from your domain by selecting one ore more of them and clicking &lt;span class=&quot;button&quot;&gt;Add&lt;/span&gt;. Alternatively, if you wanted to add everyone in the right-hand column, you could just click &lt;span class=&quot;button&quot;&gt;Add All&lt;/span&gt;.<br /> <br /> [[Image:1zimbracontgroup2.png]]<br /> <br /> You can also manually add email addresses using the box near the bottom right hand corner. Simply type the email address(es) you want to add, separate them with a comma, and click &quot;Add.&quot; <br /> <br /> [[Image:1zimbracontgroup3.png]]<br /> <br /> Once you have all the members you want in your new '''Contact Group''' simply click &lt;span class=&quot;button&quot;&gt;Save&lt;/span&gt; along the application toolbar near the top.<br /> <br /> If you want to remove a member from your '''Contact Group''' simply click the red &quot;X&quot; alongside the contact's name. <br /> <br /> [[Image:1zimbracontgroup4.png]]<br /> <br /> Remember to click &lt;span class=&quot;button&quot;&gt;Save&lt;/span&gt; along the application toolbar near the top to apply your changes!<br /> <br /> Video on creating a personal Contact Group in Zimbra: http://help.zimbra.com/videos/8x/Create_a_Contact_Group.mp4<br /> <br /> ===Searching Contacts===<br /> You can quickly search for a contact or contacts by typing in any text in the search field and clicking the '''Search''' icon [[Image:1search_icon.png]]. Be sure the pull-down menu beside the text field is set to '''Contacts'''.<br /> <br /> [[Image:1zimbrasearchcontacts.png]]<br /> <br /> ===Additional Address Books (Create, Add Contacts, Delete, etc...)===<br /> <br /> It is even possible to create multiple contact folders to help you manage your contacts. To create a new Contact Folder, ensure you have selected the '''Contacts''' tab and click the arrow beside '''New Contact''' to open a new menu. Then, simply click choose &lt;span class=&quot;button&quot;&gt;Contacts Folder&lt;/span&gt;. <br /> <br /> [[Image:1zimbraaddress1.png]]<br /> <br /> You will be prompted to name your new folder and select a location to store it. Once you click &lt;span class=&quot;button&quot;&gt;Okay&lt;/span&gt;, you will see your new contact folder listed under the '''Contacts''' heading on the left-hand column. <br /> <br /> [[Image:1zimbraaddress2.png]]<br /> <br /> Alternatively, to create a new contact folder you may right-click on the '''Contacts''' heading on the left-hand column and select &lt;span class=&quot;button&quot;&gt;New Contact Folder&lt;/span&gt;.<br /> <br /> [[Image:1zimbraaddress3.png]]<br /> <br /> ==Preferences==<br /> ===Auto-Reply or Vacation===<br /> To set an &quot;auto-reply&quot; or &quot;vacation&quot; message, click on the '''Preferences''' tab and then select the '''Out of Office''' option.<br /> <br /> [[Image:1zimbravacation1.png]]<br /> <br /> <br /> Then, be sure to enable your &quot;away&quot; message by ticking the option '''Send auto-reply message'''. In the box below that, type the message you would like sent when someone sends you an email. <br /> <br /> [[Image:1zimbravacationnew.png]]<br /> <br /> If you like, you can set the span of dates for the auto-reply message to be sent. '''If you don't set this, remember to disable your auto-reply message when you no longer wish it sent.'''<br /> <br /> You can also set a different message to be sent to &quot;external senders.&quot; In this case, that would be anyone outside of your domain. <br /> <br /> Be sure to click &lt;span class=&quot;button&quot;&gt;Save&lt;/span&gt; near the upper-left corner of the window to save your changes.<br /> <br /> Note: The Zimbra auto responder feature only sends one response per address to prevent spam abuse.<br /> <br /> Video reference: http://help.zimbra.com/videos/8x/Out_of_Office_Message.mp4<br /> <br /> ===Filters===<br /> <br /> ====Junk/SPAM Filtering====<br /> <br /> '''The following option is only available for Premium Zimbra accounts. If you would like this functionality, please contact our Sales department.'''<br /> <br /> <br /> Enabling and disabling Junk Filtering with the Zimbra web interface is quick and simple. First, click on the '''Preferences''' tab and then select '''Junk Filter'''.<br /> <br /> [[Image:1zimbrajunk1.png]]<br /> <br /> XMission has three template rules for you to choose from.<br /> <br /> *Low - Default level of spam filtering<br /> *High - Stricter level of spam filtering<br /> *Disabled - No spam filtering<br /> <br /> If you find you are getting too much SPAM, you may want to consider selecting the '''High''' option. Alternatively, if you don't want to risk losing legitimate messages you may want to choose the '''Low''' or even '''Disabled''' option. Be sure to click '''OK''' to apply your changes. <br /> <br /> [[Image:1zimbrajunk2.png]]<br /> <br /> &lt;blockquote style=&quot;background-color: lightblue; border: solid thin grey;&quot;&gt;Unfortunately, the more strict your SPAM filter, the more likely you are to risk losing legitimate messages. However, if you have a lower setting, your risk of losing legitimate messages is not as great but you may receive more SPAM. '''Please remember you may check your &quot;Junk&quot; folder at any time. This will help you refine your filtering decisions, and also ensure you don't miss any legitimate messages.'''&lt;/blockquote&gt; <br /> <br /> XMission additionally allows you to customize your Spam Assassin scoring system. You can do this using the '''Custom''' field. Spam Assassin is a robust system that presses every messages through a variety of filters to determine it's &quot;SPAM score.&quot; Essentially, however many asterisks you place in the '''Custom''' field increases or decreases the likelihood of SPAM. For example, 8 asterisks in this field (the default '''Low''' setting) permits any message that scores 8 or less to be received. Alternatively, 5 asterisks (the '''High''' setting) only permits message that score 5 or less to be received. '''Increasing the number of asterisks will permit higher scoring messages to be received whereas decreasing the number of asterisks will consider more messages &quot;Junk&quot;''''.<br /> <br /> [[Image:1zimbrajunk3.png]]<br /> <br /> &lt;blockquote style=&quot;background-color: lightblue; border: solid thin grey;&quot;&gt;It's important to remember that spammers make every effort to make messages look legitimate, and that many legitimate messages may have systemic problems that cause them to look like SPAM. Ultimately, in the immortal words of the great Grant Sperry, &quot;Fighting SPAM is more of an art than a science.&quot;'&lt;/blockquote&gt;<br /> <br /> Zimbra Base Business mailboxes use the following method to configure unwanted mail settings.<br /> <br /> https://wiki.xmission.com/Zimbra_Spam_Filtering#Zimbra_Base_Filtering<br /> <br /> [[Category:Zimbra|Basics]]<br /> <br /> ===Signatures===<br /> Enabling Signatures with the Zimbra web interface is quick and simple. Here is how:<br /> <br /> From your preferences, select Signatures as seen in the image below&lt;br&gt;<br /> [[File:Zimbra Signatures.png]]<br /> <br /> On the right side of the screen you can select New Signature and design your signature as seen below<br /> [[File:Zimbra_Signatures_2.png]]<br /> <br /> * Format in Plain Text is just that a Plain Text signature. You can also choose Format in HTML and use Color and Images in your Signature. <br /> * Using Signatures - Primary account - If you have multiple signatures you can select what signature you need for new emails or replies and forwards.<br /> <br /> <br /> ==Document and File Sharing==<br /> Working in Briefcase<br /> <br /> Briefcase can be used to share and manage documents that you create in Briefcase or documents and images that you upload to your Briefcase folders. Use Briefcase to save files in your account so that you can access these files whenever you log in to your account from any computer.<br /> <br /> You can share your briefcases folders with others who can view and edit the files in the shared Briefcase.<br /> <br /> You can create multiple briefcase folders and then upload any type of file from your computer or your computer network, save attachments sent with your email messages, and create new documents.<br /> <br /> Files in Briefcase are copies of the original file, whether the file is on your computer or an attachment to your email. Changes you make to files in your briefcase do not change the original file.<br /> <br /> Zimbra 8.X Briefcase video tutorial: http://help.zimbra.com/videos/8x/Briefcase.mp4<br /> <br /> '''NOTE''' This feature is only available with a Zimbra Premium account. If you wish to use this feature and you do not have a Premium account, please contact our sales department. <br /> <br /> ===Creating Briefcase Folders===<br /> <br /> #Go to Briefcase&gt;Folders.<br /> #Click the gear icon and select New Briefcase.<br /> #Enter a Name for the new briefcase folder.<br /> #*The briefcase folder name must be unique within the hierarchy of your all of mailbox folders. This name cannot match any top-level folder in your mailbox, calendar, or address book. For example, if you have a calendar named Holidays, you cannot name a top-level briefcase Holidays. Holidays could be a name of a briefcase within another briefcase.<br /> #Select the Color of the new briefcase file.<br /> #Select the folder hierarchy, either under Folders or under another briefcase folder. You can create a new top-level briefcase, or you can place it under an existing briefcase.<br /> #Click OK.<br /> <br /> ===Upload Files from Briefcase===<br /> <br /> #Go to the Briefcase tab and select the Briefcase to save the file.<br /> #Click Upload File and Browse to find the file to upload. <br /> #In the Notes text field, add any information about the file. This information is displayed in the file list.<br /> #To add another file, click Add.<br /> #*You cannot upload a file with the same name to the same briefcase. If a file is uploaded that already exists in the folder, an Upload Conflict dialog displays. You can either click Yes to upload the file, overwriting the existing file, or click No.<br /> #*The version number is updated if a file is overwritten.<br /> #When all files are uploaded, click OK.<br /> <br /> '''Note:''' If you selected the wrong briefcase, you can use drag and drop to move the file to the correct Briefcase folder.<br /> *If the file is too large, a warning displays. Files that you upload impact your account quota.<br /> <br /> ===Sharing Briefcase Files Externally===<br /> <br /> You can share your XMission Zimbra files with other non-XMission users by uploading them to your Zimbra Briefcase.<br /> <br /> Select Briefcase tab inside your Zimbra webmail and create New Folder.<br /> <br /> Grant an external user access to the Briefcase by right-clicking on the new folder and select Share Folder.<br /> <br /> Select External guests (view only) and enter their email address for the shared Briefcase.<br /> <br /> The external user should receive an email containing the URL of the shared briefcase along with instructions<br /> <br /> <br /> [[Category:Zimbra]]</div>

John https://wiki.xmission.com/index.php?title=Zimbra_FAQ_-_Private_Label&diff=10993 2022-03-31T15:58:44Z

<p>John: /* Private Label Billing &amp; Support */</p> <hr /> <div>XMission provides a number of services oriented to resellers, channel partners, and organizations with private label requirements.<br /> <br /> The following FAQ provides answers to the most common questions. If we are missing anything please send requests to zimbrasales@xmission.com and we will get it added.<br /> <br /> Please note, anywhere that we reference a variant of the &quot;example.com&quot; you will replace this with your primary Zimbra domain associated with your XMission Zimbra services.<br /> <br /> Let's begin.<br /> <br /> <br /> ==Available Mailboxes==<br /> <br /> XMission provides two service levels for resellers and private label environments: Basic and Professional. Zimbra Infrastructure customers with a dedicated environment may have additional mailbox levels available based on needs.<br /> <br /> <br /> ==Differences between the Basic and Professional mailboxes?==<br /> <br /> Link a chart or private label paper here.<br /> <br /> <br /> ==Private Label Billing &amp; Support==<br /> <br /> XMission bills the private label or reseller customer of record. We do not bill the mailbox customer.<br /> <br /> A minimum billing amount of $250 p/mo required on private label services. Private label clients are required to maintain one billable email box and one Static IP address.<br /> <br /> XMission invoices in advance for all services. Mailbox billing for all accounts is added or removed from billing during the first week of each calendar month.<br /> <br /> XMission supports the private label customer of record. XMission does not provide direct support to private label's end user mailbox account holders. <br /> <br /> Private label clients can contact support by phone, email, or use livesupport. <br /> XMission support information found here: https://xmission.com/support<br /> <br /> ==Portable Device Support==<br /> <br /> Absolutely, yes. They support IMAP for all portable devices and desktop applications. As well, they have webmail access. Although the Base account mobile webmail isn't as feature rich as the Premium mobile webmail experience.<br /> <br /> The Professional accounts support portable devices with both IMAP and ActiveSync.<br /> <br /> <br /> ==Static IP Address and SSL Requirements==<br /> <br /> Typically only a single IP address and SSL certificate is required. This allows you to establish your domain as the &quot;email gateway&quot; for your customer base. When you setup your domain as the &quot;email gateway&quot; for your customer base this only requires one Static IP address and one SSL certificate. Best practice is to upgrade an existing SSL certificate to wildcard and utilize a generic subdomain practice such as email.example.com or zimbra.example.com.<br /> <br /> A secondary advantage establishing your domain as the email gateway provides is that if you ever change email platforms in the future end users would not have to change settings. <br /> <br /> <br /> ==Branding Options==<br /> <br /> XMission can provide your choice of either a generic Zimbra branded login and webmail page or a custom branded login and webmail page. The choice is entirely yours. Both options require use of a Static IP address and SSL certificate.<br /> <br /> Reference this document: http://wiki.xmission.com/Customer_branded_Zimbra_webmail<br /> <br /> <br /> ==SSL Certificate Providers==<br /> <br /> All commercially available SSL providers.<br /> <br /> Information on CSR for SSL generation can be found here: http://wiki.xmission.com/Customer_branded_Zimbra_webmail<br /> <br /> <br /> ==Customer Branding Opportunities==<br /> <br /> Same as above. It requires purchase of another Static IP and SSL cert for their domain. You will be billed for the IP address and server configuration to fit the brand to the page.<br /> <br /> <br /> ==Zimbra Themes==<br /> <br /> By default you are provided with access to all Zimbra themes. Please note, the custom logo integration may not be visually pleasing with all possible Zimbra themes. Customers may also limit the themes available to the end user. This service can be made available upon request.<br /> <br /> <br /> ==MX Record Migration Impact==<br /> <br /> There can be some impact when the new mailboxes are created on the XMission Zimbra servers and when updating MX records. <br /> <br /> When a domain is added to the XMission Zimbra system any email sent from other XMission email customers will hit the local servers first and stay here, regardless of MX record settings. This is not a common occurrence but it can happen. This most commonly happens when you move your domain to XMission and any correspondence with XMission sales and support will land on the local servers.<br /> <br /> <br /> ==Suggested A Records==<br /> <br /> It is advisable to create an A record entry for the following:<br /> <br /> * Email Gateway:<br /> <br /> The A record for your email gateway domain, mail.example.com, will point to the Static IP address XMission provides you.<br /> <br /> * MX with XMission Spam Filtering:<br /> <br /> Create an A record for mx.example.com and point it to 166.70.12.20, IP address for mx.xmission.com. You then will point all your customer domains to mx.example.com. (Point your domain there as well.) This makes sure that your customer emails go through XMission spam filtering service. It is important to remove the mx setting for the previous mail provider on your domains.<br /> <br /> * MX with External Spam Filtering: <br /> <br /> Some clients prefer to use external Spam filtering services or appliances. In this case, you can use the Static IP address provided to you for your gateway (ie mail.example.com) as en entry point. Just configure your spam filtering service to relay mail to your gateway IP, and XMission's internal spam filtering will be bypassed in favor of your external spam filter. Your client's mx records should point to your external spam filtering service.<br /> <br /> * SMTP:<br /> <br /> It is highly advisable for customers to set incoming/outgoing servers as your custom URL (mail.example.com). However, we understand that some customers require smtp.example.com to replace their existing records and make transition easier. In this case create the A record pointing to the unique url (mail.example.com) or to your static IP. If you require your incoming / outgoing servers to have different hostnames than mail.example.com you must notify XMission in advance before migration.<br /> <br /> Note: Where &quot;example.com&quot; is used in the above instructions please replace with your specific mail domain.<br /> <br /> <br /> ==Point MX Records==<br /> <br /> As noted above, you can point your MX records to mx.xmission.com or if you are using an A record point them to mx.example.com (where example.com is your domain).<br /> <br /> <br /> == SPF Record ==<br /> <br /> Point SPF record to &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot; Proper SPF will help prevent your outbound email landing in the recipient's Junk folder.<br /> <br /> == Add New Mail Domain==<br /> <br /> Simply contact zimbrasales@xmission.com with the request to add a new Zimbra domain to your service. Please reference that you are a reseller or private label customer in the email.<br /> <br /> <br /> == Multi-Domain Admin Rights==<br /> <br /> Absolutely. XMission can add your admin account to the domain admin list on all your client domains. As well, you can grant domain admin rights to your end users by following these instructions: http://wiki.xmission.com/Hosted_Email:_Admin_Panel#Granting_Domain_Administrator_Access<br /> <br /> <br /> ==Mailbox Creation==<br /> <br /> You create mailboxes by logging in to the domain admin panel and create the mailbox account. http://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_an_Account<br /> <br /> <br /> ==Limit Domain Mailbox Provisioning==<br /> <br /> XMission can set a hard limit on the number of mailboxes that can be provisioned to a domain. Please contact support@xmission.com with this request. Be sure to indicate that you are a private label customer inside the correspondence.<br /> <br /> <br /> ==Migration Assistance==<br /> <br /> Zimbra provides a number of useful migration tools that can be found inside the domain administrator control panel. https://zimbraadmin.xmission.com or https://zimbraadmin.example.com<br /> <br /> Depending on the situation XMission may be able to perform migration services for large customers on a consulting basis. Fees will apply.<br /> <br /> Please read the migration articles on our blog: https://xmission.com/blog/?s=migration<br /> <br /> ==Delete Mailboxes==<br /> <br /> Mailboxes are deleted via the domain admin control panel. http://wiki.xmission.com/Hosted_Email:_Admin_Panel#Deleting_a_Zimbra_mailbox<br /> <br /> It is important to note that any provisioned mailbox is billed to your account. Changing an account status is not the same as deleting the account and will still be billed.<br /> <br /> <br /> ==Spam and Virus Filtering==<br /> <br /> Explanation of how XMission spam and virus filtering works: https://xmission.com/blog/2013/08/14/how-xmission-spam-and-virus-filtering-works<br /> <br /> XMission efforts to mitigate impact of spam on customers: https://xmission.com/blog/2015/01/30/xmission-initiates-legal-fight-against-spammers<br /> <br /> <br /> == User Spam Complaints==<br /> <br /> The spam filtering system requires some training by the end user. To do this please advise them use the &quot;Spam&quot; button in the Zimbra webmail interface. (You can also use keyboard shortcut of &quot;m+s&quot; to quickly mark as spam.)<br /> <br /> Any filters or mailing lists you had on the previous mail system would not transfer over in migration. You users will set those up again in the Preferences tab of Zimbra webmail.<br /> <br /> <br /> ==Outlook Integration==<br /> <br /> Basic mailboxes can use IMAP settings with Outlook. Professional mailboxes can utilize the Zimbra Connector for Outlook (ZCO). The ZCO can be found in the Tools section of the domain admin control panel.<br /> <br /> <br /> ==Changing End User Passwords==<br /> <br /> You handle all password changes for end user mailboxes via the domain admin control panel. Your end users with domain admin rights may also change passwords. As a security measure XMission support staff will never change mailbox passwords.<br /> <br /> <br /> ==Zimbra Aliases and Distribution Lists==<br /> <br /> It is possible to setup XMission Zimbra system to handle aliases and/or distribution list but it does require a minimum of 1 mailbox per domain. It can be a Basic account to control costs.<br /> <br /> <br /> ==Support Options==<br /> <br /> XMission provides Tier 2 support to you and your team to address customer support concerns that you cannot address on your own.<br /> <br /> The absolute best resource for your Tier 1 support needs is the XMission wiki. https://wiki.xmission.com The bulk of all your customer support requirements can be met with the documentation provided in the wiki. If there is anything missing please contact zimbrasales@xmission.com and request a new article on the topic.<br /> <br /> * Email: support@xmission.com Please indicate you are a reseller in the subject line. Typical same or next business day response.<br /> * Phone: 801-539-0852 x 4 or 877-964-7746 x 4 - All hours response.<br /> * Live Chat: https://livesupport.xmission.com - All hours response.<br /> <br /> Again https://wiki.xmission.com is your best resource for general Zimbra support.<br /> <br /> You may also reference the official Zimbra support forums: https://forums.zimbra.org<br /> <br /> <br /> ==Support Troubleshooting Guidelines==<br /> <br /> Please provide the following information with every support request via the methods outlined above.<br /> <br /> * Mailbox address<br /> * Summary of mailbox issue. Include Email client(s) in use by client and any errors being reported.<br /> * Identify steps that have been taken toward resolution<br /> * Were XMission wiki pages lacking necessary information?<br /> <br /> If there is a problem that isn't addressed inside our wiki documents [https://wiki.xmission.com] we can get these created quickly to better support moving forward. <br /> <br /> <br /> ==Securely Share Information With XMission==<br /> <br /> Any sensitive information you need to provide XMission should only be shared using https://secrets.xmission.com. You enter the note information on the ecrets page, create a custom url, and then share that URL with your XMission agent.<br /> <br /> <br /> [[Category: Zimbra]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10991 2022-03-17T18:08:55Z

<p>John: /* DKIM DNS */</p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. Besides providing greater deliverability of your messages, these mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM (Domain Key Identified Mail) also adds public key cryptography for deeper validation.<br /> <br /> XMission advises all [https://xmission.com/zimbra Zimbra clients] to configure SPF &amp; DKIM. It may sound a bit daunting but is really not very complicated. This document will walk you through it. <br /> <br /> IMPORTANT NOTE ABOUT TXT RECORD ENTRY: Depending on the syntax requirements of your DNS system you may have to include or omit the quotation marks for the record to be properly enabled. Other DNS entries on your domain should provide quick visual guidance on protocol. XMission DNS systems do ''not'' use quotation marks.<br /> <br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF (Sender Policy Framework) record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain as you could break email delivery.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common SPF record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for SPF)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> XMission shared hosting clients can [https://wiki.xmission.com/Adding/Managing_DNS_Records learn to manage DNS records here.]<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should contain &quot;include:_spf.xmission.com&quot;.<br /> <br /> If you prefer a less identifiable entry then a minimum inclusion would have the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to Fail or SoftFail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer '''only''' sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> '''Valid SPF for XMission with additional sending services'''<br /> <br /> SPF Record Merging<br /> <br /> Some customers have mailing list or other email sending requirement that require a number of records be strung together in the SPF record. Fortunately the fairly lenient syntax of SPF records makes this easy to do, here is our default record compared to some merged records:<br /> <br /> Default XMission: &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> <br /> XMission plus Mailchimp: &quot;v=spf1 include:_spf.xmission.com include:servers.mcsv.net ~all&quot;<br /> <br /> XMission plus Gmail, plus Constant Contact: &quot;v=spf1 include:_spf.xmission.com include:_spf.google.com include:spf.constantcontact.com -all&quot;<br /> <br /> == Forwarding ==<br /> <br /> '''Important note''' about forwarding (ie automatically redirecting mail from one email address to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; SPF. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot; aka &quot;Fail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy. This is why we suggest &quot;~all&quot; (&quot;SoftFail&quot;) when you initially configure SPF.<br /> <br /> == Alias Domains ==<br /> <br /> Domain aliases that are used for sending email with &quot;From:&quot; addresses will need SPF &amp; DKIM records configured. <br /> <br /> All customers are strongly encouraged to configure SPF &amp; DKIM records for all alias domains and parked domains to prevent possible abuse.<br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like ''Out of Office'' or ''Vacation'' replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, and SMTP relay. To enable this feature for a domain, two things need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key (see below)<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two TXT records to the domain. Once added you must [https://xmission.com/contact contact] [mailto:support@xmission.com support@xmission.com] to add your domain to XMission's DKIM routing file and complete the process:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> FIRST TXT RECORD<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> <br /> SECOND TXT RECORD<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> Reminder: XMission DNS systems do not require entry of the quotation marks on the records above. External DNS system may require quotation marks.<br /> <br /> <br /> '''Multiple Email Hosts with DKIM'''<br /> <br /> It is possible to use more than one host with DKIM, though this is only possible if the DNS records used to announce the public key for the security handshake don't share subdomains with each other.<br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10990 2022-03-17T17:01:40Z

<p>John: </p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. Besides providing greater deliverability of your messages, these mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM (Domain Key Identified Mail) also adds public key cryptography for deeper validation.<br /> <br /> XMission advises all [https://xmission.com/zimbra Zimbra clients] to configure SPF &amp; DKIM. It may sound a bit daunting but is really not very complicated. This document will walk you through it. <br /> <br /> IMPORTANT NOTE ABOUT TXT RECORD ENTRY: Depending on the syntax requirements of your DNS system you may have to include or omit the quotation marks for the record to be properly enabled. Other DNS entries on your domain should provide quick visual guidance on protocol. XMission DNS systems do ''not'' use quotation marks.<br /> <br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF (Sender Policy Framework) record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain as you could break email delivery.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common SPF record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for SPF)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> XMission shared hosting clients can [https://wiki.xmission.com/Adding/Managing_DNS_Records learn to manage DNS records here.]<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should contain &quot;include:_spf.xmission.com&quot;.<br /> <br /> If you prefer a less identifiable entry then a minimum inclusion would have the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to Fail or SoftFail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer '''only''' sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> '''Valid SPF for XMission with additional sending services'''<br /> <br /> SPF Record Merging<br /> <br /> Some customers have mailing list or other email sending requirement that require a number of records be strung together in the SPF record. Fortunately the fairly lenient syntax of SPF records makes this easy to do, here is our default record compared to some merged records:<br /> <br /> Default XMission: &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> <br /> XMission plus Mailchimp: &quot;v=spf1 include:_spf.xmission.com include:servers.mcsv.net ~all&quot;<br /> <br /> XMission plus Gmail, plus Constant Contact: &quot;v=spf1 include:_spf.xmission.com include:_spf.google.com include:spf.constantcontact.com -all&quot;<br /> <br /> == Forwarding ==<br /> <br /> '''Important note''' about forwarding (ie automatically redirecting mail from one email address to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; SPF. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot; aka &quot;Fail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy. This is why we suggest &quot;~all&quot; (&quot;SoftFail&quot;) when you initially configure SPF.<br /> <br /> == Alias Domains ==<br /> <br /> Domain aliases that are used for sending email with &quot;From:&quot; addresses will need SPF &amp; DKIM records configured. <br /> <br /> All customers are strongly encouraged to configure SPF &amp; DKIM records for all alias domains and parked domains to prevent possible abuse.<br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like ''Out of Office'' or ''Vacation'' replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, and SMTP relay. To enable this feature for a domain, two things need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key (see below)<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two TXT records to the domain. Once added you must [https://xmission.com/contact contact] [mailto:support@xmission.com support@xmission.com] to add your domain to XMission's DKIM routing file and complete the process:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> <br /> '''Multiple Email Hosts with DKIM'''<br /> <br /> It is possible to use more than one host with DKIM, though this is only possible if the DNS records used to announce the public key for the security handshake don't share subdomains with each other.<br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10989 2022-03-17T17:00:04Z

<p>John: </p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. Besides providing greater deliverability of your messages, these mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM (Domain Key Identified Mail) also adds public key cryptography for deeper validation.<br /> <br /> XMission advises all [https://xmission.com/zimbra Zimbra clients] to configure SPF &amp; DKIM. It may sound a bit daunting but is really not very complicated. This document will walk you through it. <br /> <br /> IMPORTANT NOTE ABOUT TXT RECORD ENTRY: Depending on the syntax requirements of your DNS system you may have to include or omit the quotation marks for the record to be properly enabled. Other DNS entries on your domain should provide quick visual guidance on protocol. XMission DNS systems do not use quotation marks.<br /> <br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF (Sender Policy Framework) record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain as you could break email delivery.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common SPF record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for SPF)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> XMission shared hosting clients can [https://wiki.xmission.com/Adding/Managing_DNS_Records learn to manage DNS records here.]<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should contain &quot;include:_spf.xmission.com&quot;.<br /> <br /> If you prefer a less identifiable entry then a minimum inclusion would have the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to Fail or SoftFail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer '''only''' sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> '''Valid SPF for XMission with additional sending services'''<br /> <br /> SPF Record Merging<br /> <br /> Some customers have mailing list or other email sending requirement that require a number of records be strung together in the SPF record. Fortunately the fairly lenient syntax of SPF records makes this easy to do, here is our default record compared to some merged records:<br /> <br /> Default XMission: &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> <br /> XMission plus Mailchimp: &quot;v=spf1 include:_spf.xmission.com include:servers.mcsv.net ~all&quot;<br /> <br /> XMission plus Gmail, plus Constant Contact: &quot;v=spf1 include:_spf.xmission.com include:_spf.google.com include:spf.constantcontact.com -all&quot;<br /> <br /> == Forwarding ==<br /> <br /> '''Important note''' about forwarding (ie automatically redirecting mail from one email address to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; SPF. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot; aka &quot;Fail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy. This is why we suggest &quot;~all&quot; (&quot;SoftFail&quot;) when you initially configure SPF.<br /> <br /> == Alias Domains ==<br /> <br /> Domain aliases that are used for sending email with &quot;From:&quot; addresses will need SPF &amp; DKIM records configured. <br /> <br /> All customers are strongly encouraged to configure SPF &amp; DKIM records for all alias domains and parked domains to prevent possible abuse.<br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like ''Out of Office'' or ''Vacation'' replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, and SMTP relay. To enable this feature for a domain, two things need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key (see below)<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two TXT records to the domain. Once added you must [https://xmission.com/contact contact] [mailto:support@xmission.com support@xmission.com] to add your domain to XMission's DKIM routing file and complete the process:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> <br /> '''Multiple Email Hosts with DKIM'''<br /> <br /> It is possible to use more than one host with DKIM, though this is only possible if the DNS records used to announce the public key for the security handshake don't share subdomains with each other.<br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10988 2022-03-16T16:11:35Z

<p>John: </p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. Besides providing greater deliverability of your messages, these mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM (Domain Key Identified Mail) also adds public key cryptography for deeper validation.<br /> <br /> XMission advises all [https://xmission.com/zimbra Zimbra clients] to configure SPF &amp; DKIM. It may sound a bit daunting but is really not very complicated. This document will walk you through it. <br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF (Sender Policy Framework) record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain as you could break email delivery.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common SPF record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for SPF)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> XMission shared hosting clients can [https://wiki.xmission.com/Adding/Managing_DNS_Records learn to manage DNS records here.]<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should contain &quot;include:_spf.xmission.com&quot;.<br /> <br /> If you prefer a less identifiable entry then a minimum inclusion would have the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to Fail or SoftFail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer '''only''' sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> '''Valid SPF for XMission with additional sending services'''<br /> <br /> SPF Record Merging<br /> <br /> Some customers have mailing list or other email sending requirement that require a number of records be strung together in the SPF record. Fortunately the fairly lenient syntax of SPF records makes this easy to do, here is our default record compared to some merged records:<br /> <br /> Default XMission: &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> <br /> XMission plus Mailchimp: &quot;v=spf1 include:_spf.xmission.com include:servers.mcsv.net ~all&quot;<br /> <br /> XMission plus Gmail, plus Constant Contact: &quot;v=spf1 include:_spf.xmission.com include:_spf.google.com include:spf.constantcontact.com -all&quot;<br /> <br /> == Forwarding ==<br /> <br /> '''Important note''' about forwarding (ie automatically redirecting mail from one email address to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; SPF. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot; aka &quot;Fail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy. This is why we suggest &quot;~all&quot; (&quot;SoftFail&quot;) when you initially configure SPF.<br /> <br /> == Alias Domains ==<br /> <br /> Domain aliases that are used for sending email with &quot;From:&quot; addresses will need SPF &amp; DKIM records configured. <br /> <br /> All customers are strongly encouraged to configure SPF &amp; DKIM records for all alias domains and parked domains to prevent possible abuse.<br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like ''Out of Office'' or ''Vacation'' replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, and SMTP relay. To enable this feature for a domain, two things need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key (see below)<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two TXT records to the domain. Once added you must [https://xmission.com/contact contact] [mailto:support@xmission.com support@xmission.com] to add your domain to XMission's DKIM routing file and complete the process:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> <br /> '''Multiple Email Hosts with DKIM'''<br /> <br /> It is possible to use more than one host with DKIM, though this is only possible if the DNS records used to announce the public key for the security handshake don't share subdomains with each other.<br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10987 2022-03-16T16:05:34Z

<p>John: /* Forwarding */</p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. Besides providing greater deliverability of your messages, these mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM also adds public key cryptography for deeper validation.<br /> <br /> XMission advises all [https://xmission.com/zimbra Zimbra clients] to configure SPF &amp; DKIM.<br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain as you could break email delivery.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common SPF record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for SPF)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> XMission shared hosting clients can [https://wiki.xmission.com/Adding/Managing_DNS_Records learn to manage DNS records here.]<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should contain &quot;include:_spf.xmission.com&quot;.<br /> <br /> If you prefer a less identifiable entry then a minimum inclusion would have the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to Fail or SoftFail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer '''only''' sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> '''Valid SPF for XMission with additional sending services'''<br /> <br /> SPF Record Merging<br /> <br /> Some customers have mailing list or other email sending requirement that require a number of records be strung together in the SPF record. Fortunately the fairly lenient syntax of SPF records makes this easy to do, here is our default record compared to some merged records:<br /> <br /> Default XMission: &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> <br /> XMission plus Mailchimp: &quot;v=spf1 include:_spf.xmission.com include:servers.mcsv.net ~all&quot;<br /> <br /> XMission plus Gmail, plus Constant Contact: &quot;v=spf1 include:_spf.xmission.com include:_spf.google.com include:spf.constantcontact.com -all&quot;<br /> <br /> == Forwarding ==<br /> <br /> '''Important note''' about forwarding (ie automatically redirecting mail from one email address to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; SPF. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot; aka &quot;Fail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy. This is why we suggest &quot;~all&quot; (&quot;SoftFail&quot;) when you initially configure SPF.<br /> <br /> == Alias Domains ==<br /> <br /> Domain aliases that are used for sending email with &quot;From:&quot; addresses will need SPF &amp; DKIM records configured. <br /> <br /> All customers are strongly encouraged to configure SPF &amp; DKIM records for all alias domains and parked domains to prevent possible abuse.<br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like ''Out of Office'' or ''Vacation'' replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, and SMTP relay. To enable this feature for a domain, two things need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key (see below)<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two TXT records to the domain. Once added you must [https://xmission.com/contact contact] [mailto:support@xmission.com support@xmission.com] to add your domain to XMission's DKIM routing file and complete the process:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> <br /> '''Multiple Email Hosts with DKIM'''<br /> <br /> It is possible to use more than one host with DKIM, though this is only possible if the DNS records used to announce the public key for the security handshake don't share subdomains with each other.<br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10986 2022-03-15T20:16:41Z

<p>John: /* Alias Domains */</p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. Besides providing greater deliverability of your messages, these mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM also adds public key cryptography for deeper validation.<br /> <br /> XMission advises all [https://xmission.com/zimbra Zimbra clients] to configure SPF &amp; DKIM.<br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain as you could break email delivery.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common SPF record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for SPF)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> XMission shared hosting clients can [https://wiki.xmission.com/Adding/Managing_DNS_Records learn to manage DNS records here.]<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should contain &quot;include:_spf.xmission.com&quot;.<br /> <br /> If you prefer a less identifiable entry then a minimum inclusion would have the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to Fail or SoftFail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer '''only''' sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> '''Valid SPF for XMission with additional sending services'''<br /> <br /> SPF Record Merging<br /> <br /> Some customers have mailing list or other email sending requirement that require a number of records be strung together in the SPF record. Fortunately the fairly lenient syntax of SPF records makes this easy to do, here is our default record compared to some merged records:<br /> <br /> Default XMission: &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> <br /> XMission plus Mailchimp: &quot;v=spf1 include:_spf.xmission.com include:servers.mcsv.net ~all&quot;<br /> <br /> XMission plus Gmail, plus Constant Contact: &quot;v=spf1 include:_spf.xmission.com include:_spf.google.com include:spf.constantcontact.com -all&quot;<br /> <br /> == Forwarding ==<br /> <br /> A note about forwarding (ie automatically redirecting mail from one email address to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; SPF. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot; aka &quot;Fail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy. This is why we suggest &quot;~all&quot; (&quot;SoftFail&quot;) when you initially configure SPF. <br /> <br /> == Alias Domains ==<br /> <br /> Domain aliases that are used for sending email with &quot;From:&quot; addresses will need SPF &amp; DKIM records configured. <br /> <br /> All customers are strongly encouraged to configure SPF &amp; DKIM records for all alias domains and parked domains to prevent possible abuse.<br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like ''Out of Office'' or ''Vacation'' replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, and SMTP relay. To enable this feature for a domain, two things need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key (see below)<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two TXT records to the domain. Once added you must [https://xmission.com/contact contact] [mailto:support@xmission.com support@xmission.com] to add your domain to XMission's DKIM routing file and complete the process:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> <br /> '''Multiple Email Hosts with DKIM'''<br /> <br /> It is possible to use more than one host with DKIM, though this is only possible if the DNS records used to announce the public key for the security handshake don't share subdomains with each other.<br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10984 2022-03-08T16:40:22Z

<p>John: /* DKIM DNS */</p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. Besides providing greater deliverability of your messages, these mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM also adds public key cryptography for deeper validation.<br /> <br /> XMission advises all [https://xmission.com/zimbra Zimbra clients] to configure SPF &amp; DKIM.<br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain as you could break email delivery.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common SPF record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for SPF)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> XMission shared hosting clients can [https://wiki.xmission.com/Adding/Managing_DNS_Records learn to manage DNS records here.]<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should contain &quot;include:_spf.xmission.com&quot;.<br /> <br /> If you prefer a less identifiable entry then a minimum inclusion would have the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to Fail or SoftFail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer '''only''' sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> '''Valid SPF for XMission with additional sending services'''<br /> <br /> SPF Record Merging<br /> <br /> Some customers have mailing list or other email sending requirement that require a number of records be strung together in the SPF record. Fortunately the fairly lenient syntax of SPF records makes this easy to do, here is our default record compared to some merged records:<br /> <br /> Default XMission: &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> <br /> XMission plus Mailchimp: &quot;v=spf1 include:_spf.xmission.com include:servers.mcsv.net ~all&quot;<br /> <br /> XMission plus Gmail, plus Constant Contact: &quot;v=spf1 include:_spf.xmission.com include:_spf.google.com include:spf.constantcontact.com -all&quot;<br /> <br /> == Forwarding ==<br /> <br /> A note about forwarding (ie automatically redirecting mail from one email address to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; SPF. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot; aka &quot;Fail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy. This is why we suggest &quot;~all&quot; (&quot;SoftFail&quot;) when you initially configure SPF. <br /> <br /> == Alias Domains ==<br /> <br /> Domain aliases that are used for sending email with &quot;From:&quot; addresses will need SPF &amp; DKIM records configured. <br /> <br /> If you're only receiving mail from that aliased domain, then there is no need to configure SPF or DKIM records.<br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like ''Out of Office'' or ''Vacation'' replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, and SMTP relay. To enable this feature for a domain, two things need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key (see below)<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two TXT records to the domain. Once added you must [https://xmission.com/contact contact] [mailto:support@xmission.com support@xmission.com] to add your domain to XMission's DKIM routing file and complete the process:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> <br /> '''Multiple Email Hosts with DKIM'''<br /> <br /> It is possible to use more than one host with DKIM, though this is only possible if the DNS records used to announce the public key for the security handshake don't share subdomains with each other.<br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10983 2022-03-08T16:38:05Z

<p>John: /* DKIM DNS */</p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. Besides providing greater deliverability of your messages, these mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM also adds public key cryptography for deeper validation.<br /> <br /> XMission advises all [https://xmission.com/zimbra Zimbra clients] to configure SPF &amp; DKIM.<br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain as you could break email delivery.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common SPF record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for SPF)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> XMission shared hosting clients can [https://wiki.xmission.com/Adding/Managing_DNS_Records learn to manage DNS records here.]<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should contain &quot;include:_spf.xmission.com&quot;.<br /> <br /> If you prefer a less identifiable entry then a minimum inclusion would have the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to Fail or SoftFail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer '''only''' sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> '''Valid SPF for XMission with additional sending services'''<br /> <br /> SPF Record Merging<br /> <br /> Some customers have mailing list or other email sending requirement that require a number of records be strung together in the SPF record. Fortunately the fairly lenient syntax of SPF records makes this easy to do, here is our default record compared to some merged records:<br /> <br /> Default XMission: &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> <br /> XMission plus Mailchimp: &quot;v=spf1 include:_spf.xmission.com include:servers.mcsv.net ~all&quot;<br /> <br /> XMission plus Gmail, plus Constant Contact: &quot;v=spf1 include:_spf.xmission.com include:_spf.google.com include:spf.constantcontact.com -all&quot;<br /> <br /> == Forwarding ==<br /> <br /> A note about forwarding (ie automatically redirecting mail from one email address to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; SPF. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot; aka &quot;Fail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy. This is why we suggest &quot;~all&quot; (&quot;SoftFail&quot;) when you initially configure SPF. <br /> <br /> == Alias Domains ==<br /> <br /> Domain aliases that are used for sending email with &quot;From:&quot; addresses will need SPF &amp; DKIM records configured. <br /> <br /> If you're only receiving mail from that aliased domain, then there is no need to configure SPF or DKIM records.<br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like ''Out of Office'' or ''Vacation'' replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, and SMTP relay. To enable this feature for a domain, two things need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key (see below)<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two TXT records to the domain. Once completed you must [https://xmission.com/contact contact] [mailto:support@xmission.com support@xmission.com] add your domain to XMission's DKIM routing file:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> <br /> '''Multiple Email Hosts with DKIM'''<br /> <br /> It is possible to use more than one host with DKIM, though this is only possible if the DNS records used to announce the public key for the security handshake don't share subdomains with each other.<br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10982 2022-03-08T16:37:14Z

<p>John: /* DKIM DNS */</p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. Besides providing greater deliverability of your messages, these mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM also adds public key cryptography for deeper validation.<br /> <br /> XMission advises all [https://xmission.com/zimbra Zimbra clients] to configure SPF &amp; DKIM.<br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain as you could break email delivery.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common SPF record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for SPF)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> XMission shared hosting clients can [https://wiki.xmission.com/Adding/Managing_DNS_Records learn to manage DNS records here.]<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should contain &quot;include:_spf.xmission.com&quot;.<br /> <br /> If you prefer a less identifiable entry then a minimum inclusion would have the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to Fail or SoftFail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer '''only''' sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> '''Valid SPF for XMission with additional sending services'''<br /> <br /> SPF Record Merging<br /> <br /> Some customers have mailing list or other email sending requirement that require a number of records be strung together in the SPF record. Fortunately the fairly lenient syntax of SPF records makes this easy to do, here is our default record compared to some merged records:<br /> <br /> Default XMission: &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> <br /> XMission plus Mailchimp: &quot;v=spf1 include:_spf.xmission.com include:servers.mcsv.net ~all&quot;<br /> <br /> XMission plus Gmail, plus Constant Contact: &quot;v=spf1 include:_spf.xmission.com include:_spf.google.com include:spf.constantcontact.com -all&quot;<br /> <br /> == Forwarding ==<br /> <br /> A note about forwarding (ie automatically redirecting mail from one email address to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; SPF. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot; aka &quot;Fail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy. This is why we suggest &quot;~all&quot; (&quot;SoftFail&quot;) when you initially configure SPF. <br /> <br /> == Alias Domains ==<br /> <br /> Domain aliases that are used for sending email with &quot;From:&quot; addresses will need SPF &amp; DKIM records configured. <br /> <br /> If you're only receiving mail from that aliased domain, then there is no need to configure SPF or DKIM records.<br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like ''Out of Office'' or ''Vacation'' replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, and SMTP relay. To enable this feature for a domain, two things need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key (see below)<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two TXT records to the domain. Once completed you must [https://xmission.com/contact contact] support@xmission.com add your domain to XMission's DKIM routing file:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> <br /> '''Multiple Email Hosts with DKIM'''<br /> <br /> It is possible to use more than one host with DKIM, though this is only possible if the DNS records used to announce the public key for the security handshake don't share subdomains with each other.<br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10981 2022-03-08T16:36:20Z

<p>John: /* DKIM DNS */</p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. Besides providing greater deliverability of your messages, these mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM also adds public key cryptography for deeper validation.<br /> <br /> XMission advises all [https://xmission.com/zimbra Zimbra clients] to configure SPF &amp; DKIM.<br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain as you could break email delivery.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common SPF record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for SPF)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> XMission shared hosting clients can [https://wiki.xmission.com/Adding/Managing_DNS_Records learn to manage DNS records here.]<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should contain &quot;include:_spf.xmission.com&quot;.<br /> <br /> If you prefer a less identifiable entry then a minimum inclusion would have the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to Fail or SoftFail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer '''only''' sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> '''Valid SPF for XMission with additional sending services'''<br /> <br /> SPF Record Merging<br /> <br /> Some customers have mailing list or other email sending requirement that require a number of records be strung together in the SPF record. Fortunately the fairly lenient syntax of SPF records makes this easy to do, here is our default record compared to some merged records:<br /> <br /> Default XMission: &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> <br /> XMission plus Mailchimp: &quot;v=spf1 include:_spf.xmission.com include:servers.mcsv.net ~all&quot;<br /> <br /> XMission plus Gmail, plus Constant Contact: &quot;v=spf1 include:_spf.xmission.com include:_spf.google.com include:spf.constantcontact.com -all&quot;<br /> <br /> == Forwarding ==<br /> <br /> A note about forwarding (ie automatically redirecting mail from one email address to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; SPF. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot; aka &quot;Fail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy. This is why we suggest &quot;~all&quot; (&quot;SoftFail&quot;) when you initially configure SPF. <br /> <br /> == Alias Domains ==<br /> <br /> Domain aliases that are used for sending email with &quot;From:&quot; addresses will need SPF &amp; DKIM records configured. <br /> <br /> If you're only receiving mail from that aliased domain, then there is no need to configure SPF or DKIM records.<br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like ''Out of Office'' or ''Vacation'' replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, and SMTP relay. To enable this feature for a domain, two things need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key (see below)<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two TXT records to the domain and then [https://xmission.com/contact contact] support@xmission.com to have XMission add your domain to XMission's DKIM routing file:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> <br /> '''Multiple Email Hosts with DKIM'''<br /> <br /> It is possible to use more than one host with DKIM, though this is only possible if the DNS records used to announce the public key for the security handshake don't share subdomains with each other.<br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10980 2022-03-07T23:12:01Z

<p>John: </p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. Besides providing greater deliverability of your messages, these mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM also adds public key cryptography for deeper validation.<br /> <br /> XMission advises all [https://xmission.com/zimbra Zimbra clients] to configure SPF &amp; DKIM.<br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain as you could break email delivery.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common SPF record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for SPF)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> XMission shared hosting clients can [https://wiki.xmission.com/Adding/Managing_DNS_Records learn to manage DNS records here.]<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should contain &quot;include:_spf.xmission.com&quot;.<br /> <br /> If you prefer a less identifiable entry then a minimum inclusion would have the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to Fail or SoftFail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer '''only''' sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> '''Valid SPF for XMission with additional sending services'''<br /> <br /> SPF Record Merging<br /> <br /> Some customers have mailing list or other email sending requirement that require a number of records be strung together in the SPF record. Fortunately the fairly lenient syntax of SPF records makes this easy to do, here is our default record compared to some merged records:<br /> <br /> Default XMission: &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> <br /> XMission plus Mailchimp: &quot;v=spf1 include:_spf.xmission.com include:servers.mcsv.net ~all&quot;<br /> <br /> XMission plus Gmail, plus Constant Contact: &quot;v=spf1 include:_spf.xmission.com include:_spf.google.com include:spf.constantcontact.com -all&quot;<br /> <br /> == Forwarding ==<br /> <br /> A note about forwarding (ie automatically redirecting mail from one email address to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; SPF. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot; aka &quot;Fail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy. This is why we suggest &quot;~all&quot; (&quot;SoftFail&quot;) when you initially configure SPF. <br /> <br /> == Alias Domains ==<br /> <br /> Domain aliases that are used for sending email with &quot;From:&quot; addresses will need SPF &amp; DKIM records configured. <br /> <br /> If you're only receiving mail from that aliased domain, then there is no need to configure SPF or DKIM records.<br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like ''Out of Office'' or ''Vacation'' replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, and SMTP relay. To enable this feature for a domain, two things need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key (see below)<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two TXT records to the domain:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> <br /> '''Multiple Email Hosts with DKIM'''<br /> <br /> It is possible to use more than one host with DKIM, though this is only possible if the DNS records used to announce the public key for the security handshake don't share subdomains with each other.<br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10979 2022-03-07T22:57:39Z

<p>John: </p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. Besides providing greater deliverability of your messages, these mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM also adds public key cryptography for deeper validation.<br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain as you could break email delivery.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common SPF record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for SPF)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should contain &quot;include:_spf.xmission.com&quot;.<br /> <br /> If you prefer a less identifiable entry then a minimum inclusion would have the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to Fail or SoftFail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer '''only''' sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> '''Valid SPF for XMission with additional sending services'''<br /> <br /> SPF Record Merging<br /> <br /> Some customers have mailing list or other email sending requirement that require a number of records be strung together in the SPF record. Fortunately the fairly lenient syntax of SPF records makes this easy to do, here is our default record compared to some merged records:<br /> <br /> Default XMission: &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> <br /> XMission plus Mailchimp: &quot;v=spf1 include:_spf.xmission.com include:servers.mcsv.net ~all&quot;<br /> <br /> XMission plus Gmail, plus Constant Contact: &quot;v=spf1 include:_spf.xmission.com include:_spf.google.com include:spf.constantcontact.com -all&quot;<br /> <br /> == Forwarding ==<br /> <br /> A note about forwarding (ie automatically redirecting mail from one email address to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; SPF. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot; aka &quot;Fail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy. This is why we suggest &quot;~all&quot; (&quot;SoftFail&quot;) when you initially configure SPF. <br /> <br /> == Alias Domains ==<br /> <br /> Domain aliases that are used for sending email with &quot;From:&quot; addresses will need SPF &amp; DKIM records configured. <br /> <br /> If you're only receiving mail from that aliased domain, then there is no need to configure SPF or DKIM records.<br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like ''Out of Office'' or ''Vacation'' replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, and SMTP relay. To enable this feature for a domain, two things need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key (see below)<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two TXT records to the domain:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> <br /> '''Multiple Email Hosts with DKIM'''<br /> <br /> It is possible to use more than one host with DKIM, though this is only possible if the DNS records used to announce the public key for the security handshake don't share subdomains with each other.<br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10978 2022-03-07T22:49:53Z

<p>John: /* DKIM DNS */</p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. Besides providing greater deliverability of your messages, these mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM also adds public key cryptography for deeper validation.<br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain as you could break email delivery.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common SPF record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for SPF)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should contain &quot;include:_spf.xmission.com&quot;.<br /> <br /> If you prefer a less identifiable entry then a minimum inclusion would have the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to Fail or SoftFail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer '''only''' sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> '''Valid SPF for XMission with additional sending services'''<br /> <br /> SPF Record Merging<br /> <br /> Some customers have mailing list or other email sending requirement that require a number of records be strung together in the SPF record. Fortunately the fairly lenient syntax of SPF records makes this easy to do, here is our default record compared to some merged records:<br /> <br /> Default XMission: &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> <br /> XMission plus Mailchimp: &quot;v=spf1 include:_spf.xmission.com include:servers.mcsv.net ~all&quot;<br /> <br /> XMission plus Gmail, plus Constant Contact: &quot;v=spf1 include:_spf.xmission.com include:_spf.google.com include:spf.constantcontact.com -all&quot;<br /> <br /> == Forwarding ==<br /> <br /> A note about forwarding (ie automatically redirecting mail from one email address to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; SPF. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot; aka &quot;Fail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy. This is why we suggest &quot;~all&quot; (&quot;SoftFail&quot;) when you initially configure SPF. <br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like ''Out of Office'' or ''Vacation'' replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, and SMTP relay. To enable this feature for a domain, two things need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key (see below)<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two TXT records to the domain:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> <br /> '''Multiple Email Hosts with DKIM'''<br /> <br /> It is possible to use more than one host with DKIM, though this is only possible if the DNS records used to announce the public key for the security handshake don't share subdomains with each other.<br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10977 2022-03-07T22:47:10Z

<p>John: /* Valid SPF for XMission */</p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. Besides providing greater deliverability of your messages, these mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM also adds public key cryptography for deeper validation.<br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain as you could break email delivery.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common SPF record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for SPF)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should contain &quot;include:_spf.xmission.com&quot;.<br /> <br /> If you prefer a less identifiable entry then a minimum inclusion would have the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to Fail or SoftFail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer '''only''' sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> '''Valid SPF for XMission with additional sending services'''<br /> <br /> SPF Record Merging<br /> <br /> Some customers have mailing list or other email sending requirement that require a number of records be strung together in the SPF record. Fortunately the fairly lenient syntax of SPF records makes this easy to do, here is our default record compared to some merged records:<br /> <br /> Default XMission: &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> <br /> XMission plus Mailchimp: &quot;v=spf1 include:_spf.xmission.com include:servers.mcsv.net ~all&quot;<br /> <br /> XMission plus Gmail, plus Constant Contact: &quot;v=spf1 include:_spf.xmission.com include:_spf.google.com include:spf.constantcontact.com -all&quot;<br /> <br /> == Forwarding ==<br /> <br /> A note about forwarding (ie automatically redirecting mail from one email address to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; SPF. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot; aka &quot;Fail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy. This is why we suggest &quot;~all&quot; (&quot;SoftFail&quot;) when you initially configure SPF. <br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like ''Out of Office'' or ''Vacation'' replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, and SMTP relay. To enable this feature for a domain, two things need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key (see below)<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two TXT records to the domain:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10976 2022-03-07T22:36:45Z

<p>John: </p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. Besides providing greater deliverability of your messages, these mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM also adds public key cryptography for deeper validation.<br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain as you could break email delivery.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common SPF record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for SPF)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should contain &quot;include:_spf.xmission.com&quot;.<br /> <br /> If you prefer a less identifiable entry then a minimum inclusion would have the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to Fail or SoftFail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer '''only''' sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == Forwarding ==<br /> <br /> A note about forwarding (ie automatically redirecting mail from one email address to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; SPF. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot; aka &quot;Fail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy. This is why we suggest &quot;~all&quot; (&quot;SoftFail&quot;) when you initially configure SPF. <br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like ''Out of Office'' or ''Vacation'' replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, and SMTP relay. To enable this feature for a domain, two things need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key (see below)<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two TXT records to the domain:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=SPF_and_DKIM&diff=10975 2022-03-07T22:15:29Z

<p>John: </p> <hr /> <div>SPF and DKIM are two important security methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf. These mechanisms prevent fraudsters from sending spoofing emails as your domain. <br /> <br /> These TXT records are entered by the domain owner wherever the domain's DNS record is managed, which may be with the registrar or hosting provider. DKIM also adds public key cryptography for deeper validation.<br /> <br /> = SPF =<br /> <br /> The following is the most commonly applied SPF record for XMission email customers but it is imperative you understand how and why this is applied. IMPORTANT: It is critical that you read and understand all SPF information below before applying the record to your domain.<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == How It Works ==<br /> <br /> Any SPF record is a string of one more more potential mail sources, prefixed by a character indicating the policy for mail source. An example of a common spf record:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf a mx ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> In this case, it says that the A and MX records for the domain are allowed to send, and all other mail fails (but with a &quot;softfail&quot;, so that mail isn't actually rejected). &quot;a&quot;, &quot;mx&quot; and &quot;all&quot;, are all individual mail sources. The &quot;~&quot; prefixed to the &quot;all&quot; source is a policy denoting that mail from the source should be considered a &quot;SoftFail&quot;.<br /> <br /> The sources are:<br /> <br /> * a - A DNS A record<br /> * mx - An MX record<br /> * ptr - A PTR record<br /> * ip4 - An ipv4 address or subnet<br /> * ip6 - An ipv6 address or subnet<br /> * include - The contents of another domain's SPF record<br /> * all - Any mail source (generally used at the end to provide a default policy)<br /> <br /> The prefix characters are:<br /> <br /> * + - Pass (Valid for spf)<br /> * - - Fail (Invalid, and reject mail)<br /> * ~ - SoftFail (Invalid, but still accept)<br /> * ? - Neutral (...whatever...)<br /> <br /> == Valid SPF for XMission ==<br /> <br /> Any SPF record for a domain sending through XMission should include the following two sources:<br /> <br /> * ip4:166.70.13.0/24<br /> * ip4:198.60.22.0/24<br /> <br /> You can include the above either with the two sources listed above, or by including XMission's spf record with &quot;include:_spf.xmission.com&quot;.<br /> <br /> Note that the SPF record policy is a decision of the domain owner's. If they want to fail or softfail on all, add other sources, etc., is up to them. We don't have a singular recommendation or requirement for SPF. If the customer only sends via XMission, the following SPF record is relatively safe:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> @ IN TXT &quot;v=spf1 a mx include:_spf.xmission.com ~all&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> == Forwarding ==<br /> <br /> A note about forwarding (ie automatically redirecting mail from one account to another, not hitting the forward button):<br /> <br /> Forwarding (under most circumstances) &lt;em&gt;BREAKS&lt;/em&gt; spf. If a domain has a &quot;-all&quot; (&quot;reject all other mail&quot;) policy in their SPF record, mail will be rejected by any servers respecting SPF after the server performing the forward. Users should keep this in mind when choosing a policy.<br /> <br /> <br /> <br /> = DKIM = <br /> <br /> == How DKIM Works ==<br /> <br /> DKIM is similar to SPF in that it uses a TXT record on the domain to define a sending policy for that domain. Where it differs is that it uses public key cryptography with this sending policy. A public key is added to that TXT record and any message that is signed with the private key (and thus validates with the public key) is then considered valid.<br /> <br /> '''DKIM will break automatic responders, like Out of Office replies.''' This is due to how DKIM verifies the sender, and how automated replies are generated and sent. This is intentional, and is a consideration that needs to be made when limiting sending from your domain via DKIM.<br /> <br /> == Adding DKIM to an XMission Domain ==<br /> <br /> We have a single private key for XMission DKIM signing. We can sign DKIM with this key on any domain sending out through XMission. It works for Zimbra domains, virtmail, relay. To enable this feature for a domain, two things will need to happen:<br /> <br /> * The domain needs proper DNS for our domainkey key<br /> * The domain needs to be added to XMission routing config as one with DKIM signing.<br /> <br /> <br /> <br /> == DKIM DNS ==<br /> <br /> Add the following two txt records to the domain in question:<br /> <br /> &lt;code&gt;&lt;pre&gt;<br /> xmission._domainkey IN TXT &quot;v=DKIM1; t=y; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCzWmoe0tzQkSUzMqliwcQQ5zY1HKk4z+Wgp+dRCRe7MmSBPftE9r5Lx1QfTfF/J8gl4k9tFsUvUBap0fk1VGMYUG/2LynVuzpkCI4JlUKF5fbx+MDNZrVi0aX73Edjd9trU6NKldVnhNg1RixDLa4aB04XJviy6+3P1h3IHNaZ0QIDAQAB&quot;<br /> _domainkey IN TXT &quot;t=y; o=~;&quot;<br /> &lt;/pre&gt;&lt;/code&gt;<br /> <br /> <br /> [[Category: Email]]</div>

John https://wiki.xmission.com/index.php?title=Hosted_Email:Outlook_2010&diff=10974 2022-03-03T15:41:21Z

<p>John: </p> <hr /> <div>'''DISCLAIMER: Microsoft deprecated Outlook 2010 on October 13, 2020.''' XMission will only support with basic configuration settings, no other troubleshooting will be provided. You are at risk using out of date software and must update for your own safety.<br /> <br /> The Zimbra webmail interface is always up to date and well supported. Please give it a try: https://zimbra.xmission.com<br /> <br /> <br /> {{ZCO}}<br /> <br /> <br /> &lt;h3&gt;Configuration Instructions&lt;/h3&gt;<br /> <br /> 1. Click on the ''File'' menu, then go to the ''Info'' submenu and click on the ''Account Settings'' button.<br /> :[[Image:2010-1.png]]<br /> &lt;br/&gt;<br /> &lt;br/&gt;<br /> &lt;br/&gt;<br /> 2. Click the ''New...'' button underneath the ''E-mail'' Tab. <br /> :[[Image:2010-2.png]]<br /> &lt;br/&gt;<br /> &lt;br/&gt;<br /> &lt;br/&gt;<br /> 3. Before filling in any information check the box labeled ''Manually configure server settings or additional server types'' and click ''Next''. <br /> :[[Image:2010-3.png]]<br /> &lt;br/&gt;<br /> &lt;br/&gt;<br /> &lt;br/&gt;<br /> 4. Select ''Internet E-mail'' from the options presented and click ''Next''. <br /> :[[Image:2010-4.png]]<br /> &lt;br/&gt;<br /> &lt;br/&gt;<br /> &lt;br/&gt;<br /> 5. Fill out the information on this window as seen below and then click on the ''More Settings...'' button.&lt;br/&gt; '''Note:''' For maximum compatibility and additional features always select IMAP as the server type.<br /> :[[Image:2010-5.png]]<br /> &lt;br/&gt;<br /> &lt;br/&gt;<br /> &lt;br/&gt;<br /> 6. Goto the ''Outgoing Server'' tab and check the box that says ''My outgoing server (SMTP) requires authentication'' and make sure ''Use same settings as my incoming mail server'' is selected underneath that. <br /> :[[Image:2010-6.png]]<br /> &lt;br/&gt;<br /> &lt;br/&gt;<br /> &lt;br/&gt;<br /> 7. Goto the ''Advanced'' tab and set both dropdown boxes that say ''Use the Following Type of Encrypted Connection'' to SSL and set ''Outgoing server (SMTP)'' to port 465. <br /> &lt;br/&gt;<br /> &lt;br/&gt;<br /> &lt;br/&gt;<br /> 8. Click the ''Finish'' button. You should now be able to send and receive mail. <br /> :[[Image:2010-7.png]]<br /> <br /> [[Category:Client Email Configuration|Zimbra|Outlook 2010]]<br /> [[Category:Zimbra|Outlook 2010]]</div>

John https://wiki.xmission.com/index.php?title=Migration_to_XMission_Zimbra&diff=10973 2022-02-09T21:06:20Z

<p>John: </p> <hr /> <div>Migration to XMission Zimbra is typically straight forward for most customers. <br /> <br /> ===Migrating Data From/To Zimbra===<br /> <br /> == Zimbra.com endorsed migration provider ==<br /> <br /> For those that wish to pay a third party to migrate their accounts to XMission Zimbra service the Zimbra blog endorses audriga as their official Zimbra migration partner. https://blog.zimbra.com/2019/08/audriga-zimbra-migration-tool/<br /> <br /> The audriga Zimbra migration tool is found here: https://zimbra.audriga.com/<br /> <br /> <br /> ===Migration Tools and Tutorials===<br /> <br /> ==Migration and Import Tools in Admin Panel:==<br /> <br /> Zimbra provides a number of quality migration tools that can be found inside the Domain Administrator control panel. https://zimbraadmin.xmission.com <br /> <br /> <br /> ===Microsoft Outlook PST Import Tool=== <br /> <br /> This tool allows users to import Microsoft Outlook PST files to the Zimbra Server. <br /> <br /> <br /> ''Migration Wizard for Microsoft Exchange'' This application performs a server-to-server migration of email, calendar and contacts from Microsoft Exchange to the Zimbra Server. https://wiki.xmission.com/Zimbra_Hosting_Admin#Importing_Accounts_from_Exchange<br /> <br /> <br /> ==Migration Tutorials== <br /> <br /> ===IMAPsync Tutorial by XMission===<br /> Highly accurate way to migrate mail data: https://wiki.xmission.com/Zimbra_Migration:_IMAPSync<br /> <br /> Pay particular attention to the IMAPsync tips and tricks section of the article.<br /> <br /> ===Non-mail Data Import to Zimbra===<br /> Zimbra.com wiki article on how to deal with non mail data: https://wiki.zimbra.com/wiki/Calendar_and_Contacts_Migration<br /> <br /> ===Google Gsuite Migration Tutorial===<br /> Google Apps migration to Zimbra with XMission using Oauth and the IMAPsync https://xmission.com/blog/2015/09/09/migrate-your-email-from-google-apps-to-zimbra-collaboration<br /> <br /> <br /> == Zimbra.com wiki migration article.==<br /> <br /> https://wiki.zimbra.com/wiki/Mail_Migration<br /> <br /> [[Category: Zimbra]]</div>

John https://wiki.xmission.com/index.php?title=Hosted_Email:_Admin_Panel&diff=10968 2021-12-10T18:22:28Z

<p>John: /* Granting Domain Administrator Access */</p> <hr /> <div>==Overview/Logging In== <br /> The Zimbra domain administration console is the browser-based user interface used to centrally manage user accounts and most settings.<br /> <br /> As a domain administrator, you will be able to create and maintain the following:<br /> <br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_an_Email_Account Email accounts]<br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_an_Alias Mailbox aliases]<br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_a_Distribution_List Distribution lists]<br /> *Resources<br /> <br /> To login to the domain administration console, go to https://zimbraadmin.xmission.com/ and login with your administrative username and password. Domain administrators can also login from the dropdown menu next to your mailbox name in the top right corner of the webmail session. Click on 'Admin Console' to proceed.<br /> <br /> ==Domain Administrator Responsibilities==<br /> <br /> It is important to understand that as domain administrators you are responsible for changing passwords, creating distribution lists, setting email forwards, managing mailboxes, training on phishing, and etc. Our support policy for email is clearly outlined at: https://xmission.com/legal_policies#emlsup We require domain administrators be added as Technical contacts on your billing account in order to receive advanced assistance from our support staff. Please keep contacts up-to-date in the [https://xmission.com/control account management portal] or contact [https://xmission.com/contact XMission Billing] for assistance.<br /> <br /> Phishing and email scams are on the rise. It is important to educate yourself and your mailbox holders on how to avoid it. Reference this guide on <br /> [https://wiki.xmission.com/Phishing_and_Email_Scams understanding phishing].<br /> <br /> ==Email Domain Health==<br /> <br /> An important part of effective business email mean protecting your domain with some simple settings to improve delivery and reduce fraud.<br /> <br /> XMission advises implementing SPF and DKIM on domains. These are two simple methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf and prevent abuse. [https://wiki.xmission.com/SPF_and_DKIM How to configure SPF and DKIM]<br /> <br /> ==About the Administrative Console==<br /> <br /> The area above the '''Content''' pane includes the '''Search''' and '''Help''' functions.<br /> <br /> '''Search''' allows you to quickly find accounts, aliases, distribution lists and resources for editing. <br /> <br /> '''Help''' utilizes Zimbra’s wiki, forums, and documentation. This is a powerful unified search to quickly find answers to common questions.<br /> <br /> [[Image:1zimbraadminpanel.png]]<br /> <br /> <br /> <br /> The '''Navigation''' pane on the left includes the following sections:<br /> <br /> *'''Home:''' At any time, clicking here will return you to the administrative Home options. <br /> <br /> *'''Manage:''' Clicking here will permit you to create and edit any accounts, aliases, distribution lists, and resources for your domain(s). <br /> <br /> *'''Help:''' utilizes Zimbra’s wiki, forums, and documentation. This is a powerful unified search to quickly find answers to common questions. <br /> <br /> [[Image:4zimbraadminpanel.png]]<br /> <br /> <br /> <br /> Alternatively, you can also click on the arrow beside the &quot;Home&quot; button. This will give you the same options listed above, as well as recent searches and the options available under &quot;Manage.&quot; In this example, the recent search was for &quot;xdesign.com.&quot;<br /> <br /> [[Image:2zimbraadminpanel.png]]<br /> <br /> <br /> <br /> Clicking on &quot;Manage&quot; either way will permit you to make changes to your existing accounts, aliases, distribution lists, and resources.<br /> <br /> *'''Accounts:''' Lists all accounts. In the Accounts folder, you create and manage end-user accounts, setting options, class of service, passwords and aliases for an account.<br /> <br /> *'''Aliases:''' Lists all aliases that have been created in Accounts. You can use the Move Alias feature from the toolbar to move an alias from one account to another.<br /> <br /> *'''Distribution Lists:''' Lists all distribution lists. You can create new distribution lists and add or delete members of a distribution list.<br /> <br /> *'''Resources:''' This lists locations or equipment that can be scheduled from your Calendar. Here is where you can create new resources and set the scheduling policy for the resource.<br /> <br /> [[Image:3zimbraadminpanel.png]]<br /> <br /> <br /> ==Creating an Email Account== <br /> Select '''Manage''' and then '''Accounts''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the email mailbox you are about to create. Enter the following required information:<br /> <br /> * '''Account Name''': This will be the mailbox account that you are about to create. In this example, we are creating &quot;bobdobbs@xdesign.com.&quot;<br /> * '''First Name''': The first name of the email user. <br /> * '''Last Name''': The last name of the email user.<br /> [[Image:1zimbraaddaccount.png]]<br /> <br /> When creating a new mailbox account you will set the Class of Service (CoS) under '''General Information / Account Setup / Class of Service'''. Don't forget to deselect the &quot;[ ] auto&quot; box to enter the class type.<br /> <br /> You may mix and match Class of Service (CoS) for mailbox accounts in your domain to maximize benefits for your organization. Details below.<br /> <br /> Something to note, XMission identifies a billable Zimbra account as mailbox with a physical email Inbox and typically belonging to one person. So even if it is not &quot;active&quot; but still provisioned, it will count toward billing. Example, a mailbox set to &quot;closed&quot; or &quot;maintenance&quot; status remains billable.<br /> <br /> ==Class of Service==<br /> <br /> To '''upgrade''' an existing account, or to change existing accounts, simply log in to the admin interface, click on '''&quot;Manage&quot;''' and select the user by double-clicking on the name. Inside the '''&quot;General Information&quot;''' pane you will see '''&quot;Account Setup&quot;''' in the middle of the page. In this area you will find '''&quot;Class of Service&quot;''' with an input box next to it and the &quot;[x] auto&quot; box checked. Deselect the &quot;[ ] auto&quot; box and type '''&quot;xmpremium&quot;''' or '''&quot;xmbase&quot;''' in the field and then hit '''&quot;Save&quot;''' towards the top right of the window. Your account is now set to the selected service level with all the features and storage associated with the account type.<br /> <br /> Click the '''&quot;Finish&quot;''' button. You will be returned to the main admin screen, and the new account will have been created at the established service level.<br /> <br /> NOTE: If the &quot;Class of Service&quot; field is not available to you, you may need to add your admin account's email address to the &quot;admins&quot; distribution list on your domain and wait up to fifteen minutes. Some older accounts do not have this setup automatically. See [https://wiki.xmission.com/Zimbra_Hosting_Admin#Granting_Domain_Administrator_Access Granting Domain Administrator Access] for more details.<br /> <br /> ==Updating Account Information==<br /> To add, change, or remove information from an account, simply double-click the account you want to edit. Alternatively, you can right-click the account you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> ==Change Password==<br /> <br /> All Zimbra domain administrator should read this quick blog post on email security: https://xmission.com/blog/2017/10/17/best-practices-for-zimbra-email-security<br /> <br /> Changing your end-user mailbox password through the Zimbra [https://zimbraadmin.xmission.com domain admin control panel] is easy, but first let's review XMission password best practices.<br /> <br /> '''XMission Zimbra Password requirements:''' <br /> <br /> XMission recommends secure passphrases consisting of five to six words, with a few special characters and numbers, since they can be much easier to remember.<br /> <br /> * Ideally it is best to use longer, more complex passphrases to properly protect your mailboxes, and your company, from hackers. Our Zimbra system supports passwords up to 64 characters. We advise using a minimum passphrase length of 12-15 characters with 25-28 characters providing very reasonable security. <br /> * Shorter passwords require use of at least 1 of the following: UPPER CASE letter, lower case letter, special characters, and a numeral to meet minimum security requirements.<br /> * Passwords expire after 1 year and must be changed at that time. Changing more frequently is advised.<br /> * You cannot re-use your current password.<br /> * Please allow 15 minutes for the new password to propagate through the system.<br /> * Write credentials down in a secure place until you memorize it then destroy the note.<br /> * Here is a quick and easy to understand visual tutorial on password security: [https://xmission.com/blog/2017/10/17/best-practices-for-zimbra-email-security | https://xkcd.com/936/ ]<br /> <br /> '''Three ways to change passwords from domain admin control panel:'''<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column. Right-mouse click on the mailbox name to reveal a drop down menu, select &quot;Change password.&quot;<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column and highlight a mailbox. Now right-mouse click on the gear icon in the top right corner. Select &quot;Change password&quot;.<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column and double click on the desired mailbox. When it opens the settings page of the mailbox use the &quot;Password&quot; area to change the password.<br /> <br /> NOTE: XMission Zimbra servers will allow a password as short as 12 characters. Short passwords are poor security. Please take the time to protect your company email data buy using a passphrase in the 25-28 character length.<br /> <br /> ==Password Expiration and Failed Login Attempts==<br /> Please note the following details about XMission's email password expiration and failed login attempts policy.<br /> <br /> Should you ever have an end-user mailbox that is not allowing login there are two primary reasons for this. <br /> * The password has expired. <br /> * There have been too many failed login attempts to the account causing it to be temporarily suspended.<br /> <br /> ==== Expired Password ====<br /> <br /> All XMission email passwords must be changed once yearly. XMission sends email notices to the user mailbox 2 (two) weeks before expiration. Please ask your mailbox owners to change their password in a timely manner.<br /> <br /> Domain administrators are *not* emailed about the user mailbox need to change their password. Repeat, domain administrators are not emailed about password expirations.<br /> <br /> ==== Failed Login Attempt - Mailbox Access Suspension ====<br /> <br /> Failed login attempt account suspension practices are a way to safeguard mailboxes from brute force attacks where a bad actor is trying to access the sensitive information inside. XMission protects customer mailboxes by temporarily suspending mail accounts with too many failed login attempts. This prevents new logins and halts all access on active mail sessions. Incoming email is not restricted.<br /> <br /> If you, or another entity, are trying to access the account with too many failed password attempts within the monitoring cycle, the system blocks access for a short period of time, after which you can again attempt to authenticate with correct credentials.<br /> <br /> '''Failed login attempt definition:''' Improper entry of a password for a valid mailbox. <br /> <br /> '''How failed login attempts are measured and enforced:''' When the first failed login attempt occurs, the monitoring cycle begins. Thereafter, each time a unique wrong password fails, that adds to the count. <br /> <br /> It is important to note that when the ''same'' wrong password is used, from any number of IP addresses or devices, it only counts as one (1) failed login attempt.<br /> <br /> During the monitoring cycle, if additional failed login attempts are made using a different password from the original attempt, it add to the failed login attempt total. IE: Bad password &quot;A&quot; activates monitoring period. A second unique password &quot;B&quot; is used bringing the total to two (2) failed attempts. If password &quot;A&quot; is used again, it counts as another new unique password totaling three (3) failed attempts. <br /> <br /> Once the maximum number of failed attempts is reached, access to the mailbox is temporarily suspended.<br /> <br /> ==== Troubleshooting ====<br /> <br /> Mailbox accounts having failed login issues appear to have the same symptoms as an expired password. The way to test is to access webmail, https://zimbra.xmission.com, with your credentials. If the password is expired it will prompt you to set a new password immediately. If the account is locked out, it will simply not validate with the credentials until the suspension period ends.<br /> <br /> If an account is temporarily suspended for too many failed password attempts you need to either wait for the suspension period to pass, reset the mailbox status to active in the domain admin panel, or contact XMission Support to have the suspension manually removed.<br /> <br /> Domain administrators can change mailbox status and passwords via the domain admin interface.<br /> <br /> NOTE: Use of Two-Factor Authentication (2FA) does not prevent account suspension due to failed authentication attempts.<br /> <br /> ==Mailbox locked for abuse==<br /> <br /> A user mailbox can also be locked for abuse. This abuse can be due to any of the following reasons;<br /> * Successfully compromised by a phishing attempt and shared their password with someone they shouldn't have.<br /> * Use of a previously compromised password on another Internet site or service.<br /> * Malware on a computer or device.<br /> * Rootkit on the computer.<br /> <br /> ''Symptoms of abuse:''<br /> <br /> Domain administrators often ask why a mailbox was locked for a spam run when they do not see evidence of malicious messages in the Sent folder. The primary reason for this is because the spammers use SMTP mail applications that do not sync the Sent mail folder. Only messages sent via the Zimbra webmail interface, via Outlook with the Zimbra Connector, or sent via ActiveSync (Exchange) configuration on mobile devices, will sync Sent messages to the mail system. So a bad actor can send copious amounts of unwanted email quickly and with no trace the end user can see. However, XMission has logs for all messages sent which we use to identify and lock accounts as well as to train system rules to prevent future abuse. <br /> <br /> Determining why a mailbox has been locked for abuse can be difficult. XMission will do their best to provide data on what was compromised and how. In some cases this is possible, in others it is not. Most often phishing and re-used passwords are the primary attack vector resulting in a locked user mailbox.<br /> <br /> &quot;The remedy:&quot;<br /> <br /> Regardless of the &quot;how&quot; all compromised mailbox users are required to change their password immediately to continue using the service. It is imperative that domain administrators do not re-use passwords or set poor temporary passwords. <br /> <br /> We strongly advise in the use of long passwords (pass phrases) and password managers such as BitWarden, Keepass, and similar.<br /> <br /> Additional compromises of the same mailbox will result in a small fine which we hope is just enough to encourage proper mailbox security. You can read about this policy here: https://xmission.com/blog/2019/05/14/our-new-compromised-email-policy<br /> <br /> ==Creating an Alias==<br /> Select '''Manage''' and then '''Aliases''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the email alias you wish to create. Enter the following required information:<br /> <br /> *'''Alias''': This is the aliased address you will create. In this example, we are adding &quot;bob.dobbs@xdesign.com.&quot; <br /> *'''Target Account''': This is the actual email box that will receive any emails directed to the aliases address. <br /> [[Image:1zimbraaddalias.png]]<br /> <br /> <br /> Click &quot;Ok&quot; to add your new alias.<br /> <br /> <br /> ==Updating Alias Information==<br /> To add, change, or remove information from an alias, simply double-click the alias you want to edit. Alternatively, you can right-click the alias you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> <br /> ==Creating a Distribution List==<br /> Select '''Manage''' and then '''Distribution Lists''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the distribution list you wish to create. Enter the following required information:<br /> <br /> * '''List Name''': This will be the email address for the mailing list. <br /> * '''Display Name''': This can be a descriptive name for the list. <br /> <br /> [[Image:1zimbraaddlist.png]]<br /> <br /> <br /> To add email addresses to the list, scroll a bit to the right and you will see a &quot;Search&quot; button below the '''Add Members to this list''' section. If you want add email addresses that are withing your Zimbra package, search for the appropriate domain name(s). In this case, we searched for &quot;xdesign.com.&quot; Highlight any results you would like to be added to the list.<br /> <br /> [[Image:1zimbraaddmembers.png]]<br /> <br /> <br /> Using the scroll bar on the right, scroll down and click the &quot;Add Selected&quot; button. <br /> <br /> [[Image:2zimbraaddmembers.png]]<br /> <br /> <br /> If you want to manually add addresses or need to add addresses that are not within Zimbra's search function, you can type the email addresses in the box pictured below. In this case, we are adding two email addresses to the list -- &quot;bobdobbs@gmail.com&quot; and &quot;bigguyjake@xmission.com.&quot; Once you've typed in the email addresses you want added to your list, simply click the &quot;Add&quot; button below. <br /> <br /> [[Image:3zimbraaddmembers.png]]<br /> <br /> <br /> ''Notes:''<br /> <br /> You can make lists members of other lists. This is a handy way to create umbrella lists. For example, if you wanted a staff list, but had various departments, you could add your employees to the departmental list, and then subscribe the departmental lists to the staff lists. This way, an account is only entered once, rather than adding an account to each list individually.<br /> <br /> Distribution Lists can also be used to forward domain based emails. For example, you may need to forward ''project@yourdomain.com'' to ''address@someotherdomain.com''. This does not require a Zimbra account for the primary domain email address.<br /> <br /> <br /> ==Updating Distribution List information==<br /> To add, change, or remove information from a list, simply double-click the list you want to edit. Alternatively, you can right-click the list you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> <br /> ==Forwarding Email to Another Address==<br /> If you wish to forward emails sent to your hosted email to another email address, first select '''Manage''' and then '''Accounts.''' Double-click the account you wish to edit or right-click and choose '''Edit''' from the pop-up menu. <br /> <br /> To add a forward, click on the '''Forwarding''' section on the left-hand column. <br /> <br /> [[Image:1zimbraforward.png]]<br /> <br /> <br /> Enter the following required information:<br /> <br /> * '''User-specified forwarding address''': This will be the email account that emails are forwarded to that the account owner is aware of. In the example below, we will be forwarding emails to &quot;bob.dobbs@xmission.com.&quot; <br /> <br /> [[Image:2zimbraforward.png]]<br /> <br /> <br /> Don't forget to choose &quot;Save&quot; near the upper right hand corner after you've added the forwarding address!<br /> <br /> <br /> * '''Forwarding addresses hidden from the user''': This can be a list of email accounts that emails are forwarded to that the account owner is unaware of. To do this, first click the &quot;Add&quot; button located below the '''Forwarding addresses hidden from the user''' box. It will prompt you to enter an email address. After you've done so, simply click &quot;Ok.&quot; In the example below, we will be forwarding messages to &quot;bobdobbs@xmission.com.&quot;<br /> <br /> [[Image:3zimbraforward.png]]<br /> <br /> NOTE: You may also use Distribution Lists to forward domain based emails without needing an account for the specific address. For example, you may need to forward ''project@mydomain.com'' to ''johndoe@someotheremail.com''. The advantage of using a Distribution List is that you eliminate the costs associated with maintaining an account just for forwarding.<br /> <br /> ==Granting Domain Administrator Access==<br /> <br /> To grant an existing mailbox domain administrator privileges start by logging in to the admin interface. Next, select their account then double click to edit. Inside the General Information area, the second category down is &quot;Account Setup.&quot; Check the &quot;Administrator&quot; checkbox below &quot;Class of Service.&quot; Once checked, a field will appear below, &quot;Administrator role.&quot; Enter &quot;admins@yourdomain.com&quot;, replacing yourdomain.com with the domain you are granting access rights for. This will add the user to a distribution list, &quot;admins&quot;, on your domain, which grants the privileges.<br /> <br /> Click &quot;Save&quot; near top-right corner to complete the assignment of rights.<br /> <br /> Note that if the &quot;Administrator&quot; checkbox does not exist, you may need to add yourself to the &quot;admins&quot; distribution list manually and wait up to fifteen minutes.<br /> <br /> ==Importing Accounts from Exchange==<br /> <br /> This article has moved: https://wiki.xmission.com/Zimbra_Migration:_Exchange_Import_Wizard<br /> <br /> ==Deleting a Zimbra Mailbox==<br /> <br /> There are two fairly simple ways to properly delete a Zimbra mailbox from the XMission system. <br /> <br /> * Log into the Zimbra domain administration panel https://zimbraadmin.xmission.com and select the &quot;Manage&quot; area on the left. Once in the management area you simply highlight the mailbox and then right-mouse click to show the option menu. Select &quot;Delete&quot; and confirm the mailbox deletion request. <br /> <br /> * From inside the domain administration panel you may also highlight the mailbox name and then click on the gear wheel in the top right corner of the browser screen to display an options menu. Inside this menu select &quot;Delete&quot; and confirm the deletion request.<br /> <br /> Notes: <br /> * Changing mailbox status is not the same as deletion. All provisioned mailboxes are billable.<br /> * Deletion of a mail domain cannot be completed via the domain admin interface and requires contacting XMission billing department.<br /> * Be certain not to delete resource accounts such as galsync or distribution lists unless you know they are no longer needed. Doing so can impact mail performance.<br /> <br /> == Zimbra Themes ==<br /> <br /> You can see all the themes [https://wiki.xmission.com/Hosted_Email:_Admin_Panel/Zimbra_Themes here]<br /> <br /> <br /> [[Category:Zimbra|Admin Panel]]<br /> <br /> <br /> {{footer}}</div>

John https://wiki.xmission.com/index.php?title=Hosted_Email:Zimbra_Self-Service_Account_Recovery&diff=10947 2021-10-14T16:29:53Z

<p>John: </p> <hr /> <div>Zimbra business email users can recover their account by resetting their own passwords by using the &quot;Forgot Password&quot; link on Zimbra webmail login page. The process utilizes a recovery email address of the users choice; it doesn't have to be under the Zimbra domain, and can be a valid third party email address. <br /> <br /> == Setting Up Password Recovery Email ==<br /> <br /> There are two parts to the account recovery using Zimbra's password reset functionality. <br /> <br /> <br /> '''Step One:''' Establish the recovery email address. <br /> <br /> In the Zimbra web client (zimbra.xmission.com), go to '''Preferences &gt; Accounts''', and you'll find a new section called '''Password Recovery Account Settings'''. Enter a valid email for password recovery address and click &quot;Add Recovery Email.&quot; <br /> <br /> <br /> '''Step Two:''' Validate the recovery email address and save.<br /> <br /> Open your recovery address mailbox and retrieve the verification code. This verification code is only valid for 10 minutes. Return to the Zimbra webmail and enter the verification code in its field under the &quot;Password Recovery Account Settings&quot; section within 10 minutes of clicking the &quot;Add Recovery Email&quot; button. This should confirm the setting. Remember to hit &quot;Save&quot; when existing Zimbra webmail preferences.<br /> <br /> <br /> Your recovery process is now validated and established.<br /> <br /> NOTE: If you have a personal Zimbra email address ending @xmission.com you will not be able to use this feature to recover your account and instead will need to update your password using the tools found at https://xmission.com/control<br /> <br /> <br /> == Using Forgot Password to Reset Your Password ==<br /> <br /> Once a recovery email is setup, the Zimbra self-service password recovery can be used. <br /> <br /> To recover your Zimbra mailbox account you can click on the &quot;Forgot Password&quot; link on the Zimbra web client login page (zimbra.xmission.com). <br /> <br /> [[File:Zimbrapwrecov1.png]]<br /> <br /> <br /> Enter the full email address of the account you are trying to recover, then click the &quot;Submit&quot; button.<br /> <br /> [[File:Zimbrapwrecov2.png]]<br /> <br /> <br /> On the following page, click the &quot;Request Code&quot; button at the bottom of the box. This will send a code to your recovery email address. Like the verification code, this reset code is only valid for 10 minutes. <br /> <br /> [[File:Zimbrapwrecov3.png]]<br /> <br /> <br /> Open that address mailbox and retrieve the reset code which you will enter on the Zimbra webmail recovery form. The email will look like this:<br /> <br /> [[File:Zimbrapwrecov4.png]]<br /> <br /> <br /> Go back to the Zimbra webmail recovery form, and enter the reset code within 10 minutes of clicking the &quot;Request Code&quot; button from the previous page. Then click the &quot;Verify Code&quot; button. <br /> <br /> [[File:Zimbrapwrecov5.png]]<br /> <br /> <br /> On this page you can either choose to log into the web client directly, or you can choose to reset your password. We'll want to choose &quot;Reset Password&quot; for this example. <br /> <br /> [[File:Zimbrapwrecov6.png]]<br /> <br /> <br /> At this point you will be prompted to establish a new password. NOTE: Always create new secure passwords, never re-use passwords from other sites as they are likely compromised. Password managers make this process easy and will generate secure passwords for you. Once you have entered and confirmed your new password, click the &quot;Submit&quot; button to set it. <br /> <br /> [[File:Zimbrapwrecov7.png]]<br /> <br /> <br /> With that, your password has been reset! <br /> <br /> IMPORTANT: Remember to update all devices and applications that were using the previous password. This can include; email, calendars, contacts, tasks, notes, and files.</div>

John https://wiki.xmission.com/index.php?title=Hosted_Email:Zimbra_Self-Service_Account_Recovery&diff=10946 2021-10-12T23:24:47Z

<p>John: </p> <hr /> <div>Pending release 10/14/21 - Zimbra business email users can recover their account by resetting their own passwords by using the &quot;Forgot Password&quot; link on Zimbra webmail login page. The process utilizes a recovery email address of the users choice; it doesn't have to be under the Zimbra domain, and can be a valid third party email address. <br /> <br /> == Setting Up Password Recovery Email ==<br /> <br /> There are two parts to the account recovery using Zimbra's password reset functionality. <br /> <br /> <br /> '''Step One:''' Establish the recovery email address. <br /> <br /> In the Zimbra web client (zimbra.xmission.com), go to '''Preferences &gt; Accounts''', and you'll find a new section called '''Password Recovery Account Settings'''. Enter a valid email for password recovery address and click &quot;Add Recovery Email.&quot; <br /> <br /> <br /> '''Step Two:''' Validate the recovery email address and save.<br /> <br /> Open your recovery address mailbox and retrieve the verification code. This verification code is only valid for 10 minutes. Return to the Zimbra webmail and enter the verification code in its field under the &quot;Password Recovery Account Settings&quot; section within 10 minutes of clicking the &quot;Add Recovery Email&quot; button. This should confirm the setting. Remember to hit &quot;Save&quot; when existing Zimbra webmail preferences.<br /> <br /> <br /> Your recovery process is now validated and established.<br /> <br /> NOTE: If you have a personal Zimbra email address ending @xmission.com you will not be able to use this feature to recover your account and instead will need to update your password using the tools found at https://xmission.com/control<br /> <br /> <br /> == Using Forgot Password to Reset Your Password ==<br /> <br /> Once a recovery email is setup, the Zimbra self-service password recovery can be used. <br /> <br /> To recover your Zimbra mailbox account you can click on the &quot;Forgot Password&quot; link on the Zimbra web client login page (zimbra.xmission.com). <br /> <br /> [[File:Zimbrapwrecov1.png]]<br /> <br /> <br /> Enter the full email address of the account you are trying to recover, then click the &quot;Submit&quot; button.<br /> <br /> [[File:Zimbrapwrecov2.png]]<br /> <br /> <br /> On the following page, click the &quot;Request Code&quot; button at the bottom of the box. This will send a code to your recovery email address. Like the verification code, this reset code is only valid for 10 minutes. <br /> <br /> [[File:Zimbrapwrecov3.png]]<br /> <br /> <br /> Open that address mailbox and retrieve the reset code which you will enter on the Zimbra webmail recovery form. The email will look like this:<br /> <br /> [[File:Zimbrapwrecov4.png]]<br /> <br /> <br /> Go back to the Zimbra webmail recovery form, and enter the reset code within 10 minutes of clicking the &quot;Request Code&quot; button from the previous page. Then click the &quot;Verify Code&quot; button. <br /> <br /> [[File:Zimbrapwrecov5.png]]<br /> <br /> <br /> On this page you can either choose to log into the web client directly, or you can choose to reset your password. We'll want to choose &quot;Reset Password&quot; for this example. <br /> <br /> [[File:Zimbrapwrecov6.png]]<br /> <br /> <br /> At this point you will be prompted to establish a new password. NOTE: Always create new secure passwords, never re-use passwords from other sites as they are likely compromised. Password managers make this process easy and will generate secure passwords for you. Once you have entered and confirmed your new password, click the &quot;Submit&quot; button to set it. <br /> <br /> [[File:Zimbrapwrecov7.png]]<br /> <br /> <br /> With that, your password has been reset! <br /> <br /> IMPORTANT: Remember to update all devices and applications that were using the previous password. This can include; email, calendars, contacts, tasks, notes, and files.</div>

John https://wiki.xmission.com/index.php?title=File:Zimbrapwrecov8.png&diff=10945 2021-10-12T22:53:54Z

<p>John: Zimbra Account Recovery - Forgot Password - Verification Code incorrect</p> <hr /> <div>Zimbra Account Recovery - Forgot Password - Verification Code incorrect</div>

John https://wiki.xmission.com/index.php?title=File:Zimbrapwrecov7.png&diff=10944 2021-10-12T22:53:11Z

<p>John: Zimbra Account Recovery - Forgot Password - Confirm reset password REMEMBER to update your new password in all applications and devices.</p> <hr /> <div>Zimbra Account Recovery - Forgot Password - Confirm reset password<br /> REMEMBER to update your new password in all applications and devices.</div>

John https://wiki.xmission.com/index.php?title=File:Zimbrapwrecov6.png&diff=10943 2021-10-12T22:52:20Z

<p>John: Zimbra Account Recovery - Forgot Password - Reset Password button</p> <hr /> <div>Zimbra Account Recovery - Forgot Password - Reset Password button</div>

John https://wiki.xmission.com/index.php?title=File:Zimbrapwrecov5.png&diff=10942 2021-10-12T22:51:42Z

<p>John: Zimbra Account Recovery - Forgot Password - Verify Code</p> <hr /> <div>Zimbra Account Recovery - Forgot Password - Verify Code</div>

John https://wiki.xmission.com/index.php?title=File:Zimbrapwrecov4.png&diff=10941 2021-10-12T22:51:05Z

<p>John: Zimbra Account Recovery - Forgot Password - Recovery address verification code.</p> <hr /> <div>Zimbra Account Recovery - Forgot Password - Recovery address verification code.</div>

John https://wiki.xmission.com/index.php?title=File:Zimbrapwrecov3.png&diff=10940 2021-10-12T22:50:25Z

<p>John: Zimbra Account Recovery - Password reset - Request Code</p> <hr /> <div>Zimbra Account Recovery - Password reset - Request Code</div>

John https://wiki.xmission.com/index.php?title=File:Zimbrapwrecov2.png&diff=10939 2021-10-12T22:49:37Z

<p>John: Zimbra Account Recovery - Forgot Password - enter username</p> <hr /> <div>Zimbra Account Recovery - Forgot Password - enter username</div>

John https://wiki.xmission.com/index.php?title=File:Zimbrapwrecov1.png&diff=10938 2021-10-12T22:48:58Z

<p>John: Zimbra Account Recovery using Forgot Password</p> <hr /> <div>Zimbra Account Recovery using Forgot Password</div>

John https://wiki.xmission.com/index.php?title=Hosted_Email:Zimbra_Self-Service_Account_Recovery&diff=10937 2021-10-12T22:43:36Z

<p>John: Zimbra Self-Service Account Recovery, Forgot Password, Password Reset, Zimbra Password, Change Zimbra Password</p> <hr /> <div>Zimbra business email users can recover their account by resetting their own passwords by using the &quot;Forgot Password&quot; link on Zimbra webmail login page. The process utilizes a recovery email address of the users choice; it doesn't have to be under the Zimbra domain, and can be a valid third party email address. <br /> <br /> == Setting Up Password Recovery Email ==<br /> <br /> There are two parts to the account recovery using Zimbra's password reset functionality. <br /> <br /> <br /> '''Step One:''' Establish the recovery email address. <br /> <br /> In the Zimbra web client (zimbra.xmission.com), go to '''Preferences &gt; Accounts''', and you'll find a new section called '''Password Recovery Account Settings'''. Enter a valid email for password recovery address and click &quot;Add Recovery Email.&quot; <br /> <br /> <br /> '''Step Two:''' Validate the recovery email address and save.<br /> <br /> Open your recovery address mailbox and retrieve the verification code. This verification code is only valid for 10 minutes. Return to the Zimbra webmail and enter the verification code in its field under the &quot;Password Recovery Account Settings&quot; section within 10 minutes of clicking the &quot;Add Recovery Email&quot; button. This should confirm the setting. Remember to hit &quot;Save&quot; when existing Zimbra webmail preferences.<br /> <br /> <br /> Your recovery process is now validated and established.<br /> <br /> NOTE: If you have a personal Zimbra email address ending @xmission.com you will not be able to use this feature to recover your account and instead will need to update your password using the tools found at https://xmission.com/control<br /> <br /> <br /> == Using Forgot Password to Reset Your Password ==<br /> <br /> Once a recovery email is setup, the Zimbra self-service password recovery can be used. <br /> <br /> To recover your Zimbra mailbox account you can click on the &quot;Forgot Password&quot; link on the Zimbra web client login page (zimbra.xmission.com). <br /> <br /> [[File:Zimbrapwrecov1.png]]<br /> <br /> <br /> Enter the full email address of the account you are trying to recover, then click the &quot;Submit&quot; button.<br /> <br /> [[File:Zimbrapwrecov2.png]]<br /> <br /> <br /> On the following page, click the &quot;Request Code&quot; button at the bottom of the box. This will send a code to your recovery email address. Like the verification code, this reset code is only valid for 10 minutes. <br /> <br /> [[File:Zimbrapwrecov3.png]]<br /> <br /> <br /> Open that address mailbox and retrieve the reset code which you will enter on the Zimbra webmail recovery form. The email will look like this:<br /> <br /> [[File:Zimbrapwrecov4.png]]<br /> <br /> <br /> Go back to the Zimbra webmail recovery form, and enter the reset code within 10 minutes of clicking the &quot;Request Code&quot; button from the previous page. Then click the &quot;Verify Code&quot; button. <br /> <br /> [[File:Zimbrapwrecov5.png]]<br /> <br /> <br /> On this page you can either choose to log into the web client directly, or you can choose to reset your password. We'll want to choose &quot;Reset Password&quot; for this example. <br /> <br /> [[File:Zimbrapwrecov6.png]]<br /> <br /> <br /> At this point you will be prompted to establish a new password. NOTE: Always create new secure passwords, never re-use passwords from other sites as they are likely compromised. Password managers make this process easy and will generate secure passwords for you. Once you have entered and confirmed your new password, click the &quot;Submit&quot; button to set it. <br /> <br /> [[File:Zimbrapwrecov7.png]]<br /> <br /> <br /> With that, your password has been reset! <br /> <br /> IMPORTANT: Remember to update all devices and applications that were using the previous password. This can include; email, calendars, contacts, tasks, notes, and files.</div>

John https://wiki.xmission.com/index.php?title=Main_Page&diff=10936 2021-10-12T22:37:37Z

<p>John: Adding Zimbra Account recovery via Forgot Password feature.</p> <hr /> <div>__NOTOC__ __NOEDITSECTION__ <br /> {| width=&quot;100%&quot; style=&quot;vertical-align:top&quot;<br /> &lt;div style=&quot;margin: 0; margin-right:10px; border: 2px solid 004,209,252; padding: 0 1em 1em 1em; background-color:#ffffff; text-align:left;&quot;&gt;<br /> &lt;h1 class=&quot;superHeader blue&quot;&gt;[[File:support.png]]XMission Support Wiki&lt;/h1&gt;<br /> '''Welcome to XMission Support Wiki. We have documentation for may of our products. If you cannot find what you need please feel free to check out our [http://wiki.xmission.com/Category:Troubleshooting Troubleshooting Page]. You can also [http://xmission.com/contact/ contact our technical support team].'''<br /> &lt;/div&gt;<br /> {| width=&quot;100%&quot; class=&quot;padding-control&quot;<br /> | width=&quot;50%&quot; style=&quot;vertical-align:top&quot; |<br /> &lt;div style=&quot;margin: 0; margin-right:15px; padding: 17px; background-color:#c0ebf4; height:230px;&quot;&gt;<br /> ==&lt;div style=&quot;background-color:#03afd3; color:white; margin:-1em; padding:1em; font-family:Arvo;&quot;&gt;Top Support Issues&lt;/div&gt;==<br /> * [[UTOPIA Setup | &lt;span style=&quot;color:#1c1f22;&quot;&gt;UTOPIA Router Configuration&lt;/span&gt;]]<br /> * [[Hosted_Email:Zimbra_Self-Service_Account_Recovery | &lt;span style=&quot;color:#1c1f22;&quot;&gt; Reset your forgotten Zimbra email password&lt;/span&gt;]]<br /> * [[Hosted_Email:_Admin_Panel#Change_Password | &lt;span style=&quot;color:#1c1f22;&quot;&gt;Zimbra Password Change&lt;/span&gt;]] (Domain Admin)<br /> * [[Zimbra Email Client Configurations | &lt;span style=&quot;color:#1c1f22;&quot;&gt;Zimbra Email Client Configuration&lt;/span&gt;]]<br /> * [[Passwords |&lt;span style=&quot;color:#1c1f22;&quot;&gt;How do I change my password?&lt;/span&gt;]]<br /> * [[Spam | &lt;span style=&quot;color:#1c1f22;&quot;&gt;Spam&lt;/span&gt;]]<br /> * [[Account_Home |&lt;span style=&quot;color:#1c1f22;&quot;&gt;How do I pay my bill?&lt;/span&gt;]]<br /> * [[Webmail | &lt;span style=&quot;color:#1c1f22;&quot;&gt;Webmail Support&lt;/span&gt;]]<br /> * [[Speedtest | &lt;span style=&quot;color:#1c1f22;&quot;&gt;Speed Concerns&lt;/span&gt;]]<br /> * [[Router and Wireless Troubleshooting | &lt;span style=&quot;color:#1c1f22;&quot;&gt;Router and Wireless Troubleshooting&lt;/span&gt;]]<br /> &lt;/div&gt;&lt;br&gt; <br /> &lt;div style=&quot;margin: 0; margin-right:15px; padding: 17px; background-color:#ffd9c4; height:170px&quot;&gt;<br /> ==&lt;div style=&quot;background-color:#ee4b00; color:white; margin:-1em; padding:1em; font-family:Arvo;&quot;&gt;Popular Articles&lt;/div&gt;==<br /> *[[Email|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Email&lt;/span&gt;]]<br /> *[[Connections|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Connections&lt;/span&gt;]]<br /> *[[Zimbra Domain Email and Collaboration Suite|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Zimbra Domain Email and Collaboration Suite&lt;/span&gt;]]<br /> *[[Proxy|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Proxy&lt;/span&gt;]]<br /> *[[General Email Settings|&lt;span style=&quot;color:#1c1f22;&quot;&gt;General Email Settings&lt;/span&gt;]]<br /> *[[Client Configuration for @XMission.com Email|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Client Configuration for @XMission.com Email&lt;/span&gt;]]<br /> &lt;/div&gt;&lt;br&gt;<br /> &lt;div style=&quot;margin: 0; margin-right:15px; padding: 17px; background-color:#eff5ce; height:140px;&quot;&gt;<br /> ==&lt;div style=&quot;background-color:#b3ca37; color:white; margin:-1em; padding:1em; font-family:Arvo;&quot;&gt;Top Categories&lt;/div&gt;==<br /> *[[Connections|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Connections&lt;/span&gt;]]<br /> *[[Email|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Email&lt;/span&gt;]]<br /> *[[Hosting|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Hosting&lt;/span&gt;]]<br /> *[[XMission_Voice|&lt;span style=&quot;color:#1c1f22;&quot;&gt;XMission Voice&lt;/span&gt;]]<br /> *[[XMission_Services|&lt;span style=&quot;color:#1c1f22;&quot;&gt;XMission Services&lt;/span&gt;]]<br /> &lt;/div&gt;&lt;br&gt;<br /> | width=&quot;50%&quot; style=&quot;vertical-align:top&quot; |<br /> &lt;div style=&quot;margin: 0; margin-right:15px; padding: 17px; background-color:#eff5ce; height:230px;&quot;&gt;<br /> ==&lt;div style=&quot;background-color:#b3ca37; color:white; margin:-1em; padding:1em; font-family:Arvo;&quot;&gt;About XMission&lt;/div&gt;==<br /> If you're just starting out, these links are recommended reading:<br /> *[[Announcements|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Announcements&lt;/span&gt;]]<br /> *[[Banners|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Banners&lt;/span&gt;]]<br /> *[[Account_Home|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Billing&lt;/span&gt;]]<br /> *[[Domains|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Domains&lt;/span&gt;]]<br /> *[[Logos|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Logos&lt;/span&gt;]]<br /> *[[:Category:Getting_Started|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Getting Started&lt;/span&gt;]]<br /> *[[Introduction|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Introduction&lt;/span&gt;]]<br /> *[[Quickstart|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Quickstart&lt;/span&gt;]]<br /> &lt;/div&gt;&lt;br&gt;<br /> &lt;div style=&quot;margin: 0; margin-right:15px; padding: 17px; background-color:#dddedf; height:170px&quot;&gt;<br /> ==&lt;div style=&quot;background-color:#717475; color:white; margin:-1em; padding:1em; font-family:Arvo;&quot;&gt;Troubleshooting&lt;/div&gt;==<br /> * [[How_to_use_ssh_keys|&lt;span style=&quot;color:#1c1f22;&quot;&gt;How to use ssh keys&lt;/span&gt;]]<br /> * [[Cloud_Hosting|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Cloud Hosting&lt;/span&gt;]]<br /> * [[Shared Hosting| &lt;span style=&quot;color:#1c1f22;&quot;&gt;Shared Hosting&lt;/span&gt;]]<br /> * [[Router and Wireless Troubleshooting|&lt;span style=&quot;color:#1c1f22;&quot;&gt;Router and Wireless Troubleshooting&lt;/span&gt;]]<br /> * [[DansGuardian_Setup|&lt;span style=&quot;color:#1c1f22;&quot;&gt;DansGuardian Setup - Content Filtering&lt;/span&gt;]]<br /> * [[:Category:Security| &lt;span style=&quot;color:#1c1f22;&quot;&gt;Security&lt;/span&gt;]]<br /> &lt;/div&gt;&lt;br&gt;<br /> &lt;div style=&quot;margin: 0; margin-right:15px; padding: 17px; background-color:#f1f2f2; height:140px&quot;&gt;<br /> ==&lt;div style=&quot;background-color:#acb0b2; color:white; margin:-1em; padding:1em; font-family:Arvo;&quot;&gt;Contact Us&lt;/div&gt;==<br /> {|<br /> |[[File:Phone.png|link=]] [[File:Mail.png|link=mailto:support@xmission.com|alt=&quot;Contact us via E-Mail!&quot;]] [[File:Live-support-2.png|link=https://livesupport.xmission.com|alt=&quot;Contact us via Live Support!&quot;]] [[File:Twitter.png|link=http://twitter.com/#!/xmission|alt=&quot;Check out our Twitter feed!&quot;]] [[File:Facebook.png|link=https://www.facebook.com/pages/XMission/6155383019|alt=&quot;Find us on Facebook!&quot;]]<br /> |-<br /> | &lt;div style=&quot;font-size:13px; color:#777; line-height:160%; width:250px;&quot;&gt;Our live technical support is available for you 24/7 at &lt;b&gt;801.539.0852&lt;/b&gt; or&lt;br /&gt; &lt;b&gt;877.XMISSION&lt;/b&gt; (877.964.7746)<br /> &lt;/div&gt;<br /> |}<br /> &lt;/div&gt;&lt;br&gt;<br /> &lt;div style=&quot;position:absolute; top:475px; left:-194px; width:160px; height:420px;&quot;&gt;[[File:Zimbra-wiki-ad.png|link=http://xmission.com/email_collaboration?cid=wikibanner1]]&lt;/div&gt;<br /> |}<br /> <br /> [[Category: Getting Started]]</div>

John https://wiki.xmission.com/index.php?title=Announcements&diff=10935 2021-09-27T19:57:02Z

<p>John: Added links to Twitter and Status.XM page.</p> <hr /> <div>==XMission Status Updates==<br /> Since 2020 XMission has been posting issues and notices to our https://twitter.com/xmissionstatus Twitter feed and on our real-time System Status page, https://status.xmission.com. We encourage all customers to follow the above notification systems to stay up to date. From time to time XMission will still send larger announcements to subscribers as necessary and the archive will remain publicly available. <br /> <br /> ==Why do XMission customers get announcements?== <br /> XMission believes in full disclosure to our clients. Not only do we think that our customers deserve to know about things that may have gone wrong or are changing with the service they're paying for, but it also saves time troubleshooting an issue that may not have been local.<br /> <br /> Announcements will also be sent if enhancements to our services or additional services are made available. Often, XMission will add a service or change the pricing for an existing service. By reading the announcements, customers can learn that a service they may have been waiting for is now available or even learn that they'll soon be saving money by using a newly available account type. <br /> <br /> <br /> ==Doesn't it make XMission look bad when things go wrong?== <br /> Quite to the contrary. All ISP's have technical problems from time to time as there is no way to avoid it. We simply do our best to fully disclose problems when they arise, even as we do our best to minimize the problems themselves. XMission often receives praise from our customers because we fully disclose problems in a timely manner.<br /> <br /> <br /> ==How can I get announcements via email?== <br /> By default, all customers automatically get announcements sent to the technical contact for their account. This can be changed by contacting XMission's accounting department via phone (in Salt Lake at 801-539-0852, or toll free at 877-964-7746) or email at [mailto:accounting@xmission.com accounting@xmission.com].<br /> <br /> <br /> ==Can I get announcements if I use IMAP?== <br /> Yes. Announcements are now simply sent to the mailbox of each account's technical contact. It is no longer necessary to receive them via POP or the alternative mailing list. <br /> <br /> <br /> ==Can I unsubscribe from the announcements list?== <br /> Although announcements are sent with our customers' best interest in mind (they help save time, frustration, and sometimes even money), XMission does allow people to &quot;unsubscribe.&quot; We highly recommend that you continue to receive them though, since they are rarely sent and provide very helpful information. To help keep the inconvenience some customers may feel to an absolute minimum, each announcement starts with a very short overview, followed by details. By skimming the overview, it can be easy to tell if it concerns you. <br /> <br /> If you have received an announcement from us already, please follow the link at the bottom of that message to stop receiving announcements. If you want to start receiving announcements again or want to stop them and don't have a current announcement you can unsubscribe with, please contact our accounting department during business hours at (801) 539-0852<br /> <br /> ==Where can I see an archive of announcements?== <br /> [https://xmission.com/announcements Here.]<br /> <br /> <br /> [[Category:About|Announcements]]<br /> [[Category:FAQ|Announcements]]<br /> [[Category:Getting Started]]</div>

John https://wiki.xmission.com/index.php?title=Hosted_Email:_Admin_Panel&diff=10904 2021-08-09T18:32:07Z

<p>John: /* Failed Login Attempt - Mailbox Access Suspension */</p> <hr /> <div>==Overview/Logging In== <br /> The Zimbra domain administration console is the browser-based user interface used to centrally manage user accounts and most settings.<br /> <br /> As a domain administrator, you will be able to create and maintain the following:<br /> <br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_an_Email_Account Email accounts]<br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_an_Alias Mailbox aliases]<br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_a_Distribution_List Distribution lists]<br /> *Resources<br /> <br /> To login to the domain administration console, go to https://zimbraadmin.xmission.com/ and login with your administrative username and password. Domain administrators can also login from the dropdown menu next to your mailbox name in the top right corner of the webmail session. Click on 'Admin Console' to proceed.<br /> <br /> ==Domain Administrator Responsibilities==<br /> <br /> It is important to understand that as domain administrators you are responsible for changing passwords, creating distribution lists, setting email forwards, managing mailboxes, training on phishing, and etc. Our support policy for email is clearly outlined at: https://xmission.com/legal_policies#emlsup We require domain administrators be added as Technical contacts on your billing account in order to receive advanced assistance from our support staff. Please keep contacts up-to-date in the [https://xmission.com/control account management portal] or contact [https://xmission.com/contact XMission Billing] for assistance.<br /> <br /> Phishing and email scams are on the rise. It is important to educate yourself and your mailbox holders on how to avoid it. Reference this guide on <br /> [https://wiki.xmission.com/Phishing_and_Email_Scams understanding phishing].<br /> <br /> ==Email Domain Health==<br /> <br /> An important part of effective business email mean protecting your domain with some simple settings to improve delivery and reduce fraud.<br /> <br /> XMission advises implementing SPF and DKIM on domains. These are two simple methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf and prevent abuse. [https://wiki.xmission.com/SPF_and_DKIM How to configure SPF and DKIM]<br /> <br /> ==About the Administrative Console==<br /> <br /> The area above the '''Content''' pane includes the '''Search''' and '''Help''' functions.<br /> <br /> '''Search''' allows you to quickly find accounts, aliases, distribution lists and resources for editing. <br /> <br /> '''Help''' utilizes Zimbra’s wiki, forums, and documentation. This is a powerful unified search to quickly find answers to common questions.<br /> <br /> [[Image:1zimbraadminpanel.png]]<br /> <br /> <br /> <br /> The '''Navigation''' pane on the left includes the following sections:<br /> <br /> *'''Home:''' At any time, clicking here will return you to the administrative Home options. <br /> <br /> *'''Manage:''' Clicking here will permit you to create and edit any accounts, aliases, distribution lists, and resources for your domain(s). <br /> <br /> *'''Help:''' utilizes Zimbra’s wiki, forums, and documentation. This is a powerful unified search to quickly find answers to common questions. <br /> <br /> [[Image:4zimbraadminpanel.png]]<br /> <br /> <br /> <br /> Alternatively, you can also click on the arrow beside the &quot;Home&quot; button. This will give you the same options listed above, as well as recent searches and the options available under &quot;Manage.&quot; In this example, the recent search was for &quot;xdesign.com.&quot;<br /> <br /> [[Image:2zimbraadminpanel.png]]<br /> <br /> <br /> <br /> Clicking on &quot;Manage&quot; either way will permit you to make changes to your existing accounts, aliases, distribution lists, and resources.<br /> <br /> *'''Accounts:''' Lists all accounts. In the Accounts folder, you create and manage end-user accounts, setting options, class of service, passwords and aliases for an account.<br /> <br /> *'''Aliases:''' Lists all aliases that have been created in Accounts. You can use the Move Alias feature from the toolbar to move an alias from one account to another.<br /> <br /> *'''Distribution Lists:''' Lists all distribution lists. You can create new distribution lists and add or delete members of a distribution list.<br /> <br /> *'''Resources:''' This lists locations or equipment that can be scheduled from your Calendar. Here is where you can create new resources and set the scheduling policy for the resource.<br /> <br /> [[Image:3zimbraadminpanel.png]]<br /> <br /> <br /> ==Creating an Email Account== <br /> Select '''Manage''' and then '''Accounts''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the email mailbox you are about to create. Enter the following required information:<br /> <br /> * '''Account Name''': This will be the mailbox account that you are about to create. In this example, we are creating &quot;bobdobbs@xdesign.com.&quot;<br /> * '''First Name''': The first name of the email user. <br /> * '''Last Name''': The last name of the email user.<br /> [[Image:1zimbraaddaccount.png]]<br /> <br /> When creating a new mailbox account you will set the Class of Service (CoS) under '''General Information / Account Setup / Class of Service'''. Don't forget to deselect the &quot;[ ] auto&quot; box to enter the class type.<br /> <br /> You may mix and match Class of Service (CoS) for mailbox accounts in your domain to maximize benefits for your organization. Details below.<br /> <br /> Something to note, XMission identifies a billable Zimbra account as mailbox with a physical email Inbox and typically belonging to one person. So even if it is not &quot;active&quot; but still provisioned, it will count toward billing. Example, a mailbox set to &quot;closed&quot; or &quot;maintenance&quot; status remains billable.<br /> <br /> ==Class of Service==<br /> <br /> To '''upgrade''' an existing account, or to change existing accounts, simply log in to the admin interface, click on '''&quot;Manage&quot;''' and select the user by double-clicking on the name. Inside the '''&quot;General Information&quot;''' pane you will see '''&quot;Account Setup&quot;''' in the middle of the page. In this area you will find '''&quot;Class of Service&quot;''' with an input box next to it and the &quot;[x] auto&quot; box checked. Deselect the &quot;[ ] auto&quot; box and type '''&quot;xmpremium&quot;''' or '''&quot;xmbase&quot;''' in the field and then hit '''&quot;Save&quot;''' towards the top right of the window. Your account is now set to the selected service level with all the features and storage associated with the account type.<br /> <br /> Click the '''&quot;Finish&quot;''' button. You will be returned to the main admin screen, and the new account will have been created at the established service level.<br /> <br /> NOTE: If the &quot;Class of Service&quot; field is not available to you, you may need to add your admin account's email address to the &quot;admins&quot; distribution list on your domain and wait up to fifteen minutes. Some older accounts do not have this setup automatically. See [https://wiki.xmission.com/Zimbra_Hosting_Admin#Granting_Domain_Administrator_Access Granting Domain Administrator Access] for more details.<br /> <br /> ==Updating Account Information==<br /> To add, change, or remove information from an account, simply double-click the account you want to edit. Alternatively, you can right-click the account you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> ==Change Password==<br /> <br /> All Zimbra domain administrator should read this quick blog post on email security: https://xmission.com/blog/2017/10/17/best-practices-for-zimbra-email-security<br /> <br /> Changing your end-user mailbox password through the Zimbra [https://zimbraadmin.xmission.com domain admin control panel] is easy, but first let's review XMission password best practices.<br /> <br /> '''XMission Zimbra Password requirements:''' <br /> <br /> XMission recommends secure passphrases consisting of five to six words, with a few special characters and numbers, since they can be much easier to remember.<br /> <br /> * Ideally it is best to use longer, more complex passphrases to properly protect your mailboxes, and your company, from hackers. Our Zimbra system supports passwords up to 64 characters. We advise using a minimum passphrase length of 12-15 characters with 25-28 characters providing very reasonable security. <br /> * Shorter passwords require use of at least 1 of the following: UPPER CASE letter, lower case letter, special characters, and a numeral to meet minimum security requirements.<br /> * Passwords expire after 1 year and must be changed at that time. Changing more frequently is advised.<br /> * You cannot re-use your current password.<br /> * Please allow 15 minutes for the new password to propagate through the system.<br /> * Write credentials down in a secure place until you memorize it then destroy the note.<br /> * Here is a quick and easy to understand visual tutorial on password security: [https://xmission.com/blog/2017/10/17/best-practices-for-zimbra-email-security | https://xkcd.com/936/ ]<br /> <br /> '''Three ways to change passwords from domain admin control panel:'''<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column. Right-mouse click on the mailbox name to reveal a drop down menu, select &quot;Change password.&quot;<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column and highlight a mailbox. Now right-mouse click on the gear icon in the top right corner. Select &quot;Change password&quot;.<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column and double click on the desired mailbox. When it opens the settings page of the mailbox use the &quot;Password&quot; area to change the password.<br /> <br /> NOTE: XMission Zimbra servers will allow a password as short as 12 characters. Short passwords are poor security. Please take the time to protect your company email data buy using a passphrase in the 25-28 character length.<br /> <br /> ==Password Expiration and Failed Login Attempts==<br /> Please note the following details about XMission's email password expiration and failed login attempts policy.<br /> <br /> Should you ever have an end-user mailbox that is not allowing login there are two primary reasons for this. <br /> * The password has expired. <br /> * There have been too many failed login attempts to the account causing it to be temporarily suspended.<br /> <br /> ==== Expired Password ====<br /> <br /> All XMission email passwords must be changed once yearly. XMission sends email notices to the user mailbox 2 (two) weeks before expiration. Please ask your mailbox owners to change their password in a timely manner.<br /> <br /> Domain administrators are *not* emailed about the user mailbox need to change their password. Repeat, domain administrators are not emailed about password expirations.<br /> <br /> ==== Failed Login Attempt - Mailbox Access Suspension ====<br /> <br /> Failed login attempt account suspension practices are a way to safeguard mailboxes from brute force attacks where a bad actor is trying to access the sensitive information inside. XMission protects customer mailboxes by temporarily suspending mail accounts with too many failed login attempts. This prevents new logins and halts all access on active mail sessions. Incoming email is not restricted.<br /> <br /> If you, or another entity, are trying to access the account with too many failed password attempts within the monitoring cycle, the system blocks access for a short period of time, after which you can again attempt to authenticate with correct credentials.<br /> <br /> '''Failed login attempt definition:''' Improper entry of a password for a valid mailbox. <br /> <br /> '''How failed login attempts are measured and enforced:''' When the first failed login attempt occurs, the monitoring cycle begins. Thereafter, each time a unique wrong password fails, that adds to the count. <br /> <br /> It is important to note that when the ''same'' wrong password is used, from any number of IP addresses or devices, it only counts as one (1) failed login attempt.<br /> <br /> During the monitoring cycle, if additional failed login attempts are made using a different password from the original attempt, it add to the failed login attempt total. IE: Bad password &quot;A&quot; activates monitoring period. A second unique password &quot;B&quot; is used bringing the total to two (2) failed attempts. If password &quot;A&quot; is used again, it counts as another new unique password totaling three (3) failed attempts. <br /> <br /> Once the maximum number of failed attempts is reached, access to the mailbox is temporarily suspended.<br /> <br /> ==== Troubleshooting ====<br /> <br /> Mailbox accounts having failed login issues appear to have the same symptoms as an expired password. The way to test is to access webmail, https://zimbra.xmission.com, with your credentials. If the password is expired it will prompt you to set a new password immediately. If the account is locked out, it will simply not validate with the credentials until the suspension period ends.<br /> <br /> If an account is temporarily suspended for too many failed password attempts you need to either wait for the suspension period to pass, reset the mailbox status to active in the domain admin panel, or contact XMission Support to have the suspension manually removed.<br /> <br /> Domain administrators can change mailbox status and passwords via the domain admin interface.<br /> <br /> NOTE: Use of Two-Factor Authentication (2FA) does not prevent account suspension due to failed authentication attempts.<br /> <br /> ==Mailbox locked for abuse==<br /> <br /> A user mailbox can also be locked for abuse. This abuse can be due to any of the following reasons;<br /> * Successfully compromised by a phishing attempt and shared their password with someone they shouldn't have.<br /> * Use of a previously compromised password on another Internet site or service.<br /> * Malware on a computer or device.<br /> * Rootkit on the computer.<br /> <br /> ''Symptoms of abuse:''<br /> <br /> Domain administrators often ask why a mailbox was locked for a spam run when they do not see evidence of malicious messages in the Sent folder. The primary reason for this is because the spammers use SMTP mail applications that do not sync the Sent mail folder. Only messages sent via the Zimbra webmail interface, via Outlook with the Zimbra Connector, or sent via ActiveSync (Exchange) configuration on mobile devices, will sync Sent messages to the mail system. So a bad actor can send copious amounts of unwanted email quickly and with no trace the end user can see. However, XMission has logs for all messages sent which we use to identify and lock accounts as well as to train system rules to prevent future abuse. <br /> <br /> Determining why a mailbox has been locked for abuse can be difficult. XMission will do their best to provide data on what was compromised and how. In some cases this is possible, in others it is not. Most often phishing and re-used passwords are the primary attack vector resulting in a locked user mailbox.<br /> <br /> &quot;The remedy:&quot;<br /> <br /> Regardless of the &quot;how&quot; all compromised mailbox users are required to change their password immediately to continue using the service. It is imperative that domain administrators do not re-use passwords or set poor temporary passwords. <br /> <br /> We strongly advise in the use of long passwords (pass phrases) and password managers such as BitWarden, Keepass, and similar.<br /> <br /> Additional compromises of the same mailbox will result in a small fine which we hope is just enough to encourage proper mailbox security. You can read about this policy here: https://xmission.com/blog/2019/05/14/our-new-compromised-email-policy<br /> <br /> ==Creating an Alias==<br /> Select '''Manage''' and then '''Aliases''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the email alias you wish to create. Enter the following required information:<br /> <br /> *'''Alias''': This is the aliased address you will create. In this example, we are adding &quot;bob.dobbs@xdesign.com.&quot; <br /> *'''Target Account''': This is the actual email box that will receive any emails directed to the aliases address. <br /> [[Image:1zimbraaddalias.png]]<br /> <br /> <br /> Click &quot;Ok&quot; to add your new alias.<br /> <br /> <br /> ==Updating Alias Information==<br /> To add, change, or remove information from an alias, simply double-click the alias you want to edit. Alternatively, you can right-click the alias you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> <br /> ==Creating a Distribution List==<br /> Select '''Manage''' and then '''Distribution Lists''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the distribution list you wish to create. Enter the following required information:<br /> <br /> * '''List Name''': This will be the email address for the mailing list. <br /> * '''Display Name''': This can be a descriptive name for the list. <br /> <br /> [[Image:1zimbraaddlist.png]]<br /> <br /> <br /> To add email addresses to the list, scroll a bit to the right and you will see a &quot;Search&quot; button below the '''Add Members to this list''' section. If you want add email addresses that are withing your Zimbra package, search for the appropriate domain name(s). In this case, we searched for &quot;xdesign.com.&quot; Highlight any results you would like to be added to the list.<br /> <br /> [[Image:1zimbraaddmembers.png]]<br /> <br /> <br /> Using the scroll bar on the right, scroll down and click the &quot;Add Selected&quot; button. <br /> <br /> [[Image:2zimbraaddmembers.png]]<br /> <br /> <br /> If you want to manually add addresses or need to add addresses that are not within Zimbra's search function, you can type the email addresses in the box pictured below. In this case, we are adding two email addresses to the list -- &quot;bobdobbs@gmail.com&quot; and &quot;bigguyjake@xmission.com.&quot; Once you've typed in the email addresses you want added to your list, simply click the &quot;Add&quot; button below. <br /> <br /> [[Image:3zimbraaddmembers.png]]<br /> <br /> <br /> ''Notes:''<br /> <br /> You can make lists members of other lists. This is a handy way to create umbrella lists. For example, if you wanted a staff list, but had various departments, you could add your employees to the departmental list, and then subscribe the departmental lists to the staff lists. This way, an account is only entered once, rather than adding an account to each list individually.<br /> <br /> Distribution Lists can also be used to forward domain based emails. For example, you may need to forward ''project@yourdomain.com'' to ''address@someotherdomain.com''. This does not require a Zimbra account for the primary domain email address.<br /> <br /> <br /> ==Updating Distribution List information==<br /> To add, change, or remove information from a list, simply double-click the list you want to edit. Alternatively, you can right-click the list you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> <br /> ==Forwarding Email to Another Address==<br /> If you wish to forward emails sent to your hosted email to another email address, first select '''Manage''' and then '''Accounts.''' Double-click the account you wish to edit or right-click and choose '''Edit''' from the pop-up menu. <br /> <br /> To add a forward, click on the '''Forwarding''' section on the left-hand column. <br /> <br /> [[Image:1zimbraforward.png]]<br /> <br /> <br /> Enter the following required information:<br /> <br /> * '''User-specified forwarding address''': This will be the email account that emails are forwarded to that the account owner is aware of. In the example below, we will be forwarding emails to &quot;bob.dobbs@xmission.com.&quot; <br /> <br /> [[Image:2zimbraforward.png]]<br /> <br /> <br /> Don't forget to choose &quot;Save&quot; near the upper right hand corner after you've added the forwarding address!<br /> <br /> <br /> * '''Forwarding addresses hidden from the user''': This can be a list of email accounts that emails are forwarded to that the account owner is unaware of. To do this, first click the &quot;Add&quot; button located below the '''Forwarding addresses hidden from the user''' box. It will prompt you to enter an email address. After you've done so, simply click &quot;Ok.&quot; In the example below, we will be forwarding messages to &quot;bobdobbs@xmission.com.&quot;<br /> <br /> [[Image:3zimbraforward.png]]<br /> <br /> NOTE: You may also use Distribution Lists to forward domain based emails without needing an account for the specific address. For example, you may need to forward ''project@mydomain.com'' to ''johndoe@someotheremail.com''. The advantage of using a Distribution List is that you eliminate the costs associated with maintaining an account just for forwarding.<br /> <br /> ==Granting Domain Administrator Access==<br /> <br /> To grant an account administrative privileges to your domain, load their account in the admin interface and check the &quot;Administrator&quot; checkbox below &quot;Class of Service&quot;. Once checked, a field will appear below, &quot;Administrator role&quot;. Enter &quot;admins@yourdomain.com&quot;, replacing yourdomain.com with the domain you are granting access to. This will add the user to a distribution list, &quot;admins&quot;, on your domain, which grants the privileges.<br /> <br /> Note that if the &quot;Administrator&quot; checkbox does not exist, you may need to add yourself to the &quot;admins&quot; distribution list manually and wait up to fifteen minutes.<br /> <br /> Many older domains had their admin account rights assigned via a different method, with a different set of privileges that did not include access to the &quot;Administrator&quot; checkbox (along with adjusting mailbox quotas and, for many older domains, the ability to change classes of service).<br /> <br /> ==Importing Accounts from Exchange==<br /> <br /> This article has moved: https://wiki.xmission.com/Zimbra_Migration:_Exchange_Import_Wizard<br /> <br /> ==Deleting a Zimbra Mailbox==<br /> <br /> There are two fairly simple ways to properly delete a Zimbra mailbox from the XMission system. <br /> <br /> * Log into the Zimbra domain administration panel https://zimbraadmin.xmission.com and select the &quot;Manage&quot; area on the left. Once in the management area you simply highlight the mailbox and then right-mouse click to show the option menu. Select &quot;Delete&quot; and confirm the mailbox deletion request. <br /> <br /> * From inside the domain administration panel you may also highlight the mailbox name and then click on the gear wheel in the top right corner of the browser screen to display an options menu. Inside this menu select &quot;Delete&quot; and confirm the deletion request.<br /> <br /> Notes: <br /> * Changing mailbox status is not the same as deletion. All provisioned mailboxes are billable.<br /> * Deletion of a mail domain cannot be completed via the domain admin interface and requires contacting XMission billing department.<br /> * Be certain not to delete resource accounts such as galsync or distribution lists unless you know they are no longer needed. Doing so can impact mail performance.<br /> <br /> == Zimbra Themes ==<br /> <br /> You can see all the themes [https://wiki.xmission.com/Hosted_Email:_Admin_Panel/Zimbra_Themes here]<br /> <br /> <br /> [[Category:Zimbra|Admin Panel]]<br /> <br /> <br /> {{footer}}</div>

John https://wiki.xmission.com/index.php?title=Zimbra_Cloud_General_Application_Settings&diff=10865 2021-07-28T21:40:12Z

<p>John: </p> <hr /> <div>These general settings will be applied to most modern email applications on desktop and mobile clients utilizing mailboxes on Zimbra Cloud.<br /> <br /> Note to domain administrators, Zimbra Cloud requires configuration of your domain via the Admin Dashboard for your mail to work. https://admin.zimbracloud.com/domains In the Dashboard you will enter your mail domain and verify the domain by adding a TXT record to DNS. Once verified, you with then configure the additional DNS settings for MX, SPF, and DKIM.<br /> <br /> <br /> {|style=&quot;width:85%, color:#333333; font-size:10pt&quot; border=&quot;0&quot;<br /> |- <br /> |align=&quot;left&quot;|'''Zimbra Cloud Mailbox Settings'''<br /> |-<br /> {| style=&quot;text-align: left; border: 1px solid #ccc;&quot; cellspacing=&quot;0&quot; cellpadding=&quot;2&quot; <br /> ! style=&quot;border-bottom:1px solid #ccc; background-color: #eef; padding:2px 8px&quot; colspan=2 | Incoming Server Information:<br /> ! style=&quot;border-style: solid; border-width: 0 0 1px 1px; border-color:#ccc; background-color: #eef; padding:2px 8px&quot; colspan=2 | Outgoing Server Information:<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Server Type: || IMAP<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Server Type: || SMTP<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Hostname: || mail.zimbracloud.com<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Hostname: || mail.zimbracloud.com &amp;nbsp;<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Port: || 993<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Port: || 587<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Enable encryption: || YES<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Enable encryption: || YES<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Authenticate Using: || Password<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Requires Authentication: || YES<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Login User Name: || Full email address &amp;nbsp;<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; |Login User Name || Full email address<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Alternate Port: || 143, 995 SSL POP3 &amp;nbsp;<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; |Alternate Port: || 465 (Must enable SSL)<br /> |-<br /> |}<br /> <br /> {|<br /> |-<br /> ||Zimbra Cloud Webmail: |||[https://mail.zimbracloud.com/ https://mail.zimbracloud.com/]<br /> |-<br /> ||Admin Interface: |||[https://admin.zimbracloud.com/ https://admin.zimbracloud.com] Or follow Admin Dashboard icon from webmail<br /> |-<br /> ||Folders: ||| Sent Mail = &quot;Sent&quot;, Drafts = &quot;Drafts&quot;, Trash = &quot;Trash&quot;, Spam = &quot;Junk&quot;<br /> |}<br /> <br /> <br /> Zimbra Connector For Outlook: https://zimbra.github.io/userguide/zcloud/userguide-zcloud.html#_zimbra_connector_for_outlook_zco <br /> <br /> <br /> iOS and Apple Mail: <br /> Server URL is https://mail.zimbracloud.com/EWS/Exchange.asmx when using the Apple &quot;Microsoft Exchange&quot; configuration tool<br /> <br /> For Apple desktop configuration, users may find installing a Profile easier as it will configure mail, calendar, and contacts. This is covered in the Zimbra 9 (Modern UI) documentation: https://zimbra.github.io/zimbra-9/user-guide.html#_mobile_or_desktop_configuration<br /> <br /> Need help? XMission offers a range of [https://wiki.xmission.com/Zimbra_Cloud#Understanding_Support_Plans Zimbra Cloud Support plans]. Please contact XMission Sales or Support to have this added to your Zimbra Cloud service today.</div>

John https://wiki.xmission.com/index.php?title=Zimbra_Cloud_General_Application_Settings&diff=10864 2021-07-28T21:35:18Z

<p>John: added EWS info for Zimbra Cloud when using iOS or Apple desktop</p> <hr /> <div>These general settings will be applied to most modern email applications on desktop and mobile clients utilizing mailboxes on Zimbra Cloud.<br /> <br /> Note to domain administrators, Zimbra Cloud requires configuration of your domain via the Admin Dashboard for your mail to work. https://admin.zimbracloud.com/domains In the Dashboard you will enter your mail domain and verify the domain by adding a TXT record to DNS. Once verified, you with then configure the additional DNS settings for MX, SPF, and DKIM.<br /> <br /> <br /> {|style=&quot;width:85%, color:#333333; font-size:10pt&quot; border=&quot;0&quot;<br /> |- <br /> |align=&quot;left&quot;|'''Zimbra Cloud Mailbox Settings'''<br /> |-<br /> {| style=&quot;text-align: left; border: 1px solid #ccc;&quot; cellspacing=&quot;0&quot; cellpadding=&quot;2&quot; <br /> ! style=&quot;border-bottom:1px solid #ccc; background-color: #eef; padding:2px 8px&quot; colspan=2 | Incoming Server Information:<br /> ! style=&quot;border-style: solid; border-width: 0 0 1px 1px; border-color:#ccc; background-color: #eef; padding:2px 8px&quot; colspan=2 | Outgoing Server Information:<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Server Type: || IMAP<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Server Type: || SMTP<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Hostname: || mail.zimbracloud.com<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Hostname: || mail.zimbracloud.com &amp;nbsp;<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Port: || 993<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Port: || 587<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Enable encryption: || YES<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Enable encryption: || YES<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Authenticate Using: || Password<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Requires Authentication: || YES<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Login User Name: || Full email address &amp;nbsp;<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; |Login User Name || Full email address<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Alternate Port: || 143, 995 SSL POP3 &amp;nbsp;<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; |Alternate Port: || 465 (Must enable SSL)<br /> |-<br /> |}<br /> <br /> {|<br /> |-<br /> ||Zimbra Cloud Webmail: |||[https://mail.zimbracloud.com/ https://mail.zimbracloud.com/]<br /> |-<br /> ||Admin Interface: |||[https://admin.zimbracloud.com/ https://admin.zimbracloud.com] Or follow Admin Dashboard icon from webmail<br /> |-<br /> ||Folders: ||| Sent Mail = &quot;Sent&quot;, Drafts = &quot;Drafts&quot;, Trash = &quot;Trash&quot;, Spam = &quot;Junk&quot;<br /> |}<br /> <br /> <br /> Zimbra Connector For Outlook: https://zimbra.github.io/userguide/zcloud/userguide-zcloud.html#_zimbra_connector_for_outlook_zco <br /> <br /> <br /> iOS and Apple Mail: <br /> Server URL is https://mail.zimbracloud.com/EWS/Exchange.asmx when using the Apple &quot;Microsoft Exchange&quot; configuration tool<br /> <br /> <br /> Need help? XMission offers a range of [https://wiki.xmission.com/Zimbra_Cloud#Understanding_Support_Plans Zimbra Cloud Support plans]. Please contact XMission Sales or Support to have this added to your Zimbra Cloud service today.</div>

John https://wiki.xmission.com/index.php?title=Hosted_Email:_Admin_Panel&diff=10863 2021-06-29T19:04:33Z

<p>John: /* Deleting a Zimbra Mailbox */</p> <hr /> <div>==Overview/Logging In== <br /> The Zimbra domain administration console is the browser-based user interface used to centrally manage user accounts and most settings.<br /> <br /> As a domain administrator, you will be able to create and maintain the following:<br /> <br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_an_Email_Account Email accounts]<br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_an_Alias Mailbox aliases]<br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_a_Distribution_List Distribution lists]<br /> *Resources<br /> <br /> To login to the domain administration console, go to https://zimbraadmin.xmission.com/ and login with your administrative username and password. Domain administrators can also login from the dropdown menu next to your mailbox name in the top right corner of the webmail session. Click on 'Admin Console' to proceed.<br /> <br /> ==Domain Administrator Responsibilities==<br /> <br /> It is important to understand that as domain administrators you are responsible for changing passwords, creating distribution lists, setting email forwards, managing mailboxes, training on phishing, and etc. Our support policy for email is clearly outlined at: https://xmission.com/legal_policies#emlsup We require domain administrators be added as Technical contacts on your billing account in order to receive advanced assistance from our support staff. Please keep contacts up-to-date in the [https://xmission.com/control account management portal] or contact [https://xmission.com/contact XMission Billing] for assistance.<br /> <br /> Phishing and email scams are on the rise. It is important to educate yourself and your mailbox holders on how to avoid it. Reference this guide on <br /> [https://wiki.xmission.com/Phishing_and_Email_Scams understanding phishing].<br /> <br /> ==Email Domain Health==<br /> <br /> An important part of effective business email mean protecting your domain with some simple settings to improve delivery and reduce fraud.<br /> <br /> XMission advises implementing SPF and DKIM on domains. These are two simple methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf and prevent abuse. [https://wiki.xmission.com/SPF_and_DKIM How to configure SPF and DKIM]<br /> <br /> ==About the Administrative Console==<br /> <br /> The area above the '''Content''' pane includes the '''Search''' and '''Help''' functions.<br /> <br /> '''Search''' allows you to quickly find accounts, aliases, distribution lists and resources for editing. <br /> <br /> '''Help''' utilizes Zimbra’s wiki, forums, and documentation. This is a powerful unified search to quickly find answers to common questions.<br /> <br /> [[Image:1zimbraadminpanel.png]]<br /> <br /> <br /> <br /> The '''Navigation''' pane on the left includes the following sections:<br /> <br /> *'''Home:''' At any time, clicking here will return you to the administrative Home options. <br /> <br /> *'''Manage:''' Clicking here will permit you to create and edit any accounts, aliases, distribution lists, and resources for your domain(s). <br /> <br /> *'''Help:''' utilizes Zimbra’s wiki, forums, and documentation. This is a powerful unified search to quickly find answers to common questions. <br /> <br /> [[Image:4zimbraadminpanel.png]]<br /> <br /> <br /> <br /> Alternatively, you can also click on the arrow beside the &quot;Home&quot; button. This will give you the same options listed above, as well as recent searches and the options available under &quot;Manage.&quot; In this example, the recent search was for &quot;xdesign.com.&quot;<br /> <br /> [[Image:2zimbraadminpanel.png]]<br /> <br /> <br /> <br /> Clicking on &quot;Manage&quot; either way will permit you to make changes to your existing accounts, aliases, distribution lists, and resources.<br /> <br /> *'''Accounts:''' Lists all accounts. In the Accounts folder, you create and manage end-user accounts, setting options, class of service, passwords and aliases for an account.<br /> <br /> *'''Aliases:''' Lists all aliases that have been created in Accounts. You can use the Move Alias feature from the toolbar to move an alias from one account to another.<br /> <br /> *'''Distribution Lists:''' Lists all distribution lists. You can create new distribution lists and add or delete members of a distribution list.<br /> <br /> *'''Resources:''' This lists locations or equipment that can be scheduled from your Calendar. Here is where you can create new resources and set the scheduling policy for the resource.<br /> <br /> [[Image:3zimbraadminpanel.png]]<br /> <br /> <br /> ==Creating an Email Account== <br /> Select '''Manage''' and then '''Accounts''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the email mailbox you are about to create. Enter the following required information:<br /> <br /> * '''Account Name''': This will be the mailbox account that you are about to create. In this example, we are creating &quot;bobdobbs@xdesign.com.&quot;<br /> * '''First Name''': The first name of the email user. <br /> * '''Last Name''': The last name of the email user.<br /> [[Image:1zimbraaddaccount.png]]<br /> <br /> When creating a new mailbox account you will set the Class of Service (CoS) under '''General Information / Account Setup / Class of Service'''. Don't forget to deselect the &quot;[ ] auto&quot; box to enter the class type.<br /> <br /> You may mix and match Class of Service (CoS) for mailbox accounts in your domain to maximize benefits for your organization. Details below.<br /> <br /> Something to note, XMission identifies a billable Zimbra account as mailbox with a physical email Inbox and typically belonging to one person. So even if it is not &quot;active&quot; but still provisioned, it will count toward billing. Example, a mailbox set to &quot;closed&quot; or &quot;maintenance&quot; status remains billable.<br /> <br /> ==Class of Service==<br /> <br /> To '''upgrade''' an existing account, or to change existing accounts, simply log in to the admin interface, click on '''&quot;Manage&quot;''' and select the user by double-clicking on the name. Inside the '''&quot;General Information&quot;''' pane you will see '''&quot;Account Setup&quot;''' in the middle of the page. In this area you will find '''&quot;Class of Service&quot;''' with an input box next to it and the &quot;[x] auto&quot; box checked. Deselect the &quot;[ ] auto&quot; box and type '''&quot;xmpremium&quot;''' or '''&quot;xmbase&quot;''' in the field and then hit '''&quot;Save&quot;''' towards the top right of the window. Your account is now set to the selected service level with all the features and storage associated with the account type.<br /> <br /> Click the '''&quot;Finish&quot;''' button. You will be returned to the main admin screen, and the new account will have been created at the established service level.<br /> <br /> NOTE: If the &quot;Class of Service&quot; field is not available to you, you may need to add your admin account's email address to the &quot;admins&quot; distribution list on your domain and wait up to fifteen minutes. Some older accounts do not have this setup automatically. See [https://wiki.xmission.com/Zimbra_Hosting_Admin#Granting_Domain_Administrator_Access Granting Domain Administrator Access] for more details.<br /> <br /> ==Updating Account Information==<br /> To add, change, or remove information from an account, simply double-click the account you want to edit. Alternatively, you can right-click the account you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> ==Change Password==<br /> <br /> All Zimbra domain administrator should read this quick blog post on email security: https://xmission.com/blog/2017/10/17/best-practices-for-zimbra-email-security<br /> <br /> Changing your end-user mailbox password through the Zimbra [https://zimbraadmin.xmission.com domain admin control panel] is easy, but first let's review XMission password best practices.<br /> <br /> '''XMission Zimbra Password requirements:''' <br /> <br /> XMission recommends secure passphrases consisting of five to six words, with a few special characters and numbers, since they can be much easier to remember.<br /> <br /> * Ideally it is best to use longer, more complex passphrases to properly protect your mailboxes, and your company, from hackers. Our Zimbra system supports passwords up to 64 characters. We advise using a minimum passphrase length of 12-15 characters with 25-28 characters providing very reasonable security. <br /> * Shorter passwords require use of at least 1 of the following: UPPER CASE letter, lower case letter, special characters, and a numeral to meet minimum security requirements.<br /> * Passwords expire after 1 year and must be changed at that time. Changing more frequently is advised.<br /> * You cannot re-use your current password.<br /> * Please allow 15 minutes for the new password to propagate through the system.<br /> * Write credentials down in a secure place until you memorize it then destroy the note.<br /> * Here is a quick and easy to understand visual tutorial on password security: [https://xmission.com/blog/2017/10/17/best-practices-for-zimbra-email-security | https://xkcd.com/936/ ]<br /> <br /> '''Three ways to change passwords from domain admin control panel:'''<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column. Right-mouse click on the mailbox name to reveal a drop down menu, select &quot;Change password.&quot;<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column and highlight a mailbox. Now right-mouse click on the gear icon in the top right corner. Select &quot;Change password&quot;.<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column and double click on the desired mailbox. When it opens the settings page of the mailbox use the &quot;Password&quot; area to change the password.<br /> <br /> NOTE: XMission Zimbra servers will allow a password as short as 12 characters. Short passwords are poor security. Please take the time to protect your company email data buy using a passphrase in the 25-28 character length.<br /> <br /> ==Password Expiration and Failed Login Attempts==<br /> Please note the following details about XMission's email password expiration and failed login attempts policy.<br /> <br /> Should you ever have an end-user mailbox that is not allowing login there are two primary reasons for this. <br /> * The password has expired. <br /> * There have been too many failed login attempts to the account causing it to be temporarily suspended.<br /> <br /> ==== Expired Password ====<br /> <br /> All XMission email passwords must be changed once yearly. XMission sends email notices to the user mailbox 2 (two) weeks before expiration. Please ask your mailbox owners to change their password in a timely manner.<br /> <br /> Domain administrators are *not* emailed about the user mailbox need to change their password. Repeat, domain administrators are not emailed about password expirations.<br /> <br /> ==== Failed Login Attempt - Mailbox Access Suspension ====<br /> <br /> Failed login attempt account suspension practices are a way to safeguard mailboxes from brute force attacks where a bad actor is trying to access the sensitive information inside. XMission protects customer mailboxes by temporarily suspending mail accounts with too many failed login attempts. <br /> <br /> If you, or another entity, are trying to access the account with too many failed password attempts within the monitoring cycle, the system blocks access for a short period of time, after which you can again attempt to authenticate with correct credentials.<br /> <br /> '''Failed login attempt definition:''' Improper entry of a password for a valid mailbox. <br /> <br /> '''How failed login attempts are measured and enforced:''' When the first failed login attempt occurs, the monitoring cycle begins. Thereafter, each time a unique wrong password fails, that adds to the count. <br /> <br /> It is important to note that when the ''same'' wrong password is used, from any number of IP addresses or devices, it only counts as one (1) failed login attempt.<br /> <br /> During the monitoring cycle, if additional failed login attempts are made using a different password from the original attempt, it add to the failed login attempt total. IE: Bad password &quot;A&quot; activates monitoring period. A second unique password &quot;B&quot; is used bringing the total to two (2) failed attempts. If password &quot;A&quot; is used again, it counts as another new unique password totaling three (3) failed attempts. <br /> <br /> Once the maximum number of failed attempts is reached, access to the mailbox is temporarily suspended.<br /> <br /> ==== Troubleshooting ====<br /> <br /> Mailbox accounts having failed login issues appear to have the same symptoms as an expired password. The way to test is to access webmail, https://zimbra.xmission.com, with your credentials. If the password is expired it will prompt you to set a new password immediately. If the account is locked out, it will simply not validate with the credentials until the suspension period ends.<br /> <br /> If an account is temporarily suspended for too many failed password attempts you need to either wait for the suspension period to pass, reset the mailbox status to active in the domain admin panel, or contact XMission Support to have the suspension manually removed.<br /> <br /> Domain administrators can change mailbox status and passwords via the domain admin interface.<br /> <br /> NOTE: Use of Two-Factor Authentication (2FA) does not prevent account suspension due to failed authentication attempts.<br /> <br /> ==Mailbox locked for abuse==<br /> <br /> A user mailbox can also be locked for abuse. This abuse can be due to any of the following reasons;<br /> * Successfully compromised by a phishing attempt and shared their password with someone they shouldn't have.<br /> * Use of a previously compromised password on another Internet site or service.<br /> * Malware on a computer or device.<br /> * Rootkit on the computer.<br /> <br /> ''Symptoms of abuse:''<br /> <br /> Domain administrators often ask why a mailbox was locked for a spam run when they do not see evidence of malicious messages in the Sent folder. The primary reason for this is because the spammers use SMTP mail applications that do not sync the Sent mail folder. Only messages sent via the Zimbra webmail interface, via Outlook with the Zimbra Connector, or sent via ActiveSync (Exchange) configuration on mobile devices, will sync Sent messages to the mail system. So a bad actor can send copious amounts of unwanted email quickly and with no trace the end user can see. However, XMission has logs for all messages sent which we use to identify and lock accounts as well as to train system rules to prevent future abuse. <br /> <br /> Determining why a mailbox has been locked for abuse can be difficult. XMission will do their best to provide data on what was compromised and how. In some cases this is possible, in others it is not. Most often phishing and re-used passwords are the primary attack vector resulting in a locked user mailbox.<br /> <br /> &quot;The remedy:&quot;<br /> <br /> Regardless of the &quot;how&quot; all compromised mailbox users are required to change their password immediately to continue using the service. It is imperative that domain administrators do not re-use passwords or set poor temporary passwords. <br /> <br /> We strongly advise in the use of long passwords (pass phrases) and password managers such as BitWarden, Keepass, and similar.<br /> <br /> Additional compromises of the same mailbox will result in a small fine which we hope is just enough to encourage proper mailbox security. You can read about this policy here: https://xmission.com/blog/2019/05/14/our-new-compromised-email-policy<br /> <br /> ==Creating an Alias==<br /> Select '''Manage''' and then '''Aliases''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the email alias you wish to create. Enter the following required information:<br /> <br /> *'''Alias''': This is the aliased address you will create. In this example, we are adding &quot;bob.dobbs@xdesign.com.&quot; <br /> *'''Target Account''': This is the actual email box that will receive any emails directed to the aliases address. <br /> [[Image:1zimbraaddalias.png]]<br /> <br /> <br /> Click &quot;Ok&quot; to add your new alias.<br /> <br /> <br /> ==Updating Alias Information==<br /> To add, change, or remove information from an alias, simply double-click the alias you want to edit. Alternatively, you can right-click the alias you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> <br /> ==Creating a Distribution List==<br /> Select '''Manage''' and then '''Distribution Lists''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the distribution list you wish to create. Enter the following required information:<br /> <br /> * '''List Name''': This will be the email address for the mailing list. <br /> * '''Display Name''': This can be a descriptive name for the list. <br /> <br /> [[Image:1zimbraaddlist.png]]<br /> <br /> <br /> To add email addresses to the list, scroll a bit to the right and you will see a &quot;Search&quot; button below the '''Add Members to this list''' section. If you want add email addresses that are withing your Zimbra package, search for the appropriate domain name(s). In this case, we searched for &quot;xdesign.com.&quot; Highlight any results you would like to be added to the list.<br /> <br /> [[Image:1zimbraaddmembers.png]]<br /> <br /> <br /> Using the scroll bar on the right, scroll down and click the &quot;Add Selected&quot; button. <br /> <br /> [[Image:2zimbraaddmembers.png]]<br /> <br /> <br /> If you want to manually add addresses or need to add addresses that are not within Zimbra's search function, you can type the email addresses in the box pictured below. In this case, we are adding two email addresses to the list -- &quot;bobdobbs@gmail.com&quot; and &quot;bigguyjake@xmission.com.&quot; Once you've typed in the email addresses you want added to your list, simply click the &quot;Add&quot; button below. <br /> <br /> [[Image:3zimbraaddmembers.png]]<br /> <br /> <br /> ''Notes:''<br /> <br /> You can make lists members of other lists. This is a handy way to create umbrella lists. For example, if you wanted a staff list, but had various departments, you could add your employees to the departmental list, and then subscribe the departmental lists to the staff lists. This way, an account is only entered once, rather than adding an account to each list individually.<br /> <br /> Distribution Lists can also be used to forward domain based emails. For example, you may need to forward ''project@yourdomain.com'' to ''address@someotherdomain.com''. This does not require a Zimbra account for the primary domain email address.<br /> <br /> <br /> ==Updating Distribution List information==<br /> To add, change, or remove information from a list, simply double-click the list you want to edit. Alternatively, you can right-click the list you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> <br /> ==Forwarding Email to Another Address==<br /> If you wish to forward emails sent to your hosted email to another email address, first select '''Manage''' and then '''Accounts.''' Double-click the account you wish to edit or right-click and choose '''Edit''' from the pop-up menu. <br /> <br /> To add a forward, click on the '''Forwarding''' section on the left-hand column. <br /> <br /> [[Image:1zimbraforward.png]]<br /> <br /> <br /> Enter the following required information:<br /> <br /> * '''User-specified forwarding address''': This will be the email account that emails are forwarded to that the account owner is aware of. In the example below, we will be forwarding emails to &quot;bob.dobbs@xmission.com.&quot; <br /> <br /> [[Image:2zimbraforward.png]]<br /> <br /> <br /> Don't forget to choose &quot;Save&quot; near the upper right hand corner after you've added the forwarding address!<br /> <br /> <br /> * '''Forwarding addresses hidden from the user''': This can be a list of email accounts that emails are forwarded to that the account owner is unaware of. To do this, first click the &quot;Add&quot; button located below the '''Forwarding addresses hidden from the user''' box. It will prompt you to enter an email address. After you've done so, simply click &quot;Ok.&quot; In the example below, we will be forwarding messages to &quot;bobdobbs@xmission.com.&quot;<br /> <br /> [[Image:3zimbraforward.png]]<br /> <br /> NOTE: You may also use Distribution Lists to forward domain based emails without needing an account for the specific address. For example, you may need to forward ''project@mydomain.com'' to ''johndoe@someotheremail.com''. The advantage of using a Distribution List is that you eliminate the costs associated with maintaining an account just for forwarding.<br /> <br /> ==Granting Domain Administrator Access==<br /> <br /> To grant an account administrative privileges to your domain, load their account in the admin interface and check the &quot;Administrator&quot; checkbox below &quot;Class of Service&quot;. Once checked, a field will appear below, &quot;Administrator role&quot;. Enter &quot;admins@yourdomain.com&quot;, replacing yourdomain.com with the domain you are granting access to. This will add the user to a distribution list, &quot;admins&quot;, on your domain, which grants the privileges.<br /> <br /> Note that if the &quot;Administrator&quot; checkbox does not exist, you may need to add yourself to the &quot;admins&quot; distribution list manually and wait up to fifteen minutes.<br /> <br /> Many older domains had their admin account rights assigned via a different method, with a different set of privileges that did not include access to the &quot;Administrator&quot; checkbox (along with adjusting mailbox quotas and, for many older domains, the ability to change classes of service).<br /> <br /> ==Importing Accounts from Exchange==<br /> <br /> This article has moved: https://wiki.xmission.com/Zimbra_Migration:_Exchange_Import_Wizard<br /> <br /> ==Deleting a Zimbra Mailbox==<br /> <br /> There are two fairly simple ways to properly delete a Zimbra mailbox from the XMission system. <br /> <br /> * Log into the Zimbra domain administration panel https://zimbraadmin.xmission.com and select the &quot;Manage&quot; area on the left. Once in the management area you simply highlight the mailbox and then right-mouse click to show the option menu. Select &quot;Delete&quot; and confirm the mailbox deletion request. <br /> <br /> * From inside the domain administration panel you may also highlight the mailbox name and then click on the gear wheel in the top right corner of the browser screen to display an options menu. Inside this menu select &quot;Delete&quot; and confirm the deletion request.<br /> <br /> Notes: <br /> * Changing mailbox status is not the same as deletion. All provisioned mailboxes are billable.<br /> * Deletion of a mail domain cannot be completed via the domain admin interface and requires contacting XMission billing department.<br /> * Be certain not to delete resource accounts such as galsync or distribution lists unless you know they are no longer needed. Doing so can impact mail performance.<br /> <br /> == Zimbra Themes ==<br /> <br /> You can see all the themes [https://wiki.xmission.com/Hosted_Email:_Admin_Panel/Zimbra_Themes here]<br /> <br /> <br /> [[Category:Zimbra|Admin Panel]]<br /> <br /> <br /> {{footer}}</div>

John https://wiki.xmission.com/index.php?title=Hosted_Email:_Admin_Panel&diff=10862 2021-06-25T20:29:14Z

<p>John: /* Deleting a Zimbra Mailbox */</p> <hr /> <div>==Overview/Logging In== <br /> The Zimbra domain administration console is the browser-based user interface used to centrally manage user accounts and most settings.<br /> <br /> As a domain administrator, you will be able to create and maintain the following:<br /> <br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_an_Email_Account Email accounts]<br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_an_Alias Mailbox aliases]<br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_a_Distribution_List Distribution lists]<br /> *Resources<br /> <br /> To login to the domain administration console, go to https://zimbraadmin.xmission.com/ and login with your administrative username and password. Domain administrators can also login from the dropdown menu next to your mailbox name in the top right corner of the webmail session. Click on 'Admin Console' to proceed.<br /> <br /> ==Domain Administrator Responsibilities==<br /> <br /> It is important to understand that as domain administrators you are responsible for changing passwords, creating distribution lists, setting email forwards, managing mailboxes, training on phishing, and etc. Our support policy for email is clearly outlined at: https://xmission.com/legal_policies#emlsup We require domain administrators be added as Technical contacts on your billing account in order to receive advanced assistance from our support staff. Please keep contacts up-to-date in the [https://xmission.com/control account management portal] or contact [https://xmission.com/contact XMission Billing] for assistance.<br /> <br /> Phishing and email scams are on the rise. It is important to educate yourself and your mailbox holders on how to avoid it. Reference this guide on <br /> [https://wiki.xmission.com/Phishing_and_Email_Scams understanding phishing].<br /> <br /> ==Email Domain Health==<br /> <br /> An important part of effective business email mean protecting your domain with some simple settings to improve delivery and reduce fraud.<br /> <br /> XMission advises implementing SPF and DKIM on domains. These are two simple methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf and prevent abuse. [https://wiki.xmission.com/SPF_and_DKIM How to configure SPF and DKIM]<br /> <br /> ==About the Administrative Console==<br /> <br /> The area above the '''Content''' pane includes the '''Search''' and '''Help''' functions.<br /> <br /> '''Search''' allows you to quickly find accounts, aliases, distribution lists and resources for editing. <br /> <br /> '''Help''' utilizes Zimbra’s wiki, forums, and documentation. This is a powerful unified search to quickly find answers to common questions.<br /> <br /> [[Image:1zimbraadminpanel.png]]<br /> <br /> <br /> <br /> The '''Navigation''' pane on the left includes the following sections:<br /> <br /> *'''Home:''' At any time, clicking here will return you to the administrative Home options. <br /> <br /> *'''Manage:''' Clicking here will permit you to create and edit any accounts, aliases, distribution lists, and resources for your domain(s). <br /> <br /> *'''Help:''' utilizes Zimbra’s wiki, forums, and documentation. This is a powerful unified search to quickly find answers to common questions. <br /> <br /> [[Image:4zimbraadminpanel.png]]<br /> <br /> <br /> <br /> Alternatively, you can also click on the arrow beside the &quot;Home&quot; button. This will give you the same options listed above, as well as recent searches and the options available under &quot;Manage.&quot; In this example, the recent search was for &quot;xdesign.com.&quot;<br /> <br /> [[Image:2zimbraadminpanel.png]]<br /> <br /> <br /> <br /> Clicking on &quot;Manage&quot; either way will permit you to make changes to your existing accounts, aliases, distribution lists, and resources.<br /> <br /> *'''Accounts:''' Lists all accounts. In the Accounts folder, you create and manage end-user accounts, setting options, class of service, passwords and aliases for an account.<br /> <br /> *'''Aliases:''' Lists all aliases that have been created in Accounts. You can use the Move Alias feature from the toolbar to move an alias from one account to another.<br /> <br /> *'''Distribution Lists:''' Lists all distribution lists. You can create new distribution lists and add or delete members of a distribution list.<br /> <br /> *'''Resources:''' This lists locations or equipment that can be scheduled from your Calendar. Here is where you can create new resources and set the scheduling policy for the resource.<br /> <br /> [[Image:3zimbraadminpanel.png]]<br /> <br /> <br /> ==Creating an Email Account== <br /> Select '''Manage''' and then '''Accounts''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the email mailbox you are about to create. Enter the following required information:<br /> <br /> * '''Account Name''': This will be the mailbox account that you are about to create. In this example, we are creating &quot;bobdobbs@xdesign.com.&quot;<br /> * '''First Name''': The first name of the email user. <br /> * '''Last Name''': The last name of the email user.<br /> [[Image:1zimbraaddaccount.png]]<br /> <br /> When creating a new mailbox account you will set the Class of Service (CoS) under '''General Information / Account Setup / Class of Service'''. Don't forget to deselect the &quot;[ ] auto&quot; box to enter the class type.<br /> <br /> You may mix and match Class of Service (CoS) for mailbox accounts in your domain to maximize benefits for your organization. Details below.<br /> <br /> Something to note, XMission identifies a billable Zimbra account as mailbox with a physical email Inbox and typically belonging to one person. So even if it is not &quot;active&quot; but still provisioned, it will count toward billing. Example, a mailbox set to &quot;closed&quot; or &quot;maintenance&quot; status remains billable.<br /> <br /> ==Class of Service==<br /> <br /> To '''upgrade''' an existing account, or to change existing accounts, simply log in to the admin interface, click on '''&quot;Manage&quot;''' and select the user by double-clicking on the name. Inside the '''&quot;General Information&quot;''' pane you will see '''&quot;Account Setup&quot;''' in the middle of the page. In this area you will find '''&quot;Class of Service&quot;''' with an input box next to it and the &quot;[x] auto&quot; box checked. Deselect the &quot;[ ] auto&quot; box and type '''&quot;xmpremium&quot;''' or '''&quot;xmbase&quot;''' in the field and then hit '''&quot;Save&quot;''' towards the top right of the window. Your account is now set to the selected service level with all the features and storage associated with the account type.<br /> <br /> Click the '''&quot;Finish&quot;''' button. You will be returned to the main admin screen, and the new account will have been created at the established service level.<br /> <br /> NOTE: If the &quot;Class of Service&quot; field is not available to you, you may need to add your admin account's email address to the &quot;admins&quot; distribution list on your domain and wait up to fifteen minutes. Some older accounts do not have this setup automatically. See [https://wiki.xmission.com/Zimbra_Hosting_Admin#Granting_Domain_Administrator_Access Granting Domain Administrator Access] for more details.<br /> <br /> ==Updating Account Information==<br /> To add, change, or remove information from an account, simply double-click the account you want to edit. Alternatively, you can right-click the account you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> ==Change Password==<br /> <br /> All Zimbra domain administrator should read this quick blog post on email security: https://xmission.com/blog/2017/10/17/best-practices-for-zimbra-email-security<br /> <br /> Changing your end-user mailbox password through the Zimbra [https://zimbraadmin.xmission.com domain admin control panel] is easy, but first let's review XMission password best practices.<br /> <br /> '''XMission Zimbra Password requirements:''' <br /> <br /> XMission recommends secure passphrases consisting of five to six words, with a few special characters and numbers, since they can be much easier to remember.<br /> <br /> * Ideally it is best to use longer, more complex passphrases to properly protect your mailboxes, and your company, from hackers. Our Zimbra system supports passwords up to 64 characters. We advise using a minimum passphrase length of 12-15 characters with 25-28 characters providing very reasonable security. <br /> * Shorter passwords require use of at least 1 of the following: UPPER CASE letter, lower case letter, special characters, and a numeral to meet minimum security requirements.<br /> * Passwords expire after 1 year and must be changed at that time. Changing more frequently is advised.<br /> * You cannot re-use your current password.<br /> * Please allow 15 minutes for the new password to propagate through the system.<br /> * Write credentials down in a secure place until you memorize it then destroy the note.<br /> * Here is a quick and easy to understand visual tutorial on password security: [https://xmission.com/blog/2017/10/17/best-practices-for-zimbra-email-security | https://xkcd.com/936/ ]<br /> <br /> '''Three ways to change passwords from domain admin control panel:'''<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column. Right-mouse click on the mailbox name to reveal a drop down menu, select &quot;Change password.&quot;<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column and highlight a mailbox. Now right-mouse click on the gear icon in the top right corner. Select &quot;Change password&quot;.<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column and double click on the desired mailbox. When it opens the settings page of the mailbox use the &quot;Password&quot; area to change the password.<br /> <br /> NOTE: XMission Zimbra servers will allow a password as short as 12 characters. Short passwords are poor security. Please take the time to protect your company email data buy using a passphrase in the 25-28 character length.<br /> <br /> ==Password Expiration and Failed Login Attempts==<br /> Please note the following details about XMission's email password expiration and failed login attempts policy.<br /> <br /> Should you ever have an end-user mailbox that is not allowing login there are two primary reasons for this. <br /> * The password has expired. <br /> * There have been too many failed login attempts to the account causing it to be temporarily suspended.<br /> <br /> ==== Expired Password ====<br /> <br /> All XMission email passwords must be changed once yearly. XMission sends email notices to the user mailbox 2 (two) weeks before expiration. Please ask your mailbox owners to change their password in a timely manner.<br /> <br /> Domain administrators are *not* emailed about the user mailbox need to change their password. Repeat, domain administrators are not emailed about password expirations.<br /> <br /> ==== Failed Login Attempt - Mailbox Access Suspension ====<br /> <br /> Failed login attempt account suspension practices are a way to safeguard mailboxes from brute force attacks where a bad actor is trying to access the sensitive information inside. XMission protects customer mailboxes by temporarily suspending mail accounts with too many failed login attempts. <br /> <br /> If you, or another entity, are trying to access the account with too many failed password attempts within the monitoring cycle, the system blocks access for a short period of time, after which you can again attempt to authenticate with correct credentials.<br /> <br /> '''Failed login attempt definition:''' Improper entry of a password for a valid mailbox. <br /> <br /> '''How failed login attempts are measured and enforced:''' When the first failed login attempt occurs, the monitoring cycle begins. Thereafter, each time a unique wrong password fails, that adds to the count. <br /> <br /> It is important to note that when the ''same'' wrong password is used, from any number of IP addresses or devices, it only counts as one (1) failed login attempt.<br /> <br /> During the monitoring cycle, if additional failed login attempts are made using a different password from the original attempt, it add to the failed login attempt total. IE: Bad password &quot;A&quot; activates monitoring period. A second unique password &quot;B&quot; is used bringing the total to two (2) failed attempts. If password &quot;A&quot; is used again, it counts as another new unique password totaling three (3) failed attempts. <br /> <br /> Once the maximum number of failed attempts is reached, access to the mailbox is temporarily suspended.<br /> <br /> ==== Troubleshooting ====<br /> <br /> Mailbox accounts having failed login issues appear to have the same symptoms as an expired password. The way to test is to access webmail, https://zimbra.xmission.com, with your credentials. If the password is expired it will prompt you to set a new password immediately. If the account is locked out, it will simply not validate with the credentials until the suspension period ends.<br /> <br /> If an account is temporarily suspended for too many failed password attempts you need to either wait for the suspension period to pass, reset the mailbox status to active in the domain admin panel, or contact XMission Support to have the suspension manually removed.<br /> <br /> Domain administrators can change mailbox status and passwords via the domain admin interface.<br /> <br /> NOTE: Use of Two-Factor Authentication (2FA) does not prevent account suspension due to failed authentication attempts.<br /> <br /> ==Mailbox locked for abuse==<br /> <br /> A user mailbox can also be locked for abuse. This abuse can be due to any of the following reasons;<br /> * Successfully compromised by a phishing attempt and shared their password with someone they shouldn't have.<br /> * Use of a previously compromised password on another Internet site or service.<br /> * Malware on a computer or device.<br /> * Rootkit on the computer.<br /> <br /> ''Symptoms of abuse:''<br /> <br /> Domain administrators often ask why a mailbox was locked for a spam run when they do not see evidence of malicious messages in the Sent folder. The primary reason for this is because the spammers use SMTP mail applications that do not sync the Sent mail folder. Only messages sent via the Zimbra webmail interface, via Outlook with the Zimbra Connector, or sent via ActiveSync (Exchange) configuration on mobile devices, will sync Sent messages to the mail system. So a bad actor can send copious amounts of unwanted email quickly and with no trace the end user can see. However, XMission has logs for all messages sent which we use to identify and lock accounts as well as to train system rules to prevent future abuse. <br /> <br /> Determining why a mailbox has been locked for abuse can be difficult. XMission will do their best to provide data on what was compromised and how. In some cases this is possible, in others it is not. Most often phishing and re-used passwords are the primary attack vector resulting in a locked user mailbox.<br /> <br /> &quot;The remedy:&quot;<br /> <br /> Regardless of the &quot;how&quot; all compromised mailbox users are required to change their password immediately to continue using the service. It is imperative that domain administrators do not re-use passwords or set poor temporary passwords. <br /> <br /> We strongly advise in the use of long passwords (pass phrases) and password managers such as BitWarden, Keepass, and similar.<br /> <br /> Additional compromises of the same mailbox will result in a small fine which we hope is just enough to encourage proper mailbox security. You can read about this policy here: https://xmission.com/blog/2019/05/14/our-new-compromised-email-policy<br /> <br /> ==Creating an Alias==<br /> Select '''Manage''' and then '''Aliases''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the email alias you wish to create. Enter the following required information:<br /> <br /> *'''Alias''': This is the aliased address you will create. In this example, we are adding &quot;bob.dobbs@xdesign.com.&quot; <br /> *'''Target Account''': This is the actual email box that will receive any emails directed to the aliases address. <br /> [[Image:1zimbraaddalias.png]]<br /> <br /> <br /> Click &quot;Ok&quot; to add your new alias.<br /> <br /> <br /> ==Updating Alias Information==<br /> To add, change, or remove information from an alias, simply double-click the alias you want to edit. Alternatively, you can right-click the alias you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> <br /> ==Creating a Distribution List==<br /> Select '''Manage''' and then '''Distribution Lists''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the distribution list you wish to create. Enter the following required information:<br /> <br /> * '''List Name''': This will be the email address for the mailing list. <br /> * '''Display Name''': This can be a descriptive name for the list. <br /> <br /> [[Image:1zimbraaddlist.png]]<br /> <br /> <br /> To add email addresses to the list, scroll a bit to the right and you will see a &quot;Search&quot; button below the '''Add Members to this list''' section. If you want add email addresses that are withing your Zimbra package, search for the appropriate domain name(s). In this case, we searched for &quot;xdesign.com.&quot; Highlight any results you would like to be added to the list.<br /> <br /> [[Image:1zimbraaddmembers.png]]<br /> <br /> <br /> Using the scroll bar on the right, scroll down and click the &quot;Add Selected&quot; button. <br /> <br /> [[Image:2zimbraaddmembers.png]]<br /> <br /> <br /> If you want to manually add addresses or need to add addresses that are not within Zimbra's search function, you can type the email addresses in the box pictured below. In this case, we are adding two email addresses to the list -- &quot;bobdobbs@gmail.com&quot; and &quot;bigguyjake@xmission.com.&quot; Once you've typed in the email addresses you want added to your list, simply click the &quot;Add&quot; button below. <br /> <br /> [[Image:3zimbraaddmembers.png]]<br /> <br /> <br /> ''Notes:''<br /> <br /> You can make lists members of other lists. This is a handy way to create umbrella lists. For example, if you wanted a staff list, but had various departments, you could add your employees to the departmental list, and then subscribe the departmental lists to the staff lists. This way, an account is only entered once, rather than adding an account to each list individually.<br /> <br /> Distribution Lists can also be used to forward domain based emails. For example, you may need to forward ''project@yourdomain.com'' to ''address@someotherdomain.com''. This does not require a Zimbra account for the primary domain email address.<br /> <br /> <br /> ==Updating Distribution List information==<br /> To add, change, or remove information from a list, simply double-click the list you want to edit. Alternatively, you can right-click the list you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> <br /> ==Forwarding Email to Another Address==<br /> If you wish to forward emails sent to your hosted email to another email address, first select '''Manage''' and then '''Accounts.''' Double-click the account you wish to edit or right-click and choose '''Edit''' from the pop-up menu. <br /> <br /> To add a forward, click on the '''Forwarding''' section on the left-hand column. <br /> <br /> [[Image:1zimbraforward.png]]<br /> <br /> <br /> Enter the following required information:<br /> <br /> * '''User-specified forwarding address''': This will be the email account that emails are forwarded to that the account owner is aware of. In the example below, we will be forwarding emails to &quot;bob.dobbs@xmission.com.&quot; <br /> <br /> [[Image:2zimbraforward.png]]<br /> <br /> <br /> Don't forget to choose &quot;Save&quot; near the upper right hand corner after you've added the forwarding address!<br /> <br /> <br /> * '''Forwarding addresses hidden from the user''': This can be a list of email accounts that emails are forwarded to that the account owner is unaware of. To do this, first click the &quot;Add&quot; button located below the '''Forwarding addresses hidden from the user''' box. It will prompt you to enter an email address. After you've done so, simply click &quot;Ok.&quot; In the example below, we will be forwarding messages to &quot;bobdobbs@xmission.com.&quot;<br /> <br /> [[Image:3zimbraforward.png]]<br /> <br /> NOTE: You may also use Distribution Lists to forward domain based emails without needing an account for the specific address. For example, you may need to forward ''project@mydomain.com'' to ''johndoe@someotheremail.com''. The advantage of using a Distribution List is that you eliminate the costs associated with maintaining an account just for forwarding.<br /> <br /> ==Granting Domain Administrator Access==<br /> <br /> To grant an account administrative privileges to your domain, load their account in the admin interface and check the &quot;Administrator&quot; checkbox below &quot;Class of Service&quot;. Once checked, a field will appear below, &quot;Administrator role&quot;. Enter &quot;admins@yourdomain.com&quot;, replacing yourdomain.com with the domain you are granting access to. This will add the user to a distribution list, &quot;admins&quot;, on your domain, which grants the privileges.<br /> <br /> Note that if the &quot;Administrator&quot; checkbox does not exist, you may need to add yourself to the &quot;admins&quot; distribution list manually and wait up to fifteen minutes.<br /> <br /> Many older domains had their admin account rights assigned via a different method, with a different set of privileges that did not include access to the &quot;Administrator&quot; checkbox (along with adjusting mailbox quotas and, for many older domains, the ability to change classes of service).<br /> <br /> ==Importing Accounts from Exchange==<br /> <br /> This article has moved: https://wiki.xmission.com/Zimbra_Migration:_Exchange_Import_Wizard<br /> <br /> ==Deleting a Zimbra Mailbox==<br /> <br /> There are two fairly simple ways to properly delete a Zimbra mailbox from the XMission system. <br /> <br /> * Log into the Zimbra domain administration panel https://zimbraadmin.xmission.com and select the &quot;Manage&quot; area on the left. Once in the management area you simply highlight the mailbox and then right-mouse click to show the option menu. Select &quot;Delete&quot; and confirm the mailbox deletion request. <br /> <br /> * From inside the domain administration panel you may also highlight the mailbox name and then click on the gear wheel in the top right corner of the browser screen to display an options menu. Inside this menu select &quot;Delete&quot; and confirm the deletion request.<br /> <br /> Notes: <br /> * Changing mailbox status is not the same as deletion. All provisioned mailboxes are billable.<br /> * Deletion of a mail domain cannot be completed via the domain admin interface and requires contacting XMission billing department.<br /> <br /> == Zimbra Themes ==<br /> <br /> You can see all the themes [https://wiki.xmission.com/Hosted_Email:_Admin_Panel/Zimbra_Themes here]<br /> <br /> <br /> [[Category:Zimbra|Admin Panel]]<br /> <br /> <br /> {{footer}}</div>

John https://wiki.xmission.com/index.php?title=Hosted_Email:_Admin_Panel&diff=10861 2021-06-25T19:50:59Z

<p>John: /* Deleting a Zimbra Mailbox */</p> <hr /> <div>==Overview/Logging In== <br /> The Zimbra domain administration console is the browser-based user interface used to centrally manage user accounts and most settings.<br /> <br /> As a domain administrator, you will be able to create and maintain the following:<br /> <br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_an_Email_Account Email accounts]<br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_an_Alias Mailbox aliases]<br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_a_Distribution_List Distribution lists]<br /> *Resources<br /> <br /> To login to the domain administration console, go to https://zimbraadmin.xmission.com/ and login with your administrative username and password. Domain administrators can also login from the dropdown menu next to your mailbox name in the top right corner of the webmail session. Click on 'Admin Console' to proceed.<br /> <br /> ==Domain Administrator Responsibilities==<br /> <br /> It is important to understand that as domain administrators you are responsible for changing passwords, creating distribution lists, setting email forwards, managing mailboxes, training on phishing, and etc. Our support policy for email is clearly outlined at: https://xmission.com/legal_policies#emlsup We require domain administrators be added as Technical contacts on your billing account in order to receive advanced assistance from our support staff. Please keep contacts up-to-date in the [https://xmission.com/control account management portal] or contact [https://xmission.com/contact XMission Billing] for assistance.<br /> <br /> Phishing and email scams are on the rise. It is important to educate yourself and your mailbox holders on how to avoid it. Reference this guide on <br /> [https://wiki.xmission.com/Phishing_and_Email_Scams understanding phishing].<br /> <br /> ==Email Domain Health==<br /> <br /> An important part of effective business email mean protecting your domain with some simple settings to improve delivery and reduce fraud.<br /> <br /> XMission advises implementing SPF and DKIM on domains. These are two simple methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf and prevent abuse. [https://wiki.xmission.com/SPF_and_DKIM How to configure SPF and DKIM]<br /> <br /> ==About the Administrative Console==<br /> <br /> The area above the '''Content''' pane includes the '''Search''' and '''Help''' functions.<br /> <br /> '''Search''' allows you to quickly find accounts, aliases, distribution lists and resources for editing. <br /> <br /> '''Help''' utilizes Zimbra’s wiki, forums, and documentation. This is a powerful unified search to quickly find answers to common questions.<br /> <br /> [[Image:1zimbraadminpanel.png]]<br /> <br /> <br /> <br /> The '''Navigation''' pane on the left includes the following sections:<br /> <br /> *'''Home:''' At any time, clicking here will return you to the administrative Home options. <br /> <br /> *'''Manage:''' Clicking here will permit you to create and edit any accounts, aliases, distribution lists, and resources for your domain(s). <br /> <br /> *'''Help:''' utilizes Zimbra’s wiki, forums, and documentation. This is a powerful unified search to quickly find answers to common questions. <br /> <br /> [[Image:4zimbraadminpanel.png]]<br /> <br /> <br /> <br /> Alternatively, you can also click on the arrow beside the &quot;Home&quot; button. This will give you the same options listed above, as well as recent searches and the options available under &quot;Manage.&quot; In this example, the recent search was for &quot;xdesign.com.&quot;<br /> <br /> [[Image:2zimbraadminpanel.png]]<br /> <br /> <br /> <br /> Clicking on &quot;Manage&quot; either way will permit you to make changes to your existing accounts, aliases, distribution lists, and resources.<br /> <br /> *'''Accounts:''' Lists all accounts. In the Accounts folder, you create and manage end-user accounts, setting options, class of service, passwords and aliases for an account.<br /> <br /> *'''Aliases:''' Lists all aliases that have been created in Accounts. You can use the Move Alias feature from the toolbar to move an alias from one account to another.<br /> <br /> *'''Distribution Lists:''' Lists all distribution lists. You can create new distribution lists and add or delete members of a distribution list.<br /> <br /> *'''Resources:''' This lists locations or equipment that can be scheduled from your Calendar. Here is where you can create new resources and set the scheduling policy for the resource.<br /> <br /> [[Image:3zimbraadminpanel.png]]<br /> <br /> <br /> ==Creating an Email Account== <br /> Select '''Manage''' and then '''Accounts''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the email mailbox you are about to create. Enter the following required information:<br /> <br /> * '''Account Name''': This will be the mailbox account that you are about to create. In this example, we are creating &quot;bobdobbs@xdesign.com.&quot;<br /> * '''First Name''': The first name of the email user. <br /> * '''Last Name''': The last name of the email user.<br /> [[Image:1zimbraaddaccount.png]]<br /> <br /> When creating a new mailbox account you will set the Class of Service (CoS) under '''General Information / Account Setup / Class of Service'''. Don't forget to deselect the &quot;[ ] auto&quot; box to enter the class type.<br /> <br /> You may mix and match Class of Service (CoS) for mailbox accounts in your domain to maximize benefits for your organization. Details below.<br /> <br /> Something to note, XMission identifies a billable Zimbra account as mailbox with a physical email Inbox and typically belonging to one person. So even if it is not &quot;active&quot; but still provisioned, it will count toward billing. Example, a mailbox set to &quot;closed&quot; or &quot;maintenance&quot; status remains billable.<br /> <br /> ==Class of Service==<br /> <br /> To '''upgrade''' an existing account, or to change existing accounts, simply log in to the admin interface, click on '''&quot;Manage&quot;''' and select the user by double-clicking on the name. Inside the '''&quot;General Information&quot;''' pane you will see '''&quot;Account Setup&quot;''' in the middle of the page. In this area you will find '''&quot;Class of Service&quot;''' with an input box next to it and the &quot;[x] auto&quot; box checked. Deselect the &quot;[ ] auto&quot; box and type '''&quot;xmpremium&quot;''' or '''&quot;xmbase&quot;''' in the field and then hit '''&quot;Save&quot;''' towards the top right of the window. Your account is now set to the selected service level with all the features and storage associated with the account type.<br /> <br /> Click the '''&quot;Finish&quot;''' button. You will be returned to the main admin screen, and the new account will have been created at the established service level.<br /> <br /> NOTE: If the &quot;Class of Service&quot; field is not available to you, you may need to add your admin account's email address to the &quot;admins&quot; distribution list on your domain and wait up to fifteen minutes. Some older accounts do not have this setup automatically. See [https://wiki.xmission.com/Zimbra_Hosting_Admin#Granting_Domain_Administrator_Access Granting Domain Administrator Access] for more details.<br /> <br /> ==Updating Account Information==<br /> To add, change, or remove information from an account, simply double-click the account you want to edit. Alternatively, you can right-click the account you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> ==Change Password==<br /> <br /> All Zimbra domain administrator should read this quick blog post on email security: https://xmission.com/blog/2017/10/17/best-practices-for-zimbra-email-security<br /> <br /> Changing your end-user mailbox password through the Zimbra [https://zimbraadmin.xmission.com domain admin control panel] is easy, but first let's review XMission password best practices.<br /> <br /> '''XMission Zimbra Password requirements:''' <br /> <br /> XMission recommends secure passphrases consisting of five to six words, with a few special characters and numbers, since they can be much easier to remember.<br /> <br /> * Ideally it is best to use longer, more complex passphrases to properly protect your mailboxes, and your company, from hackers. Our Zimbra system supports passwords up to 64 characters. We advise using a minimum passphrase length of 12-15 characters with 25-28 characters providing very reasonable security. <br /> * Shorter passwords require use of at least 1 of the following: UPPER CASE letter, lower case letter, special characters, and a numeral to meet minimum security requirements.<br /> * Passwords expire after 1 year and must be changed at that time. Changing more frequently is advised.<br /> * You cannot re-use your current password.<br /> * Please allow 15 minutes for the new password to propagate through the system.<br /> * Write credentials down in a secure place until you memorize it then destroy the note.<br /> * Here is a quick and easy to understand visual tutorial on password security: [https://xmission.com/blog/2017/10/17/best-practices-for-zimbra-email-security | https://xkcd.com/936/ ]<br /> <br /> '''Three ways to change passwords from domain admin control panel:'''<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column. Right-mouse click on the mailbox name to reveal a drop down menu, select &quot;Change password.&quot;<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column and highlight a mailbox. Now right-mouse click on the gear icon in the top right corner. Select &quot;Change password&quot;.<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column and double click on the desired mailbox. When it opens the settings page of the mailbox use the &quot;Password&quot; area to change the password.<br /> <br /> NOTE: XMission Zimbra servers will allow a password as short as 12 characters. Short passwords are poor security. Please take the time to protect your company email data buy using a passphrase in the 25-28 character length.<br /> <br /> ==Password Expiration and Failed Login Attempts==<br /> Please note the following details about XMission's email password expiration and failed login attempts policy.<br /> <br /> Should you ever have an end-user mailbox that is not allowing login there are two primary reasons for this. <br /> * The password has expired. <br /> * There have been too many failed login attempts to the account causing it to be temporarily suspended.<br /> <br /> ==== Expired Password ====<br /> <br /> All XMission email passwords must be changed once yearly. XMission sends email notices to the user mailbox 2 (two) weeks before expiration. Please ask your mailbox owners to change their password in a timely manner.<br /> <br /> Domain administrators are *not* emailed about the user mailbox need to change their password. Repeat, domain administrators are not emailed about password expirations.<br /> <br /> ==== Failed Login Attempt - Mailbox Access Suspension ====<br /> <br /> Failed login attempt account suspension practices are a way to safeguard mailboxes from brute force attacks where a bad actor is trying to access the sensitive information inside. XMission protects customer mailboxes by temporarily suspending mail accounts with too many failed login attempts. <br /> <br /> If you, or another entity, are trying to access the account with too many failed password attempts within the monitoring cycle, the system blocks access for a short period of time, after which you can again attempt to authenticate with correct credentials.<br /> <br /> '''Failed login attempt definition:''' Improper entry of a password for a valid mailbox. <br /> <br /> '''How failed login attempts are measured and enforced:''' When the first failed login attempt occurs, the monitoring cycle begins. Thereafter, each time a unique wrong password fails, that adds to the count. <br /> <br /> It is important to note that when the ''same'' wrong password is used, from any number of IP addresses or devices, it only counts as one (1) failed login attempt.<br /> <br /> During the monitoring cycle, if additional failed login attempts are made using a different password from the original attempt, it add to the failed login attempt total. IE: Bad password &quot;A&quot; activates monitoring period. A second unique password &quot;B&quot; is used bringing the total to two (2) failed attempts. If password &quot;A&quot; is used again, it counts as another new unique password totaling three (3) failed attempts. <br /> <br /> Once the maximum number of failed attempts is reached, access to the mailbox is temporarily suspended.<br /> <br /> ==== Troubleshooting ====<br /> <br /> Mailbox accounts having failed login issues appear to have the same symptoms as an expired password. The way to test is to access webmail, https://zimbra.xmission.com, with your credentials. If the password is expired it will prompt you to set a new password immediately. If the account is locked out, it will simply not validate with the credentials until the suspension period ends.<br /> <br /> If an account is temporarily suspended for too many failed password attempts you need to either wait for the suspension period to pass, reset the mailbox status to active in the domain admin panel, or contact XMission Support to have the suspension manually removed.<br /> <br /> Domain administrators can change mailbox status and passwords via the domain admin interface.<br /> <br /> NOTE: Use of Two-Factor Authentication (2FA) does not prevent account suspension due to failed authentication attempts.<br /> <br /> ==Mailbox locked for abuse==<br /> <br /> A user mailbox can also be locked for abuse. This abuse can be due to any of the following reasons;<br /> * Successfully compromised by a phishing attempt and shared their password with someone they shouldn't have.<br /> * Use of a previously compromised password on another Internet site or service.<br /> * Malware on a computer or device.<br /> * Rootkit on the computer.<br /> <br /> ''Symptoms of abuse:''<br /> <br /> Domain administrators often ask why a mailbox was locked for a spam run when they do not see evidence of malicious messages in the Sent folder. The primary reason for this is because the spammers use SMTP mail applications that do not sync the Sent mail folder. Only messages sent via the Zimbra webmail interface, via Outlook with the Zimbra Connector, or sent via ActiveSync (Exchange) configuration on mobile devices, will sync Sent messages to the mail system. So a bad actor can send copious amounts of unwanted email quickly and with no trace the end user can see. However, XMission has logs for all messages sent which we use to identify and lock accounts as well as to train system rules to prevent future abuse. <br /> <br /> Determining why a mailbox has been locked for abuse can be difficult. XMission will do their best to provide data on what was compromised and how. In some cases this is possible, in others it is not. Most often phishing and re-used passwords are the primary attack vector resulting in a locked user mailbox.<br /> <br /> &quot;The remedy:&quot;<br /> <br /> Regardless of the &quot;how&quot; all compromised mailbox users are required to change their password immediately to continue using the service. It is imperative that domain administrators do not re-use passwords or set poor temporary passwords. <br /> <br /> We strongly advise in the use of long passwords (pass phrases) and password managers such as BitWarden, Keepass, and similar.<br /> <br /> Additional compromises of the same mailbox will result in a small fine which we hope is just enough to encourage proper mailbox security. You can read about this policy here: https://xmission.com/blog/2019/05/14/our-new-compromised-email-policy<br /> <br /> ==Creating an Alias==<br /> Select '''Manage''' and then '''Aliases''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the email alias you wish to create. Enter the following required information:<br /> <br /> *'''Alias''': This is the aliased address you will create. In this example, we are adding &quot;bob.dobbs@xdesign.com.&quot; <br /> *'''Target Account''': This is the actual email box that will receive any emails directed to the aliases address. <br /> [[Image:1zimbraaddalias.png]]<br /> <br /> <br /> Click &quot;Ok&quot; to add your new alias.<br /> <br /> <br /> ==Updating Alias Information==<br /> To add, change, or remove information from an alias, simply double-click the alias you want to edit. Alternatively, you can right-click the alias you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> <br /> ==Creating a Distribution List==<br /> Select '''Manage''' and then '''Distribution Lists''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the distribution list you wish to create. Enter the following required information:<br /> <br /> * '''List Name''': This will be the email address for the mailing list. <br /> * '''Display Name''': This can be a descriptive name for the list. <br /> <br /> [[Image:1zimbraaddlist.png]]<br /> <br /> <br /> To add email addresses to the list, scroll a bit to the right and you will see a &quot;Search&quot; button below the '''Add Members to this list''' section. If you want add email addresses that are withing your Zimbra package, search for the appropriate domain name(s). In this case, we searched for &quot;xdesign.com.&quot; Highlight any results you would like to be added to the list.<br /> <br /> [[Image:1zimbraaddmembers.png]]<br /> <br /> <br /> Using the scroll bar on the right, scroll down and click the &quot;Add Selected&quot; button. <br /> <br /> [[Image:2zimbraaddmembers.png]]<br /> <br /> <br /> If you want to manually add addresses or need to add addresses that are not within Zimbra's search function, you can type the email addresses in the box pictured below. In this case, we are adding two email addresses to the list -- &quot;bobdobbs@gmail.com&quot; and &quot;bigguyjake@xmission.com.&quot; Once you've typed in the email addresses you want added to your list, simply click the &quot;Add&quot; button below. <br /> <br /> [[Image:3zimbraaddmembers.png]]<br /> <br /> <br /> ''Notes:''<br /> <br /> You can make lists members of other lists. This is a handy way to create umbrella lists. For example, if you wanted a staff list, but had various departments, you could add your employees to the departmental list, and then subscribe the departmental lists to the staff lists. This way, an account is only entered once, rather than adding an account to each list individually.<br /> <br /> Distribution Lists can also be used to forward domain based emails. For example, you may need to forward ''project@yourdomain.com'' to ''address@someotherdomain.com''. This does not require a Zimbra account for the primary domain email address.<br /> <br /> <br /> ==Updating Distribution List information==<br /> To add, change, or remove information from a list, simply double-click the list you want to edit. Alternatively, you can right-click the list you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> <br /> ==Forwarding Email to Another Address==<br /> If you wish to forward emails sent to your hosted email to another email address, first select '''Manage''' and then '''Accounts.''' Double-click the account you wish to edit or right-click and choose '''Edit''' from the pop-up menu. <br /> <br /> To add a forward, click on the '''Forwarding''' section on the left-hand column. <br /> <br /> [[Image:1zimbraforward.png]]<br /> <br /> <br /> Enter the following required information:<br /> <br /> * '''User-specified forwarding address''': This will be the email account that emails are forwarded to that the account owner is aware of. In the example below, we will be forwarding emails to &quot;bob.dobbs@xmission.com.&quot; <br /> <br /> [[Image:2zimbraforward.png]]<br /> <br /> <br /> Don't forget to choose &quot;Save&quot; near the upper right hand corner after you've added the forwarding address!<br /> <br /> <br /> * '''Forwarding addresses hidden from the user''': This can be a list of email accounts that emails are forwarded to that the account owner is unaware of. To do this, first click the &quot;Add&quot; button located below the '''Forwarding addresses hidden from the user''' box. It will prompt you to enter an email address. After you've done so, simply click &quot;Ok.&quot; In the example below, we will be forwarding messages to &quot;bobdobbs@xmission.com.&quot;<br /> <br /> [[Image:3zimbraforward.png]]<br /> <br /> NOTE: You may also use Distribution Lists to forward domain based emails without needing an account for the specific address. For example, you may need to forward ''project@mydomain.com'' to ''johndoe@someotheremail.com''. The advantage of using a Distribution List is that you eliminate the costs associated with maintaining an account just for forwarding.<br /> <br /> ==Granting Domain Administrator Access==<br /> <br /> To grant an account administrative privileges to your domain, load their account in the admin interface and check the &quot;Administrator&quot; checkbox below &quot;Class of Service&quot;. Once checked, a field will appear below, &quot;Administrator role&quot;. Enter &quot;admins@yourdomain.com&quot;, replacing yourdomain.com with the domain you are granting access to. This will add the user to a distribution list, &quot;admins&quot;, on your domain, which grants the privileges.<br /> <br /> Note that if the &quot;Administrator&quot; checkbox does not exist, you may need to add yourself to the &quot;admins&quot; distribution list manually and wait up to fifteen minutes.<br /> <br /> Many older domains had their admin account rights assigned via a different method, with a different set of privileges that did not include access to the &quot;Administrator&quot; checkbox (along with adjusting mailbox quotas and, for many older domains, the ability to change classes of service).<br /> <br /> ==Importing Accounts from Exchange==<br /> <br /> This article has moved: https://wiki.xmission.com/Zimbra_Migration:_Exchange_Import_Wizard<br /> <br /> ==Deleting a Zimbra Mailbox==<br /> <br /> There are two fairly simple ways to properly delete a Zimbra mailbox from the XMission system. <br /> <br /> * Log into the Zimbra domain administration panel https://zimbraadmin.xmission.com and select the &quot;Manage&quot; area on the left. Once in the management area you simply highlight the mailbox and then right-mouse click to show the option menu. Select &quot;Delete&quot; and confirm the mailbox deletion request. <br /> <br /> * From inside the domain administration panel you may also highlight the mailbox name and then click on the gear wheel in the top right corner of the browser screen to display an options menu. Inside this menu select &quot;Delete&quot; and confirm the deletion request.<br /> <br /> Notes: <br /> * Changing an account status is not the same as deleting the account. All provisioned mailboxes are billable.<br /> * Deletion of a mail domain cannot be completed via the domain admin interface and requires contacting XMission billing department.<br /> <br /> == Zimbra Themes ==<br /> <br /> You can see all the themes [https://wiki.xmission.com/Hosted_Email:_Admin_Panel/Zimbra_Themes here]<br /> <br /> <br /> [[Category:Zimbra|Admin Panel]]<br /> <br /> <br /> {{footer}}</div>

John https://wiki.xmission.com/index.php?title=Hosted_Email:_Admin_Panel&diff=10860 2021-06-25T18:35:03Z

<p>John: /* Deleting a Zimbra Mailbox */</p> <hr /> <div>==Overview/Logging In== <br /> The Zimbra domain administration console is the browser-based user interface used to centrally manage user accounts and most settings.<br /> <br /> As a domain administrator, you will be able to create and maintain the following:<br /> <br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_an_Email_Account Email accounts]<br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_an_Alias Mailbox aliases]<br /> *[https://wiki.xmission.com/Hosted_Email:_Admin_Panel#Creating_a_Distribution_List Distribution lists]<br /> *Resources<br /> <br /> To login to the domain administration console, go to https://zimbraadmin.xmission.com/ and login with your administrative username and password. Domain administrators can also login from the dropdown menu next to your mailbox name in the top right corner of the webmail session. Click on 'Admin Console' to proceed.<br /> <br /> ==Domain Administrator Responsibilities==<br /> <br /> It is important to understand that as domain administrators you are responsible for changing passwords, creating distribution lists, setting email forwards, managing mailboxes, training on phishing, and etc. Our support policy for email is clearly outlined at: https://xmission.com/legal_policies#emlsup We require domain administrators be added as Technical contacts on your billing account in order to receive advanced assistance from our support staff. Please keep contacts up-to-date in the [https://xmission.com/control account management portal] or contact [https://xmission.com/contact XMission Billing] for assistance.<br /> <br /> Phishing and email scams are on the rise. It is important to educate yourself and your mailbox holders on how to avoid it. Reference this guide on <br /> [https://wiki.xmission.com/Phishing_and_Email_Scams understanding phishing].<br /> <br /> ==Email Domain Health==<br /> <br /> An important part of effective business email mean protecting your domain with some simple settings to improve delivery and reduce fraud.<br /> <br /> XMission advises implementing SPF and DKIM on domains. These are two simple methods domain owners have of &quot;authorizing&quot; specific email servers to send mail on their behalf and prevent abuse. [https://wiki.xmission.com/SPF_and_DKIM How to configure SPF and DKIM]<br /> <br /> ==About the Administrative Console==<br /> <br /> The area above the '''Content''' pane includes the '''Search''' and '''Help''' functions.<br /> <br /> '''Search''' allows you to quickly find accounts, aliases, distribution lists and resources for editing. <br /> <br /> '''Help''' utilizes Zimbra’s wiki, forums, and documentation. This is a powerful unified search to quickly find answers to common questions.<br /> <br /> [[Image:1zimbraadminpanel.png]]<br /> <br /> <br /> <br /> The '''Navigation''' pane on the left includes the following sections:<br /> <br /> *'''Home:''' At any time, clicking here will return you to the administrative Home options. <br /> <br /> *'''Manage:''' Clicking here will permit you to create and edit any accounts, aliases, distribution lists, and resources for your domain(s). <br /> <br /> *'''Help:''' utilizes Zimbra’s wiki, forums, and documentation. This is a powerful unified search to quickly find answers to common questions. <br /> <br /> [[Image:4zimbraadminpanel.png]]<br /> <br /> <br /> <br /> Alternatively, you can also click on the arrow beside the &quot;Home&quot; button. This will give you the same options listed above, as well as recent searches and the options available under &quot;Manage.&quot; In this example, the recent search was for &quot;xdesign.com.&quot;<br /> <br /> [[Image:2zimbraadminpanel.png]]<br /> <br /> <br /> <br /> Clicking on &quot;Manage&quot; either way will permit you to make changes to your existing accounts, aliases, distribution lists, and resources.<br /> <br /> *'''Accounts:''' Lists all accounts. In the Accounts folder, you create and manage end-user accounts, setting options, class of service, passwords and aliases for an account.<br /> <br /> *'''Aliases:''' Lists all aliases that have been created in Accounts. You can use the Move Alias feature from the toolbar to move an alias from one account to another.<br /> <br /> *'''Distribution Lists:''' Lists all distribution lists. You can create new distribution lists and add or delete members of a distribution list.<br /> <br /> *'''Resources:''' This lists locations or equipment that can be scheduled from your Calendar. Here is where you can create new resources and set the scheduling policy for the resource.<br /> <br /> [[Image:3zimbraadminpanel.png]]<br /> <br /> <br /> ==Creating an Email Account== <br /> Select '''Manage''' and then '''Accounts''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the email mailbox you are about to create. Enter the following required information:<br /> <br /> * '''Account Name''': This will be the mailbox account that you are about to create. In this example, we are creating &quot;bobdobbs@xdesign.com.&quot;<br /> * '''First Name''': The first name of the email user. <br /> * '''Last Name''': The last name of the email user.<br /> [[Image:1zimbraaddaccount.png]]<br /> <br /> When creating a new mailbox account you will set the Class of Service (CoS) under '''General Information / Account Setup / Class of Service'''. Don't forget to deselect the &quot;[ ] auto&quot; box to enter the class type.<br /> <br /> You may mix and match Class of Service (CoS) for mailbox accounts in your domain to maximize benefits for your organization. Details below.<br /> <br /> Something to note, XMission identifies a billable Zimbra account as mailbox with a physical email Inbox and typically belonging to one person. So even if it is not &quot;active&quot; but still provisioned, it will count toward billing. Example, a mailbox set to &quot;closed&quot; or &quot;maintenance&quot; status remains billable.<br /> <br /> ==Class of Service==<br /> <br /> To '''upgrade''' an existing account, or to change existing accounts, simply log in to the admin interface, click on '''&quot;Manage&quot;''' and select the user by double-clicking on the name. Inside the '''&quot;General Information&quot;''' pane you will see '''&quot;Account Setup&quot;''' in the middle of the page. In this area you will find '''&quot;Class of Service&quot;''' with an input box next to it and the &quot;[x] auto&quot; box checked. Deselect the &quot;[ ] auto&quot; box and type '''&quot;xmpremium&quot;''' or '''&quot;xmbase&quot;''' in the field and then hit '''&quot;Save&quot;''' towards the top right of the window. Your account is now set to the selected service level with all the features and storage associated with the account type.<br /> <br /> Click the '''&quot;Finish&quot;''' button. You will be returned to the main admin screen, and the new account will have been created at the established service level.<br /> <br /> NOTE: If the &quot;Class of Service&quot; field is not available to you, you may need to add your admin account's email address to the &quot;admins&quot; distribution list on your domain and wait up to fifteen minutes. Some older accounts do not have this setup automatically. See [https://wiki.xmission.com/Zimbra_Hosting_Admin#Granting_Domain_Administrator_Access Granting Domain Administrator Access] for more details.<br /> <br /> ==Updating Account Information==<br /> To add, change, or remove information from an account, simply double-click the account you want to edit. Alternatively, you can right-click the account you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> ==Change Password==<br /> <br /> All Zimbra domain administrator should read this quick blog post on email security: https://xmission.com/blog/2017/10/17/best-practices-for-zimbra-email-security<br /> <br /> Changing your end-user mailbox password through the Zimbra [https://zimbraadmin.xmission.com domain admin control panel] is easy, but first let's review XMission password best practices.<br /> <br /> '''XMission Zimbra Password requirements:''' <br /> <br /> XMission recommends secure passphrases consisting of five to six words, with a few special characters and numbers, since they can be much easier to remember.<br /> <br /> * Ideally it is best to use longer, more complex passphrases to properly protect your mailboxes, and your company, from hackers. Our Zimbra system supports passwords up to 64 characters. We advise using a minimum passphrase length of 12-15 characters with 25-28 characters providing very reasonable security. <br /> * Shorter passwords require use of at least 1 of the following: UPPER CASE letter, lower case letter, special characters, and a numeral to meet minimum security requirements.<br /> * Passwords expire after 1 year and must be changed at that time. Changing more frequently is advised.<br /> * You cannot re-use your current password.<br /> * Please allow 15 minutes for the new password to propagate through the system.<br /> * Write credentials down in a secure place until you memorize it then destroy the note.<br /> * Here is a quick and easy to understand visual tutorial on password security: [https://xmission.com/blog/2017/10/17/best-practices-for-zimbra-email-security | https://xkcd.com/936/ ]<br /> <br /> '''Three ways to change passwords from domain admin control panel:'''<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column. Right-mouse click on the mailbox name to reveal a drop down menu, select &quot;Change password.&quot;<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column and highlight a mailbox. Now right-mouse click on the gear icon in the top right corner. Select &quot;Change password&quot;.<br /> * Inside the control panel main page click on &quot;Manage&quot; in left column and double click on the desired mailbox. When it opens the settings page of the mailbox use the &quot;Password&quot; area to change the password.<br /> <br /> NOTE: XMission Zimbra servers will allow a password as short as 12 characters. Short passwords are poor security. Please take the time to protect your company email data buy using a passphrase in the 25-28 character length.<br /> <br /> ==Password Expiration and Failed Login Attempts==<br /> Please note the following details about XMission's email password expiration and failed login attempts policy.<br /> <br /> Should you ever have an end-user mailbox that is not allowing login there are two primary reasons for this. <br /> * The password has expired. <br /> * There have been too many failed login attempts to the account causing it to be temporarily suspended.<br /> <br /> ==== Expired Password ====<br /> <br /> All XMission email passwords must be changed once yearly. XMission sends email notices to the user mailbox 2 (two) weeks before expiration. Please ask your mailbox owners to change their password in a timely manner.<br /> <br /> Domain administrators are *not* emailed about the user mailbox need to change their password. Repeat, domain administrators are not emailed about password expirations.<br /> <br /> ==== Failed Login Attempt - Mailbox Access Suspension ====<br /> <br /> Failed login attempt account suspension practices are a way to safeguard mailboxes from brute force attacks where a bad actor is trying to access the sensitive information inside. XMission protects customer mailboxes by temporarily suspending mail accounts with too many failed login attempts. <br /> <br /> If you, or another entity, are trying to access the account with too many failed password attempts within the monitoring cycle, the system blocks access for a short period of time, after which you can again attempt to authenticate with correct credentials.<br /> <br /> '''Failed login attempt definition:''' Improper entry of a password for a valid mailbox. <br /> <br /> '''How failed login attempts are measured and enforced:''' When the first failed login attempt occurs, the monitoring cycle begins. Thereafter, each time a unique wrong password fails, that adds to the count. <br /> <br /> It is important to note that when the ''same'' wrong password is used, from any number of IP addresses or devices, it only counts as one (1) failed login attempt.<br /> <br /> During the monitoring cycle, if additional failed login attempts are made using a different password from the original attempt, it add to the failed login attempt total. IE: Bad password &quot;A&quot; activates monitoring period. A second unique password &quot;B&quot; is used bringing the total to two (2) failed attempts. If password &quot;A&quot; is used again, it counts as another new unique password totaling three (3) failed attempts. <br /> <br /> Once the maximum number of failed attempts is reached, access to the mailbox is temporarily suspended.<br /> <br /> ==== Troubleshooting ====<br /> <br /> Mailbox accounts having failed login issues appear to have the same symptoms as an expired password. The way to test is to access webmail, https://zimbra.xmission.com, with your credentials. If the password is expired it will prompt you to set a new password immediately. If the account is locked out, it will simply not validate with the credentials until the suspension period ends.<br /> <br /> If an account is temporarily suspended for too many failed password attempts you need to either wait for the suspension period to pass, reset the mailbox status to active in the domain admin panel, or contact XMission Support to have the suspension manually removed.<br /> <br /> Domain administrators can change mailbox status and passwords via the domain admin interface.<br /> <br /> NOTE: Use of Two-Factor Authentication (2FA) does not prevent account suspension due to failed authentication attempts.<br /> <br /> ==Mailbox locked for abuse==<br /> <br /> A user mailbox can also be locked for abuse. This abuse can be due to any of the following reasons;<br /> * Successfully compromised by a phishing attempt and shared their password with someone they shouldn't have.<br /> * Use of a previously compromised password on another Internet site or service.<br /> * Malware on a computer or device.<br /> * Rootkit on the computer.<br /> <br /> ''Symptoms of abuse:''<br /> <br /> Domain administrators often ask why a mailbox was locked for a spam run when they do not see evidence of malicious messages in the Sent folder. The primary reason for this is because the spammers use SMTP mail applications that do not sync the Sent mail folder. Only messages sent via the Zimbra webmail interface, via Outlook with the Zimbra Connector, or sent via ActiveSync (Exchange) configuration on mobile devices, will sync Sent messages to the mail system. So a bad actor can send copious amounts of unwanted email quickly and with no trace the end user can see. However, XMission has logs for all messages sent which we use to identify and lock accounts as well as to train system rules to prevent future abuse. <br /> <br /> Determining why a mailbox has been locked for abuse can be difficult. XMission will do their best to provide data on what was compromised and how. In some cases this is possible, in others it is not. Most often phishing and re-used passwords are the primary attack vector resulting in a locked user mailbox.<br /> <br /> &quot;The remedy:&quot;<br /> <br /> Regardless of the &quot;how&quot; all compromised mailbox users are required to change their password immediately to continue using the service. It is imperative that domain administrators do not re-use passwords or set poor temporary passwords. <br /> <br /> We strongly advise in the use of long passwords (pass phrases) and password managers such as BitWarden, Keepass, and similar.<br /> <br /> Additional compromises of the same mailbox will result in a small fine which we hope is just enough to encourage proper mailbox security. You can read about this policy here: https://xmission.com/blog/2019/05/14/our-new-compromised-email-policy<br /> <br /> ==Creating an Alias==<br /> Select '''Manage''' and then '''Aliases''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the email alias you wish to create. Enter the following required information:<br /> <br /> *'''Alias''': This is the aliased address you will create. In this example, we are adding &quot;bob.dobbs@xdesign.com.&quot; <br /> *'''Target Account''': This is the actual email box that will receive any emails directed to the aliases address. <br /> [[Image:1zimbraaddalias.png]]<br /> <br /> <br /> Click &quot;Ok&quot; to add your new alias.<br /> <br /> <br /> ==Updating Alias Information==<br /> To add, change, or remove information from an alias, simply double-click the alias you want to edit. Alternatively, you can right-click the alias you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> <br /> ==Creating a Distribution List==<br /> Select '''Manage''' and then '''Distribution Lists''' section. Click on the gear icon [[Image:gear_icon.png]] and select '''New'''. This will open a dialogue asking for information about the distribution list you wish to create. Enter the following required information:<br /> <br /> * '''List Name''': This will be the email address for the mailing list. <br /> * '''Display Name''': This can be a descriptive name for the list. <br /> <br /> [[Image:1zimbraaddlist.png]]<br /> <br /> <br /> To add email addresses to the list, scroll a bit to the right and you will see a &quot;Search&quot; button below the '''Add Members to this list''' section. If you want add email addresses that are withing your Zimbra package, search for the appropriate domain name(s). In this case, we searched for &quot;xdesign.com.&quot; Highlight any results you would like to be added to the list.<br /> <br /> [[Image:1zimbraaddmembers.png]]<br /> <br /> <br /> Using the scroll bar on the right, scroll down and click the &quot;Add Selected&quot; button. <br /> <br /> [[Image:2zimbraaddmembers.png]]<br /> <br /> <br /> If you want to manually add addresses or need to add addresses that are not within Zimbra's search function, you can type the email addresses in the box pictured below. In this case, we are adding two email addresses to the list -- &quot;bobdobbs@gmail.com&quot; and &quot;bigguyjake@xmission.com.&quot; Once you've typed in the email addresses you want added to your list, simply click the &quot;Add&quot; button below. <br /> <br /> [[Image:3zimbraaddmembers.png]]<br /> <br /> <br /> ''Notes:''<br /> <br /> You can make lists members of other lists. This is a handy way to create umbrella lists. For example, if you wanted a staff list, but had various departments, you could add your employees to the departmental list, and then subscribe the departmental lists to the staff lists. This way, an account is only entered once, rather than adding an account to each list individually.<br /> <br /> Distribution Lists can also be used to forward domain based emails. For example, you may need to forward ''project@yourdomain.com'' to ''address@someotherdomain.com''. This does not require a Zimbra account for the primary domain email address.<br /> <br /> <br /> ==Updating Distribution List information==<br /> To add, change, or remove information from a list, simply double-click the list you want to edit. Alternatively, you can right-click the list you wish to update and choose &quot;Edit&quot; from the pop-up menu.<br /> <br /> <br /> ==Forwarding Email to Another Address==<br /> If you wish to forward emails sent to your hosted email to another email address, first select '''Manage''' and then '''Accounts.''' Double-click the account you wish to edit or right-click and choose '''Edit''' from the pop-up menu. <br /> <br /> To add a forward, click on the '''Forwarding''' section on the left-hand column. <br /> <br /> [[Image:1zimbraforward.png]]<br /> <br /> <br /> Enter the following required information:<br /> <br /> * '''User-specified forwarding address''': This will be the email account that emails are forwarded to that the account owner is aware of. In the example below, we will be forwarding emails to &quot;bob.dobbs@xmission.com.&quot; <br /> <br /> [[Image:2zimbraforward.png]]<br /> <br /> <br /> Don't forget to choose &quot;Save&quot; near the upper right hand corner after you've added the forwarding address!<br /> <br /> <br /> * '''Forwarding addresses hidden from the user''': This can be a list of email accounts that emails are forwarded to that the account owner is unaware of. To do this, first click the &quot;Add&quot; button located below the '''Forwarding addresses hidden from the user''' box. It will prompt you to enter an email address. After you've done so, simply click &quot;Ok.&quot; In the example below, we will be forwarding messages to &quot;bobdobbs@xmission.com.&quot;<br /> <br /> [[Image:3zimbraforward.png]]<br /> <br /> NOTE: You may also use Distribution Lists to forward domain based emails without needing an account for the specific address. For example, you may need to forward ''project@mydomain.com'' to ''johndoe@someotheremail.com''. The advantage of using a Distribution List is that you eliminate the costs associated with maintaining an account just for forwarding.<br /> <br /> ==Granting Domain Administrator Access==<br /> <br /> To grant an account administrative privileges to your domain, load their account in the admin interface and check the &quot;Administrator&quot; checkbox below &quot;Class of Service&quot;. Once checked, a field will appear below, &quot;Administrator role&quot;. Enter &quot;admins@yourdomain.com&quot;, replacing yourdomain.com with the domain you are granting access to. This will add the user to a distribution list, &quot;admins&quot;, on your domain, which grants the privileges.<br /> <br /> Note that if the &quot;Administrator&quot; checkbox does not exist, you may need to add yourself to the &quot;admins&quot; distribution list manually and wait up to fifteen minutes.<br /> <br /> Many older domains had their admin account rights assigned via a different method, with a different set of privileges that did not include access to the &quot;Administrator&quot; checkbox (along with adjusting mailbox quotas and, for many older domains, the ability to change classes of service).<br /> <br /> ==Importing Accounts from Exchange==<br /> <br /> This article has moved: https://wiki.xmission.com/Zimbra_Migration:_Exchange_Import_Wizard<br /> <br /> ==Deleting a Zimbra Mailbox==<br /> <br /> There are two fairly simple ways to properly delete a Zimbra mailbox from the XMission system. <br /> <br /> * Log into the Zimbra domain administration panel https://zimbraadmin.xmission.com and select the &quot;Manage&quot; area on the left. Once in the management area you simply highlight the mailbox and then right-mouse click to show the option menu. Select &quot;Delete&quot; and confirm the mailbox deletion request. <br /> <br /> * From inside the domain administration panel you may also highlight the mailbox name and then click on the gear wheel in the top right corner of the browser screen to display an options menu. Inside this menu select &quot;Delete&quot; and confirm the deletion request.<br /> <br /> Note: Changing an account status is not the same as deleting the account and will still be billed. All provisioned mailboxes are billable.<br /> <br /> == Zimbra Themes ==<br /> <br /> You can see all the themes [https://wiki.xmission.com/Hosted_Email:_Admin_Panel/Zimbra_Themes here]<br /> <br /> <br /> [[Category:Zimbra|Admin Panel]]<br /> <br /> <br /> {{footer}}</div>

John https://wiki.xmission.com/index.php?title=Domains&diff=10843 2021-02-17T14:56:12Z

<p>John: Added Domain Contact Information modification approval details.</p> <hr /> <div>= Definition of a Domain =<br /> A domain name is a word or set of words followed by a suffix (e.g.: '''xmission.com''') that can be associated with many Internet services. The most popular association is for web pages (e.g.: '''http://www.xmission.com'''). Domain names are also used with mail (e.g.: '''username@xmission.com'''), ftp, and several other popular services. The way a domain name is linked to a service is through DNS or Domain Name Services. DNS links a name to an IP address (a set of numbers that identifies each individual machine connected to the Internet). Nearly everything on the Internet has an IP address in one form or another. Linking a domain name to an IP address makes it easier for people to remember. For example, if you wanted to go to XMission's home page, you would find it easier to remember '''www.xmission.com''' than the IP address, which is '''198.60.22.4'''.<br /> <br /> =Domain Registration=<br /> To register a new domain, you must first have an '''XMission account''' (@XMission.com). Existing customers can, then, go to the [http://domains.xmission.com/reg_system.cgi domain registration system] to either register a new domain or transfer an existing domain from another registrar.<br /> <br /> ==Domain Registration System==<br /> <br /> ===New Domains===<br /> On our [http://domains.xmission.com/ registration page] enter the domain name you would like to register in the box labeled &lt;span class=&quot;button&quot;&gt;Register a Domain:&lt;/span&gt; followed by clicking '''Check Availability'''. <br /> <br /> [[File:domains_xm_home.png|400px]]<br /> <br /> If the domain is available, you will be allowed to continue the registration.<br /> <br /> [[File:domains_xm_available.png|400px]]<br /> <br /> You will be presented with a estimated domain cost and login:<br /> <br /> ===Pricing===<br /> Domain pricing depends on the TLD you are registering with XMission. XMission supports most TLD's starting with .com, .net. and .org. Should you move or decide to leave XMission, this domain will remain yours for the duration of the time purchased. Domains purchased via XMission are transferable to other registrars. The domain registration fee will be billed to your XMission account at completion.<br /> <br /> [[File:domains_xm_estimated.png|400px]]<br /> <br /> ===Domain Management===<br /> <br /> XMission is a reseller for [https://tucowsdomains.com/ Tucows Domains], to manage your domain after it is registered you will need to create a Username and Password. Note: This does not have to be the same as your XMission username and password, so be certain that you don't lose it. <br /> <br /> [[File:domains_tucows_account.png|400px]]<br /> <br /> ====Client====<br /> * New client - If you are new to XMission registration you will be a new client. Do not use this feature if you've registered domains with XMission prior. If you register more than one domain with XMission and use &quot;New client&quot; for each domain you will have unique profiles for each one and will not be able to manage them all under one login.<br /> <br /> * Existing client - If you have registered a domain with XMission in the past you will need to provide the domain name and use the Username and Password you created at that time. If you have forgotten the username or password please contact support.<br /> <br /> ===Whois Contact===<br /> All domain registrations require ''who is'' information. Please fill out the requested information for Owner, Contact and Billing. Note: ICANN requires this information to be valid and current. It will be verified time to time and if the verification is not completed your domain will be placed on hold.<br /> <br /> [[File:domains_xm_whois.png|400px]]<br /> <br /> You can check the boxes &quot;Same as&quot; if your organization does not have unique contacts and click ''VERIFY ORDER''.<br /> <br /> Once you have verified all required information has been provided and click &lt;span class=&quot;button&quot;&gt;ORDER NOW!&lt;/span&gt;.<br /> <br /> =Domain Renewing=<br /> When your domain is up for renewal, OpenSRS, the registrar we resell through, will send a '''paper invoice''' to the '''billing address''' on the domain. As an additional reminder, XMission will send an '''email reminder''' to the account that the domain was registered to. The charge for an extra year will be charged along with your next month of Internet services. If you do not wish to renew, please contact accounting and notify them that you would like the domain to lapse.<br /> <br /> === Day 0 to day -40 ===<br /> During the Grace Period, the domain name is still considered to be owned by you, the registrant, and the WHOIS information continues to display the registrant's information (or WHOIS Privacy, if applicable).<br /> <br /> During the 40 days following the expiry date (Grace Period) you can reinstate the domain name simply by renewing it.<br /> <br /> === Redemption: Days -40 to -70 ===<br /> One of the most costly things to happen to a domain is when they go into a redemption, days -40 to -70.<br /> <br /> After the 40 day Grace Period, if the domain name has not been renewed, it may be queued for deletion and eventually dropped or auctioned off<br /> <br /> '''Important:''' Once the domain name is queued to enter the Live Auction, it cannot be redeemed by the original registrant.<br /> <br /> Live Auction will take place from day -41 to -45. <br /> <br /> If your domain name was not sent to the Live Auction, you can redeem your domain name during the 30 day Redemption Period.<br /> <br /> The cost for bringing a domain out of redemption is '''$80 dollars''' that includes the '''1 year renewal'''.<br /> <br /> === -70 to -75 ===<br /> After the Redemption Period, if the domain name has not been auctioned off and acquired by another party, it is dropped and made available for re-registration by the general public.<br /> <br /> === -70 to day -100 ===<br /> It is possible that a company called YummyNames, owned by Tucows, may decide to purchase the expired domain during the redemption period. They may decide to retain the domain name or sell it, depending on the Fair Market Value.<br /> <br /> =Domain Transferring=<br /> If you are transferring a domain to XMission from another registrar, go to our [https://domains.xmission.com domains management] page and select &lt;span class=&quot;button&quot;&gt;Transfer a Domain to XMission&lt;/span&gt;. You will be guided through the rest of the process as if you were registering a new domain. Another year will be added to your existing term. (E.g. If you registered for a year with another registrar and there is still 6 months left, you will still have that 6 months in addition to your new registration duration with XMission.) <br /> <br /> '''NOTE: In order to successfully transfer a domain, XMission requires customers to keep their email addresses current.'''<br /> <br /> When a customer decides to transfer a domain, they will receive a series of emails with instructions on the process. However, the following challenges often arise:<br /> # The email never arrives due to spam filters, etc.<br /> # The customer may not respond quickly enough to the emails. After '''5 days''', the customer must start the transfer again.<br /> # The customer may have the wrong email address associated with the domain.<br /> # The customer may not have their password for the domains management page, which is separate from their XMission account password.<br /> <br /> To successfully transfer a domain, the following conditions must exist:<br /> # A domain '''cannot be in a locked or hold status'''.<br /> # For reseller to reseller transfers - or registrar to registrar transfers - '''the domain must have resided with the losing registrar for more than 60 days''' since it was first registered or transferred there.<br /> # Transfers add one year to the domain's registration; therefore, the gaining reseller must have a sufficient balance for the renewal in order to complete the transfer request.<br /> # Domain names that are expired but not deleted (up to 40 days past the expiry date, for most TLDs) '''can''' be transferred.<br /> # The current administrative contact's email address must be '''valid''', to allow for the confirmation of the transfer request.<br /> <br /> '''NOTE: A domain's name servers cannot be changed during a registrar transfer. The nameservers will remain the same during the transfer, and they can be changed once the domain has reached the receiving registrar.'''<br /> <br /> '''Extra Info'''<br /> <br /> Not all registrars handle transfers/renewals or registrations the same as our reseller. Some places don't want to let domains go so they drag their feet and make it difficult which is annoying but there really is nothing we can do about it.<br /> <br /> '''See Also'''<br /> *[http://wiki.xmission.com/Domain_Transfer_and_Redemption Domain Transfer and Redemption]<br /> <br /> =Modifying Domain Contact Information=<br /> <br /> Every time Contact information is modified, registered, or transferred; ICANN requires all accredited registrars to verify your new contact details. The XMission Domains system will email you a critical message containing a Subject line containing: &quot;VERIFICATION REQUIRED - ...&quot; The body of the email contains links to the ICANN policy on Contact modifications and a link from the URL &quot;approve.domainadmin.com&quot; which you *must* follow to approve the changes. As a security measure, if the changes are not approved the domain will be suspended. Suspension means the domain will be prevented from transferring, the contact information will not be updated, and all domain related services which stop working which includes items such as web hosting and email. If you received this message in error or suspect phishing, please notify XMission Support.<br /> <br /> <br /> =DNS Services=<br /> <br /> XMission offers additional DNS services, which many hosting packages already include. You may want to use these in addition to a hosting package. They're also available for those who only require one of these services and not an entire hosting package. Please see our Pricing for a complete price list. <br /> <br /> ==Primary DNS==<br /> The authoritative primary source for domain service direction. (E.g. Tells the whole world at which IP address to find where to send mail for '''mydomain.com''' or what IP address is associated with '''bob.mydomain.com'''.) <br /> <br /> ==Secondary DNS==<br /> Back-up source for domain service direction. This is only necessary if the primary source does not answer. <br /> <br /> ==Parking==<br /> Holding a registered domain with no associated services. <br /> <br /> ==Alias==<br /> A domain name that resolves to another domain name. (E.g. '''http://www.example.com''' would open the same file as '''http://www.example/webpage.html''') An alias will keep the domain the visitor entered in the address bar of their browser.<br /> <br /> ==Redirect==<br /> A domain name that's directed to another part of your web site. (E.g. '''http://subdomain.example.com''' would open the files under '''/home/users/a/acctname/subdomain''', or another chosen directory.)<br /> <br /> ==Domain Locking==<br /> When locking is enabled for a domain, any requests to transfer the domain to another registrar or hosting company will automatically fail. This can be used to prevent fraudulent transfers of the domain, while locking is enabled. Domain locking is handled through the [https://manage.opensrs.net/ OpenSRS Domain Management Portal].<br /> <br /> ==WHOIS/Contact Privacy==<br /> Domain Name WHOIS / Contact Privacy hides the identity of a domain Registrant when someone does a WHOIS lookup on that Registrant’s domain. The benefit of having WHOIS Privacy is that the Registrant’s identity, including address, phone number, and email address, is shielded from spammers, identity thieves, scammers, and other undesirables. WHOIS privacy is handled through the [https://manage.opensrs.net/ OpenSRS Domain Management Portal]. Once logged in, select '''Reseller Contact''', then next to '''Enable Whois Privacy''' select '''Hide''', and lastly hit '''save'''.<br /> <br /> Contact Privacy is '''$5.00 per domain''' yearly and is a non-refundable fee. Note: This fee from XMission is approximately half of what the other common registrar services charge.<br /> <br /> You can enable Contact Privacy for a domain at any time. If enabled, it expires at the same time as the domain name. If the domain is set to auto-renew, Contact Privacy also auto-renews (and incurs any associated cost) at the same time. <br /> <br /> If someone tries to contact an email address associated with a domain that is protected by Contact Privacy, they receive an auto-responder message instructing them to visit the [https://contactprivacy.com Contact Privacy] page in order to reach the registrant.<br /> <br /> [http://en.wikipedia.org/wiki/Domain_privacy What is Domain Privacy?]<br /> <br /> [http://xmission.com/contact If needed XMission is available to assist with further questions.]<br /> <br /> ==See Also==<br /> [http://wiki.xmission.com/DNS DNS]<br /> <br /> = Related Links=<br /> *[[Adding/Managing DNS Records]]<br /> *[[Manage Domains]]<br /> *[[Hosting]]<br /> *[[Domain Transfer and Redemption]]<br /> *[[DNS]]<br /> *[[Name Servers]]<br /> <br /> <br /> [[Category:About|Domains]]<br /> [[Category:Getting Started]]</div>

John https://wiki.xmission.com/index.php?title=Zimbra_Cloud_General_Application_Settings&diff=10842 2021-02-09T22:19:59Z

<p>John: </p> <hr /> <div>These general settings will be applied to most modern email applications on desktop and mobile clients utilizing mailboxes on Zimbra Cloud.<br /> <br /> Note to domain administrators, Zimbra Cloud requires configuration of your domain via the Admin Dashboard for your mail to work. https://admin.zimbracloud.com/domains In the Dashboard you will enter your mail domain and verify the domain by adding a TXT record to DNS. Once verified, you with then configure the additional DNS settings for MX, SPF, and DKIM.<br /> <br /> <br /> {|style=&quot;width:85%, color:#333333; font-size:10pt&quot; border=&quot;0&quot;<br /> |- <br /> |align=&quot;left&quot;|'''Zimbra Cloud Mailbox Settings'''<br /> |-<br /> {| style=&quot;text-align: left; border: 1px solid #ccc;&quot; cellspacing=&quot;0&quot; cellpadding=&quot;2&quot; <br /> ! style=&quot;border-bottom:1px solid #ccc; background-color: #eef; padding:2px 8px&quot; colspan=2 | Incoming Server Information:<br /> ! style=&quot;border-style: solid; border-width: 0 0 1px 1px; border-color:#ccc; background-color: #eef; padding:2px 8px&quot; colspan=2 | Outgoing Server Information:<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Server Type: || IMAP<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Server Type: || SMTP<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Hostname: || mail.zimbracloud.com<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Hostname: || mail.zimbracloud.com &amp;nbsp;<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Port: || 993<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Port: || 587<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Enable encryption: || YES<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Enable encryption: || YES<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Authenticate Using: || Password<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Requires Authentication: || YES<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Login User Name: || Full email address &amp;nbsp;<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; |Login User Name || Full email address<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Alternate Port: || 143, 995 SSL POP3 &amp;nbsp;<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; |Alternate Port: || 465 (Must enable SSL)<br /> |-<br /> |}<br /> <br /> {|<br /> |-<br /> ||Zimbra Cloud Webmail: |||[https://mail.zimbracloud.com/ https://mail.zimbracloud.com/]<br /> |-<br /> ||Admin Interface: |||[https://admin.zimbracloud.com/ https://admin.zimbracloud.com] Or follow Admin Dashboard icon from webmail<br /> |-<br /> ||Folders: ||| Sent Mail = &quot;Sent&quot;, Drafts = &quot;Drafts&quot;, Trash = &quot;Trash&quot;, Spam = &quot;Junk&quot;<br /> |}<br /> <br /> <br /> Zimbra Connector For Outlook: https://zimbra.github.io/userguide/zcloud/userguide-zcloud.html#_zimbra_connector_for_outlook_zco<br /> <br /> Need help? XMission offers a range of [https://wiki.xmission.com/Zimbra_Cloud#Understanding_Support_Plans Zimbra Cloud Support plans]. Please contact XMission Sales or Support to have this added to your Zimbra Cloud service today.</div>

John https://wiki.xmission.com/index.php?title=Zimbra_Cloud_General_Application_Settings&diff=10841 2021-02-09T22:13:41Z

<p>John: </p> <hr /> <div>These general settings will be applied to most modern email applications on desktop and mobile clients utilizing mailboxes on Zimbra Cloud.<br /> <br /> Note to domain administrators, Zimbra Cloud requires configuration of your domain via the Admin Dashboard for your mail to work. https://admin.zimbracloud.com/domains In the Dashboard you will enter your mail domain and verify the domain by adding a TXT record to DNS. Once verified, you with then configure the additional DNS settings for MX, SPF, and DKIM.<br /> <br /> <br /> {|style=&quot;width:85%, color:#333333; font-size:10pt&quot; border=&quot;0&quot;<br /> |- <br /> |align=&quot;left&quot;|'''Zimbra Cloud Mailbox Settings'''<br /> |-<br /> {| style=&quot;text-align: left; border: 1px solid #ccc;&quot; cellspacing=&quot;0&quot; cellpadding=&quot;2&quot; <br /> ! style=&quot;border-bottom:1px solid #ccc; background-color: #eef; padding:2px 8px&quot; colspan=2 | Incoming Server Information:<br /> ! style=&quot;border-style: solid; border-width: 0 0 1px 1px; border-color:#ccc; background-color: #eef; padding:2px 8px&quot; colspan=2 | Outgoing Server Information:<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Server Type: || IMAP<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Server Type: || SMTP<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Hostname: || mail.zimbracloud.com<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Hostname: || mail.zimbracloud.com &amp;nbsp;<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Port: || 993<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Port: || 587<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Enable encryption: || YES<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Enable encryption: || YES<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Authenticate Using: || Password<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Requires Authentication: || YES<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Login User Name: || Full email address &amp;nbsp;<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; |Login User Name || Full email address<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Alternate Port: || 143, 995 SSL POP3 &amp;nbsp;<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; |Alternate Port: || 465 (Must enable SSL)<br /> |-<br /> |}<br /> <br /> {|<br /> |-<br /> ||Zimbra Cloud Webmail: |||[https://mail.zimbracloud.com/ https://mail.zimbracloud.com/]<br /> |-<br /> ||Admin Interface: |||[https://admin.zimbracloud.com/ https://admin.zimbracloud.com] Or follow Admin Dashboard icon from webmail<br /> |-<br /> ||Folders: ||| Sent Mail = &quot;Sent&quot;, Drafts = &quot;Drafts&quot;, Trash = &quot;Trash&quot;, Spam = &quot;Junk&quot;<br /> |}<br /> <br /> <br /> Zimbra Connector For Outlook: https://zimbra.github.io/userguide/zcloud/userguide-zcloud.html#_zimbra_connector_for_outlook_zco</div>

John https://wiki.xmission.com/index.php?title=Zimbra_Cloud_General_Application_Settings&diff=10840 2021-02-09T22:11:05Z

<p>John: </p> <hr /> <div>Zimbra Cloud general settings will be applied to most modern email applications on desktop and mobile clients.<br /> <br /> '''Important:''' Zimbra Cloud requires configuration of your domain via the Admin Dashboard for your mail to work. https://admin.zimbracloud.com/domains In the Dashboard you will enter your mail domain, verify the domain by adding a TXT record to DNS. Then you configure the additional DNS settings for MX, SPF, and DKIM.<br /> <br /> <br /> {|style=&quot;width:85%, color:#333333; font-size:10pt&quot; border=&quot;0&quot;<br /> |- <br /> |align=&quot;left&quot;|'''Zimbra Cloud Mailbox Settings'''<br /> |-<br /> {| style=&quot;text-align: left; border: 1px solid #ccc;&quot; cellspacing=&quot;0&quot; cellpadding=&quot;2&quot; <br /> ! style=&quot;border-bottom:1px solid #ccc; background-color: #eef; padding:2px 8px&quot; colspan=2 | Incoming Server Information:<br /> ! style=&quot;border-style: solid; border-width: 0 0 1px 1px; border-color:#ccc; background-color: #eef; padding:2px 8px&quot; colspan=2 | Outgoing Server Information:<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Server Type: || IMAP<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Server Type: || SMTP<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Hostname: || mail.zimbracloud.com<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Hostname: || mail.zimbracloud.com &amp;nbsp;<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Port: || 993<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Port: || 587<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Enable encryption: || YES<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Enable encryption: || YES<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Authenticate Using: || Password<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Requires Authentication: || YES<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Login User Name: || Full email address &amp;nbsp;<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; |Login User Name || Full email address<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Alternate Port: || 143, 995 SSL POP3 &amp;nbsp;<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; |Alternate Port: || 465 (Must enable SSL)<br /> |-<br /> |}<br /> <br /> {|<br /> |-<br /> ||Zimbra Cloud Webmail: |||[https://mail.zimbracloud.com/ https://mail.zimbracloud.com/]<br /> |-<br /> ||Admin Interface: |||[https://admin.zimbracloud.com/ https://admin.zimbracloud.com] Or follow Admin Dashboard icon from webmail<br /> |-<br /> ||Folders: ||| Sent Mail = &quot;Sent&quot;, Drafts = &quot;Drafts&quot;, Trash = &quot;Trash&quot;, Spam = &quot;Junk&quot;<br /> |}<br /> <br /> <br /> Zimbra Connector For Outlook: https://zimbra.github.io/userguide/zcloud/userguide-zcloud.html#_zimbra_connector_for_outlook_zco</div>

John https://wiki.xmission.com/index.php?title=Zimbra_Cloud_General_Application_Settings&diff=10839 2021-02-09T22:05:39Z

<p>John: Zimbra Cloud General Application Settings.</p> <hr /> <div>Zimbra Cloud general settings will be applied to most modern email applications on desktop and mobile clients.<br /> <br /> Zimbra Cloud Webmail: https://mail.zimbracloud.com<br /> <br /> {|style=&quot;width:85%, color:#333333; font-size:10pt&quot; border=&quot;0&quot;<br /> |- <br /> |align=&quot;left&quot;|'''Zimbra Cloud Mailbox Settings'''<br /> |-<br /> {| style=&quot;text-align: left; border: 1px solid #ccc;&quot; cellspacing=&quot;0&quot; cellpadding=&quot;2&quot; <br /> ! style=&quot;border-bottom:1px solid #ccc; background-color: #eef; padding:2px 8px&quot; colspan=2 | Incoming Server Information:<br /> ! style=&quot;border-style: solid; border-width: 0 0 1px 1px; border-color:#ccc; background-color: #eef; padding:2px 8px&quot; colspan=2 | Outgoing Server Information:<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Server Type: || IMAP<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Server Type: || SMTP<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Hostname: || mail.zimbracloud.com<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Hostname: || mail.zimbracloud.com &amp;nbsp;<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Port: || 993<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Port: || 587<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Enable encryption: || YES<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Enable encryption: || YES<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Authenticate Using: || Password<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; | Requires Authentication: || YES<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Login User Name: || Full email address &amp;nbsp;<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; |Login User Name || Full email address<br /> |-<br /> |style=&quot;padding:2px 8px&quot; |Alternate Port: || 143, 995 SSL POP3 &amp;nbsp;<br /> |style=&quot;border-left:1px solid #ccc; padding:2px 8px&quot; |Alternate Port: || 465 (Must enable SSL)<br /> |-<br /> |}<br /> <br /> {|<br /> |-<br /> ||Webmail Interface: |||[https://mail.zimbracloud.com/ https://mail.zimbracloud.com/]<br /> |-<br /> ||Admin Interface: |||[https://admin.zimbracloud.com/ https://admin.zimbracloud.com] Or follow Admin Dashboard icon from webmail<br /> |-<br /> ||Folders: ||| Sent Mail = &quot;Sent&quot;, Drafts = &quot;Drafts&quot;, Trash = &quot;Trash&quot;, Spam = &quot;Junk&quot;<br /> |}<br /> <br /> Zimbra Cloud requires you to configure your domain via the Admin Dashboard. https://admin.zimbracloud.com/domains Here you will enter your new mail domain, verify the domain by adding a TXT record. Then you configure the DNS with settings for MX, SPF, and DKIM.</div>

John https://wiki.xmission.com/index.php?title=Zimbra_Cloud&diff=10838 2021-02-09T22:02:45Z

<p>John: /* Online Zimbra Cloud Support Links: */</p> <hr /> <div>Zimbra Cloud by XMission is a new Zimbra email platform hosted on Oracle Cloud Services and supported by XMission.<br /> <br /> Zimbra Cloud can be purchased as a fully supported product or as a stand-alone service where the user self-supports using available online resources.<br /> <br /> Zimbra Cloud is intended to be a one-size-fits-all model and is not as configurable as Zimbra 8.8.X or Zimbra 9.X however it does have offer 30 GB quota with extensive integrations and features appealing to the wider market in need of domain email services.<br /> <br /> ==Product Pages==<br /> * Zimbra Cloud Pricing: https://xmission.com/zimbra_cloud<br /> * XMission Support Plans for Zimbra Cloud: https://xmission.com/zimbra_cloud_support<br /> <br /> ==Login Pages==<br /> * Zimbra Cloud Webmail: https://mail.zimbracloud.com<br /> * Zimbra Cloud Admin Dashboard: https://admin.zimbracloud.com<br /> <br /> ==Online Zimbra Cloud Support Links:==<br /> <br /> User guide: https://zimbra.github.io/userguide/zcloud/userguide-zcloud.html<br /> <br /> General help: https://info.zimbra.com/zimbra-cloud-email-help<br /> <br /> Admin guide: https://admin.zimbracloud.com/support --&gt; requires domain admin login credentials<br /> <br /> Application settings: [[Zimbra Cloud General Application Settings]]<br /> <br /> ==Understanding Support Plans==<br /> Business customers can choose from the following Zimbra Cloud support options as provided by XMission. Billable plans are charged for the total number of domain mailboxes. Support levels cannot be mixed and matched. Paid support plans have a minimum 90 day commitment before any downgrade is available.<br /> * '''Premier Support''' - Provides all mailbox holders with 24x7 phone and live chat support, unlimited email support tickets, and access to online support documents. $3 per mailbox <br /> * '''Admin Support''' - Provides email support tickets for up to two domain admins supporting the larger domain mailbox base, plus access to online support documents. $1 per mailbox<br /> * '''Trial Support''' - Provides access to online support documents and 4 email support tickets during trial period zimbracloudtrial@xmission.com $0 per mailbox<br /> * '''Online Support''' - Provided no support services. Customer will use online support documentation following the provided help links in the Zimbra Cloud user webmail interface and admin dashboard. $0 per mailbox<br /> <br /> ==Overview and Features==<br /> <br /> Video overview of Zimbra Cloud: https://youtu.be/gjoc-0YHp-M <br /> <br /> Subscribe to the Zimbra YouTube channel: https://www.youtube.com/c/zimbra/videos<br /> <br /> Features: $2.95 per mailbox monthly<br /> * 30 GB mailbox quota <br /> * Contacts<br /> * Calendar<br /> * Cloud Storage and local Briefcase<br /> * Video conferencing<br /> * Chat room and presence<br /> * Integrations include: [https://support.zimbracloud.com/integrations/slack/ Slack], [https://support.zimbracloud.com/integrations/zoom Zoom], [https://zimbra.github.io/userguide/zcloud/userguide-zcloud.html#_jitsi Jitsi], [https://zimbra.github.io/userguide/zcloud/userguide-zcloud.html#_zulip Zulip], [https://support.zimbracloud.com/integrations/google-drive Google Drive], [https://support.zimbracloud.com/integrations/microsoft-onedrive OneDrive], [https://support.zimbracloud.com/integrations/dropbox DropBox], LifeSize, [https://zimbra.github.io/userguide/zcloud/userguide-zcloud.html#_video_call_preferences Webex], [https://zimbra.github.io/userguide/zcloud/userguide-zcloud.html#_activesync ActiveSync], [https://zimbra.github.io/userguide/zcloud/userguide-zcloud.html#_zimbra_connector_for_outlook_zco Zimbra Connector for Outlook (ZCO)] <br /> * User Migration Tool</div>

John