<html>
<head>
<style>
P
{
margin:0px;
padding:0px
}
body
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body>i`m still not getting in.. i now have this error:<br><br>Feb 17 23:48:42 School-Mail dovecot: Dovecot v1.0.rc15 starting up<br>Feb 17 23:49:04 School-Mail dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AG1hcmsAbWFyaw==<br>Feb 17 23:49:04 School-Mail dovecot: auth(default): pam(mark,127.0.0.1): pam_authenticate() failed: Authentication failure<br>Feb 17 23:49:05 School-Mail dovecot: imap-login: Disconnected: user=<mark>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured<br>Feb 17 23:49:05 School-Mail dovecot: auth(default): client out: FAIL 1 user=mark<br><br><br>and just to be sure.. here is my dovecot.conf file:<br>## Dovecot configuration file<br><br># If you're in a hurry, see http://wiki.dovecot.org/QuickConfiguration<br><br># '#' character and everything after it is treated as comments. Extra spaces<br># and tabs are ignored. If you want to use either of these explicitly, put the<br># value inside quotes, eg.: key = "# char and trailing whitespace "<br><br># Default values are shown for each setting, it's not required to uncomment<br># any of the lines.<br><br># Base directory where to store runtime data.<br>#base_dir = /var/run/dovecot/<br><br># Protocols we want to be serving: imap imaps pop3 pop3s<br># If you only want to use dovecot-auth, you can set this to "none".<br>#protocols = imap imaps pop3 pop3s<br>protocols = imap pop3<br><br># IP or host address where to listen in for connections. It's not currently<br># possible to specify multiple addresses. "*" listens in all IPv4 interfaces.<br># "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4<br># interfaces depending on the operating system.<br>#<br># If you want to specify ports for each service, you will need to configure<br># these settings inside the protocol imap/pop3 { ... } section, so you can<br># specify different ports for IMAP/POP3. For example:<br># protocol imap {<br># listen = *:10143<br># ssl_listen = *:10943<br># ..<br># }<br># protocol pop3 {<br># listen = *:10100<br># ..<br># }<br>#listen = [::]<br>listen =<br><br># Disable LOGIN command and all other plaintext authentications unless<br># SSL/TLS is used (LOGINDISABLED capability). Note that if the remote IP<br># matches the local IP (ie. you're connecting from the same computer), the<br># connection is considered secure and plaintext authentication is allowed.<br>disable_plaintext_auth = no<br><br># Should all IMAP and POP3 processes be killed when Dovecot master process<br># shuts down. Setting this to "no" means that Dovecot can be upgraded without<br># forcing existing client connections to close (although that could also be<br># a problem if the upgrade is eg. because of a security fix). This however<br># means that after master process has died, the client processes can't write<br># to log files anymore.<br>#shutdown_clients = yes<br>##<br>## Logging<br>##<br><br># Use this logfile instead of syslog(). /dev/stderr can be used if you want to<br># use stderr for logging (ONLY /dev/stderr - otherwise it is closed).<br>#log_path =<br><br># For informational messages, use this logfile instead of the default<br>#info_log_path =<br><br># Prefix for each line written to log file. % codes are in strftime(3)<br># format.<br>#log_timestamp = "%b %d %H:%M:%S "<br><br># Syslog facility to use if you're logging to syslog. Usually if you don't<br># want to use "mail", you'll use local0..local7. Also other standard<br># facilities are supported.<br>#syslog_facility = mail<br><br>##<br>## SSL settings<br>##<br><br># IP or host address where to listen in for SSL connections. Defaults<br># to above if not specified.<br>#ssl_listen =<br>ssl_listen =<br># Disable SSL/TLS support.<br>#ssl_disable = no<br><br># PEM encoded X.509 SSL/TLS certificate and private key. They're opened before<br># dropping root privileges, so keep the key file unreadable by anyone but<br># root. Included doc/mkcert.sh can be used to easily generate self-signed<br># certificate, just make sure to update the domains in dovecot-openssl.cnf<br>#ssl_cert_file = /etc/pki/dovecot/certs/dovecot.pem<br>#ssl_key_file = /etc/pki/dovecot/private/dovecot.pem<br><br># If key file is password protected, give the password here. Alternatively<br># give it when starting dovecot with -p parameter.<br>#ssl_key_password =<br><br># File containing trusted SSL certificate authorities. Usually not needed.<br># The CAfile should contain the CA-certificate(s) followed by the matching<br># CRL(s). CRL checking is new in dovecot .rc1<br>#ssl_ca_file =<br><br># Request client to send a certificate.<br>#ssl_verify_client_cert = no<br><br># How often to regenerate the SSL parameters file. Generation is quite CPU<br># intensive operation. The value is in hours, 0 disables regeneration<br># entirely.<br>#ssl_parameters_regenerate = 168<br><br># SSL ciphers to use<br>#ssl_cipher_list = ALL:!LOW<br><br># Show protocol level SSL errors.<br>#verbose_ssl = no<br><br>##<br>## Login processes<br>##<br><br># Directory where authentication process places authentication UNIX sockets<br># which login needs to be able to connect to. The sockets are created when<br># running as root, so you don't have to worry about permissions. Note that<br># everything in this directory is deleted when Dovecot is started.<br>#login_dir = /var/run/dovecot/login<br><br># chroot login process to the login_dir. Only reason not to do this is if you<br># wish to run the whole Dovecot without roots.<br># http://wiki.dovecot.org/Rootless<br>#login_chroot = yes<br><br># User to use for the login process. Create a completely new user for this,<br># and don't use it anywhere else. The user must also belong to a group where<br># only it has access, it's used to control access for authentication process.<br># Note that this user is NOT used to access mails.<br># http://wiki.dovecot.org/UserIds<br>#login_user = dovecot<br><br># Set max. process size in megabytes. If you don't use<br># login_process_per_connection you might need to grow this.<br>#login_process_size = 32<br><br># Should each login be processed in it's own process (yes), or should one<br># login process be allowed to process multiple connections (no)? Yes is more<br># secure, espcially with SSL/TLS enabled. No is faster since there's no need<br># to create processes all the time.<br>#login_process_per_connection = yes<br><br># Number of login processes to keep for listening new connections.<br>#login_processes_count = 3<br><br># Maximum number of login processes to create. The listening process count<br># usually stays at login_processes_count, but when multiple users start logging<br># in at the same time more extra processes are created. To prevent fork-bombing<br># we check only once in a second if new processes should be created - if all<br># of them are used at the time, we double their amount until the limit set by<br># this setting is reached.<br>#login_max_processes_count = 128<br><br># Maximum number of connections allowed per each login process. This setting<br># is used only if login_process_per_connection=no. Once the limit is reached,<br># the process notifies master so that it can create a new login process.<br># You should make sure that the process has at least<br># 16 + login_max_connections * 2 available file descriptors.<br>#login_max_connections = 256<br><br># Greeting message for clients.<br>#login_greeting = Dovecot ready.<br><br># Space-separated list of elements we want to log. The elements which have<br># a non-empty variable value are joined together to form a comma-separated<br># string.<br>#login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c<br><br># Login log format. %$ contains login_log_format_elements string, %s contains<br># the data we want to log.<br>#login_log_format = %$: %s<br><br>##<br>## Mailbox locations and namespaces<br>##<br><br># Location for users' mailboxes. This is the same as the old default_mail_env<br># setting. The default is empty, which means that Dovecot tries to find the<br># mailboxes automatically. This won't work if the user doesn't have any mail<br># yet, so you should explicitly tell Dovecot the full location.<br>#<br># If you're using mbox, giving a path to the INBOX file (eg. /var/mail/%u)<br># isn't enough. You'll also need to tell Dovecot where the other mailboxes are<br># and where Dovecot can place its index files. This is called the "root mail<br># directory", and it must be the first path given in the mail_location setting.<br>#<br># There are a few special variables you can use, eg.:<br>#<br># %u - username<br># %n - user part in user@domain, same as %u if there's no domain<br># %d - domain part in user@domain, empty if there's no domain<br># %h - home directory<br>#<br># See doc/variables.txt for full list. Some examples:<br>#<br># mail_location = maildir:~/Maildir<br># mail_location = mbox:~/mail:INBOX=/var/mail/%u<br># mail_location = mbox:/var/mail/%d/%1n/%n:INDEX=/var/indexes/%d/%1n/%n<br>#<br># http://wiki.dovecot.org/MailLocation<br>#<br>#mail_location =<br><br># If you need to set multiple mailbox locations or want to change default<br># namespace settings, you can do it by defining namespace sections:<br>#<br># You can have private, shared and public namespaces. The only difference<br># between them is how Dovecot announces them to client via NAMESPACE<br># extension. Shared namespaces are meant for user-owned mailboxes which are<br># shared to other users, while public namespaces are for more globally<br># accessible mailboxes.<br>#<br># REMEMBER: If you add any namespaces, the default namespace must be added<br># explicitly, ie. mail_location does nothing unless you have a namespace<br># without a location setting. Default namespace is simply done by having a<br># namespace with empty prefix.<br>#namespace private {<br> # Hierarchy separator to use. You should use the same separator for all<br> # namespaces or some clients get confused. '/' is usually a good one.<br> # The default however depends on the underlying mail storage format.<br> #separator =<br><br> # Prefix required to access this namespace. This needs to be different for<br> # all namespaces. For example "Public/".<br> #prefix =<br><br> # Physical location of the mailbox. This is in same format as<br> # mail_location, which is also the default for it.<br> #location =<br><br> # There can be only one INBOX, and this setting defines which namespace<br> # has it.<br> #inbox = yes<br><br> # If namespace is hidden, it's not advertised to clients via NAMESPACE<br> # extension or shown in LIST replies. This is mostly useful when converting<br> # from another server with different namespaces which you want to depricate<br> # but still keep working. For example you can create hidden namespaces with<br> # prefixes "~/mail/", "~%u/mail/" and "mail/".<br> #hidden = yes<br>#}<br><br># Grant access to these extra groups for mail processes. Typical use would be<br># to give "mail" group write access to /var/mail to be able to create dotlocks.<br>#mail_extra_groups =<br><br># Allow full filesystem access to clients. There's no access checks other than<br># what the operating system does for the active UID/GID. It works with both<br># maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/<br># or ~user/.<br>#mail_full_filesystem_access = no<br><br>##<br>## Mail processes<br>##<br><br># Enable mail process debugging. This can help you figure out why Dovecot<br># isn't finding your mails.<br>#mail_debug = no<br><br># Log prefix for mail processes. See doc/variables.txt for list of possible<br># variables you can use.<br>#mail_log_prefix = "%Us(%u): "<br><br># Use mmap() instead of read() to read mail files. read() seems to be a bit<br># faster with my Linux/x86 and it's better with NFS, so that's the default.<br># Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes.<br>#mail_read_mmaped = no<br><br># Don't use mmap() at all. This is required if you store indexes to shared<br># filesystems (NFS or clustered filesystem).<br>#mmap_disable = no<br><br># Don't write() to mmaped files. This is required for some operating systems<br># which use separate caches for them, such as OpenBSD.<br>#mmap_no_write = no<br><br># Locking method for index files. Alternatives are fcntl, flock and dotlock.<br># Dotlocking uses some tricks which may create more disk I/O than other locking<br># methods. NOTE: If you use NFS, remember to change also mmap_disable setting!<br>#lock_method = fcntl<br><br># Drop all privileges before exec()ing the mail process. This is mostly<br># meant for debugging, otherwise you don't get core dumps. It could be a small<br># security risk if you use single UID for multiple users, as the users could<br># ptrace() each others processes then.<br>#mail_drop_priv_before_exec = no<br><br># Show more verbose process titles (in ps). Currently shows user name and<br># IP address. Useful for seeing who are actually using the IMAP processes<br># (eg. shared mailboxes or if same uid is used for multiple accounts).<br>#verbose_proctitle = no<br><br># Valid UID range for users, defaults to 500 and above. This is mostly<br># to make sure that users can't log in as daemons or other system users.<br># Note that denying root logins is hardcoded to dovecot binary and can't<br># be done even if first_valid_uid is set to 0.<br>#first_valid_uid = 500<br>#last_valid_uid = 0<br><br># Valid GID range for users, defaults to non-root/wheel. Users having<br># non-valid GID as primary group ID aren't allowed to log in. If user<br># belongs to supplementary groups with non-valid GIDs, those groups are<br># not set.<br>#first_valid_gid = 1<br>#last_valid_gid = 0<br><br># Maximum number of running mail processes. When this limit is reached,<br># new users aren't allowed to log in.<br>#max_mail_processes = 1024<br><br># Set max. process size in megabytes. Most of the memory goes to mmap()ing<br># files, so it shouldn't harm much even if this limit is set pretty high.<br>#mail_process_size = 256<br><br># Maximum allowed length for mail keyword name. It's only forced when trying<br># to create new keywords.<br>#mail_max_keyword_length = 50<br><br># Default umask to use for mail files and directories.<br>#umask = 0077<br><br># ':' separated list of directories under which chrooting is allowed for mail<br># processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too).<br># This setting doesn't affect login_chroot or auth_chroot variables.<br># WARNING: Never add directories here which local users can modify, that<br># may lead to root exploit. Usually this should be done only if you don't<br># allow shell access for users. See doc/configuration.txt for more information.<br>#valid_chroot_dirs =<br><br># Default chroot directory for mail processes. This can be overridden for<br># specific users in user database by giving /./ in user's home directory<br># (eg. /home/./user chroots into /home). Note that usually there is no real<br># need to do chrooting, Dovecot doesn't allow users to access files outside<br># their mail directory anyway.<br>#mail_chroot =<br><br>##<br>## Mailbox handling optimizations<br>##<br><br># Space-separated list of fields to initially save into cache file. Currently<br># these fields are allowed:<br>#<br># flags, date.sent, date.received, size.virtual, size.physical<br># mime.parts, imap.body, imap.bodystructure<br>#<br># Different IMAP clients work in different ways, so they benefit from<br># different cached fields. Some do not benefit from them at all. Caching more<br># than necessary generates useless disk I/O, so you don't want to do that<br># either.<br>#<br># Dovecot attempts to automatically figure out what client wants and it keeps<br># only that. However the first few times a mailbox is opened, Dovecot hasn't<br># yet figured out what client needs, so it may not perform optimally. If you<br># know what fields the majority of your clients need, it may be useful to set<br># these fields by hand. If client doesn't actually use them, Dovecot will<br># eventually drop them.<br>#<br># Usually you should just leave this field alone. The potential benefits are<br># typically unnoticeable.<br>#mail_cache_fields =<br><br># Space-separated list of fields that Dovecot should never save to cache file.<br># Useful if you want to save disk space at the cost of more I/O when the fields<br># needed.<br>#mail_never_cache_fields =<br><br># The minimum number of mails in a mailbox before updates are done to cache<br># file. This allows optimizing Dovecot's behavior to do less disk writes at<br># the cost of more disk reads.<br>#mail_cache_min_mail_count = 0<br><br># When IDLE command is running, mailbox is checked once in a while to see if<br># there are any new mails or other changes. This setting defines the minimum<br># time to wait between those checks. Dovecot is however able to use dnotify<br># and inotify with Linux to reply immediately after the change occurs.<br>#mailbox_idle_check_interval = 30<br><br># Save mails with CR+LF instead of plain LF. This makes sending those mails<br># take less CPU, especially with sendfile() syscall with Linux and FreeBSD.<br># But it also creates a bit more disk I/O which may just make it slower.<br># Also note that if other software reads the mboxes/maildirs, they may handle<br># the extra CRs wrong and cause problems.<br>#mail_save_crlf = no<br><br>##<br>## Maildir-specific settings<br>##<br><br># By default LIST command returns all entries in maildir beginning with dot.<br># Enabling this option makes Dovecot return only entries which are directories.<br># This is done by stat()ing each entry, so it causes more disk I/O.<br># (For systems setting struct dirent->d_type, this check is free and it's<br># done always regardless of this setting)<br>#maildir_stat_dirs = no<br><br># Copy mail to another folders using hard links. This is much faster than<br># actually copying the file. This is problematic only if something modifies<br># the mail in one folder but doesn't want it modified in the others. I don't<br># know any MUA which would modify mail files directly. IMAP protocol also<br># requires that the mails don't change, so it would be problematic in any case.<br># If you care about performance, enable it.<br>#maildir_copy_with_hardlinks = no<br><br>##<br>## mbox-specific settings<br>##<br><br># Which locking methods to use for locking mbox. There are four available:<br># dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe<br># solution. If you want to use /var/mail/ like directory, the users<br># will need write access to that directory.<br># fcntl : Use this if possible. Works with NFS too if lockd is used.<br># flock : May not exist in all systems. Doesn't work with NFS.<br># lockf : May not exist in all systems. Doesn't work with NFS.<br>#<br># You can use multiple locking methods; if you do the order they're declared<br># in is important to avoid deadlocks if other MTAs/MUAs are using multiple<br># locking methods as well. Some operating systems don't allow using some of<br># them simultaneously.<br>#mbox_read_locks = fcntl<br>#mbox_write_locks = fcntl<br><br># Maximum time in seconds to wait for lock (all of them) before aborting.<br>#mbox_lock_timeout = 300<br><br># If dotlock exists but the mailbox isn't modified in any way, override the<br># lock file after this many seconds.<br>#mbox_dotlock_change_timeout = 120<br><br># When mbox changes unexpectedly we have to fully read it to find out what<br># changed. If the mbox is large this can take a long time. Since the change<br># is usually just a newly appended mail, it'd be faster to simply read the<br># new mails. If this setting is enabled, Dovecot does this but still safely<br># fallbacks to re-reading the whole mbox file whenever something in mbox isn't<br># how it's expected to be. The only real downside to this setting is that if<br># some other MUA changes message flags, Dovecot doesn't notice it immediately.<br># Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK<br># commands.<br>#mbox_dirty_syncs = yes<br><br># Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE,<br># EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored.<br>#mbox_very_dirty_syncs = no<br><br># Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK<br># commands and when closing the mailbox). This is especially useful for POP3<br># where clients often delete all mails. The downside is that our changes<br># aren't immediately visible to other MUAs.<br>#mbox_lazy_writes = yes<br><br># If mbox size is smaller than this (in kilobytes), don't write index files.<br># If an index file already exists it's still read, just not updated.<br><br>#mbox_min_index_size = 0<br><br>##<br>## dbox-specific settings<br>##<br><br># Maximum dbox file size in kilobytes until it's rotated.<br>#dbox_rotate_size = 2048<br><br># Minimum dbox file size in kilobytes before it's rotated<br># (overrides dbox_rotate_days)<br>#dbox_rotate_min_size = 16<br><br># Maximum dbox file age in days until it's rotated. Day always begins from<br># midnight, so 1 = today, 2 = yesterday, etc. 0 = check disabled.<br>#dbox_rotate_days = 0<br><br>##<br>## IMAP specific settings<br>##<br><br>protocol imap {<br> # Login executable location.<br> #login_executable = /usr/libexec/dovecot/imap-login<br><br> # IMAP executable location. Changing this allows you to execute other<br> # binaries before the imap process is executed.<br> #<br> # This would write rawlogs into ~/dovecot.rawlog/ directory:<br> # mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap<br> #<br> # This would attach gdb into the imap process and write backtraces into<br> # /tmp/gdbhelper.* files:<br> # mail_executable = /usr/libexec/dovecot/gdbhelper /usr/libexec/dovecot/imap<br> #<br> #mail_executable = /usr/libexec/dovecot/imap<br><br> # Maximum IMAP command line length in bytes. Some clients generate very long<br> # command lines with huge mailboxes, so you may need to raise this if you get<br> # "Too long argument" or "IMAP command line too large" errors often.<br> #imap_max_line_length = 65536<br><br> # Support for dynamically loadable plugins. mail_plugins is a space separated<br> # list of plugins to load.<br> #mail_plugins =<br> #mail_plugin_dir = /usr/lib/dovecot/imap<br><br> # Send IMAP capabilities in greeting message. This makes it unnecessary for<br> # clients to request it with CAPABILITY command, so it saves one round-trip.<br> # Many clients however don't understand it and ask the CAPABILITY anyway.<br> #login_greeting_capability = no<br><br> # Override the IMAP CAPABILITY response.<br> #imap_capability =<br><br> # Workarounds for various client bugs:<br> # delay-newmail:<br> # Send EXISTS/RECENT new mail notifications only when replying to NOOP<br> # and CHECK commands. Some clients ignore them otherwise, for example<br> # OSX Mail. Outlook Express breaks more badly though, without this it<br> # may show user "Message no longer in server" errors. Note that OE6 still<br> # breaks even with this workaround if synchronization is set to<br> # "Headers Only".<br> # outlook-idle:<br> # Outlook and Outlook Express never abort IDLE command, so if no mail<br> # arrives in half a hour, Dovecot closes the connection. This is still<br> # fine, except Outlook doesn't connect back so you don't see if new mail<br> # arrives.<br> # netscape-eoh:<br> # Netscape 4.x breaks if message headers don't end with the empty "end of<br> # headers" line. Normally all messages have this, but setting this<br> # workaround makes sure that Netscape never breaks by adding the line if<br> # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..]<br> # commands. Note that RFC says this shouldn't be done.<br> # tb-extra-mailbox-sep:<br> # With mbox storage a mailbox can contain either mails or submailboxes,<br> # but not both. Thunderbird separates these two by forcing server to<br> # accept '/' suffix in mailbox names in subscriptions list.<br> # The list is space-separated.<br> #imap_client_workarounds = outlook-idle<br>}<br><br>##<br>## POP3 specific settings<br>##<br><br>protocol pop3 {<br> # Login executable location.<br> #login_executable = /usr/libexec/dovecot/pop3-login<br><br> # POP3 executable location. See IMAP's mail_executable above for examples<br> # how this could be changed.<br> #mail_executable = /usr/libexec/dovecot/pop3<br><br> # Don't try to set mails non-recent or seen with POP3 sessions. This is<br> # mostly intended to reduce disk I/O. With maildir it doesn't move files<br> # from new/ to cur/, with mbox it doesn't write Status-header.<br> #pop3_no_flag_updates = no<br><br> # Support LAST command which exists in old POP3 specs, but has been removed<br> # from new ones. Some clients still wish to use this though. Enabling this<br> # makes RSET command clear all \Seen flags from messages.<br> #pop3_enable_last = no<br><br> # If mail has X-UIDL header, use it as the mail's UIDL.<br> #pop3_reuse_xuidl = no<br><br> # Keep the mailbox locked for the entire POP3 session.<br> #pop3_lock_session = no<br><br> # POP3 UIDL format to use. You can use following variables:<br> #<br> # %v - Mailbox UIDVALIDITY<br> # %u - Mail UID<br> # %m - MD5 sum of the mailbox headers in hex (mbox only)<br> # %f - filename (maildir only)<br> #<br> # If you want UIDL compatibility with other POP3 servers, use:<br> # UW's ipop3d : %08Xv%08Xu<br> # Courier version 0 : %f<br> # Courier version 1 : %u<br> # Courier version 2 : %v-%u<br> # Cyrus (<= 2.1.3) : %u<br> # Cyrus (>= 2.1.4) : %v.%u<br> # Older Dovecots : %v.%u<br> # tpop3d : %Mf<br> #<br> # Note that Outlook 2003 seems to have problems with %v.%u format which was<br> # Dovecot's default, so if you're building a new server it would be a good<br> # idea to change this. %08Xu%08Xv should be pretty fail-safe.<br> #<br> # NOTE: Nowadays this is required to be set explicitly, since the old<br> # default was bad but it couldn't be changed without breaking existing<br> # installations. %08Xu%08Xv will be the new default, so use it for new<br> # installations.<br> #<br> #pop3_uidl_format = %08Xu%08Xv<br><br> # POP3 logout format string:<br> # %t - number of TOP commands<br> # %p - number of bytes sent to client as a result of TOP command<br> # %r - number of RETR commands<br> # %b - number of bytes sent to client as a result of RETR command<br> # %d - number of deleted messages<br> # %m - number of messages (before deletion)<br> # %s - mailbox size in bytes (before deletion)<br> #pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s<br><br> # Support for dynamically loadable plugins. mail_plugins is a space separated<br> # list of plugins to load.<br> #mail_plugins =<br> #mail_plugin_dir = /usr/lib/dovecot/pop3<br><br> # Workarounds for various client bugs:<br> # outlook-no-nuls:<br> # Outlook and Outlook Express hang if mails contain NUL characters.<br> # This setting replaces them with 0x80 character.<br> # oe-ns-eoh:<br> # Outlook Express and Netscape Mail breaks if end of headers-line is<br> # missing. This option simply sends it if it's missing.<br> # The list is space-separated.<br> #pop3_client_workarounds =<br>}<br><br>##<br>## LDA specific settings<br>##<br><br>protocol lda {<br> # Address to use when sending rejection mails.<br> postmaster_address = postmaster@example.com<br><br> # Hostname to use in various parts of sent mails, eg. in Message-Id.<br> # Default is the system's real hostname.<br> #hostname =<br><br> # Support for dynamically loadable plugins. mail_plugins is a space separated<br> # list of plugins to load.<br> #mail_plugins =<br> #mail_plugin_dir = /usr/lib/dovecot/lda<br><br> # Binary to use for sending mails.<br> #sendmail_path = /usr/lib/sendmail<br><br> # UNIX socket path to master authentication server to find users.<br> #auth_socket_path = /var/run/dovecot/auth-master<br>}<br><br>##<br>## Authentication processes<br>##<br><br># Executable location<br>#auth_executable = /usr/libexec/dovecot/dovecot-auth<br><br># Set max. process size in megabytes.<br>#auth_process_size = 256<br><br># Authentication cache size in kilobytes. 0 means it's disabled.<br># Note that bsdauth, PAM and vpopmail require cache_key to be set for caching<br># to be used. Also note that currently auth cache doesn't work very well if<br># you're using multiple passdbs with same usernames in them.<br>#auth_cache_size = 0<br># Time to live in seconds for cached data. After this many seconds the cached<br># record is no longer used, *except* if the main database lookup returns<br># internal failure. We also try to handle password changes automatically: If<br># user's previous authentication was successful, but this one wasn't, the<br># cache isn't used. For now this works only with plaintext authentication.<br>#auth_cache_ttl = 3600<br><br># Space separated list of realms for SASL authentication mechanisms that need<br># them. You can leave it empty if you don't want to support multiple realms.<br># Many clients simply use the first one listed here, so keep the default realm<br># first.<br>#auth_realms =<br># Default realm/domain to use if none was specified. This is used for both<br># SASL realms and appending @domain to username in plaintext logins.<br>#auth_default_realm =<br><br># List of allowed characters in username. If the user-given username contains<br># a character not listed in here, the login automatically fails. This is just<br># an extra check to make sure user can't exploit any potential quote escaping<br># vulnerabilities with SQL/LDAP databases. If you want to allow all characters,<br># set this value to empty.<br>#auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@<br><br># Username character translations before it's looked up from databases. The<br># value contains series of from -> to characters. For example "#@/@" means<br># that '#' and '/' characters are translated to '@'.<br>#auth_username_translation =<br><br># Username formatting before it's looked up from databases. You can use<br># the standard variables here, eg. %Lu would lowercase the username, %n would<br># drop away the domain if it was given, or "%n-AT-%d" would change the '@' into<br># "-AT-". This translation is done after auth_username_translation changes.<br>#auth_username_format =<br><br># If you want to allow master users to log in by specifying the master<br># username within the normal username string (ie. not using SASL mechanism's<br># support for it), you can specify the separator character here. The format<br># is then <username><separator><master username>. UW-IMAP uses "*" as the<br># separator, so that could be a good choice.<br>#auth_master_user_separator =<br><br># Username to use for users logging in with ANONYMOUS SASL mechanism<br>#auth_anonymous_username = anonymous<br><br># More verbose logging. Useful for figuring out why authentication isn't<br># working.<br>auth_verbose = yes<br><br># Even more verbose logging for debugging purposes. Shows for example SQL<br># queries.<br>auth_debug = yes<br><br># In case of password mismatches, log the passwords and used scheme so the<br># problem can be debugged. Requires auth_debug=yes to be set.<br>auth_debug_passwords = yes<br><br># Maximum number of dovecot-auth worker processes. They're used to execute<br># blocking passdb and userdb queries (eg. MySQL and PAM). They're<br># automatically created and destroyed as needed.<br>#auth_worker_max_count = 30<br><br># Kerberos keytab to use for the GSSAPI mechanism. Will use the system<br># default (usually /etc/krb5.keytab) if not specified.<br>#auth_krb5_keytab =<br><br>auth default {<br> # Space separated list of wanted authentication mechanisms:<br> # plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi<br> mechanisms = plain<br><br> #<br> # Password database is used to verify user's password (and nothing more).<br> # You can have multiple passdbs and userdbs. This is useful if you want to<br> # allow both system users (/etc/passwd) and virtual users to login without<br> # duplicating the system users into virtual database.<br> #<br> # http://wiki.dovecot.org/PasswordDatabase<br> #<br> # By adding master=yes setting inside a passdb you make the passdb a list<br> # of "master users", who can log in as anyone else. Unless you're using PAM,<br> # you probably still want the destination user to be looked up from passdb<br> # that it really exists. This can be done by adding pass=yes setting to the<br> # master passdb.<br> #<br> # http://wiki.dovecot.org/MasterPassword<br><br> # Users can be temporarily disabled by adding a passdb with deny=yes.<br> # If the user is found from that database, authentication will fail.<br> # The deny passdb should always be specified before others, so it gets<br> # checked first. Here's an example:<br><br> #passdb passwd-file {<br> # File contains a list of usernames, one per line<br> #args = /etc/dovecot.deny<br> #deny = yes<br> #}<br><br> # PAM authentication. Preferred nowadays by most systems.<br> # Note that PAM can only be used to verify if user's password is correct,<br> # so it can't be used as userdb. If you don't want to use a separate user<br> # database (passwd usually), you can use static userdb.<br> # REMEMBER: You'll need /etc/pam.d/dovecot file created for PAM<br> # authentication to actually work.<br> # http://wiki.dovecot.org/PasswordDatabase/PAM<br>passdb pam {<br> # use /etc/pam.d/imap and /etc/pam.d/pop3<br> args = *<br>}<br> # /etc/passwd or similar, using getpwnam()<br> # In many systems nowadays this uses Name Service Switch, which is<br> # configured in /etc/nsswitch.conf.<br> # http://wiki.dovecot.org/AuthDatabase/Passwd<br> #passdb passwd {<br> #}<br><br> # /etc/shadow or similiar, using getspnam(). Deprecated by PAM nowadays.<br> # http://wiki.dovecot.org/PasswordDatabase/Shadow<br> #passdb shadow {<br> #}<br> # PAM-like authentication for OpenBSD.<br> # http://wiki.dovecot.org/PasswordDatabase/BSDAuth<br> #passdb bsdauth {<br> # [cache_key=<key>] - See cache_key in PAM for explanation.<br> #args =<br> #}<br><br> # passwd-like file with specified location<br> # http://wiki.dovecot.org/AuthDatabase/PasswdFile<br> #passdb passwd-file {<br> # Path for passwd-file<br> #args =<br> #}<br><br> # checkpassword executable authentication<br> # NOTE: You will probably want to use "userdb prefetch" with this.<br> # http://wiki.dovecot.org/PasswordDatabase/CheckPassword<br> #passdb checkpassword {<br> # Path for checkpassword binary<br> #args =<br> #}<br><br> # SQL database<br> # http://wiki.dovecot.org/AuthDatabase/SQL<br> #passdb sql {<br> # Path for SQL configuration file, see doc/dovecot-sql.conf for example<br> #args =<br> #}<br><br> # LDAP database<br> # http://wiki.dovecot.org/AuthDatabase/LDAP<br> #passdb ldap {<br> # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example<br> #args =<br> #}<br><br> # vpopmail authentication<br> # http://wiki.dovecot.org/AuthDatabase/VPopMail<br> #passdb vpopmail {<br> # [cache_key=<key>] - See cache_key in PAM for explanation.<br> #args =<br> #}<br><br> #<br> # User database specifies where mails are located and what user/group IDs<br> # own them. For single-UID configuration use "static".<br> #<br> # http://wiki.dovecot.org/UserDatabase<br> #<br><br> # /etc/passwd or similar, using getpwnam()<br> # In many systems nowadays this uses Name Service Switch, which is<br> # configured in /etc/nsswitch.conf. WARNING: nss_ldap is known to be broken<br> # with Dovecot. Don't use it, or users might log in as each others!<br> # http://wiki.dovecot.org/AuthDatabase/Passwd<br> userdb passwd {<br> }<br><br> # passwd-like file with specified location<br> # http://wiki.dovecot.org/AuthDatabase/PasswdFile<br> #userdb passwd-file {<br> # Path for passwd-file<br> #args =<br> #}<br><br> # static settings generated from template<br> # http://wiki.dovecot.org/UserDatabase/Static<br> #userdb static {<br> # Template for the fields. Can return anything a userdb could normally<br> # return. For example:<br> #<br> # args = uid=500 gid=500 home=/var/mail/%u<br> #<br> #args =<br> #}<br><br> # SQL database<br> # http://wiki.dovecot.org/AuthDatabase/SQL<br> #userdb sql {<br> # Path for SQL configuration file, see doc/dovecot-sql.conf for example<br> #args =<br> #}<br><br> # LDAP database<br> # http://wiki.dovecot.org/AuthDatabase/LDAP<br> #userdb ldap {<br> # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example<br> #args =<br> #}<br><br> # vpopmail<br> # http://wiki.dovecot.org/AuthDatabase/VPopMail<br> #userdb vpopmail {<br> #}<br><br> # "prefetch" user database means that the passdb already provided the<br> # needed information and there's no need to do a separate userdb lookup.<br> # This can be made to work with SQL and LDAP databases, see their example<br> # configuration files for more information how to do it.<br> # http://wiki.dovecot.org/UserDatabase/Prefetch<br> #userdb prefetch {<br> #}<br><br> # User to use for the process. This user needs access to only user and<br> # password databases, nothing else. Only shadow and pam authentication<br> # requires roots, so use something else if possible. Note that passwd<br> # That user is specified by userdb above.<br> user = root<br><br> # Directory where to chroot the process. Most authentication backends don't<br> # work if this is set, and there's no point chrooting if auth_user is root.<br> # Note that valid_chroot_dirs isn't needed to use this setting.<br> #chroot =<br><br> # Number of authentication processes to create<br> #count = 1<br><br> # Require a valid SSL client certificate or the authentication fails.<br> #ssl_require_client_cert = no<br><br> # Take the username from client's SSL certificate, using<br> # X509_NAME_get_text_by_NID() which returns the subject's DN's<br> # CommonName.<br> #ssl_username_from_cert = no<br><br> # It's possible to export the authentication interface to other programs:<br> #socket listen {<br> #master {<br> # Master socket is typically used to give Dovecot's local delivery<br> # agent access to userdb so it can find mailbox locations. It can<br> # however also be used to disturb regular user authentications.<br> # WARNING: Giving untrusted users access to master socket may be a<br> # security risk, don't give too wide permissions to it!<br> #path = /var/run/dovecot/auth-master<br> #mode = 0600<br> # Default user/group is the one who started dovecot-auth (root)<br> #user =<br> #group =<br> #}<br> #client {<br> # The client socket is generally safe to export to everyone. Typical use<br> # is to export it to your SMTP server so it can do SMTP AUTH lookups<br> # using it.<br> #path = /var/run/dovecot/auth-client<br> #mode = 0660<br> #}<br> #}<br>}<br><br># If you wish to use another authentication server than dovecot-auth, you can<br># use connect sockets. They assumed to be already running, Dovecot's master<br># process only tries to connect to them. They don't need any other settings<br># than the path for the master socket, as the configuration is done elsewhere.<br># Note that the client sockets must exist in the login_dir.<br>#auth external {<br># socket connect {<br># master {<br># path = /var/run/dovecot/auth-master<br># }<br># }<br>#}<br><br>##<br>## Dictionary server settings<br>##<br><br># Dictionary can be used by some plugins to store key=value lists.<br># Currently this is only used by dict quota backend. The dictionary can be<br># used either directly or though a dictionary server. The following dict block<br># maps dictionary names to URIs when the server is used. These can then be<br># referenced using URIs in format "proxy:<name>".<br><br>dict {<br> #quota = mysql:/etc/dovecot-dict-quota.conf<br>}<br><br>##<br>## Plugin settings<br>##<br><br>plugin {<br> # Here you can give some extra environment variables to mail processes.<br> # This is mostly meant for passing parameters to plugins. %variable<br> # expansion is done for all values.<br><br><br> # Quota plugin. Multiple backends are supported:<br> # dirsize: Find and sum all the files found from mail directory<br> # dict: Keep quota stored in dictionary (eg. SQL)<br> # maildir: Maildir++ quota<br> # fs: Read-only support for filesystem quota<br> #quota = maildir<br><br> # ACL plugin. vfile backend reads ACLs from "dovecot-acl" file from maildir<br> # directory. You can also optionally give a global ACL directory path where<br> # ACLs are applied to all users' mailboxes. The global ACL directory contains<br> # one file for each mailbox, eg. INBOX or sub.mailbox.<br> #acl = vfile:/etc/dovecot-acls<br><br> # Convert plugin. If set, specifies the source storage path which is<br> # converted to destination storage (mail_location).<br> #convert_mail = mbox:%h/mail<br><br> # Trash plugin. When saving a message would make user go over quota, this<br> # plugin automatically deletes the oldest mails from configured mailboxes<br> # until the message can be saved within quota limits. The configuration file<br> # is a text file where each line is in format: <priority> <mailbox name><br> # Mails are first deleted in lowest -> highest priority number order<br> #trash = /etc/dovecot-trash.conf<br>}<br><br><br><br><br><br><br><br>----------------<br>and that is my dovecot.conf that comes with my dovecot installation automatically when i type: yum install dovecot<br>if anyone is willing to share his dovecot.conf file.. ?? (a working one ofcause ;))<br><br>Thanx.<br>Mark.<br><br /><hr />Met MSN Spaces kun je per e-mail je weblog bijwerken. Publiceer leuke verhalen, foto's en meer! Het is gratis! <a href='http://clk.atdmt.com/MSN/go/msnnksac0030000001msn/direct/01/?href=http://www.imagine-msn.com/spaces' target='_new'>Het is gratis!</a></body>
</html>