Перейти к концу метаданных
Переход к началу метаданных

Вы просматриваете старую версию данной страницы. Смотрите текущую версию.

Сравнить с текущим просмотр истории страницы

« Предыдущий Версия 2 Следующий »

Office 365 выходит в двух версиях:

  • Small Business Plan - Журнальные сообщения не поддерживаются, но можно настроить пересылку BCC на сервер Архива. 
  • Enterprise Plan -  Журнальные сообщения поддерживаются. 

 Small Business Plan 

a)  Настройка журнального почтового ящика

  1. Авторизуйтесь в Office 365 как администратор. 
  2. Нажмите User Management
  3. Create a new user dedicated to mail journaling 
  4. Login to Office 365 as the newly created user
  5. Create the user's temporary password

б) Create a forwarding / BCC rule

  1. Login to Office 365 as an administrator
  2. In Exchange Online Management, Click Mail Control->Rules
  3. Create a new BCC rule to forward all mail traffic to the newly created user

в) Obtain IMAP Server Connection Information
  1. In Exchange Online Management, Click Manage My Organization->Another User
  2. Select the new user to manage
  3.  Go to Settings for POP, IMAP, SMTP
  4.  Make note of the IMAP settings for later use

d) Create an IMAP Connection in Архива
  1. Login to Архива as an Administrator
  2. In Configuration->Connections, create a new IMAP Connection
  3. Enter IMAP Connection details noted above
  4. Click Test Connection to verify the connection works
  5. Check Enabled and Save

Enterprise Plan

Журналирование может осуществляться двумя способами: 

  • IMAP журналирование  - All mail is journalled to a temporary journal mailbox. Архива retrieves mail from the journal mailbox via IMAP over the Internet. 
  • SMTP журналирование - Архива listens on port 25 for SMTP traffic. Office 365 is configured to forward mail directly to Архива using the SMTP protocol.

IMAP журналирование

Icon

Note: This method is slower than the SMTP forwarding approach

a)  Journal Mailbox Setup
  1. Login to Office 365 as an administrator
  2. Click on User Management
  3. Create a new user dedicated to mail journaling 
  4. Login to Office 365 as the newly created user
  5. Create the user's temporary password

b) Create a Journaling rule

  1. Login to Office 365 as an administrator
  2. Select Manage My Organization > Mail Control > Journal Rules > New
  3. Create a new BCC rule to forward all mail traffic to the newly created user
  4. Select "Apply to all messages" for "if the message is sent to or from.." 
  5. Select "All messages" for "Journal the following messages..."
  6. In "send journal reports to", type the email address of the newly created journal user above

 

c) Obtain IMAP Server Connection Information
  1. In Exchange Online Management, Click Manage My Organization->Another User
  2. Select the new user to manage
  3.  Go to Settings for POP, IMAP, SMTP
  4.  Make note of the IMAP settings for later use

d) Create an IMAP Connection in Архива
  1. Login to Архива as an Administrator
  2. In Configuration->Connections, create a new IMAP Connection
  3. Enter IMAP Connection details noted above
  4. Set Allow Partial fetches to false (see workaround note below)
  5. Click Test Connection to verify the connection works
  6. Check Enabled and Save

Office 365 Workaround:  There have been reports that journaling stops with the following error outputted in the debug.log file: failed to retrieve messages during polling operation:message number (35246) out of bounds (35245). To workaround this issue, please disable Partial Fetches in the IMAP client configuration.

e) Verify the server is archiving

  1. Click Status->Summary or Status-Charts to verify that emails are being archived
     
Office 365  IMAP Journaling Bug: Some customers have reported that Office 365 has a problem deleting emails from the journal account after a period. 
Workaround (from Microsoft):  Note the email account we are using with IMAP is called 'journal1'

"From reviewing the case I can see that the journal1 mailbox has a RetainDeletedItemsFor : 14.00:00:00, which is the default of 14 days.
I would recommend changing this down to 1 day to see if this clears down the recoverable deleted items and keeps it below 30Gb for the journal1 mailbox.
Follow these steps:
  1. Open powershell and connect to your tenant then perform the following: “Get-MailboxFolderStatistics -Identity journal1| sort-object -descending -property FolderAndSubfolderSize | ft name, *size*, item* -autosize”
  2. Perform “get-mailbox journal1|Set-Mailbox -RetainDeletedItemsFor 1.00:00:00”
  3. Perform “Start-ManagedFolderAssistant journal1”
  4. Perform “Get-MailboxFolderStatistics -Identity journal1| sort-object -descending -property FolderAndSubfolderSize | ft name, *size*, item* -autosize” and see if you see a reduction in the “Recoverable Items” in the “FolderAndSubfolderSize” column."

SMTP журналирование

a) Create an SMTP Listener in Архива

  1. Login to Архива as an Administrator
  2. In Configuration->Listeners, create a new SMTP Listener
  3. Modify the Listener to listen on port 25
  4. Click Save

b) Configure networking such that Office 365 can reach Архива on port 25

  1. Configure the company firewall to either
    a) Port forward traffic on 25 to the Архива IP address (OR)
    b) Place Архива server in the DMZ
  2. Modify the MX record of a suitable domain (under your control) to forward SMTP traffic to the Архива server
  3. Telnet to port 25 on the domain to verify that Архива's SMTP server is listening and reachable

c) Create a Journaling rule

  1. Login to Office 365 as an administrator
  2. Select Manage My Organization > Mail Control > Journal Rules > New
  3. Create a new BCC rule to forward all mail traffic to the newly created user
  4. Select "Apply to all messages" for "if the message is sent to or from.." 
  5. Select "All messages" for "Journal the following messages..."
  6. In "send journal reports to", type mailarchiva@domain.com (where domain.com must be substituted with the domain you use above)

e) Verify the server is archiving

  1. Click Status->Summary or Status-Charts to verify that emails are being archived

 

  • Ни одной