On May 2, 2012, at 3:23 PM, Tom Hendrikx wrote:
> Sorry for being an arse, but I fail to see why you don't simply follow
> up on my advise (and report back) over at [sdlu] about this
I did what you suggested (turning on the verbose auth logging in Dovecot)
and replied about it. Thanked you prof
On 02-05-12 22:45, ghe wrote:
>
> I've asked on several lists, googled, and read books. I can't figure out
> what's going on. I thought the lack of rhost= indicated one of my monit
> monitors. So I turned them all off, and the entries came right in.
>
Sorry for being an arse, but I fail to see
On 5/2/12 2:57 PM, Gary Chambers wrote:
If this is an Ubuntu system, it could be a problem with the dovecot PAM
authentication configuration.
Well, it's Debian -- that's pretty close :-)
I saw this problem a couple of years ago,
fixed it (but don't remember how), but then an update to my ser
Glenn,
May 2 14:02:15 server dovecot-auth: pam_unix(dovecot:auth):
authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=be rhost=
If this is an Ubuntu system, it could be a problem with the dovecot PAM
authentication configuration. I saw this problem a couple of years ago,
fixed i
I've been having an interesting (to me) problem. I'm getting auth.log
entries like this:
May 2 14:02:15 server dovecot-auth: pam_unix(dovecot:auth): authentication
failure; logname= uid=0 euid=0 tty=dovecot ruser=be rhost=
every 10 minutes. Note the empty rhost= data. 'be' was a username --
