Bug 57083 - [PATCH] Update mail/postfix to 2.0.16
Summary: [PATCH] Update mail/postfix to 2.0.16
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-22 10:30 UTC by osa
Modified: 2003-10-01 20:56 UTC (History)
1 user (show)

See Also:

Attachments
file.diff (3.57 KB, patch)
2003-09-22 10:30 UTC, osa 		no flags Details | Diff
postfix.patch (3.03 KB, patch)
2003-10-01 16:11 UTC, Vivek Khera 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description osa 2003-09-22 10:30:16 UTC 
	Update mail/postfix to 2.0.16
	Also include Patch to black-list domain names by their
	mail servers (such as Verisign's mail sink) or by their
	DNS servers (second revision: don't defer mail when DNS
	lookup fails; lookup grandparent NS records).
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2003-09-27 04:15:22 UTC 
Hi,

Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/57083.
Do you approve this update?

Edwin

-- 
Edwin Groothuis
edwin@freebsd.org
http://www.mavetju.org
Comment 2 Vivek Khera 2003-09-29 15:19:36 UTC 
>>>>> "EG" == Edwin Groothuis <edwin@freebsd.org> writes:

EG> Hi,
EG> Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/57083.
EG> Do you approve this update?

Sorry for taking so long... I hadn't realized the ports freeze was
lifted, since I keep getting kicked off the ports@ mailing list for
some reason.

The postfix-2.0-ns-mx-acl-patch.gz conflicts with the TLS patch.  when
the SSL+TLS patch is applied, it fails.  there needs to be a way to
turn off the postfix-2.0-ns-mx-acl-patch for this case.

curiously, the IPV6+TLS patch has no conflicts...

So, no, I cannot approve this patch without a resolution to the patch
conflict.  I think that the ns-mx-acl patch should be another knob on
the configure page, or something you define on the command line.

If you want to revise it let me know, else I'll submit a patch without
the ns-mx-acl bits, since I don't use them.

Thanks.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.                Khera Communications, Inc.
Internet: khera@kciLink.com       Rockville, MD       +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera   http://www.khera.org/~vivek/
Comment 3 Vivek Khera 2003-10-01 16:11:05 UTC 
>>>>> "SAO" == Sergey A Osokin <osa@FreeBSD.org> writes:

>> The postfix-2.0-ns-mx-acl-patch.gz conflicts with the TLS patch.  when
>> the SSL+TLS patch is applied, it fails.  there needs to be a way to
>> turn off the postfix-2.0-ns-mx-acl-patch for this case.

SAO> OK. Here is another version of patch without of
SAO> postfix-2.0-ns-mx-acl-patch.gz

Actually, it turns out that the conflict was with the TLS patch and
postfix 2.0.16.  If you update the TLS patch to the latest one for
postfix 2.0.16, your original patch works fine.  Here's your original
patch updated, ready for committing.
Comment 4 Sergey A. Osokin freebsd_committer freebsd_triage 2003-10-01 20:55:59 UTC 
State Changed
From-To: open->closed

Committed with modifications from maintainer, thanks!