<?xml version="1.0" encoding="utf-8"?>
<page xmlns="http://projectmallard.org/1.0/" xmlns:its="http://www.w3.org/2005/11/its" type="topic" id="mail-error-no-provider-available" xml:lang="el">

  <info>
    <desc>What to do when this error is shown.</desc>
    
    <link type="guide" xref="index#common-mail-problems"/>

    <revision pkgversion="2.28.3" version="0.2" date="2010-12-08" status="review"/>
    <credit type="author">
      <name>April Gonzales</name>
      <email>loonycookie@gmail.com</email>
    </credit>
    <license>
      <p>Creative Commons Share Alike 3.0</p>
    </license>    

  </info>

<title>Error message "No provider available for protocol email"</title>

<p>This error message may be displayed for a number of reasons:</p>
<list>

<item>
<p>The filters used do not match the account they are associated with.</p>
<p>This happens when the <file>filters.xml</file> file is copied and used on a fresh install of Evolution on a new machine.</p>
<p>Accounts have unique ID numbers, and filters refer to these accounts directly. Simply copying the <file>filters.xml</file> file will cause a version mismatch with Evolution, affecting the filter rules.</p>

</item>
<item><p>The account settings may not have been copied properly.</p></item>
<item><p>The account settings were modified.</p></item>
</list>

<p>To fix this problem, edit the email filters and re-select the folder for each Copy/Move filter. To do this:</p>
<steps>
<item><p>Go to <guiseq><gui>Edit</gui><gui>Message Filters</gui></guiseq>.</p></item>
<item><p>Select the Copy/Move filter and click <gui>Edit</gui>.</p></item>
<item><p>Refer to the list of folders associated with that particular filter. Click on the button that allows you to modify the folders assigned for that filter. Set the folders again. </p></item>
</steps>

<note>
<p>Advanced users may also be interested in this write up: <link href="https://thomas.apestaart.org/thomas/trac/wiki/Evolution">How to keep the Evolution filters in sync on multiple machines by Thomas Vander Stichele </link>
</p>
</note>

<!-- The guide referenced above might make a useful addition to the docs. We should consider asking Thomas for permission to include it, if it seems suitable. -->

</page>
