Back on 2004/03/02 I sent an email to the maintainer of
ports/mail/teapop as qupoted below.
I guess you could say it is a maintainer timeout. <big evil g]rin> The
update is such a simple one that I don't need a fix in the tree - I
<have> the data needed to be up to date.
Some new users may not.
What is the appropriate way to deal with this?
<quote mail to maintainer>
Thanks to your very clean port of Teapop it was easy to bring it up to
date for my new server by just changing the version # in the makefile
and doing a make fetch so I could generate the hashes before doing a
Here is the content of distinfo now:
MD5 (teapop-0.3.8.tar.gz) = c322c20018663a1a9b7860966cbd4ed2
RMD160 (teapop-0.3.8.tar.gz) = fce3606748c33bd71134c09d8bb3e65aaabcdfa3
SHA1 (teapop-0.3.8.tar.gz) = 33632cc34148d88408bcb9afa5433c1a103f3cf5
I don't know what, if anything, is needed to complete a port update or
I would have sent you diffs but it is so clean that it is hardly saving
you much work.
Thanks for the original.
Kick it in or forget it. The release notes make it clear that it is a
good idea to update:
0.3.8 + Allow port to listen to in standalone to be changed with -P.
(Patch by: "Malte S. Stretz" <[hidden email]>)
! Reduce memory footprint
(Idea from: "Malte S. Stretz" <[hidden email]>)
+ Warn when teapop.passwd isn't found and default authentication
+ Introduce softlock, which gives the client an empty mailbox
instead of an error.
- Proper handling of CRLF in Maildirs.
(Found by: Matthew Sayler <[hidden email]>)
* Release date: 25-Nov-2003
<end release note>
From the land "down under": Australia.
Do we look <umop apisdn> from up over?
Do NOT CC me - I am subscribed to the list.
Replies to the sender address will fail except from the list-server.