similar to: inetd & corrupt environment

http://dovecot.org/releases/dovecot-1.0.rc11.tar.gz http://dovecot.org/releases/dovecot-1.0.rc11.tar.gz.sig Hopefully the last RC release? As far as I know there are no major problems left now. If nothing big shows up, v1.0 should be out in a couple of weeks. * Renamed default_mail_env to mail_location. default_mail_env still works for backwards compatibility. * deliver: When sending

http://dovecot.org/releases/dovecot-1.0.rc11.tar.gz http://dovecot.org/releases/dovecot-1.0.rc11.tar.gz.sig Hopefully the last RC release? As far as I know there are no major problems left now. If nothing big shows up, v1.0 should be out in a couple of weeks. * Renamed default_mail_env to mail_location. default_mail_env still works for backwards compatibility. * deliver: When sending

Hi everyone, Our company has decided to make a fake POP3 (and possibly IMAP) server, which accepts any user name and password combination and shows there are no new messages. This is for the purpose that when our mail cluster passes out, we can redirect our clients to this server while we fix our mail system. This way we can prevent our users from getting errors. We are using the latest

Does anyone know of a way to rate limit ssh connections from an IP address ? We are starting to see more and more brute force attempts to guess simple passwords "/usr/sbin/inetd -wWl -C 10" is nice for slowing down attempts to services launched via inetd. Is there an equiv method for doing this to sshd? Running from inetd has some issues supposedly. ---Mike

I was just thinking how they could be easily supported. This would work, right? : imap stream tcp nowait root /usr/sbin/tcpd /usr/local/libexec/dovecot/imap-login imaps stream tcp nowait root /usr/sbin/tcpd /usr/local/libexec/dovecot/imap-login --ssl imap-login would try to connect to master process using some named socket. If it couldn't, it would create the master process itself. Master

Hi all, I want to start dovecot through DJBs Daemontools-supervise, is there a configuration option that lets dovecot stay in foreground? best regards, Jens

Dovecot with libwrap doesn't work on FreeBSD for some reason or another. I have these lines in my /etc/hosts.allow: ALL: LOCAL 127.0.0.1: allow pop3: ALL: allow ALL: ALL: deny Yet when you try to telnet to localhost, port 110 this is what happens: Aug 29 22:48:38 dodo dovecot: pop3-login: Error: connect(tcpwrap) failed: Permission denied I also tried auth_debug=yes to see what's wrong

Hello, I''m trying to run the latest/greatest mongrel version: % sudo gem install mongrel ... Successfully installed mongrel-1.1 % gem list mongrel mongrel (1.1) % ruby -v ruby 1.8.4 (2005-12-24) [powerpc-darwin7.9.0] % uname -a Darwin NewYork.local 7.9.0 Darwin Kernel Version 7.9.0: Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC Power Macintosh powerpc

Hello! I've tried to set up dovecot in conjuction with vpopmail, and running it under djb's tcpserver instead of (x)inetd. Btw - there was no reference to setting dovecot up using (x)inetd either in the manuals/faqs i read, though I didn't search all that hard. Anyway, back to my Q: vpopmail uses vchkpw as an authentication mechanism, and with tcpserver I can do relaycontrol (based

Hi, Trying to setup dovecot in a test environment. I need to run it on an alternate port for imaps. it doesn't seem like I can specify it on the listen line. any ideas? -sv

Hi, I've just started trying allow_nets on one of my servers. I have auth_debug and auth_verbose both enabled and the output is as follows: Oct 28 13:05:48 mink dovecot: auth-worker(default): auth(user at domain.net,x.x.x.x): allow_nets: Matching for network 127.0.0.1/8 Oct 28 13:05:48 mink dovecot: auth-worker(default): auth(user at domain.net,x.x.x.x): allow_nets: Matching for network

hi, what do you tyhink about it? especially the faq comment about dovecot? http://www.bincimap.andreas.hanssen.name/ -- Levente "Si vis pacem para bellum!"

Browsing in the 2003-September archives, I found out how to start dovecot from inetd (using imap-login instead of imap). Still I've got a few problems. I prefer not using inetd, but that seams impossible (see my 1st email). And telnetting to port 143 results in an immediate connection close. Hmmm, I'll continue exploring the archives. Regards Evert

I'm working to get Dovecot 2.0.13 working along with qmail, Vpopmail and Squirrelmail on a Debian 6.0.2 system, Dovecot compiled, not from a package. Vpopmail has a widely known assigned user/group ID of 89 and is the owner of all the mail folders. Regardless of value of first_valid_uid (1, 89, other), Dovecot denies Squirrelmail connection, saying it can't allow access to UID 89.

Hello, we would like to use rsync (2.6.2 manualy patched and recompiled) in daemon mode spawned by inetd (Solaris 5.8 Environment). /etc/services: rsync 1234/tcp #RSYNC daemon /etc/inet/inetd.conf: rsync stream tcp nowait publish /usr/bin/rsync rsyncd --daemon --port 1234 . Alas, this does not seem to work, there is the following error message in the log file:

Hello, I run dovecot-2/Maildir/LDAP user/passdb and would like to be able to deny acess to users who connect from certain domains/IP (google.com for instance since in that case they gave their credentials to a third party). My understanding is that I cannot use some negative form of "allow_nets". The only mechanism I can think of is tcp_wrappers. However, dovecot documentation mention

I'm currently running version 2.0.7 of samba(CIFS9000). I have HPUX 11.x installed on the samba server. When I try to run this from inetd it doesn't work. I can run a startup script that runs the smbd as a daemon and it works fine. But if I try to run it from inetd it won't start. The previous version of Samba 1.9.18p10 that I had on this server worked fine. Is this a bug in

Hi. I don''t know if this one is known, but I can''t recall seeing anything about it. If it is old news I apologize. I discovered a bug in the inetd that comes with NetKit-B-0-08 and older. If a single SYN is sent to port 13 of the server, inetd will die of Broken Pipe: write(3, "Sun Jan 12 21:50:35 1997\r\n", 26) = -1 EPIPE (Broken pipe) --- SIGPIPE (Broken pipe) ---

Hopefully I'm not out to lunch here. I ported tftp-hpa to our proprietary OS, VOS (at stratus.com). We've always runs the old legacy tftpd from inetd, so I wanted to continue doing so with tftp-hpa. It seems to work okay, but I noticed that the code in tftpd.c has a 'while (1)' loop that has this at the end: /* * Now that we have read the request packet from

Hello. I know that it is recommended to run smbd as a standalone daemon and to avoid inetd. Can you please tell me why inetd is discouraged and what problems it imposes? Also, I have one user who is having problems accessing her personal files on a MacOSX 10.3.2 via smb. Any ideas what may be causing it? Judy Lin NACS-DCS