Create fetch mails rules.

Each retrieval rule have it's own settings. With this feature you can specify many options in order to help the process to retrieve  correctly your message from the remote mailbox.

  • Click on Fetchmail rules tab.
  • On the table, click on "New rule'"

The form display to sections:

  • Server Options section defines parameters for connecting and retreive messages.
  • User options section defines local account settings and schedule rule process (if schedule is enabled)



  • enable: Enable or disable the retreival process for this rule.

  • server: Mailbox server hostname or IP address. 
  • Alternate DNS names of mailserver: This option option is for use with multidrop mailboxes.
    It allows you to pre-declare a list of DNS aliases for a server.
    This is an optimization hack that allows you to trade space for speed.
    When fetchmail, while processing a multidrop mailbox, grovels through message headers looking for names of the mailserver, pre-declaring common ones can save it from having to do DNS lookups.
    Note: the names you give as arguments are matched as suffixes -- if you specify (say) ‘’, this will match not just a hostnamed, but any hostname that ends with ‘’; such as (say) and 

  • protocol:
    Protocol used to retreive messages such has POP3/IMAP/IMAP4..., Auto for auto-detection.    

  • port:  Remote port of the mailbox server (optional).

  • MAX size (Kb):
    Messages larger than this size will not be fetched and will be left on the server.
    If the fetch protocol permits (in particular, under IMAP or POP3) the message will not be marked seen.
    An explicit of 0 overrides any limits.
    This option is intended for those needing to strictly control fetch time due to expensive and variable phone rates.
    This option does not work with ETRN or ODMR.

  • SSL fingerprint:
    Specify the fingerprint of the server key (an MD5 hash of the key) in hexadecimal notation with colons separating groups of two digits.
    The letter hex digits must be in upper case.
    This is the default format OpenSSL uses, and the one fetchmail uses to report the fingerprint when an SSL connection is established.
    When this is specified, fetchmail will compare the server key fingerprint with the given one, and the connection will fail if they do not match.
    This can be used to prevent man-in-the-middle attacks.
  • Discard Delivered-To headers:
    This option controls wether Delivered-To headers will be kept in fetched mail (the default) or discarded.
    These headers are added by Qmail and Postfix mailservers in order to avoid mail loops but may get in your way if you try to "mirror" a mailserver within the same domain.
    Use with caution.
  • Connection Timeout:
    This option allows you to set a server-nonresponse timeout in seconds.
    If a mailserver does not send a greeting message or respond to commands for the given number of seconds, fetchmail will hang up on it.
    Without such a timeout fetchmail might hang up indefinitely trying to fetch mail from a down host. This would be particularly annoying for a fetchmail running in background.
    If a given connection receives too many timeouts in succession, fetchmail will consider it wedged and stop retrying, the calling user will be notified by email if this happens.

  • Trace all polls:
    Tell fetchail to poll trace information in the form ‘polling %s account %s’ to the Received line it generates, where the %s parts are replaced by the user’s remote name and the poll label (the Received header also normally includes the server’s truename).
    This can be used to facilate mail filtering based on the account it is being received from       

  • Use ssl:
    Causes the connection to the mail server to be encrypted via SSL.
    Connect to the server using the specified base protocol over a connection secured by SSL.
    SSL support must be present at the server.
    If no port is specified, the connection is attempted to the well known port of the SSL version of the base protocol.
    This is generally a different port than the port used by the base protocol.
    For IMAP, this is port 143 for the clear protocol and port 993 for the SSL secured protocol.

  • Strictly check the server certificate:
    Causes fetchmail to strictly check the server certificate against a set of local trusted certificates.
    If the server certificate is not signed by one of the trusted ones (directly or indirectly), the SSL connection will fail.
    This checking should prevent man-in-the-middle attacks against the SSL connection.
    Note that CRLs are seemingly not currently supported by OpenSSL in certificate verification!
    Your system clock should be reasonably accurate when using this option.

  • Fetch all mess:
    Retrieve both old (seen) and new messages from the mailserver.
    The default is to fetch only messages the server has not marked seen.
    Under POP3, this option also forces the use of RETR rather than TOP.
    Note that POP2 retrieval behaves as though --all is always on (see RETRIEVAL FAILURE MODES below) and this option does not work with ETRN or ODMR.

  • Keep messages:
    Retrieved messages on the remote mailserver.
    Normally, messages are deleted from the folder on the mailserver after they have been retrieved.
    Enable this option causes retrieved messages to remain in your folder on the mailserver.
    This option does not work with ETRN or ODMR.            

  • Delete messages after retreive them:
    Delete retrieved messages from the remote mailserver.
    This option forces retrieved mail to be deleted.
    It may be useful if you have specified a default of Keep messages.
    This option is forced on with ETRN and ODMR