James Knott wrote:

James Knott wrote:

...

I must be dense. I've been trying to get Dovecot 2.0 going, but I can't even get it to connect. To keep things simple, I'm just using plain IMAP port 143. I'VE tried both passwd& shadow authentication. With passwd, I get a password error, but nothing happens with shadow. Further on this, ps auxw|grep dovecot shows:

jknott@acserver:~> ps auxw|grep dovecot root 12191 0.0 0.0 10752 864 ? Ss 11:34 0:00 /usr/sbin/dovecot dovecot 12192 0.0 0.0 8636 904 ? S 11:34 0:00 dovecot/anvil root 12193 0.0 0.0 8760 1044 ? S 11:34 0:00 dovecot/log jknott 12349 0.0 0.0 7792 832 pts/11 S+ 11:40 0:00 grep dovecot

This is less than the docs show. Also, telnet to port 143 gets:

Connected to localhost. Escape character is '^]'. * OK Waiting for authentication process to respond.. * BYE Disconnected for inactivity. Connection closed by foreign host.

So, I can't even get authorized to connect.

Start with enabling auth debugging in dovecot, then try again and check the log file (/var/log/mail). -- Per Jessen, Zürich (16.9°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

James Knott wrote:

I've given up on 2.0 and installed 1.2 instead. While better, it still has a way to go. I find Dovecot to be extremely frustrating to set up. It seems to be a matter of trial & error following "suggestions" in the very poor documentation.

I also thought the dovecot docus were a little difficult and lacking, but once I got the general dovecot concept, it's not at all that bad. The dovecot wikis are very good for instance. I've got two dovecot 2.0 instances running, the second one as a regular mailserver (for hosted customers). I'm using mysql for database, TLS, sieve and quotas. -- Per Jessen, Zürich (10.6°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

James Knott wrote:

Per Jessen wrote:

...

I also thought the dovecot docus were a little difficult and lacking, but once I got the general dovecot concept, it's not at all that bad. The dovecot wikis are very good for instance. I've got two dovecot 2.0 instances running, the second one as a regular mailserver (for hosted customers). I'm using mysql for database, TLS, sieve and quotas.

How do you get multiple users working? I can only get one. A 2nd can't even log in.

I didn't do anything in particular :-) All of my users are virtual, so userid, homedir, quota and password are all stored in mysql. -- Per Jessen, Zürich (14.2°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

James Knott wrote:

Per Jessen wrote:

...

...

...

How do you get multiple users working? I can only get one. A 2nd can't even log in. I didn't do anything in particular:-)

All of my users are virtual, so userid, homedir, quota and password are all stored in mysql.

I have even tried manually logging with with telnet local host 143. Below is an example of the one ID that works "jknott" and one that doesn't "mailtest". I can log into the server, via ssh or su - from my own account to mailtest and other IDs.

Sep 22 09:31:44 acserver dovecot: imap-login: Login: user=<mailtest>, method=PLAIN, rip=::1, lip=::1, mpid=23787, secured Sep 22 09:31:44 acserver dovecot: imap(mailtest): Error: user mailtest: Initialization failed: mail_location not set and autodetection failed: Mail storage auto detection failed with home=/home/mailtest

My guess - you haven't set mail_location, so auto-detection fails because mailtest has never received any mail. I would update dovecot.conf and set mail_location. -- Per Jessen, Zürich (19.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 09/22/2011 09:28 AM, James Knott wrote:

James Knott wrote:

...

I have even tried manually logging with with telnet local host 143. Below is an example of the one ID that works "jknott" and one that doesn't "mailtest". I can log into the server, via ssh or su - from my own account to mailtest and other IDs.

I've found the fix. I had to add "mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u" to dovecot.conf.

Now to get fetchmail going.

AARGH, should have caught it, I think the default for 2.0 is 'mbox:~/Mail...' What I do with fetchmail is set up the user ~/.fetchmailrc as: poll mail.3111skyline.com protocol IMAP : user david with password ********** ssl sslfingerprint "A2:6B:1A:F3:F6:2D:58:75:F4:33:B8:91:AB:C1:09:27" To get the correct sslfingerprint, just run: fetchmail -cv from the command line after generating the dovecot certs. fetchmail will show you the fingerprint it is expecting. Just use that for the fingerprint in ~/.fetchmailrc -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Per Jessen wrote:

...

AARGH, should have caught it, I think the default for 2.0 is

...

'mbox:~/Mail...'

No, in dovecot 2.0 mail_location is empty by default, and dovecot will attempt to locate your mails automagically.

The curious thing is that one account worked, but no others. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Per Jessen wrote:

...

The curious thing is that one account worked, but no others. Did the one have some mail, the others none?

The others couldn't connect at all. I even tried using telnet localhost 143, but that failed too for other accounts. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2011-09-23 at 07:41 +0200, Per Jessen wrote:

No, in dovecot 2.0 mail_location is empty by default, and dovecot will attempt to locate your mails automagically.

Dovecot 1 too, but it failed in my case. Also I understand all users must have the same storage type. I don't know if version 2 is different. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk58buwACgkQtTMYHG2NR9UGzACggBQufXWwbF4VO2/uENVenUr+ m/0An3tIttdraAvB0QtV53GNb9ycql4L =y8Io -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hello, On Thu, 22 Sep 2011, David C. Rankin wrote:

poll mail.3111skyline.com protocol IMAP : user david with password ********** ssl sslfingerprint "A2:6B:1A:F3:F6:2D:58:75:F4:33:B8:91:AB:C1:09:27"

No need for that. fetchmailrc is quite free form. I usually have: ## [comments] poll SERVER1 with proto POP3 ## comments user "USER1" there with password "PASS1" is dh here options ... # some disabled option ... ## comments user "USER2" there with password "PASS2" is dh here options ... ## comments user "USER3" there with password "PASS3" is user3 here options ... ## [comments] poll SERVER2 with proto IMAP ## comments user "USER2" there with password "PASS4" is dh here options ... ## comments user "USER4" there with password "PASS5" is user4 here options ... ## comments skip SERVER3 ... the generously sprinkled with comments about what e-mails are in what account, e.g. what lands in the box of USER1 on SERVER1 etc. And the syntax can be even more verbose or terse. HTH, -dnh -- A funny symbol that I can't read has just been input. Continue, and I'll forget that it ever happened. -- a TeX message -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2011-09-20 at 15:15 -0400, James Knott wrote:

Carlos E. R. wrote:

...

View this thread: http://forums.opensuse.org/showthread.php?t=447542

That's how I did it.

All I see in there is the suggestion to use an IMAP server, not anything about configuring dovecot.

Post number 20 :-) - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk55DzgACgkQtTMYHG2NR9VthACfQN4M01VTTZwttu3M3epSU4M7 z5IAoIM+fGX5JkZ98vvGPfR20mjXrPqo =XqPD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2011-09-21 at 07:55 +0200, Per Jessen wrote:

...

Post number 20 :-)

You should have posted the direct link :-)

Yep, I forgot.

Not a bad howto, although very short. I guess the openSUSE default setup will do the rest.

Absolutely, I only wrote about what I had to change from the defaults. - -- Cheers, Carlos E. R. (from 11.4 x86_64 "Celadon" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEARECAAYFAk552AUACgkQtTMYHG2NR9WhDQCbBS5XGF+udmZ78jwB+49d9/ns SIoAn0dU1Cvq6EbCwntLRWBplX7CrrHG =l4e4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Per Jessen wrote:

James Knott wrote:

...

Carlos E. R. wrote:

...

View this thread: http://forums.opensuse.org/showthread.php?t=447542

That's how I did it. All I see in there is the suggestion to use an IMAP server, not anything about configuring dovecot. I thought I'd go with Dovecot, because others here recommended it, but from what I can see, it's a real disaster. V2 does not appear to be functional at all. Completely disagree, it's been working very well for me for a little over a year now. I'm sure we can help you getting your setup to work too, but lets see some config files etc. otherwise it's like groping in the dark.

I've now got it so that I can use Dovecot 2.0 to access one account. However, I cannot connect with a 2nd. All the server settings are the same, other than user ID. As this server will be used over a dozen employees, this is a bit of an issue. Here's the current dovecot.conf: ## Dovecot configuration file # If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration # "doveconf -n" command gives a clean output of the changed settings. Use it # instead of copy&pasting files when posting to the Dovecot mailing list. # '#' 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 # those. These are exceptions to this though: No sections (e.g. namespace {}) # or plugin settings are added by default, they're listed only as examples. # Paths are also just examples with the real defaults being based on configure # options. The paths listed here are for configure --prefix=/usr # --sysconfdir=/etc --localstatedir=/var # Protocols we want to be serving. ##protocols = imap imaps pop3 lmtp # A comma separated list of IPs or hosts where to listen in for connections. # "*" listens in all IPv4 interfaces, "::" listens in all IPv6 interfaces. # If you want to specify non-default ports or anything more complex, # edit conf.d/master.conf. #listen = *, :: # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Greeting message for clients. #login_greeting = Dovecot ready. # Space separated list of trusted network ranges. Connections from these # IPs are allowed to override their IP addresses and ports (for logging and # for authentication checks). disable_plaintext_auth is also ignored for # these networks. Typically you'd specify your IMAP proxy servers here. #login_trusted_networks = # Sepace separated list of login access check sockets (e.g. tcpwrap) #login_access_sockets = # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Should all processes be killed when Dovecot master process shuts down. # Setting this to "no" means that Dovecot can be upgraded without # forcing existing client connections to close (although that could also be # a problem if the upgrade is e.g. because of a security fix). #shutdown_clients = yes # If non-zero, run mail commands via this many connections to doveadm server, # instead of running them directly in the same process. #doveadm_worker_count = 0 # UNIX socket or host:port used for connecting to doveadm server #doveadm_socket_path = doveadm-server # Space separated list of environment variables that are preserved on Dovecot # startup and passed down to all of its child processes. You can also give # key=value pairs to always set specific settings. #import_environment = TZ ## ## Dictionary server settings ## # Dictionary can be used to store key=value lists. This is used by several # plugins. The dictionary can be accessed either directly or though a # dictionary server. The following dict block maps dictionary names to URIs # when the server is used. These can then be referenced using URIs in format # "proxy::<name>". dict { #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext } # Most of the actual configuration gets included below. The filenames are # first sorted by their ASCII value and parsed in that order. The 00-prefixes # in filenames are intended to make it easier to understand the ordering. !include conf.d/*.conf # A config file can also tried to be included without giving an error if # it's not found: !include_try local.conf ######################### ssl = yes # Preferred permissions: root:root 0444 ssl_cert =

James Knott wrote:

Per Jessen wrote:

...

James Knott wrote:

...

Carlos E. R. wrote:

...

View this thread: http://forums.opensuse.org/showthread.php?t=447542

That's how I did it. All I see in there is the suggestion to use an IMAP server, not anything about configuring dovecot. I thought I'd go with Dovecot, because others here recommended it, but from what I can see, it's a real disaster. V2 does not appear to be functional at all. Completely disagree, it's been working very well for me for a little over a year now. I'm sure we can help you getting your setup to work too, but lets see some config files etc. otherwise it's like groping in the dark.

I've now got it so that I can use Dovecot 2.0 to access one account. However, I cannot connect with a 2nd. All the server settings are the same, other than user ID. As this server will be used over a dozen employees, this is a bit of an issue.

Here's the current dovecot.conf:

dict { } !include conf.d/*.conf

!include_try local.conf

ssl = yes ssl_cert =

I'm not familiar with the openSUSE default config, but the above is all that is left when I remove the comments. Maybe also post the pertinent bits of conf.d/*.conf? Back to the key issue - one account works, the second one doesn't. Which error messages are you seeing, typically in /var/log/mail? Have you set "auth_debug = yes" in some config file? -- Per Jessen, Zürich (14.3°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org