Bernd Wurst wrote:
Am Mittwoch, 20. Dezember 2006 10:42 schrieb Alessandro Vesely:
GPLv3 should
come in a few months and Courier's Copyright holder may want to use it.
Then, there will still be an incompatibility: would the DomainKeys
Identified Mail (DKIM) addition have to be reverted in
Hi,
I have installed courier with pam auth. It seems to work all fine. I just
did the test perftest1 and the mail was delivered fine on the maildir I
created.
When I try to logon using imap or the webmail though I get the reply “Unable
to open the maildir for this account -- the maildir doesn't
Jean-Marc Liotier wrote:
I found no information online about this error, so I turn to this list...
12:22 [EMAIL PROTECTED] ~# tail -f /var/log/mail.log -n 100 | grep malloc
Dec 13 12:20:20 kivu couriertcpd: malloc: Input/output error
Dec 13 12:20:25 kivu couriertcpd: malloc: Input/output
Hello,
If I send an E-Mails from the Domain freenet.de over an
foreign ISP like smtp.wnadoo.fr, 80% of the E-Mails
become bounced which is generaly a normal SPAM protection.
If I send over mx.freenet.de I need to use auth-smtp
in conjunction with TLS and SSL...
The MTA in my
stelios writes:
« HTML content follows »
Hi,
I have installed courier with pam auth. It seems to work all fine. I just d
id the test perftest1 and the mail was delivered fine on the maildir I crea
ted.
When I try to logon using imap or the webmail though I get the reply “Unabl
e to open
Michelle Konzack writes:
Hello,
If I send an E-Mails from the Domain freenet.de over an
foreign ISP like smtp.wnadoo.fr, 80% of the E-Mails
become bounced which is generaly a normal SPAM protection.
If I send over mx.freenet.de I need to use auth-smtp
in conjunction with TLS and SSL...
The
All
I am currently evaluating the Courier mail package as a replacement for our
student email system. I installed a test setup using local accounts which
worked fine. I then blew that away, started from scratch and am now
endeavouring to get everything working authenticating to our Novell
Stephen Meatheringham wrote:
It is simply complaining that the passwords are not matching under authpwd.
If the user exists in the local password file then it falls through to
authshadow and works.
You should be using authpam, which will work for both local and LDAP
users. If you
It is simply complaining that the passwords are not matching under
authpwd. If the user exists in the local password file then it falls
through to authshadow and works.
You should be using authpam, which will work for both local and LDAP
users. If you don't have libauthpam.so with your
