[opensuse] postfix not using access
openSUSE 13.1 x86_64 postfix-2.9.6-7.4.1.x86_64 Recently solved an apache2 log problem w/wpad.dat entries by changing my no-ip.org account from wildcard to non-wildcard. May or may not be related, but ever since that date postfix appears to not be utilizing /etc/postfix/access: main.cf: smtpd_sender_restrictions = hash:/etc/postfix/access smtpd_client_restrictions = check_client_access hash:/etc/postfix/access, permit smtpd_recipient_restrictions = permit_mynetworks, ... check_client_access hash:/etc/postfix/access, ... permit access: ... <address> REJECT spam not accepted here <address> REJECT spam not accepted here <address> REJECT spam not accepted here <address> REJECT spam not accepted here <address> REJECT spam not accepted here <address> REJECT spam not accepted here ... My mail logs contained entries "REJECT spam not accepted here" but no more. A search of the mail logs for <address> shows no rejections with any code/reason. What has happened and why is "access" no longer being used by postfix. Yes, I run "postmap /etc/postfix/access" after every edit and restart postfix service. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan:
openSUSE 13.1 x86_64 postfix-2.9.6-7.4.1.x86_64
Recently solved an apache2 log problem w/wpad.dat entries by changing my no-ip.org account from wildcard to non-wildcard. May or may not be related, but ever since that date postfix appears to not be utilizing /etc/postfix/access:
main.cf: smtpd_sender_restrictions = hash:/etc/postfix/access smtpd_client_restrictions = check_client_access hash:/etc/postfix/access, permit smtpd_recipient_restrictions = permit_mynetworks, ... check_client_access hash:/etc/postfix/access, ... permit
Using the same access file for senders, clients and recipients? Better to use separate files. What is your network config in main.cf?
access: ... <address> REJECT spam not accepted here <address> REJECT spam not accepted here <address> REJECT spam not accepted here <address> REJECT spam not accepted here <address> REJECT spam not accepted here <address> REJECT spam not accepted here ...
My mail logs contained entries "REJECT spam not accepted here" but no more. A search of the mail logs for <address> shows no rejections with any code/reason.
Hard to tell for sure without context but it appears that postfix did read access. postfix will generally complain loudly if it can't read a file given it in main.cf. Also. REJECT does not appear to be a valid action. For a reject action you should use a numerical rejection code. Postfix should log complaints about invalid actions in access, etc. Read the access file or the postfix documentation in /usr/share/doc/packages/postfix*/ for more info.
What has happened and why is "access" no longer being used by postfix. Yes, I run "postmap /etc/postfix/access" after every edit and restart postfix service.
What is it doing differently from before? Rejecting mail? Not rejecting mail? This is perhaps best asked on the postfix-users mailing list where the experts are. You must subscribe to post anything. But be sure to Read The Fine Manual(s), the debugging how-to and the debugging readme first. Subscribe at www.postfix.org/lists.html or send mail to majordomo@postfix.org with the subject "subscribe postfix-users" When you post the question include the output of postconf -n (or postconf -nf if your main.cf contains long lines) and access because that's the first thing they'll want to look at. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* jdebert
Patrick Shanahan:
openSUSE 13.1 x86_64 postfix-2.9.6-7.4.1.x86_64
Recently solved an apache2 log problem w/wpad.dat entries by changing my no-ip.org account from wildcard to non-wildcard. May or may not be related, but ever since that date postfix appears to not be utilizing /etc/postfix/access:
main.cf: smtpd_sender_restrictions = hash:/etc/postfix/access smtpd_client_restrictions = check_client_access hash:/etc/postfix/access, permit smtpd_recipient_restrictions = permit_mynetworks, ... check_client_access hash:/etc/postfix/access, ... permit
Using the same access file for senders, clients and recipients? Better to use separate files.
you are right, I missed that. Removed.
What is your network config in main.cf?
relay_domains = $mydestination, hash:/etc/postfix/relay myhostname = wahoo.wahoo.no-ip.org mydestination = $myhostname,localhost.$mydomain,$mydomain mynetworks_style = subnet disable_dns_lookups = no relayhost = smtp-server.indy.rr.com
access: ... <address> REJECT spam not accepted here <address> REJECT spam not accepted here ...
My mail logs contained entries "REJECT spam not accepted here" but no more. A search of the mail logs for <address> shows no rejections with any code/reason.
Hard to tell for sure without context but it appears that postfix did read access. postfix will generally complain loudly if it can't read a file given it in main.cf.
Also. REJECT does not appear to be a valid action. For a reject action you should use a numerical rejection code. Postfix should log complaints about invalid actions in access, etc. Read the access file or the postfix documentation in /usr/share/doc/packages/postfix*/ for more info.
What has happened and why is "access" no longer being used by postfix. Yes, I run "postmap /etc/postfix/access" after every edit and restart postfix service.
What is it doing differently from before? Rejecting mail? Not rejecting mail?
Not rejecting mail
This is perhaps best asked on the postfix-users mailing list where the experts are. You must subscribe to post anything. But be sure to Read The Fine Manual(s), the debugging how-to and the debugging readme first.
Subscribe at www.postfix.org/lists.html or send mail to majordomo@postfix.org with the subject "subscribe postfix-users"
When you post the question include the output of postconf -n (or postconf -nf if your main.cf contains long lines) and access because that's the first thing they'll want to look at.
If the above doesn't ring any bells, I will go there next. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan
* jdebert
[01-24-14 22:22]: [...] Also. REJECT does not appear to be a valid action. For a reject action you should use a numerical rejection code. Postfix should log complaints about invalid actions in access, etc. Read the access file or the postfix documentation in /usr/share/doc/packages/postfix*/ for more info.
ps: REJECT ACTIONS Postfix version 2.3 and later support enhanced status codes as defined in RFC 3463. When no code is specified at the beginning of the text below, Postfix inserts a default enhanced status code of "5.7.1" in the case of reject actions, and "4.7.1" in the case of defer actions. See "ENHANCED STATUS CODES" below. tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan
* Patrick Shanahan
[01-24-14 23:13]: * jdebert
[01-24-14 22:22]: [...] Also. REJECT does not appear to be a valid action. For a reject action you should use a numerical rejection code. Postfix should log complaints about invalid actions in access, etc. Read the access file or the postfix documentation in /usr/share/doc/packages/postfix*/ for more info.
ps: REJECT ACTIONS Postfix version 2.3 and later support enhanced status codes as defined in RFC 3463. When no code is specified at the beginning of the text below, Postfix inserts a default enhanced status code of "5.7.1" in the case of reject actions, and "4.7.1" in the case of defer actions. See "ENHANCED STATUS CODES" below.
postfix injects "554 5.7.1"
2014-01-24T20:20:27.299010-05:00 wahoo postfix/smtpd[27537]: NOQUEUE:
reject: RCPT from pqr.highdqr.us[198.98.114.173]: 554 5.7.1
* Patrick Shanahan
* jdebert
[01-24-14 22:22]: Patrick Shanahan:
openSUSE 13.1 x86_64 postfix-2.9.6-7.4.1.x86_64
Recently solved an apache2 log problem w/wpad.dat entries by changing my no-ip.org account from wildcard to non-wildcard. May or may not be related, but ever since that date postfix appears to not be utilizing /etc/postfix/access:
main.cf: smtpd_sender_restrictions = hash:/etc/postfix/access smtpd_client_restrictions = check_client_access hash:/etc/postfix/access, permit smtpd_recipient_restrictions = permit_mynetworks, ... check_client_access hash:/etc/postfix/access, ... permit
Using the same access file for senders, clients and recipients? Better to use separate files.
you are right, I missed that. Removed.
And this was the *problem*. Solved, tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
jdebert
-
Patrick Shanahan