[Dovecot] Port variable in LMTP userdb lookups?
Hi all, I'm currently changing some systems to use the redirector service, which means that to get local deliveries going I need to get lmtp set up so it can be redirected as well. This is working fine, however we have a number of different ports running on our servers depending on which brand a customer is using. When the time comes to do the user look up, we use (port, user, domain) to do a unique database lookup which works fine for everything (proxied pop, imap, lmtp straight pop, imap) but not straight lmtp - perhaps because it doesn't have a 2-stage login process unlike the pop/imap protocols. Looking at the SQL query we are issuing, the %a port variable is set to 0 even though the connection is coming in from TCP. Is there a way to change this? We are running dovecot 2.0.12 however looking through the changelogs I can't see this would be fixed in the newest version. Thanks, Mark
Re: [Dovecot] imap proxy for Gmail
On 10/19/2011 9:31 PM, Jumping Mouse wrote: I have a situation were I want to be able to give teachers access to their Google apps for education email through Squirrelmail. The network that they are on blocks gmail.I am able to get Squirrelmail to communicate with Gmail via imap. I am looking at getting persistant imap connections to improve the user experience. I have looked at IMAPPROXY but this application is not compatible with the gmail imaps (ssl-encrypted imap over port 993). I recall reading somewhere that Dovecot has a built in imapproxy that could be used for this. Can someone please point me to documentation or other information on how I might achieve the above stated goal? You are probably thinking of the imapc backend for Dovecot. Not sure if it gives the persistent connections you are looking for or not since I've never used it.
Re: [Dovecot] too many open files and v1.2
Hi Timo thanks for your reply. I understand you're basically saying upgrade to v2 but maybe this could be of interest for you. After we lowered the login_max_processes_count again the problem reappeared so I'm not sure whether that doesn't indicate a different problem. Regards, Michael On Tuesday 18 October 2011 15:57:23 Timo Sirainen wrote: On Thu, 2011-10-06 at 12:42 +0100, Michael Moritz wrote: Hi I've found an older thread http://www.dovecot.org/list/dovecot/2010-March/047886.html which mentions that this is a bug in version 1. I'm on Debian squeeze (1:1.2.15-7) and got errors like these recently Oct 5 11:29:29 mail dovecot: dovecot: pipe() failed: Too many open files Oct 5 11:29:32 mail dovecot: dovecot: pipe() failed: Too many open files Oct 5 11:29:32 mail dovecot: dovecot: Temporary failure in creating login processes, slowing down for now These errors come from the dovecot master process. Each child process uses up a few fds for pipes. As a work around I've increased login_max_processes_count from 256 to 512 and it seems to have helped (as I suspected stale opened files). That only makes it easier to reach, since now there can be more child processes eating up more fds. My colleague thinks it's hitting the kernel open file limit ulimit -n (currently at 1024) but I don't see how that could happen if the number of process is nowhere near that. I don't remember how many fds each process takes in v1.x, probably between 1 and 3. So if you for a while had hundreds of imap or pop3 processes, you could run into that limit. v2.x doesn't use as many fds.
[Dovecot] can not receive email upgrading from ubuntu 11.4 to 11.10
Dear all, I have the following error when i am sending an email to my email server postfix + dovecot. #5.3.0 x-unix; /usr/lib/dovecot/deliver: invalid option -- 'n' Usage: dovecot-lda [-c config file] [-a address] [-d username] [-p path] [-f envelope sender] [-m mailbox] [-e] [-k] #SMTP# The problem occurred after i upgraded my server from ubuntu 11.4 to 11.10. i kindly ask you if you can help me thank you in advance for your kind attention. -- View this message in context: http://old.nabble.com/can-not-receive-email-upgrading-from-ubuntu-11.4-to-11.10-tp32681149p32681149.html Sent from the Dovecot mailing list archive at Nabble.com.
[Dovecot] Expire plugin not executing for sieve plugin?
Running dovecot 1.2.12 on ubuntu 10.10. Here is the problem: I have
mysql backend for expire. I am using the dovecot-postfix package which
creates /etc/dovecot/conf.d/01-mail-stack-delivery.conf which looks like
this:
# Some general options
protocols = imap imaps managesieve
disable_plaintext_auth = no
ssl = yes
ssl_cert_file = /etc/ssl/certs/ssl-mail.pem
ssl_key_file = /etc/ssl/private/ssl-mail.key
ssl_cipher_list =
ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM
mail_location = maildir:~/Maildir
auth_username_chars =
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@
# IMAP configuration
protocol imap {
mail_max_userip_connections = 10
imap_client_workarounds = outlook-idle delay-newmail
mail_plugins = expire
}
# LDA configuration
protocol lda {
postmaster_address = postmaster
mail_plugins = sieve expire
quota_full_tempfail = yes
deliver_log_format = msgid=%m: %$
rejection_reason = Your message to %t was automatically
rejected:%n%r
}
# Plugins configuration
plugin {
sieve=~/.dovecot.sieve
sieve_dir=~/sieve
# If the user has no personal active script (i.e. if the file
# indicated in sieve= does not exist), use this one:
sieve_global_path = /var/lib/dovecot/sieve/default.sieve
}
The sieve is:
require fileinto;
require imap4flags;
if header :contains X-Spam-Flag YES {
setflag \\Seen;
fileinto SPAM;
stop;
}
Originally, this did not have the setflag or stop - I added them hoping
to fix the problem, but no luck. The problem is this: when spam
assassin has flagged a message as spam, the sieve runs and the message
is in fact filed into the SPAM folder, but no expire entry is added to
the database. If I move such a message from the SPAM folder to the
Inbox and then back to SPAM, voila, I *do* get the entry created. Here
is the mysql table before and after I did the move/move:
mysql select * from expires;
+--+---+--+
| username | mailbox | expire_stamp |
+--+---+--+
| dswartz | Deleted Items | 1319720163 |
| dswartz | Sent | 1319120165 |
| denise | Trash | 1319139920 |
| samantha | Trash | 1319136146 |
| denise | Sent | 1319655872 |
| danielle | Sent | 1319192230 |
| samantha | Sent | 1319268855 |
| dswartz | Trash | 1319725884 |
| samantha | SPAM | 1321504531 |
+--+---+--+
9 rows in set (0.00 sec)
mysql select * from expires;
+--+---+--+
| username | mailbox | expire_stamp |
+--+---+--+
| dswartz | Deleted Items | 1319720163 |
| dswartz | Sent | 1319120165 |
| denise | Trash | 1319139920 |
| samantha | Trash | 1319136146 |
| denise | Sent | 1319655872 |
| danielle | Sent | 1319192230 |
| samantha | Sent | 1319268855 |
| dswartz | Trash | 1319725884 |
| samantha | SPAM | 1321504531 |
| dswartz | SPAM | 1321714666 |
+--+---+--+
10 rows in set (0.00 sec)
It's almost like the fileinto stuff is not running the plugin code at
all, or am I totally on drugs? If I can't get a fix for this, I at
least now can think of a hack to fix it. e.g. every night, run a
script that adds a now timestamp for everyone's SPAM folder to trick
the periodic expire tool code into checking that folder, but obviously
I'd rather have a real fix :) If this is just 'how it works', is it
better in 2.0?
Re: [Dovecot] can not receive email upgrading from ubuntu 11.4 to 11.10
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Nikolaos
On 19/10/11 10:54, Nikolaos Petronikolos wrote:
#5.3.0 x-unix; /usr/lib/dovecot/deliver: invalid option -- 'n'
Usage: dovecot-lda [-c config file] [-a address] [-d
username] [-p path] [-f envelope sender] [-m mailbox] [-e]
[-k] #SMTP#
The problem occurred after i upgraded my server from ubuntu 11.4 to
11.10.
11.10 upgrades dovecot from 1.2.x to 2.0.x; as a result the -n flag is
no longer accepted by dovecot-lda; You can fix this by removing the -n
flag from the postfix configuration;
sudo postconf -e mailbox_command = /usr/lib/dovecot/deliver -c
/etc/dovecot/conf.d/01-mail-stack-delivery.conf -m \\${EXTENSION}\
This is a bug in the Ubuntu packaging; it would be great if you could
raise a bug in Ubuntu as well (I'll probably work on a stable release
update for this one):
https://bugs.launchpad.net/ubuntu/+source/dovecot/+filebug
Cheers
James
- --
James Page
Ubuntu Core Developer
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCAAGBQJOoD7QAAoJEL/srsug59jDHUcQAJfL4jU+wNMK22kYOCKsTRkr
eHBUZ0IQ1Yv2IscqRpW8WaAAg6r7tufMoodI/MY1N4w2FHfwJAAMiCfU/8gTyfHD
/FxwVH5Phk+InEYDEc7YMCdgTwh936yiOKkQjz65aGO3kUIg42QSNHOBq30L4VV7
b4cnwIlwALjA/8U2HrZr6XHBwZ9YoyxoLY3m6R9MCcCNpEEUUh1tH4i2FuZYFHmJ
CokbWA2XHJCli4yZ5d+1JM3D0u/Sg2w1bczT3kkIE8HhGgOpCidbYRrOKTrHrFOl
0GKvHQkxvosqfLt8rdrjJlhNlGjPdRdu22vsMy43rS80knN70ltyTH3K5kiW2q6/
skqQjwgZ4y41sqsKq8WnuYuSfeH2TSrglzSXQ2W8vOOAJArqwLLst5E3+Ift3Pig
0BhNlSyQyWhdE4TE9zbGnUPK8GLXLU82LcTegpz6d3mxAcCs7+SnNiYPnRrNxTA1
YqqBdcAfCMeS5B3w5ZQRQDvKOIZOPqyIeZPX2g5bOM4ngDnZoJfIOf6RkBX/DPVw
UCgU1AjWWHtrcTby7h4s3xX+EaPUpEFj8eg30GW5exsSMM6ASuU+HtQpO3rEobDB
uG9AvHahf6Y9fAuSdxjcHQg6xyWDEYNaW3MNZauaD92IvaTP2uTyQvopk3ahyOWK
7lpTV7qZ776fNbK5OYrX
=W3fO
-END PGP SIGNATURE-
[Dovecot] Expire plugin not executing for sieve plugin?
Running dovecot 1.2.12 on ubuntu 10.10. Here is the problem: I have
mysql backend for expire. I am using the dovecot-postfix package which
creates /etc/dovecot/conf.d/01-mail-stack-delivery.conf which looks like
this:
# Some general options
protocols = imap imaps managesieve
disable_plaintext_auth = no
ssl = yes
ssl_cert_file = /etc/ssl/certs/ssl-mail.pem
ssl_key_file = /etc/ssl/private/ssl-mail.key
ssl_cipher_list =
ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM
mail_location = maildir:~/Maildir
auth_username_chars =
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@
# IMAP configuration
protocol imap {
mail_max_userip_connections = 10
imap_client_workarounds = outlook-idle delay-newmail
mail_plugins = expire
}
# LDA configuration
protocol lda {
postmaster_address = postmaster
mail_plugins = sieve expire
quota_full_tempfail = yes
deliver_log_format = msgid=%m: %$
rejection_reason = Your message to %t was automatically
rejected:%n%r
}
# Plugins configuration
plugin {
sieve=~/.dovecot.sieve
sieve_dir=~/sieve
# If the user has no personal active script (i.e. if the file
# indicated in sieve= does not exist), use this one:
sieve_global_path = /var/lib/dovecot/sieve/default.sieve
}
The sieve is:
require fileinto;
require imap4flags;
if header :contains X-Spam-Flag YES {
setflag \\Seen;
fileinto SPAM;
stop;
}
Originally, this did not have the setflag or stop - I added them hoping
to fix the problem, but no luck. The problem is this: when spam
assassin has flagged a message as spam, the sieve runs and the message
is in fact filed into the SPAM folder, but no expire entry is added to
the database. If I move such a message from the SPAM folder to the
Inbox and then back to SPAM, voila, I *do* get the entry created. Here
is the mysql table before and after I did the move/move:
mysql select * from expires;
+--+---+--+
| username | mailbox | expire_stamp |
+--+---+--+
| dswartz | Deleted Items | 1319720163 |
| dswartz | Sent | 1319120165 |
| denise | Trash | 1319139920 |
| samantha | Trash | 1319136146 |
| denise | Sent | 1319655872 |
| danielle | Sent | 1319192230 |
| samantha | Sent | 1319268855 |
| dswartz | Trash | 1319725884 |
| samantha | SPAM | 1321504531 |
+--+---+--+
9 rows in set (0.00 sec)
mysql select * from expires;
+--+---+--+
| username | mailbox | expire_stamp |
+--+---+--+
| dswartz | Deleted Items | 1319720163 |
| dswartz | Sent | 1319120165 |
| denise | Trash | 1319139920 |
| samantha | Trash | 1319136146 |
| denise | Sent | 1319655872 |
| danielle | Sent | 1319192230 |
| samantha | Sent | 1319268855 |
| dswartz | Trash | 1319725884 |
| samantha | SPAM | 1321504531 |
| dswartz | SPAM | 1321714666 |
+--+---+--+
10 rows in set (0.00 sec)
It's almost like the fileinto stuff is not running the plugin code at
all, or am I totally on drugs? If I can't get a fix for this, I at
least now can think of a hack to fix it. e.g. every night, run a
script that adds a now timestamp for everyone's SPAM folder to trick
the periodic expire tool code into checking that folder, but obviously
I'd rather have a real fix :) If this is just 'how it works', is it
better in 2.0?
Re: [Dovecot] Auth Worker failures
On 18 October 2011 10:37, Timo Sirainen t...@iki.fi wrote:
On Wed, 2011-10-12 at 10:24 -0400, Simon Brereton wrote:
Of all the accounts on the box, it's only mine that throws this up.
Since its LIP is localhost, it could really only be for webmail - but
I don't always leave the webmail open, so I'm curious to know how this
gets there and what it is.
Any suggestions? I find it difficult to believe I have an IMAP
process in a script somewhere (especially with my user account - the
postmaster account, I could believe, but not with my personal one)..
You could enable auth_debug_passwords=yes and see what password it
tries.
The first day I did this, I forgot to restart dovecot. Doh. This
morning I had:
Oct 20 06:25:14 mail dovecot: auth(default): client in:
AUTH#0112#011PLAIN#011service=imap#011secured#011lip=127.0.0.1#011rip=127.0.0.1#011lport=143#011rport=50683#011resp=--alsoremoved--==
Oct 20 06:25:14 mail dovecot: auth-worker(default):
sql(si...@example.net,127.0.0.1): query: SELECT EmailAdd AS user,
Password AS password, concat('/var/spool/mail/virtual/',MailDirLoc)
as userdb_home, 999 as userdb_uid, 115 as userdb_gid FROM MailAccounts
WHERE Username='si...@example.net' AND active = '1';
Oct 20 06:25:14 mail dovecot: auth-worker(default):
sql(si...@example.net,127.0.0.1): Password mismatch
Oct 20 06:25:14 mail dovecot: auth-worker(default):
md5_verify(si...@example.net): Not a valid MD5-CRYPT or PLAIN-MD5
password
Oct 20 06:25:14 mail dovecot: auth-worker(default):
smd5_verify(si...@example.net): SMD5 password too short
Oct 20 06:25:14 mail dovecot: auth-worker(default):
ssha_verify(si...@example.net): SSHA password too short
Oct 20 06:25:14 mail dovecot: auth-worker(default):
ssha256_verify(si...@example.net): SSHA256 password too short
Oct 20 06:25:14 mail dovecot: auth-worker(default): Invalid OTP data in passdb
Oct 20 06:25:14 mail dovecot: auth-worker(default): Invalid OTP data in passdb
Oct 20 06:25:14 mail dovecot: auth-worker(default):
sql(si...@example.net,127.0.0.1): CRYPT() != 'RaNDomsTRinG'
Oct 20 06:25:16 mail dovecot: auth(default): client out:
FAIL#0112#011user=si...@example.net
Oct 20 06:25:26 mail dovecot: auth(default): client in:
AUTH#0113#011PLAIN#011service=imap#011secured#011lip=127.0.0.1#011rip=127.0.0.1#011lport=143#011rport=50683#011resp=--truncated--
Oct 20 06:25:26 mail dovecot: auth-worker(default):
sql(si...@example.net,127.0.0.1): query: SELECT EmailAdd AS user,
Password AS password, concat('/var/spool/mail/virtual/',MailDirLoc)
as userdb_home, 999 as userdb_uid, 115 as userdb_gid FROM MailAccounts
WHERE Username='si...@example.net' AND active = '1';
Oct 20 06:25:26 mail dovecot: auth-worker(default):
sql(si...@example.net,127.0.0.1): Password mismatch
Oct 20 06:25:26 mail dovecot: auth-worker(default):
md5_verify(si...@example.net): Not a valid MD5-CRYPT or PLAIN-MD5
password
Oct 20 06:25:26 mail dovecot: auth-worker(default):
smd5_verify(si...@example.net): SMD5 password too short
Oct 20 06:25:26 mail dovecot: auth-worker(default):
ssha_verify(si...@example.net): SSHA password too short
Oct 20 06:25:26 mail dovecot: auth-worker(default):
ssha256_verify(si...@example.net): SSHA256 password too short
Oct 20 06:25:26 mail dovecot: auth-worker(default): Invalid OTP data in passdb
Oct 20 06:25:26 mail dovecot: auth-worker(default): Invalid OTP data in passdb
Oct 20 06:25:26 mail dovecot: auth-worker(default):
sql(si...@example.net,127.0.0.1): CRYPT() != 'RaNDomsTRinG'
Oct 20 06:25:28 mail dovecot: auth(default): client out:
FAIL#0113#011user=si...@example.net
Oct 20 06:25:43 mail dovecot: auth(default): client in:
AUTH#0114#011PLAIN#011service=imap#011secured#011lip=127.0.0.1#011rip=127.0.0.1#011lport=143#011rport=50683#011resp=--alsoremoved--==
Oct 20 06:25:43 mail dovecot: auth-worker(default):
sql(si...@example.net,127.0.0.1): query: SELECT EmailAdd AS user,
Password AS password, concat('/var/spool/mail/virtual/',MailDirLoc)
as userdb_home, 999 as userdb_uid, 115 as userdb_gid FROM MailAccounts
WHERE Username='si...@example.net' AND active = '1';
Oct 20 06:25:43 mail dovecot: auth-worker(default):
sql(si...@example.net,127.0.0.1): Password mismatch
Oct 20 06:25:43 mail dovecot: auth-worker(default):
md5_verify(si...@example.net): Not a valid MD5-CRYPT or PLAIN-MD5
password
Oct 20 06:25:43 mail dovecot: auth-worker(default):
smd5_verify(si...@example.net): SMD5 password too short
Oct 20 06:25:43 mail dovecot: auth-worker(default):
ssha_verify(si...@example.net): SSHA password too short
Oct 20 06:25:43 mail dovecot: auth-worker(default):
ssha256_verify(si...@example.net): SSHA256 password too short
Oct 20 06:25:43 mail dovecot: auth-worker(default): Invalid OTP data in passdb
Oct 20 06:25:43 mail dovecot: auth-worker(default): Invalid OTP data in passdb
Oct 20 06:25:43 mail dovecot: auth-worker(default):
sql(si...@example.net,127.0.0.1): CRYPT() != 'RaNDomsTRinG'
Oct 20 06:25:45 mail dovecot: auth(default): client out:
FAIL#0114#011user=si...@example.net
[Dovecot] Don't Know Where Emails Are Or What's Happening
Hi;
I'm new to Dovecot and Postfix.
I'm trying to enable these with MySQL support and postfixadmin. I've
got all those services up and running (finally!); however, I can't
figure out if the emails are being received and/or stored. I'm pretty
sure Postfix is receiving them because I dealt with certain errors
and they're now gone. Here's some data:
Dovecot ver.
0.91
[root@example postfix]# /sbin/service dovecot
-n
doveconf: Warning: NOTE: You can get a new clean config file
with: doveconf -n dovecot-new.conf
doveconf: Warning:
Obsolete setting in /usr/local/etc/dovecot/dovecot.conf:5:
imap_client_workarounds=outlook-idle is no longer necessary
doveconf:
Warning: Obsolete setting in /usr/local/etc/dovecot/dovecot.conf:17:
add auth_ prefix to all settings inside auth {} and remove the auth
{} section completely
doveconf: Warning: Obsolete setting in
/usr/local/etc/dovecot/dovecot.conf:21: passdb sql {} has been
replaced by passdb { driver=sql }
doveconf: Warning: Obsolete
setting in /usr/local/etc/dovecot/dovecot.conf:24: userdb sql {} has
been replaced by userdb { driver=sql }
doveconf: Warning: Obsolete
setting in /usr/local/etc/dovecot/dovecot.conf:27: userdb prefetch {}
has been replaced by userdb { driver=prefetch }
doveconf: Warning:
Obsolete setting in /usr/local/etc/dovecot/dovecot.conf:29: auth_user
has been replaced by service auth { user }
Usage:
/etc/init.d/dovecot {start|stop|reload|restart|force-reload}
tail
/var/log/maillog
Oct 20 10:13:59 example postfix/smtpd[28141]:
warning: problem talking to service rewrite: Success
Oct 20
10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30178 exit status 1
Oct
20 10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30179 exit status 1
Oct
20 10:13:59 example postfix/smtpd[28458]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example
postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30180 exit status 1
Oct
20 10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30181 exit status 1
Oct
20 10:13:59 example postfix/smtpd[28483]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example
postfix/smtpd[28460]: warning: problem talking to service rewrite:
Success
Oct 20 10:13:59 example postfix/master[4000]: warning:
process /usr/libexec/postfix/trivial-rewrite pid 30182 exit status 1
Oct 20 10:13:59 example postfix/smtpd[28455]: warning: problem
talking to service rewrite: Success
Oct 20 10:13:59 example
postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30183 exit status 1
Oct
20 10:13:59 example postfix/smtpd[28484]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example
postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30184 exit status 1
Oct
20 10:13:59 example postfix/smtpd[29917]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example
postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30185 exit status 1
Oct
20 10:13:59 example postfix/smtpd[29953]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example
postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30186 exit status 1
Oct
20 10:13:59 example postfix/smtpd[28485]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example
postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30187 exit status 1
Oct
20 10:14:15 example postfix/smtpd[30152]: connect from
unknown[66.248.165.32]
Oct 20 10:14:15 example
postfix/smtpd[30152]: lost connection after EHLO from
unknown[66.248.165.32]
Oct 20 10:14:15 example
postfix/smtpd[30152]: disconnect from unknown[66.248.165.32]
I
also get this in there:
Oct 20 10:13:15 example
postfix/smtpd[30152]: warning: dict_nis_init: NIS domain name not set
- NIS lookups disabled
Oct 20 10:13:15 example
postfix/smtpd[30152]: cannot load Certificate Authority data:
disabling TLS support
Oct 20 10:13:15 example
postfix/smtpd[30152]: warning: TLS library problem:
30152:error:02001002:system library:fopen:No such file or
directory:bss_file.c:122:fopen('/etc/pki/tls/c
erts/cert.pem','r'):
Oct
20 10:13:15 example postfix/smtpd[30152]: warning: TLS library
problem: 30152:error:2006D080:BIO routines:BIO_new_file:no such
file:bss_file.c:125:
Oct 20 10:13:15 example postfix/smtpd[30152]:
warning: TLS library problem: 30152:error:0B084002:x509 certificate
routines:X509_load_cert_crl_file:system lib:by_file.c:279:
Oct 20
10:13:15 example postfix/smtpd[30152]: connect from
unknown[66.248.165.32]
Oct 20 10:13:15 example
postfix/smtpd[30152]: lost connection after EHLO from
unknown[66.248.165.32]
Oct 20 10:13:15 example
postfix/smtpd[30152]: disconnect from unknown[66.248.165.32]
Oct
20 10:13:57 example postfix/proxymap[28446]: warning: mysql query
failed: You have
[Dovecot] Email filters
Can someone tell me how I can configure Dovecot to use message filters on incoming email? When I now activate my mail account on my mobile phone and Thunderbird (or any other mail client with message filters) is not online, I get a huge pile of email in my INBOX that I have to go thru, while 90% is not that interesting to read as they belong to Spam messages, newsletters etc. Thanks in advance Jos Chrispijn
Re: [Dovecot] Don't Know Where Emails Are Or What's Happening
On 20 October 2011 18:28, Jack Fredrikson jackfredrik...@yahoo.com wrote:
Hi;
I'm new to Dovecot and Postfix.
I'm trying to enable these with MySQL support and postfixadmin. I've
got all those services up and running (finally!); however, I can't
figure out if the emails are being received and/or stored. I'm pretty
sure Postfix is receiving them because I dealt with certain errors
and they're now gone. Here's some data:
Dovecot ver.
0.91
First, get a newer version of Dovecot. You don't say what OS you're
working on, but I'm pretty sure it will support a newer version.
[root@example postfix]# /sbin/service dovecot
-n
doveconf: Warning: NOTE: You can get a new clean config file
with: doveconf -n dovecot-new.conf
doveconf: Warning:
Obsolete setting in /usr/local/etc/dovecot/dovecot.conf:5:
imap_client_workarounds=outlook-idle is no longer necessary
doveconf:
Warning: Obsolete setting in /usr/local/etc/dovecot/dovecot.conf:17:
add auth_ prefix to all settings inside auth {} and remove the auth
{} section completely
doveconf: Warning: Obsolete setting in
/usr/local/etc/dovecot/dovecot.conf:21: passdb sql {} has been
replaced by passdb { driver=sql }
doveconf: Warning: Obsolete
setting in /usr/local/etc/dovecot/dovecot.conf:24: userdb sql {} has
been replaced by userdb { driver=sql }
doveconf: Warning: Obsolete
setting in /usr/local/etc/dovecot/dovecot.conf:27: userdb prefetch {}
has been replaced by userdb { driver=prefetch }
doveconf: Warning:
Obsolete setting in /usr/local/etc/dovecot/dovecot.conf:29: auth_user
has been replaced by service auth { user }
Usage:
/etc/init.d/dovecot {start|stop|reload|restart|force-reload}
tail
/var/log/maillog
Oct 20 10:13:59 example postfix/smtpd[28141]:
warning: problem talking to service rewrite: Success
Oct 20
10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30178 exit status 1
Oct
20 10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30179 exit status 1
Oct
20 10:13:59 example postfix/smtpd[28458]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example
postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30180 exit status 1
Oct
20 10:13:59 example postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30181 exit status 1
Oct
20 10:13:59 example postfix/smtpd[28483]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example
postfix/smtpd[28460]: warning: problem talking to service rewrite:
Success
Oct 20 10:13:59 example postfix/master[4000]: warning:
process /usr/libexec/postfix/trivial-rewrite pid 30182 exit status 1
Oct 20 10:13:59 example postfix/smtpd[28455]: warning: problem
talking to service rewrite: Success
Oct 20 10:13:59 example
postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30183 exit status 1
Oct
20 10:13:59 example postfix/smtpd[28484]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example
postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30184 exit status 1
Oct
20 10:13:59 example postfix/smtpd[29917]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example
postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30185 exit status 1
Oct
20 10:13:59 example postfix/smtpd[29953]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example
postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30186 exit status 1
Oct
20 10:13:59 example postfix/smtpd[28485]: warning: problem talking to
service rewrite: Success
Oct 20 10:13:59 example
postfix/master[4000]: warning: process
/usr/libexec/postfix/trivial-rewrite pid 30187 exit status 1
Oct
20 10:14:15 example postfix/smtpd[30152]: connect from
unknown[66.248.165.32]
Oct 20 10:14:15 example
postfix/smtpd[30152]: lost connection after EHLO from
unknown[66.248.165.32]
Oct 20 10:14:15 example
postfix/smtpd[30152]: disconnect from unknown[66.248.165.32]
I
also get this in there:
Were you testing from 66.248.165.32? You still have too many errors
from postfix and you need to sort out your MTA (Mail Transport) before
you worry about the MDA (Mail Delivery).
Oct 20 10:13:15 example
postfix/smtpd[30152]: warning: dict_nis_init: NIS domain name not set
- NIS lookups disabled
Oct 20 10:13:15 example
postfix/smtpd[30152]: cannot load Certificate Authority data:
disabling TLS support
Oct 20 10:13:15 example
postfix/smtpd[30152]: warning: TLS library problem:
30152:error:02001002:system library:fopen:No such file or
directory:bss_file.c:122:fopen('/etc/pki/tls/c
erts/cert.pem','r'):
Oct
20 10:13:15 example postfix/smtpd[30152]: warning: TLS library
problem: 30152:error:2006D080:BIO routines:BIO_new_file:no such
file:bss_file.c:125:
Oct 20 10:13:15
Re: [Dovecot] Email filters
Hi Jos, On 10/21/2011 12:49 AM, Jos Chrispijn wrote: Can someone tell me how I can configure Dovecot to use message filters on incoming email? When I now activate my mail account on my mobile phone and Thunderbird (or any other mail client with message filters) is not online, I get a huge pile of email in my INBOX that I have to go thru, while 90% is not that interesting to read as they belong to Spam messages, newsletters etc. http://wiki2.dovecot.org/Pigeonhole Regards, Stephan.
Re: [Dovecot] Don't Know Where Emails Are Or What's Happening
From: Simon Brereton simon.brere...@buongiorno.com To: dovecot@dovecot.org dovecot@dovecot.org Sent: Thursday, October 20, 2011 7:07 PM Subject: Re: [Dovecot] Don't Know Where Emails Are Or What's Happening First, I'm subscribing to postfix as per your recc and I upgraded my dovecot. What the heck was I doing with such an old version?! lol. My OS is CentOS. At a minimum your daemons are running - congratulations! That's always a good start and I remember when I was setting up the sense of achievement that brought. Uhuh! But for now you need to get postfix working (their list is great). Perhaps if you give more details on your system I can point you to a better howto. And maybe more information on what you're trying to achieve? Virtual domain? Virtual domains? Multiple users? Local users? All these have an impact on what the solution is. I have clients with their various domains hosted on my server to whom I need to serve email. There will only be me on a slice of one machine interfacing with dovecot/postfix. I have integrated/am integrating Amavis, ClamAV, Spamassassin, PostfixAdmin and SquirrelMail. Thanks, Jack
