[Dovecot] Temporary Failure that's Permanent!
Hi;
I continue to be plagued with this error:
Oct 25 10:49:18 myserver postfix/pipe[3712]: 0423257901AB: to=,
relay=dovecot, delay=109318, delays=109318/0.14/0/0.1, dsn=4.3.0,
status=deferred (temporary failure
It's been a week that I've been working day and night to get this fixed.
I forgot to add this information:
[root]# doveconf -n
auth_mechanisms = plain login
first_valid_gid = 12
first_valid_uid = 86
mail_location = maildir:/var/vmail/%d/%u
passdb {
args = /usr/local/etc/dovecot/sql.conf
driver = sql
}
plugin {
quota = maildir:storage=10240:messages=1000
trash = /usr/local/etc/dovecot/trash.conf
}
protocols = imap pop3
service auth {
unix_listener auth-userdb {
group = postfix
mode = 0660
user = postfix
}
user = root
}
ssl_cert =
Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem
From: Jack Fredrikson
To: Jack Fredrikson ; Giles Coochey
Cc: "simon.brere...@buongiorno.com" ; Dovecot
Mailing List
Sent: Tuesday, October 25, 2011 11:01 AM
Subject: Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem
I have solved at least another part of the problem that was causing the setuig
error. I changed my postfix/master.cf file from this:
dovecot unix - n n - - pipe
flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/dovecot-lda -f
${sender} -d ${recipient}
to this:
dovecot unix - n n - - pipe
flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/dovecot-lda -f
${sender} ${recipient}
taking out the d flag. Now dovecot doesn't complain. *However*, I've *still*
got this devil plaguing me:
Oct 25 10:49:18 myserver postfix/pipe[3712]: 0423257901AB: to=,
relay=dovecot, delay=109318, delays=109318/0.14/0/0.1, dsn=4.3.0,
status=deferred (temporary failure
Ya know, I know I'm not the sharpest tool in the shed when it comes to
programming, but I have *never* worked *so hard* on an installation as this one
with so little success! It took me a day to install qmail the first time
around. I've been a week on this!! Please help me figure this mess out. For the
record, I did rebuild dovecot but that obviously didn't help. I did change the
posfix files to pump out a bunch of debugging info:
adding a -D flag to every smptd service in master.cf
This in main.cf:
debug_peer_level = 3
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
xxgdb $daemon_directory/$process_name $process_id & sleep 5
debug_peer_list = 127.0.0.1
#debug_peer_list =
and it doesn't give me any output like it did the first time, so I assume
(perhaps incorrectly) there are no errors.
TIA,
Jack
Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem
From: Giles Coochey To: Jack Fredrikson Cc: "simon.brere...@buongiorno.com" ; Dovecot Mailing List Sent: Tuesday, October 25, 2011 10:02 AM Subject: Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem I just discovered this: [root@myserver postfix]# ls -al /usr/libexec/dovecot/ total 8 drwxr-xr-x 2 root root 4096 Oct 22 08:59 . drwxr-xr-x 9 root root 4096 Oct 23 08:36 .. lrwxrwxrwx 1 root root 34 Oct 22 08:59 deliver -> /usr/local/libexec/dovecot/deliver [root@myserver postfix]# ls -al /usr/local/libexec/dovecot/deliver* lrwxrwxrwx 1 root root 11 Oct 20 17:14 /usr/local/libexec/dovecot/deliver -> dovecot-lda Huh? So I made a softlink directly to /usr/local/libexec/dovecot/dovecot-lda (which is where it resides) But I'm still getting the same errors: Oct 25 07:58:47 lda(f...@bar.com): Fatal: setgid(12(mail) from userdb lookup) failed with euid=512(vmail), gid=512(vmail), egid=512(vmail): Operation not permitted (This binary should probably be called with process group set to 12(mail) instead of 512(vmail)) I need to change the gid because it's wrong. Now, rebuilding dovecot isn't going to do that because we don't set such things in the flags to rebuild. So where in tarnation do we??? TIA, Jack > On my Centos 5.x: > > [root@gate ~]# rpm -qf /usr/libexec/dovecot/deliver > dovecot-2.0.15-1.0.cf.rhel5 > [root@gate ~]# rpm -qf /usr/libexec/dovecot/dovecot-lda > dovecot-2.0.15-1.0.cf.rhel5 > > What dovecot do you have? 2.0.15 I built mine the old way: ./configure --with-mysql make make install So how would I rebuild just this one file? From where does it get its data? I need to change the first_valid_gid. TIA, Jack
Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem
From: Giles Coochey To: Jack Fredrikson Cc: "simon.brere...@buongiorno.com" ; Dovecot Mailing List Sent: Tuesday, October 25, 2011 10:02 AM Subject: Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem > On my Centos 5.x: > > [root@gate ~]# rpm -qf /usr/libexec/dovecot/deliver > dovecot-2.0.15-1.0.cf.rhel5 > [root@gate ~]# rpm -qf /usr/libexec/dovecot/dovecot-lda > dovecot-2.0.15-1.0.cf.rhel5 > > What dovecot do you have? 2.0.15 I built mine the old way: ./configure --with-mysql make make install So how would I rebuild just this one file? From where does it get its data? I need to change the first_valid_gid. TIA, Jack
Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem
From: Simon Brereton To: Dovecot Mailing List Sent: Tuesday, October 25, 2011 9:53 AM Subject: Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem > I can't speak to CentOS, but I'm not sure you need to be "creating" > any files - especially not in libexec. Are you sure your dovecot > installation isn't hosed somehow? Of course I'm not sure and rebuilding dovecot is what I'll do if all else fails. When I discovered the problem in my dovecot logs, I searched for the offending GID and discovered it in /usr/local/libexec/dovecot/deliver which, of course, is a binary. How did it get there? Certainly not when I did my ./configure make make install dance with dovecot's src distro. How did it get there?? How do I change it??` TIA, Jack
Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem
From: Jack Fredrikson To: "simon.brere...@buongiorno.com" ; Dovecot Mailing List Sent: Tuesday, October 25, 2011 6:47 AM Subject: Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem Or, conversely, how do I create this file: /usr/local/libexec/dovecot/deliver The problem is the first_valid_uid and first_valid_gid need to be reset. What file is called to create "deliver"? Please help. TIA, Jack
Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem
From: Simon Brereton To: Dovecot Mailing List Sent: Tuesday, October 25, 2011 12:46 AM Subject: Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem I think I've found the problem. How do I create this file? /usr/local/libexec/dovecot/deliver-ldaTIA, Jack
Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem
From: Jerry To: dovecot@dovecot.org Sent: Monday, October 24, 2011 7:27 PM Subject: Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem >> sendmail_path = /usr/sbin/sendmail.postfix > Are you sure about that "sendmail" path? It certainly isn't like that > on my machine. Well, I changed it to just "sendmail" (since I had that file, too) but with the same result. I remember creating that file earlier but I don't remember where and searching around my system I can't xargs grep it. What do you recommend? TIA, Jack
Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem
From: Tom Hendrikx
To: dovecot@dovecot.org
Sent: Monday, October 24, 2011 6:00 PM
Subject: Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem
> Adding dovecot to the postfix group would be considered a security issue
> by many. Don't so this unless you actually think it wil help you (it won't).
Thanks. I took it out.
> Please see http://dev.mysql.com/doc/refman/5.5/en/connecting.html,
> especially the part that starts with "On Unix, MySQL programs treat the
> host name localhost specially,"
>
> Then show proof that this command works:
>
> mysql -udovecot -pxxx -h 127.0.0.1 postfix
My bad. I had the wrong p/w in sql.conf :-}
So now I'm connected to the database as dovecot, but I'm still getting these
dad-blamed errors:
BC81A57901AD: to=, relay=dovecot, delay=25695,
delays=25695/0.02/0/0.28, dsn=4.3.0, status=deferred (temporary failure)
# 2.0.15: /usr/local/etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-028stab094.3 x86_64 CentOS release 5.7 (Final) vzfs
auth_mechanisms = plain login
mail_location = maildir:/var/vmail/%d/%u
passdb {
args = /usr/local/etc/dovecot/sql.conf
driver = sql
}
plugin {
quota = maildir:storage=10240:messages=1000
trash = /usr/local/etc/dovecot/trash.conf
}
protocols = imap pop3
service auth {
unix_listener auth-userdb {
group = postfix
mode = 0660
user = postfix
}
user = root
}
ssl_cert =
Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem
From: Simon Brereton To: dovecot@dovecot.org Sent: Monday, October 24, 2011 5:04 PM Subject: Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem > Who owns /var/vmail? ls -al /var/vmail/ total 8 drwxrwx--- 2 vmail mail 4096 Oct 19 18:45 . drwxr-xr-x 26 root root 4096 Oct 23 08:35 .. /usr/sbin/usermod -a -G mail,postfix dovecot And I'm still getting the same error: dovecot: auth-worker: Error: mysql(localhost): Connect failed to database (postfix): Access denied for user 'dovecot'@'localhost' (using password: YES) TIA, Jack
Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem
From: Tom Hendrikx
To: dovecot@dovecot.org
Sent: Monday, October 24, 2011 3:24 PM
Subject: Re: [Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem
First up, thanks for the links, Simon, but they didn't help :( I still need to
chmod 666 /usr/local/var/run/dovecot/auth-userdb
and I'm still getting the same error:
Oct 24 13:40:57 myserver dovecot: auth-worker: Error: mysql(localhost): Connect
failed to database (postfix): Access denied for user 'dovecot'@'localhost'
(using password: YES) - waiting for 5 seconds before retry
> The "(using password: YES)" part of the error indicates that your
> connection to the server was established successfully. However, it seems
> that user 'dovecot' has no access to database 'postfix', which you did
> not test on the command line either.
>
> What happens on the commandline when you enter (after logging in:
> use postfix; show tables;
I can log in *just fine* as dovecot and show tables, etc.
# 2.0.15: /usr/local/etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-028stab094.3 x86_64 CentOS release 5.7 (Final) vzfs
auth_mechanisms = plain login
mail_location = maildir:/var/vmail/%d/%u
passdb {
args = /usr/local/etc/dovecot/sql.conf
driver = sql
}
plugin {
quota = maildir:storage=10240:messages=1000
trash = /usr/local/etc/dovecot/trash.conf
}
protocols = imap pop3
service auth {
unix_listener auth-userdb {
mode = 0660
}
user = root
}
ssl_cert =
[Dovecot] Marathon Day 6 of First Install: MySQL Connection Problem
Hi; This is my 6th day installing my first Postfix/Dovecot installation. The Postfix mailing list indicates I've got the MTA under control so now I'm seeking your help with the MDA. I get these errors with legitimate email addresses: Oct 24 11:47:38 myserver dovecot: auth-worker: Error: mysql(localhost): Connect failed to database (postfix): Access denied for user 'dovecot'@'localhost' (using password: YES) - waiting for 25 seconds before retry Now I've logged in myself: mysql -u dovecot -p Enter password: xxx and succeeded. What am I doing wrong? I've noticed that every time I restart dovecot I get this error in the dovecot-deliver.log: Oct 24 11:31:11 lda: Error: userdb lookup: connect(/usr/local/var/run/dovecot/auth-userdb) failed: Permission denied (euid=512(vmail) egid=512(vmail) missing +r perm: /usr/local/var/run/dovecot/auth-userdb, dir owned by 0:0 mode=0755) Oct 24 11:31:11 lda: Fatal: Internal error occurred. Refer to server log for more information. Every time I go to chmod 666 on that file, restarting dovecot wipes those permissions. How fix? Even when I fix that, I still get the "temporary failure". Please advise. TIA, Jack
Re: [Dovecot] Temporary Failures
This is *only* a PS to my last response (e.g., please be sure to read last response). Rob0 stated I should be using dovecot-lda. After running in circles it appears that dovecot-lda is incorporated into dovecot proper any more and I've duly incorporated it into my dovecot.conf file. Jack
Re: [Dovecot] Temporary Failures
From: Simon Brereton
To: Jack Fredrikson
Cc: "dovecot@dovecot.org"
Sent: Sunday, October 23, 2011 2:41 PM
Subject: Re: [Dovecot] Temporary Failures
First up, apologies for double-posting. I actually posted this last one
yesterday and the other one this afternoon.
Someone suggested I use the dovecot-new.conf file. If you've ever opened that
up, everything's commented out and it only publishes the defaults anyway!
Basically worthless if you're doing anything sophisticated, which includes
pretty much anything :)
> What version of dovecot are you currently using?
2.0.15
> Can you post this file?
> /usr/local/etc/dovecot/dovecot.conf
mail_location = maildir:/var/vmail/%d/%u
maildir_copy_with_hardlinks = yes
protocol imap {
mail_plugins = quota imap_quota
# imap_client_workarounds = outlook-idle delay-newmail
}
protocol pop3 {
mail_plugins = quota
pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
}
protocol lda {
postmaster_address = postmas...@creative.vi
mail_plugins = quota
log_path = /var/log/dovecot-deliver.log
info_log_path = /var/log/dovecot-deliver.log
}
auth default {
mechanisms = plain login
passdb pam {
}
userdb passwd {
}
user = root
socket listen {
client {
path = /var/spool/postfix/private/auth
mode = 0660
user = postfix
group = postfix
}
}
}
dict {
}
plugin {
quota = maildir:storage=10240:messages=1000
# acl = vfile:/usr/local/etc/dovecot/acls
trash = /usr/local/etc/dovecot/trash.conf
}
protocols = imap pop3
disable_plaintext_auth = yes
ssl = yes
#ssl_disable = no
ssl_cert =
[Dovecot] Temporary Failures
Hi;
I keep getting errors like this one:
Oct 22 16:51:08 example postfix/pipe[12021]: C2F705790169:
to=, relay=dovecot, delay=2.1, delays=2/0.01/0/0.08,
dsn=4.3.0, status=deferred (temporary failure. Command output: 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:19: passdb pam {} has been
replaced by passdb { driver=pam } doveconf: Warning: Obsolete setting in
/usr/local/etc/dovecot/dovecot.conf:21: userdb passwd {} has been replaced by
userdb { driver=passwd } doveconf: Warning: Obsolete setting in
/usr/local/etc/dovecot/dovecot.conf:23: auth_user has
been replaced by service auth { user } doveconf:
Why don't they get delivered? Also, I've tried to follow the advice in the
warnings and it never works. I've tried the doveconf -n > dovcot-new.conf
command and the same conf file I've been using pops up. Can someone post some
code that reflects how the new conf file should look?
TIA,
Jack
[Dovecot] First Installation, Problems...
Hi;
[root@example jack]# /usr/local/sbin/dovecot --version
2.0.15
[root@example jack]# /usr/local/bin/doveconf -n
# 2.0.15: /usr/local/etc/dovecot/dovecot.conf
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 }
# OS: Linux 2.6.18-028stab094.3 x86_64 CentOS release 5.4 (Final) vzfs
auth_mechanisms = plain login
mail_location = maildir:/var/vmail/%d/%u
passdb {
args = /usr/local/etc/dovecot/sql.conf
driver = sql
}
plugin {
quota = maildir:storage=10240:messages=1000
trash = /usr/local/etc/dovecot/trash.conf
}
service auth {
unix_listener /var/run/dovecot/auth-master {
group = mail
mode = 0660
user = vmail
}
unix_listener /var/spool/postfix/private/auth {
group = mail
mode = 0660
user = postfix
}
user = nobody
}
ssl = no
userdb {
args = /usr/local/etc/dovecot/sql.conf
driver = sql
}
userdb {
driver = prefetch
}
protocol imap {
imap_client_workarounds = delay-newmail
mail_plugins = quota imap_quota
}
protocol pop3 {
mail_plugins = quota
pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
}
protocol lda {
info_log_path = /var/log/dovecot-deliver.log
log_path = /var/log/dovecot-deliver.log
mail_plugins = quota
postmaster_address = postmas...@creative.vi
}
It appears that I have postfix at least partially working:
postfix/pipe[5280]: 9FDE0579012F: to=, relay=spamfilter, delay=6,
delays=3/0.01/0/3, dsn=2.0.0, status=sent (delivered via spamfilter service)
I don't know where it ended up :-} There's nothing in /var/vmail, the dovecot
destination. This is true even before I set the postfix content_filter to
spamassassin (when it said "delivered to Maildir" or some such). Please advise.
TIA,
Jack
Re: [Dovecot] Don't Know Where Emails Are Or What's Happening
Wait a minute! PostfixAdmin has no problems with MySQL. They have a setup page that verifies the MySQL connection among other things, and everything checks out perfectly well. At any rate, Simon, am now communicating with the Postfix list as well ;) Thanks, Jack
Re: [Dovecot] Don't Know Where Emails Are Or What's Happening
From: Simon Brereton To: "dovecot@dovecot.org" Sent: Friday, October 21, 2011 10:12 AM Subject: Re: [Dovecot] Don't Know Where Emails Are Or What's Happening > Well, unless the link I sent you helped you with the the table locking > problem, ask over there for help on making sure that postfix is > accepting and delivering mail. Or accepting at least. Didn't help :( > Did you plan on having postfix or dovecot do the delivery (using dovecot-lda)? postfix as MTA, dovecot as MDA. Am I missing something here? > Okay - fairly common setup. I don't use postfix-admin, but if that's > what created your mysql tables that could also be a starting point to > look for the table lock errors. Ok. Thanks, Jack
Re: [Dovecot] Don't Know Where Emails Are Or What's Happening
From: Simon Brereton To: "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
[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
