[Dovecot] Dovecot 2.0 and BSDI 4.X
All right, I am trying to migrating to 2.0 but running into problems.
from my typescript:
Script started on Wed Aug 18 23:24:58 2010
doctor.nl2k.ab.ca//usr/home/doctor$ tail -f /var/log/maillog | egrep dovecot
Aug 18 23:25:31 doctor dovecot: master: Dovecot v2.0.0 starting up (core dumps disabled)
Aug 18 23:25:31 doctor dovecot: log: Error: net_accept() failed: Invalid argument
Aug 18 23:25:31 doctor dovecot: master: Warning: service(anvil): process_limit reached, client connections are being dropped
quit
^C
doctor.nl2k.ab.ca//usr/home/doctor$ /usr/doc veo cot/sbin/dovecot -n
# 2.0.0: /usr/dovecot/etc/dovecot/dovecot.conf
# OS: BSD/OS 4.3 i386
auth_cache_negative_ttl = 3600 s
base_dir = /var/run/dovecot/
disable_plaintext_auth = no
first_valid_uid = 100
listen = *
login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c
mail_debug = yes
mail_location = mbox:~/mail:INBOX=/var/mail/%u
mail_log_prefix = %Us(%u):
mdbox_rotate_size = 2048
passdb {
args = /etc/master.passwd
driver = passwd-file
}
protocols = pop3 imap
service auth {
executable = /usr/dovecot/libexec/dovecot/auth
user = root
vsz_limit = 256
}
service imap-login {
chroot = login
client_limit = 256
executable = /usr/dovecot/libexec/dovecot/imap-login
inet_listener imaps {
address = 204.209.81.1
}
process_limit = 128
process_min_avail = 3
service_count = 1
user = dovecot
vsz_limit = 64
}
service imap {
executable = /usr/dovecot/libexec/dovecot/imap
process_limit = 512
vsz_limit = 256
}
service pop3-login {
chroot = login
client_limit = 256
executable = /usr/dovecot/libexec/dovecot/pop3-login
inet_listener pop3s {
address = 204.209.81.1
}
process_limit = 128
process_min_avail = 3
service_count = 1
user = dovecot
vsz_limit = 64
}
service pop3 {
executable = /usr/dovecot/libexec/dovecot/pop3
process_limit = 512
vsz_limit = 256
}
ssl_cert = </etc/ssl/certs/dovecot.pem
ssl_cipher_list = ALL:!LOW:!SSLv2
ssl_key = </etc/ssl/private/dovecot.pem
userdb {
driver = passwd
}
userdb {
args = /etc/passwd
driver = passwd-file
}
protocol imap {
imap_client_workarounds = delay-newmail tb-extra-mailbox-sep
imap_idle_notify_interval = 120 s
imap_logout_format = bytes=%i/%o
imap_max_line_length = 65536
mail_max_userip_connections = 10
mail_plugin_dir = /usr/dovecot/lib/dovecot/imap
}
protocol pop3 {
mail_max_userip_connections = 3
mail_plugin_dir = /usr/dovecot/lib/dovecot/pop3
pop3_enable_last = no
pop3_lock_session = no
pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s
pop3_no_flag_updates = no
pop3_reuse_xuidl = no
pop3_save_uidl = no
pop3_uidl_format = %08Xu%08Xv
}
You have new mail in /var/mail/doctor
doctor.nl2k.ab.ca//usr/home/doctor$ exit
exit
Script done on Wed Aug 18 23:26:07 2010
telneting into the ports work, but
the clients seem to stuck in an infinite loop.
-- Member - Liberal International This is doctor@nl2k.ab.ca Ici doctor@nl2k.ab.ca God, Queen and country! Never Satan President Republic! Beware AntiChrist rising! http://twitter.com/rootnl2k http://www.facebook.com/dyadallee Australia!! Vote to throw the REpublicans to the sharks!
On Wed, 2010-08-18 at 23:37 -0600, The Doctor wrote:
Aug 18 23:25:31 doctor dovecot: log: Error: net_accept() failed: Invalid argument
http://hg.dovecot.org/dovecot-2.0/rev/565f18727209 fixes this?
Aug 18 23:25:31 doctor dovecot: master: Warning: service(anvil): process_limit reached, client connections are being dropped
I'm not really sure about this.. This still happens with the above change? Anything else logged before it? Do you even have anvil process?
listen = * .. service imap-login { inet_listener imaps { address = 204.209.81.1 }
Better to set the address in the listen setting instead of explicitly for different inet_listeners.
On Thu, Aug 19, 2010 at 06:22:09PM +0100, Timo Sirainen wrote:
On Wed, 2010-08-18 at 23:37 -0600, The Doctor wrote:
Aug 18 23:25:31 doctor dovecot: log: Error: net_accept() failed: Invalid argument
http://hg.dovecot.org/dovecot-2.0/rev/565f18727209 fixes this?
Aug 18 23:25:31 doctor dovecot: master: Warning: service(anvil): process_limit reached, client connections are being dropped
I'm not really sure about this.. This still happens with the above change? Anything else logged before it? Do you even have anvil process?
listen = * .. service imap-login { inet_listener imaps { address = 204.209.81.1 }
Better to set the address in the listen setting instead of explicitly for different inet_listeners.
Seems for like porting bugs.
Easy to fix.
-- Member - Liberal International This is doctor@nl2k.ab.ca Ici doctor@nl2k.ab.ca God, Queen and country! Never Satan President Republic! Beware AntiChrist rising! http://twitter.com/rootnl2k http://www.facebook.com/dyadallee Australia!! Vote to throw the REpublicans to the sharks!
On Thu, Aug 19, 2010 at 06:22:09PM +0100, Timo Sirainen wrote:
On Wed, 2010-08-18 at 23:37 -0600, The Doctor wrote:
Aug 18 23:25:31 doctor dovecot: log: Error: net_accept() failed: Invalid argument
http://hg.dovecot.org/dovecot-2.0/rev/565f18727209 fixes this?
NOt certain.
Aug 18 23:25:31 doctor dovecot: master: Warning: service(anvil): process_limit reached, client connections are being dropped
I'm not really sure about this.. This still happens with the above change? Anything else logged before it? Do you even have anvil process?
Yes, the anvil process is a postfix process.
listen = * .. service imap-login { inet_listener imaps { address = 204.209.81.1 }
Better to set the address in the listen setting instead of explicitly for different inet_listeners.
Had to resort back to inet_listener .
Question how is the auth process handled in 2 that differs from 1?
Because in Dovecot 1 I had
auth_executable = /usr/contrib/libexec/dovecot/dovecot-auth
and in Dovecot 2 I have
executable = /usr/dovecot/libexec/dovecot/auth
-- Member - Liberal International This is doctor@nl2k.ab.ca Ici doctor@nl2k.ab.ca God, Queen and country! Never Satan President Republic! Beware AntiChrist rising! http://twitter.com/rootnl2k http://www.facebook.com/dyadallee Australia!! Vote to throw the REpublicans to the sharks!
The Doctor put forth on 8/20/2010 9:24 PM:
On Thu, Aug 19, 2010 at 06:22:09PM +0100, Timo Sirainen wrote:
On Wed, 2010-08-18 at 23:37 -0600, The Doctor wrote:
Aug 18 23:25:31 doctor dovecot: log: Error: net_accept() failed: Invalid argument
http://hg.dovecot.org/dovecot-2.0/rev/565f18727209 fixes this?
Wind River discontinued BSD/OS (BSDi) in 2003, 7 years ago. This version of BSDi "The Doctor" is running thus hasn't seen a patch for _at least_ 7 years. Seven year old gcc environment? No wonder things don't work.
Is there any real legitimate reason either of you are wasting your time with trying to make Dovecot work on a 7+ year old _DEAD_ operating system?
Why haven't you moved this box up to the latest version of FreeBSD or OpenBSD?
-- Stan
On Sat, Aug 21, 2010 at 11:58 AM, Stan Hoeppner <stan@hardwarefreak.com>wrote:
The Doctor put forth on 8/20/2010 9:24 PM:
On Thu, Aug 19, 2010 at 06:22:09PM +0100, Timo Sirainen wrote:
On Wed, 2010-08-18 at 23:37 -0600, The Doctor wrote:
Aug 18 23:25:31 doctor dovecot: log: Error: net_accept() failed: Invalid argument
http://hg.dovecot.org/dovecot-2.0/rev/565f18727209 fixes this?
Wind River discontinued BSD/OS (BSDi) in 2003, 7 years ago. This version of BSDi "The Doctor" is running thus hasn't seen a patch for _at least_ 7 years. Seven year old gcc environment? No wonder things don't work.
Is there any real legitimate reason either of you are wasting your time with trying to make Dovecot work on a 7+ year old _DEAD_ operating system?
Why haven't you moved this box up to the latest version of FreeBSD or OpenBSD?
Looks like even I woke up my FreeBSD 4.0 today, Timo would be willing to help me make Dovecot 2.0 run on it.
I think it's something to do with these hard core programmers. They never see failure as an option!
This BSD/OS fellow really need to run something else. 7 year old OS - it's like running Windows (spit!) 95 in 2010.
-- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223
"If you have nothing good to say about someone, just shut up!." -- Lucky Dube
On Mon, 2010-08-23 at 17:03 +0300, Odhiambo Washington wrote:
Looks like even I woke up my FreeBSD 4.0 today, Timo would be willing to help me make Dovecot 2.0 run on it.
I think it's something to do with these hard core programmers. They never see failure as an option!
If making Dovecot run on some specific OS requires only a few changes, I'll do it. Doesn't matter how old it is. But if it's starting to look like it would require larger changes, then I'll probably forget about it..
On Mon, 23 Aug 2010 15:21:15 +0100 Timo Sirainen <tss@iki.fi> articulated:
On Mon, 2010-08-23 at 17:03 +0300, Odhiambo Washington wrote:
Looks like even I woke up my FreeBSD 4.0 today, Timo would be willing to help me make Dovecot 2.0 run on it.
I think it's something to do with these hard core programmers. They never see failure as an option!
If making Dovecot run on some specific OS requires only a few changes, I'll do it. Doesn't matter how old it is. But if it's starting to look like it would require larger changes, then I'll probably forget about it..
Well, in my opinion, if the BSD people have all ready abandoned it, it is probably time for you to do so also. With FreeBSD-8.1 officially released, continued use of a deprecate OS makes no sense at all, assuming that the OP knows how to upgrade his installation. If he doesn't, then that is a whole new ballgame.
-- Jerry ✌ Dovecot.user@seibercom.net
Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header.
Diplomacy is to do and say, the nastiest thing in the nicest way.
BalfourOn 21.8.2010, at 3.24, The Doctor wrote:
Aug 18 23:25:31 doctor dovecot: master: Warning: service(anvil): process_limit reached, client connections are being dropped
I'm not really sure about this.. This still happens with the above change? Anything else logged before it? Do you even have anvil process?
Yes, the anvil process is a postfix process.
Dovecot has its own anvil process too (yeah, I stole the name from Postfix).
listen = * .. service imap-login { inet_listener imaps { address = 204.209.81.1 }
Better to set the address in the listen setting instead of explicitly for different inet_listeners.
Had to resort back to inet_listener .
Question how is the auth process handled in 2 that differs from 1?
What does that have to do with anything?
Because in Dovecot 1 I had
auth_executable = /usr/contrib/libexec/dovecot/dovecot-auth
and in Dovecot 2 I have
executable = /usr/dovecot/libexec/dovecot/auth
Only the binary name changed from dovecot-auth to auth.
On Sat, Aug 21, 2010 at 01:40:00PM +0100, Timo Sirainen wrote:
On 21.8.2010, at 3.24, The Doctor wrote:
Aug 18 23:25:31 doctor dovecot: master: Warning: service(anvil): process_limit reached, client connections are being dropped
I'm not really sure about this.. This still happens with the above change? Anything else logged before it? Do you even have anvil process?
Yes, the anvil process is a postfix process.
Dovecot has its own anvil process too (yeah, I stole the name from Postfix).
listen = * .. service imap-login { inet_listener imaps { address = 204.209.81.1 }
Better to set the address in the listen setting instead of explicitly for different inet_listeners.
Had to resort back to inet_listener .
Question how is the auth process handled in 2 that differs from 1?
What does that have to do with anything?
I am just wondering what else has changed?
IT seems that the authentication is caught in a non-ending loop.
Because in Dovecot 1 I had
auth_executable = /usr/contrib/libexec/dovecot/dovecot-auth
and in Dovecot 2 I have
executable = /usr/dovecot/libexec/dovecot/auth
Only the binary name changed from dovecot-auth to auth.
-- Member - Liberal International This is doctor@nl2k.ab.ca Ici doctor@nl2k.ab.ca God, Queen and country! Never Satan President Republic! Beware AntiChrist rising! http://twitter.com/rootnl2k http://www.facebook.com/dyadallee Australia!! Vote to throw the REpublicans to the sharks!
On Sat, 2010-08-21 at 07:08 -0600, The Doctor wrote:
Question how is the auth process handled in 2 that differs from 1?
What does that have to do with anything?
I am just wondering what else has changed?
IT seems that the authentication is caught in a non-ending loop.
Why does it seem that? What exactly does it say now log when starting up? Does it answer/log anything when telneting to port 143?
participants (5)
-
Jerry
-
Odhiambo Washington
-
Stan Hoeppner
-
The Doctor
-
Timo Sirainen