Hi,
I have some domains protected by an external antispam gateway, those domains
are removed from the rcpthosts settings of qmail, and the antispam gateway is
added in the /etc/tcp.smtp to be allowed to relay...
This way, only the antispam gateway is able to send emails for the domain to
the
hello there, Diego
the thing is the current version of vpopmail does not support secure connection
to ldap. I was going to write a patch to make it, but right now I'm awfully
busy at work... you can change 636 (LDAPS_PORT) for 389 (LDAP_PORT) for awhile
as a temporary way out...
-
Vitali Malicky wrote:
hello there, Diego
the thing is the current version of vpopmail does not support secure
connection to ldap. I was going to write a patch to make it, but right
now I'm awfully busy at work...
If you do, please be sure to submit it on SourceForge so we can add it
sure, Rick, beyond any doubts.
- Original Message -
From: Rick Widmer [EMAIL PROTECTED]
To: vchkpw@inter7.com
Sent: Tuesday, December 19, 2006 4:05 PM
Subject: Re: [vchkpw] vpopmail with openldap
Vitali Malicky wrote:
hello there, Diego
the thing is the current version
Having trouble getting my first ezmlm list to run on a newly built
server with vpopmail 5.4.10 and CHKUSER 2.0.8b.
CHKUSER was built using chkuser_settings.h with:
--
/*
* The following #define set the character used for
Thanks to everyone who has commented on the threads '5.4.17 patches'
and '.vpopmail-* instead of .qmail-*'. After all that I've decided to
think about it some more. :)
First, the status of 5.4.18. I believe I now have everything together
that will be going into the next release in CVS.
chkuser 2.0.9 will solve this problem, as last version of ezmlm has
no more a file chkuser used for checking the list existence.
Enabling alias is another way to solve this problem.
Tonino
At 19.50 19/12/2006, you wrote:
SOLVED:
Per this thread (google cache):
