[Dovecot] Can't connect to auth server
I'm trying to phase out procmail and move to dovecot-sieve instead. It ain't proving easy. I'll describe my setup:
Centos 5.2 box with dovecot 1.1.4 and dovecot-sieve 1.1.6 from ATrpms.
A single user account is used to store all our email (the account is called maildb).
Getmail is being used to fetch the email from various ISP mailboxes. I want to deliver mail to different folders in maildb's Maildir/ depending on who the email is addressed to (the procmail recipes currently do that).
Getmail destination section looks like this: [destination] type = MDA_external path = /usr/libexec/dovecot/deliver arguments = ("-d", "maildb") allow_root_commands = true
When I run getmail I get this error in dovecot.log: deliver(maildb): May 04 22:15:26 Error: Can't connect to auth server at /var/run/dovecot/auth-master: No such file or directory
It's true that I don't have a file called auth-master. I guess I should have but until I started this dovecot-sieve work it was never a problem. I have no idea what that file should look like. As I installed from binary RPMs I would have thought one would have come with the install.
Can anyone help?
Regards, Phill
I'm trying to phase out procmail and move to dovecot-sieve instead. It ain't proving easy. I'll describe my setup:
Centos 5.2 box with dovecot 1.1.4 and dovecot-sieve 1.1.6 from ATrpms.
A single user account is used to store all our email (the account is called maildb).
Getmail is being used to fetch the email from various ISP mailboxes. I want to deliver mail to different folders in maildb's Maildir/ depending on who the email is addressed to (the procmail recipes currently do that).
Getmail destination section looks like this: [destination] type = MDA_external path = /usr/libexec/dovecot/deliver arguments = ("-d", "maildb") allow_root_commands = true
When I run getmail I get this error in dovecot.log: deliver(maildb): May 04 22:15:26 Error: Can't connect to auth server at /var/run/dovecot/auth-master: No such file or directory
It's true that I don't have a file called auth-master. I guess I should have but until I started this dovecot-sieve work it was never a problem. I have no idea what that file should look like. As I installed from binary RPMs I would have thought one would have come with the install.
Can anyone help?
Anyone? I'm pretty stuck if I can't resolve this :(
Regards, Phill
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, 9 May 2009, Phill Edwards wrote:
- Getmail destination section looks like this: [destination] type = MDA_external path = /usr/libexec/dovecot/deliver arguments = ("-d", "maildb")
It's true that I don't have a file called auth-master. I guess I should have but until I started this dovecot-sieve work it was never a
See http://wiki.dovecot.org/LDA
"-d <username>: Destination username. If given, the user information is looked up from dovecot-auth."
You need Dovecot running and providing the auth socket, see http://wiki.dovecot.org/MainConfig?highlight=auth-master
Bye,
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iQEVAwUBSgfA1HWSIuGy1ktrAQKIPQf/WGlbMobhIPkOAfDybhZSJMFCu18eiHa1 0aDoXqfhXK7B/KuEpMnBcK80pgIYguABh8+BEaSCTEs7Nx4fKjT2oL74dAdnv0Kr okzs27fxJQE88oy46JloZIYUWnjnk/MMNMrJZgXc1OcpOMpG3jWWLKjaNVNnDSgM WZC/yQzYKXKhYqICrFjnr6b5JNJQSXo6JvlhoC/E38YNRQhW/AUqRIgdyOhqqXpq wezN1F4hm4XTnmORRUYm/GwTKY2AHa50eqN6wNUb6vokeH0bT6MYXmBcpG6lqgCS 650msVUTqWXyNx7c2kpuO+8m38VvjQy70/CaZhWTMkWHi+WAFuvqQQ== =5NXu -----END PGP SIGNATURE-----
- Getmail destination section looks like this: [destination] type = MDA_external path = /usr/libexec/dovecot/deliver arguments = ("-d", "maildb")
It's true that I don't have a file called auth-master. I guess I should have but until I started this dovecot-sieve work it was never a
See http://wiki.dovecot.org/LDA
"-d <username>: Destination username. If given, the user information is looked up from dovecot-auth."
You need Dovecot running and providing the auth socket, see http://wiki.dovecot.org/MainConfig?highlight=auth-master
Thanks for your reply, but I still don't understand how to fix my issue. I had a look at the wiki page and it says: "auth_socket_path = /var/run/dovecot/auth-master UNIX socket path to master authentication server to find users."
The file auth-master doesn't exist anywhere on my system, and the wiki doesn't tell me how to create it or what its contents should look like. So I still don't understand how I make dovecot provide the auth socket.
Regards, Phill
Thanks for your reply, but I still don't understand how to fix my issue. I had a look at the wiki page and it says: "auth_socket_path = /var/run/dovecot/auth-master UNIX socket path to master authentication server to find users."
The file auth-master doesn't exist anywhere on my system, and the wiki doesn't tell me how to create it or what its contents should look like. So I still don't understand how I make dovecot provide the auth socket.
Actually, I think I may have solved my own problem here. In order for auth-master to be created the following lines have to be uncommented in dovecot.conf:
#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 #mode = 0600 # Default user/group is the one who started dovecot-auth (root) #user = #group = #} #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 #} #}
needs to look like this:
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 mode = 0600 # Default user/group is the one who started dovecot-auth (root) user = group = } #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 deliberately hadn't uncommented them before because the top of dovecot.conf says this:
# '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace "
# Default values are shown for each setting, it's not required to uncomment # any of the lines.
Clearly that last part is incorrect because in this case it WAS necessary to uncomment the lines in the socket listen stanza in order for it to work.
I hope this helps someone else.
Regards, Phill
On Tue, 2009-05-12 at 23:31 +1000, Phill Edwards wrote:
I deliberately hadn't uncommented them before because the top of dovecot.conf says this:
# '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace "
# Default values are shown for each setting, it's not required to uncomment # any of the lines.
Clearly that last part is incorrect because in this case it WAS necessary to uncomment the lines in the socket listen stanza in order for it to work.
Yeah. Changed the text: http://hg.dovecot.org/dovecot-1.1/rev/a5c3f5ea8732
I had such problem, and I didn't find any information about "auth-master" socket My mail.log was pretty clear, but there were several repeating "...Error: Can't connect to auth server at /var/run/dovecot/auth-master: No such file or directory" in the /etc/dovecot/dovecot.log. It was lasting several days while I was searching about this issue. Finally I found one old entry in dovecot.log :"Error: auth(default): mysql: Missing value in connect string: host", I rechecked my /etc/dovecot/dovecot-sql.conf and there was one extra space in connection string. "connect = host =127.0.0.1" instead of "connect = host=127.0.0.1" Now mail-server works perfectly and "auth-master" was created automatically in the /var/run/dovecot directory. =)
Phill Edwards wrote:
I'm trying to phase out procmail and move to dovecot-sieve instead. It ain't proving easy. I'll describe my setup:
Centos 5.2 box with dovecot 1.1.4 and dovecot-sieve 1.1.6 from ATrpms.
A single user account is used to store all our email (the account is called maildb).
Getmail is being used to fetch the email from various ISP mailboxes. I want to deliver mail to different folders in maildb's Maildir/ depending on who the email is addressed to (the procmail recipes currently do that).
Getmail destination section looks like this: [destination] type = MDA_external path = /usr/libexec/dovecot/deliver arguments = ("-d", "maildb") allow_root_commands = true
When I run getmail I get this error in dovecot.log: deliver(maildb): May 04 22:15:26 Error: Can't connect to auth server at /var/run/dovecot/auth-master: No such file or directory
It's true that I don't have a file called auth-master. I guess I should have but until I started this dovecot-sieve work it was never a problem. I have no idea what that file should look like. As I installed from binary RPMs I would have thought one would have come with the install.
Can anyone help?
Regards, Phill
-- View this message in context: http://old.nabble.com/Can%27t-connect-to-auth-server-tp23367592p30913694.htm... Sent from the Dovecot mailing list archive at Nabble.com.
participants (4)
-
KokTis
-
Phill Edwards
-
Steffen Kaiser
-
Timo Sirainen