Perhaps a dumb question, or two...
To create new dat files and invalidate the old file handles the make*
scripts have to be run - the script which calls these could call all the
appropriate courier restarts - couldn't it? In the window between these new
events, the temporary failures would just re
Use SpamAssassin for qualifying mail as spam. You can then filter it. If you need help
integrating Spamassassin with Courier just send an e-mail to my address.
Regards
Manfred
- Original Message -
From: "David Mir" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 12,
I gave up on trying to get procmail to use use deliverquota ( if anyone
has this working please respond )
and compiled maildrop with support for deliverquota. From what I
understood in the man page,
this is what I need for mailbox command in postfix. The install script
updated my master.cf autom
On Thu, 13 Nov 2003, MH - Entwicklung wrote:
> Use SpamAssassin for qualifying mail as spam. You can then filter it.
> If you need help integrating Spamassassin with Courier just send an
> e-mail to my address.
I'm just curious how you go about doing it.
I'm using the following in /etc/courier/ma
I am setting up a Courier mail server to have it's mail accounts managed
through Novell Account Management (NAM) and Novell's edirectory.
The user accounts will be "psuedo-virtual" in that the accounts exist
locally in the passwd file but password authentication will be passed up
to the Novell
my maildroprc ist a bit different because we're delivering to an extra account. The
first if-statement is to prevent loops. We're running spamassassin in daemon mode this
is why you see /usr/bin/spamc instead of spamassassin.
if ((/^X\-Spam\-Checker\-Version:.*mail\.heubach\-edv\.*/))
{
}
e
Thanks Gordon, I will try to test it out and see how. But I need to find out
where it cause the problem first.
Vincent
- Original Message -
From: "Gordon Messmer" <[EMAIL PROTECTED]>
Cc: "Courier" <[EMAIL PROTECTED]>
Sent: Thursday, November 13, 2003 6:38 AM
Subject: Re: [courier-users]
Thanks. Since my post I noticed that this was only occurring on one of my
MX's and that MX was the one I'd had LDAP aliasing enabled on for testing.
After turning LDAP aliasing off the problem went away.
I don't quite understand why/how this would affect it?
I'm currently running Courier 0.43.1.
Gabriel Ambuehl wrote:
Hi Jerome Bullert,
you wrote.
JB> We can tell ourselves that the chance of "[EMAIL PROTECTED]"
JB> successfully entering the password of "[EMAIL PROTECTED]" is remote,
JB> but it's probably not as remote as we'd like to think. In this scenario,
JB> since we know that both
Vincent - it's like this...
When you do a makealiases or something similar on one system, it rewrites
the files - on the other system, it has handles open to files which have
been essentially "deleted" and rewritten - so they are no good - when it
tries to read it will fail.
You would need to res
Systems Administrator wrote:
On Mon, 10 Nov 2003, Jerome Bullert wrote:
Most mail users are not used to entering the fully qualified email
address as the "username", when they've been taught that the "username"
is that portion of the email address before the "@" sign, and the
Hi crew,
I am migrating from an older server, to a freshly built box. I have
migrated my LDAP database where I am currently successfully running 0.41
on the old server and 0.44 on the new server. I am doing virtual domains
and the only auth module I am using is authldap. Most config files are
near
Mitch (WebCob) wrote:
Perhaps a dumb question, or two...
To create new dat files and invalidate the old file handles the make*
scripts have to be run - the script which calls these could call all the
appropriate courier restarts - couldn't it? In the window between these new
events, the temporary
Saxon Jones writes:
Thanks. Since my post I noticed that this was only occurring on one of my
MX's and that MX was the one I'd had LDAP aliasing enabled on for testing.
After turning LDAP aliasing off the problem went away.
I don't quite understand why/how this would affect it?
I'm currently run
Drew Gibson writes:
My question is:-
What accounts does Courier authenticate through the pam.d/courier module?
Nothing gets authenticated through pam.d/courier.
Courier uses only the following pam services: imap, imaps, pop3, pop3s,
webmail, and smtp.
Will it only authenticate mail accounts fo
Sam Varshavchik wrote:
Drew Gibson writes:
My question is:-
What accounts does Courier authenticate through the pam.d/courier
module?
Nothing gets authenticated through pam.d/courier.
Courier uses only the following pam services: imap, imaps, pop3,
pop3s, webmail, and smtp.
Will it only au
16 matches
Mail list logo
