Sam Varshavchik <[EMAIL PROTECTED]> writes:
> Lloyd Zusman writes:
>
>> Hmm ... what if I do this:
>> file contents
>>
>> defaultdomain defdom.com
>> me home.defdom.com (note the "home" subdomain)
>> locals
Lloyd Zusman writes:
Hmm ... what if I do this:
file contents
defaultdomain defdom.com
me home.defdom.com (note the "home" subdomain)
locals (empty)
hosteddomains defdom.com and o
Sam Varshavchik <[EMAIL PROTECTED]> writes:
> Lloyd Zusman writes:
>
>> I used webadmin to move that one domain from the "Local domains" section
>> to the "Locally hosted domains" section (i.e., from "locals" to
>> "hosteddomains"). After webadmin did its job, I expected to see an
>> empty "local
Mike Bydalek writes:
Now I have Courier successfully authenticating against either Kerberos
or LDAP. The problem is, when it authenticates against Kerberos, it
pulls all of the homedirectory, etc. information from the system. What
I need it to do is pull everything from LDAP, yet authenticat
Lloyd Zusman writes:
I used webadmin to move that one domain from the "Local domains" section
to the "Locally hosted domains" section (i.e., from "locals" to
"hosteddomains"). After webadmin did its job, I expected to see an
empty "locals" file in my courier directory. However, webadmin delete
Sam Varshavchik <[EMAIL PROTECTED]> writes:
> Lloyd Zusman writes:
>
>> The only way I can think of to make this happen would be for me to put
>> my "defaultdomain" entry also into "hosteddomains". If I do that,
>> should I remove it from "locals", or do I need to keep it both in
>> "locals" and
Sam Varshavchik <[EMAIL PROTECTED]> writes:
> Lloyd Zusman writes:
>
>> The only way I can think of to make this happen would be for me to put
>> my "defaultdomain" entry also into "hosteddomains". If I do that,
>> should I remove it from "locals", or do I need to keep it both in
>> "locals" and
Jeff Jansen <[EMAIL PROTECTED]> writes:
> Lloyd Zusman wrote:
>>
>> [ ... ]
>>
>> A related question: can "locals" be completely empty (or non-existent),
>> as long as all my domains appear in "hosteddomains"?
>
> Sure - you don't need a local domain. Everything can be a hosteddomains
> - just
Lloyd Zusman asfast.com> writes:
>
> Jay Lee pbu.edu> writes:
> >
> > [ ... ]
> >
> > If you know the IP Addresses of the servers that are sending the invalid
> > email you may be able to use smtpaccess to turn off the dns checks for
> > these addresses:
> >
> > x.x.x.x allow,BOFCHECKDNS=0
>
Jay Lee pbu.edu> writes:
>
> Lloyd Zusman wrote:
> >
> > [ ... ]
> >
> > I'm already using SPF, and I'm telling courier not to reject the mail when
> > SPF checks fail, but rather, to just have courier write the SPF-Received
> > headers, which I then check in some home-grown courierfilter module
Hello.
Currently I have Courier setup for LDAP authentication. What we started
to do was implement Kerberos authentication in our network. After
reading around, it seems the only way to get Courier to authenticate
using Kerberos is by using the authpam module. In my authdaemonrc, I
changed
Lloyd Zusman wrote:
Jay Lee pbu.edu> writes:
Lloyd Zusman wrote:
[ ... ]
I'd like to be able to tell courier that this small handful of
internally known domain names from work be treated as being legal, even
though the DNS test fails for them in the "outside world" ... and that
all other m
Jay Lee pbu.edu> writes:
>
> Lloyd Zusman wrote:
> >
> > [ ... ]
> >
> > I'd like to be able to tell courier that this small handful of
> > internally known domain names from work be treated as being legal, even
> > though the DNS test fails for them in the "outside world" ... and that
> > all o
Lloyd Zusman wrote:
I'm using the BOFHCHECKDNS="1" setting in the esmptd configuration file
to automatically reject email from domains that cannot be verified by
DNS.
However, is there a way to configure courier to automatically reject
mail from most illegal domains, but to allow it to come thro
I'm using the BOFHCHECKDNS="1" setting in the esmptd configuration file
to automatically reject email from domains that cannot be verified by
DNS.
However, is there a way to configure courier to automatically reject
mail from most illegal domains, but to allow it to come through from
a small, prec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sam Varshavchik wrote:
> Nope. If FAM support is available, it gets compiled and used.
>
> The fault is really with Suse. If it doesn't use FAM, it should NOT
> even install the client libraries. It is a packaging error to install
> the client libr
Jeff Jansen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lloyd Zusman wrote:
In order to keep my maildrop processing rules simple and consistent, and
for other reasons which I won't go into here, I'd like, if possible, for
the "defaultdomain" to also get processed with "@domain.tld" at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lloyd Zusman wrote:
> In order to keep my maildrop processing rules simple and consistent, and
> for other reasons which I won't go into here, I'd like, if possible, for
> the "defaultdomain" to also get processed with "@domain.tld" attached.
>
> The
18 matches
Mail list logo
