-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/22/2012 7:07 AM, Matt Brookings wrote:
> On 04/22/2012 09:02 AM, Matt Kane wrote:
> > You guys don't work on Saturday? This started happening early
> > yesterday evening.
>
> I'm not sure if you're jo
You guys don't work on Saturday? This started happening early yesterday evening.
On Apr 22, 2012, at 6:58 AM, Matt Brookings wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 04/22/2012 08:59 AM, Matt Kane wrote:
>> A bit delayed IMO but thanks n
A bit delayed IMO but thanks none the less. I've been forwarding these messages
to the address in the auto responder hoping he would fix it.
On Apr 22, 2012, at 6:55 AM, Matt Brookings wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Well, our apologies that happened. It's all cl
gure out
without logging. Once I got logging working correctly the problem made
itself obvious.
Thanks again for all your help.
Matt
Jens Ott - intergenia AG wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt Kane schrieb:
Quoting Joshua Megerman <[EMAIL PROTECTED]>:
I
Quoting Joshua Megerman <[EMAIL PROTECTED]>:
I don't have it enabled, and I have no problems running qmail-smtpd as
vpopmail:vchkpw using tcpserver flags (-u vpopmail -g vchkpw). Which TLS
patch set are you using?
I am using the Gentoo ebuild and I have read all the negative
information reg
Quoting Joshua Megerman <[EMAIL PROTECTED]>:
Sounds like there's something funky going on with the chkuser patch for
you - do you have the same problem when not using TLS? I'm not a chkuser
expert, but have you double-checked your chkuser settings?
The only extra setting I'm using is the CHKU
me in the right direction?
Thanks,
Matt Kane
[EMAIL PROTECTED]
