similar to: 1.0rc7 working well

Fellow Dovecot'ers. I tried something tonight that I should have done a while back: Turned on verbose logging in the authentication section. I'm still unable to get the mail client I'm experimenting with (Pegasus) to complete a pop3s connection, in that I still get an indication of a failed password. However, at least I'm a little closer to understanding the failure itself.

Fellow users, This is just a heads-up to let the list know that I'm still unable to get ANY sort of pop3 or pop3s authentication to work with Dovecot. Just as a sanity check, I set up an entirely separate system, running FreeBSD 6.1 production, postfix 2.3, and Dovecot 1.0rc2, as a testbed. I got the exact same problem that I had with the NetBSD 3.0 production server, specifically that

Fellow Dovecot'ers, I've -almost- got Dovecot completely functional, and I will add that it works just fine for non-authenticated POP3. The problem begins when I try to use authentication for same against the system's /etc/passwd section. This is the error message that comes up in /var/log/maillog Jul 9 21:14:10 featherweb dovecot: auth(default): pam(kyrrin at

Fellow techies, OK... This is going to go down as one of those "D'Oh!" moments in the world of computers. Boy, do I feel dumb... In short: I found the problem. One miserable little line in 'dovecot.conf' called 'auth_default_realm =.' I had this set to 'bluefeathertech.com,' thinking it was necessary to do so. I was wrong, at least for my environment,

Hi, Curtis (and the group), I tried setting up Dovecot's auth default section as you described, with both authdb and userdb set to 'passwd.' It let the authenticated session start on the POP side, but I got consistent authentication failures on the client side that the passwords didn't match. I don't have any more time to mess with it this morning, but I will make it a

pop3 and pop3s under protocolos but still seeing the imap-login process, it sounds like your dovecot install isn't reading the proper configuration = file (or at least the one you're editing). Maybe that's why these changes = don't seem to do anything? --=20 Jeff Graves, MCSA Image Source, Inc. 508.966.5200 x31=20 www.image-src.com -----Original Message----- From: dovecot-bounces

How does one go about generating a local password database for apop authentication? Or can it simply run against /etc/passwd, using a PAM entry? (I forgot to append this to my last message... sorry...). Thanks much. -=-=-=-=-=-=-=-=-=-=-=- Bruce Lane, Owner & Head Hardware Heavy, Blue Feather Technologies -- http://www.bluefeathertech.com kyrrin (at) bluefeathertech do/t c=o=m "If

Hi, gang, There have been numerous postings, scattered across various Internet forums (including this one), about problems encountered using Veritas Backup Exec 8.6 and higher with Samba-sourced shares from *nix servers. In my particular case, I have a Windows NT Server 4.0-based backup system, which is supposed to be able to back up the other Windows systems on the LAN, plus several SPARC boxes

Fellow Samba folk, I'm in the process of resurrecting one of my servers with FreeBSD 6.0/Production, and Samba 3.x (I installed the FreeBSD-obtained package). I'm using 'domain' for the security mode, and the Samba server was successfully joined to my domain. It -almost- works. I can see the share from my Windows 2000 system, and browse it. However, I cannot write to it. I keep

Hi, Petar, For whatever reason, I didn't see your most recent reply until I checked the web archives. To answer your questions... Is my dovecot running chrooted? Not that I know of. However, the option to (apparently) decide this is confusing at best. Here is what I have entered. # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole

Fellow samba folk, This one's making me want to tear out what little hair I have left. THE *NIX PLATFORM: FreeBSD 7.0-RELEASE, Samba 3.3.8. THE ENVIRONMENT: Small domain, Windows 2003 servers and XP-pro based workstations. The FreeBSD server is a member server in the domain, so at least that works. THE SYMPTOMS: This is bizarre. I can, using mount_smbfs on the FreeBSD side, easily

Good day, gang, Chris McKeever was kind enough to write back to me over the weekend regarding the problems I'd experienced in using Backup Exec 8.x and 9.x to connect to Samba shares on a NetBSD system. Between his comments and my direct experience, I've only found ONE combination that will work, and that is: NetBSD 1.6, Samba 2.2.8a, and Backup Exec 8.6. If you take NetBSD up to 1.6.1,

Fellow Samba-shakers, I've run into an odd problem, and I'm seeking the advice of anyone who has implemented Veritas Backup Exec 8.6 or 9.0, on an NT 4.0 server platform, to perform backups of NetBSD 1.6x systems via Samba file shares. Said problem did NOT manifest itself until I tried using Samba 3.0.0. I have jumped back to 2.2.8a, since that's the last version that was known to

Fellow samba folk, Please disregard my earlier message. I have solved the problem, and it appears to have been a combination of things. First, somehow (I have no idea how), the Samba package must have gotten corrupted during installation. I cleaned up the mess, reinstalled, and had much better results. Second issue: I followed the instructions at this link, Section 2.6, VERY carefully, to

Fellow samba dancers, Here's my situation: I've got a NetBSD (1.6) box running smoothly enough with the most recent stable Samba release (2.2.7a). I have no problems whatsoever browsing, reading, and writing files from NT boxes to the shared directory using File Manager or Explorer. Our NT server is a PDC, and has Veritas Backup Exec 8.6 and a tape library on it. This serves as the

Fellow samba dancers, Before I lose it, and teach our server to fly, I think it best if I ask the experts. THE SETUP: FreeBSD 7.0-Release, i386 platform (Proliant ML530 to be exact), Samba version 3.0.31,1. Windows domain based on Windows 2000 Advanced Server, with mixed NT-style and Active Directory style security. Domain name is FREEDOM_RIDGE, two active-directory domain controllers called

Hi All, First I would like to thank all who gave me pointers on where to look for the applications. There are also some of you who wanted me to post my findings. Hence I have decided to post a mini how-to. I actually ran a sniffer on it, and all messages are encrypted. :) If there's any prob, just drop me a line. Rgrds, Wong. begin 666 How-To Ssecure pop or imap.txt [mod: Grrr... I now

Dagmar d'Surreal wrote: > Original text cut My fault is that the instructions were for SlackwareLinux 3.3 andI *did not* mention that! Please, accept my appologies ... But also you can read from the INSTALL of tcpdump, that *if* you want you can leave it under the structure of tcpdump source tree, especially if you have any problems. On my system it wouldn't want to compile

Fellow dovecot'ers, I'm just getting started with Dovecot, and I'm not a programmer, so please be gentle. ;-) THE PLATFORM: NetBSD 3.0/SPARC, Postfix 2.3-RC8, current Dovecot RC (I forgot the number). Maildir-type directories. THE GOAL: To accommodate authenticated (remote) POP3 users with APOP or SSL/TLS, and allow users on the internal network (192.168.x.x) to just use basic

Hi, I just upgraded a 0.99 installation to 1.0rc7 (going from mbox to maildir along the way, but that's another story), and I'm seeing a rather fast fd quick; I already had to restart dovecot once, after a few hours. What is leaked are pipes, left open on the master dovecot process while the other end is long gone. I can't tell right now if it happens for every single login process