Frequently Asked Questions
How Scalable is MailArchiva? Does it work in large enterprise environments?
MailArchiva is optimized to cater for heavy work loads and larger archives. Some of the biggest companies and government entities around are using MailArchiva successfully.
What ever happened to MailArchiva Open Source Edition?
We stopped working on it many years ago. The reason being, we needed to license various third party commercial libraries, and the third party vendors wouldn't allow us to do so if we continued to offer MailArchiva as an open-source solution.
Why did you take the decision to offer MailArchiva On Premise for free for less than 10 mailboxes?
It's part of our marketing strategy. Our long-term goal is to try and get as many companies using our software as possible. We want them to experience the power and benefits of the product. When they eventually grow to become a sizeable company, they will hopefully approach us for a commercial license.
Can I still get commercial support if I am using MailArchiva On Premise and have less than twenty mailboxes?
Yes you can, but you'll need to purchase MailArchiva On Premise for a minimum of 10 mailboxes.
MailArchiva queue folder has a large number of entries inside it.
Please upgrade your server to the latest version. Recent versions have the ability to restrict the queue size to a user-defined value (specified in Configuration->Archive).
The import of large PST files is slow. How can I speed things up?
MailArchiva uses third party libs to parse PST files. They sometimes use quite a lot of memory when processing large PST files. Thus, try increasing the amount of heap space available to the server.
My server's CPU is unusually high even though MailArchiva is not fully loaded.
This situation can also occur if too much heap space is allocated to MailArchiva. In this case, set the maximum heap space to 6G. Alternatively, please upgrade to the latest version to see if the problem is resolved. If not, contact us for a resolution.
I accidently sent 1000’s of archived emails to myself, and I am trying to stop sending them now, but the process will not stop. How do I stop it from continuing to send more archived emails to me?
Stop the server and delete the smtp queue directory. They are usually located /var/opt/mailarchiva/ROOT/queue/smtpclient/* (Linux) and C:\ProgramData\MailArchiva\ROOT\queue\smtpclient\* (Windows). Thereafter, start the server again.
Is there a way with the MailArchiva Cloud, to import all the mail from an On-Premise Exchange Server?
Yes, it is possible. Direct import is available from both MS Exchange and Office 365. See http://help.mailarchiva.com/enterprise-email-migration$exchangeimport for direct import instructions from Microsoft Exchange. To import from a remote Exchange server, port forward ports 389, 135, 49670 and 49667 from the On Premise Active Directory server to archiva.com. Also, when defining AD authentication, uncheck DNS lookups, and specify the port forwarded external IP address of the customer's AD server. Before performing an Exchange import, be sure to upgrade to the latest patch release of MailArchiva.
How do I import / migrate emails into MailArchiva?
MailArchiva is capable of importing from EML, PST, MBOX, OST, direct Exchange import, direct GSuite, etc. For importing of PST files, the easiest is to copy the PST data to a couple of folders on the server, and use the Import from server feature to import the data. In regards to Exchange import, you would simply configure the Exchange connection, and then perform a direct import from MS Exchange. In the latter case, MailArchiva connects to Exchange web services API, scans all mailboxes, and imports the data to the archive. The product is available for use while imports are occurring. Once MailArchiva is connected to Exchange, to import data from Exchange, it is a simple matter of clicking Import, choosing the Exchange connection, and clicking the import button. It is possible to specify which mailboxes you want imported in the import dialog.
How to export all mail associated with an email address?
Login to the MailArchiva console as admin, click Configuration->General->Limits tab. Increase Max Selection and Export limits to max. Go to Search. In the search box, type "anyaddress:email@example.com" (while substituting the email with the desired user's email). Click Select All. Then click Export and choose a suitable export format. Click Export.
Why does MailArchiva use two connections to MS Exchange, and what are they used for?
There are two Exchange connections.
1) SMTP Listener: MailArchiva is configured to receive journaling traffic from MS Exchange on the SMTP interface. This connection is used for communicating emails only.
2) Exchange Client Connection: MailArchiva connects to Exchange server via Exchange web services (REST) interface. The purpose of this connection is to synchronize folders, calendars and contacts (since this information cannot be obtained by the usual SMTP interface).
I have a server where Mailarchiva is installed and all the "X" mails are loaded into it, I can create multiple users who access it but if I want to upload "Y" mails, how can I make sure that the mails do not mix?
MailArchiva is not akin to a mail server where emails associated with different mailboxes are stored separately. All imported data is stored in one giant repository. Afterwards, when users login into the system, they are assigned a role with a view filter that defines which emails the users can see in the search results. For example, the user role by default has a view filter of %email%. This macro is replaced with the user's email address obtained from an authentication server (e.g. Active Directory, Azure) at the time of login. If a user is assigned the Auditor role, then by default there is no filtering applied (meaning they can see all emails) as Auditor role view filter is empty. If basic authentication is used, then the user's email address for filtering purposes is obtained directly from MailArchiva's users.xml file in the config path.
When logged in as Administrator and trying to perform a search I received the error below in red, at the top of the Mail Archiva interface “Search Access is Denied. User has no email address”. Why?
When the user logs in, if Active Directory authentication is enabled, the email address of the user is retrieved from proxyAddresses LDAP field in Active Directory. Some users may not have email addresses. For example, it is common for admin users not to have an exchange mailbox associated with them, but for the account to still exist in AD. In this case, the standard behaviour of MailArchiva is to allow the user access to the system, but not allow the user to search. If you have AD authentication enabled in Configuration->Logins, then most likely the admin user doesn't have a mailbox associated. If you want to search all users, then you could edit the Administrator role in Configuration->Roles, and clear out the view filter. Save, and attempt to search again. This will show all mail to all users.
I've setup Office 365 to put journal mail into MailArchiva On-Premise but its not working. Why?
To get O365 to communicate with MailArchiva, create an SMTP listener in MailArchiva in Configuration->Listeners to listen on port 25, and ensure that port 25 is forwarded on your firewall to the MailArchiva server, and that an A record has been created on the company public DNS (e.g. archiva) that points to this external IP address. MailArchiva's SMTP server should be accessible via the terminal from outside your network, by typing "telnet archiva.company.com 25". if a response is not received, it means either port 25 is not forwarded correctly, there is a firewall is blocking the communications, or MailArchiva is not listening on the port. When creating the journal rule in Office 365, use the email address equivalent to firstname.lastname@example.org where archiva.company.com resolves to the external IP address from which port 25 is forwarded on your firewall. Furthermore, O65 requires a StartTLS secured connection to be able to communicate. Thus, it is necessary to import a certificate in MailArchiva signed by a trusted public CA such as Verisign (i.e. not a self-signed one). FYI: The same certificate can be used for both securing the console (i.e. HTTP/S) and for SMTP purposes. Once the certificate is installed, in the SMTP listener created earlier, set connection mode to "TLS", in the certificate authentication field, select "MailArchiva certificate store" and select the imported certificate in the SMTP listener. Feel free to experiment with "authenticate client certificates" enabled/disabled.
Why aren't subjects used as filenames in exports?
Once upon a time, we used subjects as a filename, but switched away from that approach years ago due to the problems that ensued as a result. Subjects tend to contain characters in them that do not comply with the acceptable character requirements imposed by the various file systems. When adding a subject as a filename, one has to account for the fact that there are duplicate subjects. The system, therefore, needs to check whether the file exists or not prior to writing the file. Believe it or not, this extra "exists" check slows down the export process because an additional I/O operation must be performed on the export of each document. Some customers perform exports of 100k emails at a time. Performance is critical for them. Furthermore, when writing a file, it becomes necessary to strip out the illegal characters from the filename. This issue is compounded by the fact that different filesystems accept different character sets in a filename. In many cases, after stripping the combined intersection of all illegal characters across all filesystems, one may be left with a husk of a filename that increases the likelihood of filename conflicts with other files already written to disk. To avoid conflicts, it is then necessary to append a numeric sequential suffix to the filename. Ultimately, the suffixes can get into the thousands. You end up with filenames such as "123233.eml", " 123234 .eml", etc. Totally meaningless. To top it off, the extra exists check, and appending of a numeric suffix requires that threads are synchronized, and it impacts parallelism, ultimately reducing the performance of the export. I understand that micro-companies might find it convenient to use filename's as subjects, but for bigger companies with big exports, it doesn't work for the reasons outlined above.
Found this information useful? Visit mailarchiva.com to learn more about MailArchiva.