1 Topic by Lexa83

  • Lexa83
  • Lexa83
  • Member
  • Offline
  • Registered: 2016-09-15
  • Posts: 67

Topic: Question/Thoughts?

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.5-1
- Linux/BSD distribution name and version: Ubuntu 16.04.1 LTS
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? YES
- Related log if you're reporting an issue:
====

I was having some issues and adjusted the my Recipient restrictions so permit_mynetworks is now before check_policy_service inet:127.0.0.1:7777

What are some of the repercussions I may see from doing this?

Thanks for your thoughts in advance

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,165

Re: Question/Thoughts?

Postfix applies the restrictions in specified order. So if 'permit_mynetworks' is placed before "check_policy_service inet:127.0.0.1:7777" (iRedAPD), all emails sent from clients listed in Postfix "mynetworks" parameter will bypass iRedAPD, that means: all iRedAPD don't work for them.