Bugzilla Bug 48796

Postfix 2.1 was released today, see Changelog for full list of changes. It's
long.

Warning: Postfix 2.1 will read old queue files, but older Postfix versions WILL
NOT read queue files from 2.1. BE VERY CAREFUL IF YOU DECIDE TO DOWNGRADE WHEN
TESTING EBUILDS RESULTING FROM THIS REQUEST. (I assume you would need to
disable additions to the queue while allowing files still in the queue to be
processed)

Reproducible: Always
Steps to Reproduce:

postfix 2.1 won't be going in until the TLS and IPV6 patches catch up.

It appears that the TLS/IPv6 patch has caught up!
http://www.ipnet6.org/postfix/

Will we see a postfix 2.1.0 ebuild soon, or should I just write my own?

Created an attachment (id=30279) [details]
postfix-2.1.0.ebuild

Attached is a modified postfix-2.0.19-r2.ebuild. I took out vda, postgre,
ns-mx-acl patches. Emerge fine with USE="+ipv6 -ldap +maildir -mbox +mysql +pam
+sasl +ssl"
ipv6: not tested
maildir: OK
mysql: OK
pam: OK
sasl: OK (pwcheck_method: auxprop)
ssl: OK
I am using courier-imap.

I actually have everything written and ready to be committed. I'll get them in
in the next few days.  Stay tuned.

Created an attachment (id=30630) [details]
Postfix 2.1 announce e-mail

For a very brief overview of the new features

Yesterday Postfix 2.1.1 / 2.1 patch 1 was released to fix a problem with 2.1. 
Here is the announce e-mail:

Subject: Postfix 2.0 patch 01
Date: Mon, 3 May 2004 16:26:55 -0400 (EDT)
From: wietse@porcupine.org (Wietse Venema)

Patch 01 fixes a signal 11 problem in the check_policy_service
feature when SASL support is compiled in but turned off in the
SMTP server (smtpd_sasl_auth_enable = no).

     1599 May  3 13:33 postfix-2.1-patch01.gz
   321214 May  3 13:31 postfix-2.1.1.HISTORY
    26665 Apr 22 18:57 postfix-2.1.1.RELEASE_NOTES
  1969624 May  3 13:33 postfix-2.1.1.tar.gz
      152 May  3 13:34 postfix-2.1.1.tar.gz.sig

The same problem is fixed in snapshot 20040504:

   324659 May  3 13:31 postfix-2.2-20040504.HISTORY
      556 Apr 21 21:14 postfix-2.2-20040504.RELEASE_NOTES
  1989111 May  3 15:47 postfix-2.2-20040504.tar.gz
      152 May  3 15:48 postfix-2.2-20040504.tar.gz.sig

Besides this, 2.1.1 and 20040504 fix some documentation erratae.

Available via ftp://ftp.porcupine.org/mirrors/postfix-release/index.html
and soon via the mirror sites listed at http://www.postfix.org/.

Wietse

I'm aware.  This is going to be in soon.  Stay tuned.

*** Bug 49078 has been marked as a duplicate of this bug. ***

renamed ebuild to postfix-2.1.1.ebuild to test install of patchlevel-01,
appears to work ok.

So...  anyone out there will to release the ebuild to the general public?
There are some major enhancements in 2.1 that many have been waiting impatiently for.

Created an attachment (id=31550) [details]
postfix-2.1.1.ebuild

postfix-2.1.1.ebuild
modified ebuild to download only incremental patchlevels.
vda patch: postfix-2.1.1
TLS patch: pfixtls-0.8.18-2.1.0-0.9.7d
IPv6 patch: ipv6-1.24-pf-2.1.1.patch.gz
TLS + IPv6 patch: tls+ipv6-1.24-pf-2.1.1.patch.gz

user note:
save target as /usr/local/net-mail/postfix/postfix-2.1.1.ebuild
# cp -r /usr/net-mail/postfix/files /usr/local/net-mail/postfix/
# ebuild /usr/local/net-mail/postfix/postfix-2.1.1.ebuild digest

OOPS:
save target as /usr/local/net-mail/postfix/postfix-2.1.1.ebuild
# cp -r /usr/net-mail/postfix/files /usr/local/net-mail/postfix/
# ebuild /usr/local/net-mail/postfix/postfix-2.1.1.ebuild digest

should be:
save target as /usr/local/portage/net-mail/postfix/postfix-2.1.1.ebuild
# cp -r /usr/portage/net-mail/postfix/files /usr/local/portage/net-mail/postfix/
# ebuild /usr/local/portage/net-mail/postfix/postfix-2.1.1.ebuild digest

Anyone know when this will enter portage?

Please add qshape tool to installation.

postfix-2.1.1.ebuild:

[...]

src_install () {
	/bin/sh postfix-install \
[...]
	# Install an rmail for UUCP, closing bug #19127.
	dobin auxiliary/rmail/rmail
        
        # Install qshape tool.
        dobin auxiliary/qshape/qshape.pl
[...]

If this ver. is not in portage anytime soon, then why not add the newest
postfix 2.0.20 to portage, as unstable at the very least?! Both were released
20040503, its been 21 days after all... (yeah I'm a spoiled Gentoo user ;)

I see that I was wrong above - the versions were released earlier (can't find
the date though)...

I'm sorry for "spamming" my embarrasing mistakes out!
This bug says "Opened: 2004-04-23 09:10 PST", the day of the postfix 2.1 release, so it's been one month today. 
Postfix 2.1.1 was released 2004-05-04 - 20 days ago. 
What is the status of releasing the 2.1.1 ebuild? Should I use the attached ebuild on my private mailserver - or is the release just arround the corner?

Or should I open a new ebuild request for the 1 month old Postfix 2.0.20?

I setup an overlay directory (in make.conf), downloaded the ebuild attached to
this call, added the qhape install line (That's SUCH a usefull tool) and ripped
the '~' out the keywords statement (to stop portage from trying to downgrade
later).
Everything seems to be working Ok for me.....
This new version should (with greylisting and verify) cut out 90% of the mail
coming into my systems.
I continue to wonder exactally how long a 'few days' (see comment #4) is ; )

*taps this bug to get it some attention*

comment #18
Looks like a few days is more then 35 days.

I'm using the posted 2.1.1 ebuild with the qshape change. Seems ok.

Seriously, doesn't gentoo have some mechanism so that these kind of things
don't happen?  There have been ebuilds available on bugzilla for over a month
but no gentoo devs can put them in portage for testing by mere mortals?  A
month and a half after the postfix 2.0 release I would expect it to be
available and marked stable by now.

To answer the last question, we're currently looking for some people to help
with the backlog of mail-related bugs that we have.  If you're interested,
please mail recruiters@gentoo.org with a list of qualifications.

I'm trying to contact the maintainer, who I'm told is in the process of
moving right now.  Ping this bug if you haven't heard back in 24 hours or so.

Is there any reason why this ebuild won't install the "sample" files:

# postconf sample_directory
sample_directory = /usr/share/doc/postfix-2.1.1/sample

# ls -l /usr/share/doc/postfix-2.1.1/sample
ls: /usr/share/doc/postfix-2.1.1/sample: No such file or directory

I see that the "sample" stuff is specified in the ebuild but I'm not sure why it's not being "installed"

comment #22 : quoted from RELEASE_NOTES:
[quote]
[Feature 20040331] Complete documentation rewrite. All parameters
are now described in postconf(5), and all commands and daemons are
shown in their proper context in the OVERVIEW document.
- All documents come as HTML and ASCII text.
- All HTML documents have hyperlinks for every parameter name,
  for every Postfix manual page, and for every README file.
- All documents specify what feature is available in what release.
- The sample-*.cf configuration files no longer exist. The information
  is now available in HTML documents, README files and UNIX man pages).
- The mumble_table example configuration files no longer exist.
[/quote]
so I guess we can take that line out to avoid confusion.

Created an attachment (id=32666) [details]
new version with qshape and without sample dir...

Attached is a new version of the postfix ebuild that adds the qshape tool and
removes any reference to the 'sample' dir.  From what I can tell, there is no
reason for this not to be included in Gentoo.

Anybody know what the deal is w/ the lack of postgres support?  No current
patch I take it?  I'm not too keen on adding a portage package with _less_ 
functionality than the current version.

Also, if anybody wants to make the changes to the ebuild before I get around
to it, the new postfix ebuild needs to have optional mailwrapper support
added to it (just like in 2.0.19-r3).

Created an attachment (id=32681) [details]
new ebuild with postgres and mailwrapper support

added postgres back and optional mailwrapper (code from
postfix-2.0.19-r3.ebuild).
postgres support is not tested.

Added to CVS.  Thanks to all who worked on this ebuild.