Re: [Dovecot] Connection refused with auth-master after upgrading to Dovecot 1.0 rc 28

2007-04-10 Thread Jason Warner
Timo,

I really want to thank you for taking the time to look at this. I'm a newbie
with a little Linux experience, so I'm in charge of the mail server. It
makes it nice to deal with someone who really knows what they are doing.

 -Original Message-
 From: Timo Sirainen [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, April 10, 2007 8:46 AM
 To: Jason Warner
 Cc: 'Jason Warner'; dovecot@dovecot.org
 Subject: Re: [Dovecot] Connection refused with auth-master after
 upgradingto Dovecot 1.0 rc 28
 
 On Mon, 2007-04-09 at 08:45 -0600, Jason Warner wrote:
 Apr  2 12:56:32 mail deliver([EMAIL PROTECTED]):
 net_connect(/var/run/dovecot/auth-master) failed: Connection
refused
   
Delete this file. Restart Dovecot. Does it get recreated?
   
When I delete the file and restart Dovecot it is recreated.
  
   Does this then happen every time when running deliver? Does netstat
   show that dovecot-auth is listening in that path?
 
  When running deliver from the command line, I do not get the error. The
  error only appears when deliver is run from Postfix.
 
 And you gave deliver -d parameter when running from command line? If it
 works from there but not from Postfix, then the problem has something to
 do with how deliver is started. Did you try running as the same user as
 what Postfix runs it with?

When I run deliver with the -d parameter, it does deliver a message to the
intended user. I've tried just about everything I know how to do with the
Dovecot LDA in the master.cf config file for Postfix. Here is the line as it
stands now:

# Dovecot LDA
dovecot   unix  -   n   n   -   -   pipe
  flags=DRhu user=vmail:mail argv=/usr/libexec/dovecot/deliver -d
${recipient}

That line worked just fine up until the update. After some looking, we were
running 1.0 rc 15 so this step up to 28 was quite a move. Fortunately, the
mail server is working with our virtual setup, but our vacation message
setup relied on the sieve portions of the Dovecot LDA. Thanks again for
taking a look at this.

 
  Netstat shows the following when running.
 
  unix  2  [ ACC ] STREAM LISTENING 255526 private/dovecot
  unix  2  [ ACC ] STREAM LISTENING 1176428
  /var/run/dovecot/auth-master
 
 So it should be accepting connections.
 
  It appears that the auth-master is running. How would I check to make
 sure
  that it is listening and responding properly to requests?
 
 There really isn't any other way than to run deliver. auth_debug=yes
 will also log something whenever deliver is run and dovecot-auth sees
 something.




Re: [Dovecot] Connection refused with auth-master after upgrading to Dovecot 1.0 rc 28

2007-04-10 Thread Timo Sirainen
On Tue, 2007-04-10 at 09:11 -0600, Jason Warner wrote:

 When I run deliver with the -d parameter, it does deliver a message to
 the
 intended user. I've tried just about everything I know how to do with
 the
 Dovecot LDA in the master.cf config file for Postfix. Here is the line
 as it
 stands now:
 
 # Dovecot LDA
 dovecot   unix  -   n   n   -   -   pipe
   flags=DRhu user=vmail:mail argv=/usr/libexec/dovecot/deliver -d
 ${recipient} 

So what about running deliver as vmail?

sudo su vmail -s /usr/libexec/dovecot/deliver -d [EMAIL PROTECTED]

What OS do you use? Do you use SELinux or anything like that?



signature.asc
Description: This is a digitally signed message part


Re: [Dovecot] Connection refused with auth-master after upgrading to Dovecot 1.0 rc 28

2007-04-06 Thread Timo Sirainen

On 3.4.2007, at 17.38, Jason Warner wrote:


 Fedora pushed out an update to Dovecot 1.0 rc 28 today. After
 upgrading, mail isn't delivered to local recipients. My log file is
 full of error messages similar to the following:

 Apr  2 12:56:32 mail deliver([EMAIL PROTECTED]):
 net_connect(/var/run/dovecot/auth-master) failed: Connection  
refused


Delete this file. Restart Dovecot. Does it get recreated?


When I delete the file and restart Dovecot it is recreated.


Does this then happen every time when running deliver? Does netstat  
show that dovecot-auth is listening in that path?


Connection refused means either that no-one is listening on the other  
side, or that its listen queue got full.


PGP.sig
Description: This is a digitally signed message part


Re: [Dovecot] Connection refused with auth-master after upgrading to Dovecot 1.0 rc 28

2007-04-03 Thread Jason Warner

Timo,

Thanks for your time.

On 4/2/07, Timo Sirainen [EMAIL PROTECTED] wrote:

On Mon, 2007-04-02 at 13:10 -0600, Jason Warner wrote:
 Fedora pushed out an update to Dovecot 1.0 rc 28 today. After
 upgrading, mail isn't delivered to local recipients. My log file is
 full of error messages similar to the following:

 Apr  2 12:56:32 mail deliver([EMAIL PROTECTED]):
 net_connect(/var/run/dovecot/auth-master) failed: Connection refused

Delete this file. Restart Dovecot. Does it get recreated?


When I delete the file and restart Dovecot it is recreated.



 I'm including some snippets from my dovecot.conf file that pertain to
 the auth-master file:

dovecot -n shows what Dovecot really uses. It might show something
different than what you thought you had.





Here is the output from dovecot -n:

[EMAIL PROTECTED] dovecot]# /usr/local/sbin/dovecot -c /etc/dovecot.conf -n
# /etc/dovecot.conf
protocols: imap imaps pop3 pop3s
ssl_cert_file: /etc/pki/dovecot/certs/pop3.pem
ssl_key_file: /etc/pki/dovecot/private/pop3.pem
login_dir: /usr/local/var/run/dovecot/login
login_executable(default): /usr/local/libexec/dovecot/imap-login
login_executable(imap): /usr/local/libexec/dovecot/imap-login
login_executable(pop3): /usr/local/libexec/dovecot/pop3-login
default_mail_env: maildir:/home/vmail/mail/%n
mail_location: maildir:/home/vmail/mail/%n
mail_executable(default): /usr/local/libexec/dovecot/imap
mail_executable(imap): /usr/local/libexec/dovecot/imap
mail_executable(pop3): /usr/local/libexec/dovecot/pop3
mail_plugin_dir(default): /usr/local/lib/dovecot/imap
mail_plugin_dir(imap): /usr/local/lib/dovecot/imap
mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3
pop3_uidl_format(default):
pop3_uidl_format(imap):
pop3_uidl_format(pop3): %08Xu%08Xv
auth default:
 passdb:
   driver: ldap
   args: /etc/dovecot-ldap.conf
 userdb:
   driver: static
   args: uid=502 gid=502 home=/home/vmail/mail/%n
mail=maildir:/home/vmail/mail/%n/
 socket:
   type: listen
   client:
   master:
 path: /var/run/dovecot/auth-master
 mode: 384
 user: vmail
 group: mail


Some other information that I've learned might be helpful in helping
to troubleshoot this problem:

1. I'm using Postfix and delivering mail to virtual users.
2. The problem presents itself when using the Dovecot LDA. If I go
back to my old virtual settings (not using the Dovecot LDA) then mail
is delivered again.
3. The Dovecot LDA is added with this line in my master.cf for Postfix:
# Dovecot LDA
dovecot   unix  -   n   n   -   -   pipe
 flags=DRhu user=vmail:mail argv=/usr/libexec/dovecot/deliver -d ${recipient}


[Dovecot] Connection refused with auth-master after upgrading to Dovecot 1.0 rc 28

2007-04-02 Thread Jason Warner

Fedora pushed out an update to Dovecot 1.0 rc 28 today. After
upgrading, mail isn't delivered to local recipients. My log file is
full of error messages similar to the following:

Apr  2 12:56:32 mail deliver([EMAIL PROTECTED]):
net_connect(/var/run/dovecot/auth-master) failed: Connection refused

I'm including some snippets from my dovecot.conf file that pertain to
the auth-master file:

protocol lda {
 # Address to use when sending rejection mails.
 postmaster_address = [EMAIL PROTECTED]

 mail = maildir:/home/vmail/mail/%n

 # Hostname to use in various parts of sent mails, eg. in Message-Id.
 # Default is the system's real hostname.
 #hostname =

 # Support for dynamically loadable plugins. mail_plugins is a space separated
 # list of plugins to load.
 #mail_plugins =
 #mail_plugin_dir = /usr/lib/dovecot/lda
 mail_plugins = cmusieve
 mail_plugin_dir = /usr/lib/dovecot/lda

 # Binary to use for sending mails.
 #sendmail_path = /usr/lib/sendmail

 # UNIX socket path to master authentication server to find users.
 auth_socket_path = /var/run/dovecot/auth-master
 #auth_socket_path = /home/vmail/mail/auth-master
}

 socket listen {
   master {
 # Master socket provides access to userdb information. It's typically
 # used to give Dovecot's local delivery agent access to userdb so it
 # can find mailbox locations.
 path = /var/run/dovecot/auth-master
 #path = /home/vmail/mail/auth-master
 mode = 0600
 # Default user/group is the one who started dovecot-auth (root)
 user = vmail
 group = mail
   }
   #client {
 # The client socket is generally safe to export to everyone. Typical use
 # is to export it to your SMTP server so it can do SMTP AUTH lookups
 # using it.
 #path = /var/run/dovecot/auth-client
 #mode = 0660
   #}
 }

I have been beating my head against this trying to change the
permissions to 0777, changing the directory of the socket, changing
the auth user, and just about anything else I can find in any thread
that relates to this error. Any help would be greatly appreciated.