Sam wrote:
thanks it worked out.
i changed my config from see below
the login via imap and pop is working, but maildrop stopped to work
together
this is the error message in /var/log/mail.log
pr 10 23:24:37 ms1 postfix/pipe[14203]: B77C9CE8147:
to=[EMAIL PROTECTED], relay=maildrop,
On Thu, Apr 10, 2008 at 11:34:38PM +0200, Marco Kammerer wrote:
thanks it worked out.
i changed my config from see below
the login via imap and pop is working, but maildrop stopped to work together
this is the error message in /var/log/mail.log
pr 10 23:24:37 ms1 postfix/pipe[14203]:
On Wed, Apr 09, 2008 at 05:03:28PM +0200, Marco Kammerer wrote:
Is there also a way to determine which IP Adress the Client has.
No, this information is not passed from the frontend to authdaemond.
There have been a couple of patches which add the IP address to the
authdaemond protocol posted
Brian Candler wrote on April 09, 2008 3:27 PM
# AAA not working
#MYSQL_AUXOPTIONS_FIELD
CONCAT(disableimap=,IF($(service)='imaps',disableimaps,disableimap),,disablepop3=,disablepop3,,disablewebmail=,disablewebmail)
...
the thing is that mysql gets in the line AAA the - $(service) not as
Marco Kammerer writes:
thanks it worked out.
i changed my config from see below
the login via imap and pop is working, but maildrop stopped to work together
this is the error message in /var/log/mail.log
pr 10 23:24:37 ms1 postfix/pipe[14203]: B77C9CE8147:
to=[EMAIL PROTECTED],
Brian Candler [EMAIL PROTECTED] wrote on Wednesday, April 09, 2008
3:27 PM
On Sat, Apr 05, 2008 at 12:19:03AM +0200, Marco Kammerer wrote:
# AAA not working
#MYSQL_AUXOPTIONS_FIELD
CONCAT(disableimap=,IF($(service)='imaps',disableimaps,disableimap),,disa
