Configuration » Remote Server Settings: Common NNTP POP3 SMTP
Default user account for incoming mails
The user account selected here will get all mails fetched from this server if no other valid account is given by mailfilters, by script commands or by the "Automatically distribute ..." option described below.
If no default account is selected here, account "admin" will always be used as default.
Section name for filtering incoming mails
Section name in file MailFilt.hst, which is used for filtering when fetching mails from this server. If a single star ("*") is given, only the global filters will be used.
Automatically distribute mails to recognized accounts
If marked, every mail fetched from this server is automatically examined for information about its recipients. If mail addresses are found, that are assigned to local accounts, the default user given above is ignored and the mail will automatically be distributed to the mailboxes of the accounts found.
The header lines of the mail that are examined for recipient information are: To, Apparently-To, Cc, Bcc, Envelope-To, X-Envelope-To, Original-Recipient, X-Resent-For, X-Resent-To, Resent-To and Received.
Please note, that mails fetched by POP3 in most cases do not contain any reliable recipient information, especially if the mail was only sent by BCC (blind carbon copy). The reliable information about recipients (the so called "envelope" or the "envelope headers") is normally discarded after a mail has reached its final destination mailbox, though some providers save this reliable information in headers like the ones given in the list above.
Please note also, that the automatical distribution is turned off, if any mailfilter in MailFilt.hst chooses to do something different with the mail, e. g. redirecting the mail to other accounts as the default user or posting it to a newsgroup.
Leave mails on server
If marked, mails loaded from this server are not deleted, i. e. they remain on the server.
Authenticate by USER/PASS, ... APOP, ... AUTH (SASL)
Determines the methods that may be used to authenticate on this server. If multiple methods are selected, Hamster tries all of the selected ones until successfully logged in (sequence is: AUTH, then APOP and finally USER/PASS).
Unlike the other methods, USER/PASS is supported on most servers and is therefore enabled by default, but be aware, that username and password are sent as clear text with this method.
APOP is not widely supported. It uses some type of checksum (a "message digest") of the password, so transmitted data does not contain password's text directly.
Support for AUTH is available on newer servers. It supports different mechanisms for authentication with different levels of security (see "SASL mechanisms" below"). Similar to above APOP, most of these mechanisms do not transmit password's text directly, but PLAIN and LOGIN mechanisms do.
SASL mechanisms to be used for authentication
Defines a list of SASL mechanisms (separated by space), which may be used to login on this server by AUTH command. An empty setting means, that all supported mechanisms may be used.
Be aware, that PLAIN and LOGIN mechanisms transmit the password nearly as
clear text, it is only base64 encoded in this case.
Currently supported are: DIGEST-MD5 CRAM-SHA1 CRAM-MD5 PLAIN LOGIN