Bug 474541
Summary: | Duplicate recipient filter fails on virtual alias expansion | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Eric Janz <eric.janz> |
Component: | postfix | Assignee: | Jaroslav Škarvada <jskarvad> |
Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 5.2 | CC: | azelinka, sputhenp, tao, vincew |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | postfix-2.3.3-5.el5 | Doc Type: | Bug Fix |
Doc Text: |
Prior to this update, the "aggresive" recipient duplicate elimination was broken. This could lead to reception of multiple copies of e-mails for users that were specified in multiple virtual aliases. Now if the enable_original_recipient configuration option is set to "no" the recipient duplicate elimination will work correctly and users will not receive multiple copies of e-mails.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-01-08 07:26:54 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 743405, 807971 |
Description
Eric Janz
2008-12-04 11:40:50 UTC
Just to be sure, the aliases are specified in virtual alias table? And is the enable_original_recipient option disabled? Yes, we are using in main.cf virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf # cat /etc/postfix/mysql_virtual_alias_maps.cf user = blablabla password = blablablapassword hosts = localhost dbname = postfix table = alias select_field = goto where_field = address and SELECT * FROM `postfix`.`alias` where address like 'user%'; returns: address goto ------ ----- user1 user4,user1 user4 user4 I tried with enable_original_recipient set to NO and the result is the same as when I dont set it (default is YES, AFAIK) In our old system this does not happen with the same setup although the enable_original_recipient is not explicitly disabled. Best Regards, Eric Janz That's odd, with postfix-2.1.5-4.2.RHEL4 I'm getting duplicates unless the option is disabled. Can you please try this package to see if it's better? It includes the 20070520 patch. http://people.redhat.com/mlichvar/tmp/postfix-474541/ Hi Miroslav, it works fine. With your package and the option enable_original_recipient = no the duplicates have disappeared. Thanks a lot, Best Regards, Eric Janz This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?". Can you please review this issue as soon as possible. We are now using Miroslav's postfix package and can not update to any newer version until this problem is fixed. Best Regards, Eric Janz This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?". This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Prior to this update, the "aggresive" recipient duplicate elimination was broken. This could lead to reception of multiple copies of e-mails for users that were specified in multiple virtual aliases. Now if the enable_original_recipient configuration option is set to "no" the recipient duplicate elimination will work correctly and users will not receive multiple copies of e-mails. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0054.html |