Hi Postfix community,

Does anybody know the original reason of why there is no way to adjust response code for Alias expansion error (internal loop detected) in Postfix settings?

Log: unreasonable virtual_alias_maps map nesting for j....@example.com -- message not accepted, try again later

Response:  host outgoing-node-01.example.com[192.0.2.10] said: 451 4.6.0 Alias expansion error (in reply to end of DATA command)

From my understanding this is quite permanent configuration error and it should result in some 5xx error code instead of 451 one which hardcoded in set in cleanup of Postfix, as it doesn't going to be resolved on it's own, it requires fixing of configuration of alias in database, file or whatever.

I checked docs as well as src code and as far as I see there is no way to adjust it postfix/postfix/src/cleanup/cleanup_map1n.c at 646ffe205bca7ae89c88e6ef5686706e0ef768f4 · vdukhovni/postfix <https://github.com/vdukhovni/postfix/blob/646ffe205bca7ae89c88e6ef5686706e0ef768f4/postfix/src/cleanup/cleanup_map1n.c#L129-L139>

More over issue has significantly bigger impact due to nature of how verify (double-bounce) works - it checks deliverability up to "RCPT TO:", but alias expansion done only at DATA, so there is no way to not accept such email. Is there is any reasons why alias expansion not done at RCPT TO? From my view it's should be done here.

Issue reproduce when you have 2 MTAs when first MTA is incoming MX and second MTA is outgoing node that doing actual alias expansion and delivery.

Moving alias expansion to first MTA is possible but it still doesn't solve issue in general, as I don't want to answer to external MTA with 451 soft fail error in this case.

--
Regards,
Dmytro Alieksieiev
DevOps Engineer
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org

Reply via email to