[Dovecot] Warning: SSL is disabled because global ssl=no, ignoring ssl=yes for subsection

2011-05-02 Thread Peter Bell

Hi all,

This is my first message to the list.

I've been experimenting with running dovecot on my unRAID server 
(basically, a parity-protected array of disks, running on a slackware 
13.1 platform).


Someone on the unRAID forum had built a binary distribution of dovecot 
1.1.20 and I got this up and running without too much trouble.


Today, I've been building the latest dovecot release (2.0.12) and 
getting this up and running.  My biggest problem has been reconstructing 
the configuration file but, after a few diversions, I'm now back up and 
running, with access to my mail once more.


However, I'm just a little bit miffed that I can't get rid of this warning.

My configuration:
root@Tower:~# doveconf -n
# 2.0.12: /usr/local/etc/dovecot/dovecot.conf
doveconf: Warning: SSL is disabled because global ssl=no, ignoring 
ssl=yes for subsection

# OS: Linux 2.6.36.2-unRAID i686 Slackware 13.1.0 fuse.shfs
disable_plaintext_auth = no
listen = *
mail_location = maildir:/mnt/user/Maildir/%u
passdb {
  args = /etc/passwd.dovecot
  driver = passwd-file
}
protocols = imap
service auth {
  user = root
}
service imap-login {
  inet_listener imap {
port = 143
  }
}
ssl = no
userdb {
  args = /etc/passwd.dovecot
  driver = passwd-file
}
root@Tower:~#

Can someone point me to where the (implicit?) ssl=yes is coming from?

In the meantime I will have a play at mail fetching, comparing dumping 
the mails straight into maildir, with using the dovecote lda.


Thanks for any advice.

--
---
Peter Bell


Re: [Dovecot] 2.0.12 Coredump under Solaris 10 *SOLVED*

2011-05-02 Thread Denny Schierz
hi,

Am Freitag, den 29.04.2011, 14:44 +0300 schrieb Timo Sirainen:

 =home=/imap/spool/%d/%1n/%n

that works :-) Thanks

cu denny



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


[Dovecot] is reverse dns down ?

2011-05-02 Thread Voytek Eymont
Hi guys, is that a genuine email from the list, I'm getting it rejected as
it's missing reverse hostname:

May  2 21:21:41 postfix/smtpd[18033]: NOQUEUE: reject: RCPT from
unknown[194.89.34.45]: 450 4.7.1 Client host rejected: cannot find your
reverse hostname, [194.89.34.45]; from=dovecot-boun...@dovecot.org
to=voy...@sbt.net.au proto=ESMTP helo=mkentta.iki.fi

# host mkentta.iki.fi
mkentta.iki.fi has address 194.89.34.45
mkentta.iki.fi mail is handled by 10 mkentta.iki.fi.
mkentta.iki.fi mail is handled by 100 smtp.menturagroup.com.

# host  194.89.34.45
Host 45.34.89.194.in-addr.arpa. not found: 3(NXDOMAIN)




-- 
Voytek



Re: [Dovecot] is reverse dns down ?

2011-05-02 Thread Esther YĆ©benes --Conzentra--
attachment: blog.jpgattachment: twitter.jpgattachment: linkedin.jpgattachment: facebook.jpg

Re: [Dovecot] is reverse dns down ?

2011-05-02 Thread Stan Hoeppner

On 5/2/2011 6:30 AM, Voytek Eymont wrote:


# host  194.89.34.45
Host 45.34.89.194.in-addr.arpa. not found: 3(NXDOMAIN)


~$ host 194.89.34.45
45.34.89.194.in-addr.arpa domain name pointer mkentta.iki.fi.

~$ prdns.pl 194.89.34.45/32
194.89.34.45: mkentta.iki.fi

~$ rdns-tool.pl 194.89.34.45/32
using mask 32
   194.89.34.45: mkentta.iki.fi

Looks like there's a DNS issue on your end.  Try flushing your cache. 
For obvious reasons Postfix returns a 450 in this case, so the list 
server will attempt delivery for a few days.


If you don't run your own resolver on your Postfix MX I suggest you do 
so.  I use PowerDNS recursor on my MX MTAs.  Works great.  Setup takes 
less than 5 minutes.  Caching is in memory only, not disk, so a restart 
clears everything.


--
Stan


Re: [Dovecot] IMAP vs. POP3

2011-05-02 Thread Eric Shubert

On 04/28/2011 10:31 AM, Matt wrote:

Does IMAP create much additional system load vs. POP3?



How much is much?

They do have different usage patterns. The server load also depends on 
how each client program is configured. Some client configurations create 
more of a load than others (eg how messages are cached on the client). 
My impression is that the client configuration can affect system load 
more so than the difference between IMAP and POP3.


Generally speaking, IMAP is preferable to POP3 due to the accessibility 
it provides from multiple clients/devices. POP3 is the past, IMAP is the 
future.


--
-Eric 'shubes'



[Dovecot] Restricting IMAP

2011-05-02 Thread Matt
I want to restrict IMAP use too 127.0.0.1 and to only certain
usernames.  Such as f...@my777domain.com would be allowed to use IMAP.
 How would I do that with Dovecot or can I?  Basically I want webmail
to work with IMAP regardless of username but I only want certain
usernames allowed to use IMAP remotely.


Re: [Dovecot] Warning: SSL is disabled because global ssl=no, ignoring ssl=yes for subsection

2011-05-02 Thread Willie Gillespie

On 05/02/2011 04:19 AM, Peter Bell wrote:
 However, I'm just a little bit miffed that I can't get rid of this 
warning.


 My configuration:
 root@Tower:~# doveconf -n
 # 2.0.12: /usr/local/etc/dovecot/dovecot.conf
 doveconf: Warning: SSL is disabled because global ssl=no, ignoring
 ssl=yes for subsection
 # OS: Linux 2.6.36.2-unRAID i686 Slackware 13.1.0 fuse.shfs

 Can someone point me to where the (implicit?) ssl=yes is coming from?

Timo fixed this just a little while back (April 20th)
Fixed: http://hg.dovecot.org/dovecot-2.0/rev/7d60cd847c70


Re: [Dovecot] is reverse dns down ?

2011-05-02 Thread /dev/rob0
On Mon, May 02, 2011 at 10:30:44PM +1100, Voytek Eymont wrote:
 Hi guys, is that a genuine email from the list, I'm getting it 
 rejected as it's missing reverse hostname:
 
 May 2 21:21:41 postfix/smtpd[18033]: NOQUEUE: reject: RCPT
 from unknown[194.89.34.45]: 450 4.7.1 Client host rejected:
 cannot find your reverse hostname, [194.89.34.45]; 
 from=dovecot-boun...@dovecot.org to=voy...@sbt.net.au 
 proto=ESMTP helo=mkentta.iki.fi
 
 # host mkentta.iki.fi
 mkentta.iki.fi has address 194.89.34.45
 mkentta.iki.fi mail is handled by 10 mkentta.iki.fi.
 mkentta.iki.fi mail is handled by 100 smtp.menturagroup.com.
 
 # host  194.89.34.45
 Host 45.34.89.194.in-addr.arpa. not found: 3(NXDOMAIN)

We discussed this the other day under Timo's thread about 
dovecot.org. It seems that ns.ripe.net., one of the NS hosts for 
89.194.in-addr.arpa., is not returning the PTR for 
45.34.89.194.in-addr.arpa. AFAICS the other NS hosts seem to be 
working fine, but if your resolver was unlucky enough to hit 
ns.ripe.net., you have a host with no PTR.

It's like Russian roulette with rDNS. I suspect it might be a 
casualty of DNSSEC, but I get the same noerror response when
querying with +dnssec and +nodnssec.

At this point those who use the normally safe and reasonable 
reject_unknown_reverse_client_hostname restriction should consider 
whitelisting mkentta.iki.fi[194.89.34.45] in the MTA.

And Timo needs to scream louder at the ISP. ;)
-- 
Offlist mail to this address is discarded unless
/dev/rob0 or not-spam is in Subject: header


Re: [Dovecot] Restricting IMAP

2011-05-02 Thread Rick Romero

Quoting Matt lm7...@gmail.com:


I want to restrict IMAP use too 127.0.0.1 and to only certain
usernames.  Such as f...@my777domain.com would be allowed to use IMAP.
 How would I do that with Dovecot or can I?  Basically I want webmail
to work with IMAP regardless of username but I only want certain
usernames allowed to use IMAP remotely.


You can use post-login scripting:
http://wiki2.dovecot.org/PostLoginScripting

Rick