Robert Moskowitz wrote:

I am running a new mailserver virtual domain environment with postfix
and mysql for the virtual domain definitions.  amavis-new seems to be
rejecting all emails for my one domain not a sub domain of my main
one.  That is, my domain (as you can see from my email addr) is
htt-consult.com and I have not problems processing emails for
labs.htt-consult.com addresses.  However I am seeing in the logwatch
email in the amavis-new section:

 **Unmatched Entries**
        1   (26010-02-3) Open relay? Nonlocal recips but not
originating:res...@communaljob.com
        1   (27713-04-4) Open relay? Nonlocal recips but not
originating:res...@communaljob.com
        1   (24487-05-4) Open relay? Nonlocal recips but not
originating:res...@communaljob.com
        1   (26339-01-2) Open relay? Nonlocal recips but not
originating:res...@communaljob.com
        1   (27916-03-3) Open relay? Nonlocal recips but not
originating:res...@communaljob.com

Messages a plenty.

These are warnings, not rejects.

Assuming that domain communaljob.com is not one of your local domains,
the problem is that mail was not considered to be originating from
your site. This means that you either forgot to list all your internal
IP address spaces in the @mynetworks list, or in a more difficult setup
where your users are submitting authenticated mail to your MSA from
remote IP addresses, in which case you need to configure a dedicated
policy bank with 'originating=>1' property for such mail submissions.

A background story:

  A combination of msgs.originating and msgrcpt.is_local tells a
  direction a message is traveling:

  originating is_local
N N open relay (probably misconfigured @local_domains_maps
                                or $originating flag not set)
      N        Y    inbound message
      Y        N    outbound message
      Y        Y    internal message (inside or authenticated -> inside)

  Note that a direction is a per-recipient property, a multi-recipient
  message can be outbound for some recipients and internal for others
  at the same time.


No spamassasin section in logwatch, interestingly. Where do I allow
this to work?

Perhaps you have SpamAssassin disabled by @bypass_spam_checks_maps,
or maybe by a non-default @spam_scanners.

  Mark

Reply via email to