EFA5 Greylisting toggle, does not change main.cf

[e-d-i-t]

My batchedSMTP mail connection failed as port 2501 was not replying when greylisting is off.
So when I looked in mail.log I saw it was still probing port 2501 for greylisting.

MAIN.CF
smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination, reject_non_fqdn_recipient, reject_unknown_recipient_domain, check_recipient_access hash:/etc/postfix/recipient_access, check_policy_service inet:127.0.0.1:2501, reject_unverified_recipient

And I changed this manually to:

smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination, reject_non_fqdn_recipient, reject_unknown_recipient_domain, check_recipient_access hash:/etc/postfix/recipient_access

[shawniverson]

This is strange. I am able to toggle greylisting via eFa-Configure and the check_policy_service inet:127.0.0.1:2501 appears and drops off like is should. Looking at the code I don't see anything obvious that would cause this to happen.

[e-d-i-t]

Maybe because I was still using an updated version of a beta now being 5.0.0.8?
Do I need to re-install fresh since 5 is live?
I can always do a fresh new virtual machine install to check if it alters the main.cf in postfix.

[shawniverson]

Shouldn't have to, the updates are cumulative, so switching from beta to release shouldn't have caused this sort of issue.