OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: Root relay issue

From: /dev/rob0 (rob0gmx.co.uk)
Date: Thu Jul 20 2006 - 14:44:30 CDT


Top-posting makes the discussion much harder to follow; please don't.

I wrote:
> > rootmydomain.com permit_mynetworks,reject
>
> This is not what the RESTRICTION_CLASS_README told you to do! The
> access(5) lookup has to be a single result, that is, a restriction
> class.

On Thursday 20 July 2006 14:25, Johnson, S wrote:
> Hmm. I'm lost...?

And I wrote before looking at RESTRICTION_CLASS_README. There is, in
fact, an example just like yours. I thought the access(5) lookup result
had to be a single restriction.

> I'm sure it's rootmydomain having the bulk of issues (According to
> the header anyway). I do see a small amount of spam coming in at

WHICH header? Delivered-To: ? X-Original-To:? Logs are better because
there's no doubt.

> postmaster, but it's not as big... YET. =/ (Can I have 5 minutes
> alone with these spammers??)
>
> The maillog has nothing like that at all. I forgot to mention that I
> did check the log and it does not like the check_recipient_access. I
> get an error:
> Jul 20 10:50:26 www postfix/smtpd[8837]: warning: restriction
> `check_recipient_access' after `check_relay_domains' is ignored

Okay, your lookup is ignored. Also, your "check_relay_domains" is
deprecated.

At this point, as Noel said, we need to see "postconf -n" and the
complete logs for one such mail that you'd like to reject. Since
"postconf -n" excludes your restriction classes, you should also show
those from your main.cf, as well as the relevant contents of any files
to which they refer.
--
    Offlist mail to this address is discarded unless
    "/dev/rob0" or "not-spam" is in Subject: header