Hot answers tagged

35

From a DNS perspective you have SRV DNS records which allow the use of DNS for publishing services and service discovery. Their main use is to allow services to run easily on non-standard ports and to reduce the configuration burden when setting up clients. A SRV record has the following form: _Service._Protocol.Name. TTL Class SRV Priority Weight Port ...


11

Yes In this particular case, you are using a 'Maildir' format mailbox. In Maildir, it's safe to use 'rm' to remove an individual piece of email, to use 'mv' to move an individual mail between folders on the same file system, etc. With other mail storage types, it may not be safe to rm a single email. More about Maildir: http://cr.yp.to/proto/maildir....


10

Carry out the following: apt-get install php5-imap However it's not enabled by default so enable it with: php5enmod imap Then bounce apache: service apache2 restart Done.


10

A tuple of (folder name, folder UIDVALIDITY, message UID) distinguishes a message from all others in an IMAP account. For any given message, that tuple can change between sessions, so you might want to track its Message-ID as a backup in case this happens. Yes, it really is that annoying.


9

The listen = addr:port config is deprecated in newer versions of dovecot. The new way of doing things is with service { inet_listener imap { address = ... } }. On my system it's in /etc/dovecot/conf.d/10-master.conf: service imap-login { inet_listener imap { address = 127.0.0.1 } }


9

The auth_http does two main things: It authenticates users (including various options to effectively delay users on failed authentication). And it determines which backend to use (and which username and password to use in backend authentication, if at all). While in some cases authentication can be handled directly by a backend, it's not something always ...


9

This is normal; it's exactly the same that happens, if you try to telnet HTTPS 443; the port 993 is for IMAPS, which uses TLS. In TLS connection (from RFC 5246, 7.4.1.2 Client Hello): When a client first connects to a server, it is required to send the ClientHello as its first message. The client can also send a ClientHello in response to a ...


9

getmail seems to support IMAP IDLE. So you can write a simple systemd job: [Unit] Description=Starts getmail After=network.target [Service] ExecStart=/usr/bin/getmail --idle=INBOX Restart=on-failure [Install] WantedBy=multi-user.target Put it in /etc/systemd/system/getmail-idle.service and run systemctl enable --now getmail-idle. Of course you may need ...


8

You're probably not sharing the same mailbox location/folder and/or mailbox delivery style (MBOX vs. MDIR) in both Postfix and Dovecot. As a result, Postfix is (correctly) writing under "/home/mailuser/Maildir" (where you see your mail arriving, under the "new" subfolder), but as dovecot is searching somewhere else... it doesn't find such mails (so you get a ...


7

The different meaning of tls:// and ssl:// in $config['default_host'] is unfortunately not documented. tls:// means usage of STARTTLS, thus usually port 143 ssl:// means usage of TLS, thus usually port 993 The same is valid for $config['smtp_server'] and ports 25 and 587 for tls://, ports 465 for ssl://. Can't give any source for this information, as I (...


6

The main IMAP protocol document is RFC3501. Section 2.3.2 describes the standard flags every IMAP implementation must work with. Are the system flags sufficiently widely supported that I can reasonably depend on them in my application? Indeed, RFC3501 describes the universal system flags. Are user-defined flags sufficiently widely supported? There ...


6

I tried the accepted answer and it failed - the dovecot versions in play are probably too far apart and we also switched the underlying MTA. So here is a more robust solution: doveadm import Assuming you're hosting emails for the domain hosted.tld and an account exists for the login local.account@hosted.tld (or maybe simply ruth) and the backup from the ...


6

I don't know what you mean when you say UIDs are not unique in a mailbox, just in subfolders. By subfolders, do you mean anything other than INBOX? In any case, it sounds wrong. UIDs are in fact unique within each folder and it doesn't matter it it's INBOX or any other folder. What can happen is that UIDs can change between sessions. Generally this happens ...


6

Unfortunately both are very common. Most of the OpenSource software I've found uses Junk, and most of the Proprietary software seems to use Spam. New users may be accustomed to either... The only "solution" I've found is to use one or the other, and to do so very consistently. At home I use RoundCube as well, and I standardized on "Junk" long before. If I ...


6

ActiveSync and IMAP are quite similar. Both ActiveSync and IMAP IDLE maintain a dormant TCP session for inbound push notifications. IMAP IDLE handles 'push' email as well FYI. Both are quite conservative with bandwidth usage. Bandwidth consumption in practice will be more determined by configuration parameters than protocol choice. Setting things like '...


6

This behaviour depends on the mail client, not the server itself. There should be an option in your mail client to put a copy of sent e-mails in the "Sent" folder.


6

Firstly I assume that user celestine (with password 100995) is set up correctly in your system (simply check if a login is successful with no further errors / warnings). According to your dovecot.conf, you set up your server authentication process using Lookup databases with passwd. That's fine as User Database, but with passwd as Password Database you can'...


6

In my config : $config['default_host'] = 'imaps://domain.tld'; // TCP port used for IMAP connections $config['default_port'] = 993; I know that it is not the doc, but it is working. Think about certificate : it should be compliant with your domain.tld


6

once i have problem with one of my mail servers i use these in dovecot.conf : auth_verbose=yes auth_debug=yes auth_debug_passwords=yes mail_debug=yes verbose_ssl=yes auth_verbose_passwords=plain then use: tail -f /var/log/mail.log you will see everything that is going on behind the scene..


6

You can also do the following on the command-line without configuration files: # doveadm -Dv \ -o imapc_host=<SOURCE_HOST> \ -o imapc_user=<SOURCE_USERNAME> \ -o imapc_password=<SOURCE_PASSWORD> \ -o imapc_features=rfc822.size \ -o imapc_ssl=starttls \ -o mail_fsync=never \ backup -R -u <DESTINATION_MAILBOX> imapc: I ...


6

I'm not an expert in either dovecot or postfix, but it looks like you have postfix configured to use Maildir style mailboxes, but you're telling dovecot to use mbox style mailboxes. Take a look at the postfix docs for the home_mailbox config option, or the dovecot docs for the mail_location config option to figure out which one you need to change (and ...


6

There are separate configuration files for PHP when called via Apache and when called via the CLI. For example, in Debian (at least), these are in /etc/php5/apache2/php.ini and /etc/php5/cli/php.ini, respectively. The fact that you manually declared imagick.so in apache2/php.ini might not mean anything - most distributions have some other way of managing ...


6

Honest advice, use normal user accounts and let your Linux system authenticate the users. This is easy to manage and very secure. I don't want to say that other systems are insecure but I trust my Linux system when it comes to storing and authenticating passwords. I use these commands to create users manually. This way they can do no harm on my system. ...


5

I'd seriously push for fighting the political battle to allow IMAP access to the Exchange system. IMAP and POP can be enabled on a per-account basis. Since this is a workflow item with a defined business application, there's definitely a purpose... I'd be more suspicious of a the long-term viability of a workaround solution or anything that adds more ...


5

The Plugin that @hostemaster mentioned is not really needed if you don't deal with thousand of users. Just create an easy script like this: #!/bin/bash # DOVEADM="/usr/local/dovecot/bin/doveadm"; $DOVEADM expunge -A mailbox Trash savedbefore 90d $DOVEADM expunge -A mailbox Junk savedbefore 60d And run it daily as an cronjob. This will remove all ...


5

But here's more, is there a way to set up a filter, so that only machine to whom the reply was intended will see it and none of the others will or go directly to whom it was intended. And also have the ability for those machines to forward emails to each other via some internal lan accounts. No.


5

By definition of the SMTP RFC all this server does is relay mail. SMTP does not save copies to a sent folder. That's all dependent on the client mail readers.


5

Try iptables -A INPUT -p tcp -m multiport --dports 25,110,143,993,995 -j REJECT This should block all incoming attempts to TCP ports 25 (SMTP), IMAP (plaintext and secure; 143 and 993) and POP (ditto, 110 and 995). If postfix listens on an MUA port (possibly 587) you'll need to add that to the list as well. That said, John Auld's suggestion above of ...


5

The Dovecot wiki seems to have an error, or maybe the name of the ssl_username_from_cert setting has changed. On my Ubuntu host with Dovecot 2.2.9, in /etc/dovecot/conf.d/10-auth.conf, I have: # Take the username from client's SSL certificate, using # X509_NAME_get_text_by_NID() which returns the subject's DN's # CommonName. #auth_ssl_username_from_cert =...


Only top voted, non community-wiki answers of a minimum length are eligible