Commit graph

12 commits

Author SHA1 Message Date
Dirk Meyer
e15a13a912 - make pkg-message prefix aware
- use rcng style start script
PR:		142799
Submitted by:	Sevan Janiyan
2010-01-16 12:39:56 +00:00
Dirk Meyer
2589e2491c - conversion to rc_subr and OPTIONS style
PR:		100773
Submitted by:	marck (Dmitry Morozovsky)

- keep compatibility checks
- make optiosn overriadeabel flor slave ports
- force UNIQUENAME to avoid conflichts between ports
2006-07-25 11:27:44 +00:00
Dirk Meyer
eaf40e832a - cleanup 2006-05-19 04:32:01 +00:00
Dirk Meyer
bb8719d37f - use DOCSDIR
- new option STANDALONE_POP3
Submitted by:   osa

- USE_REINPLACE for all options
- cleanup targets
Submitted by:   dinoex
2003-12-04 03:28:54 +00:00
Dirk Meyer
867beb1a9c - Update to 0.5.9
- Fix bug found by nunotex@pt-quorum.com
- discussion at http://marc.theaimsgroup.com/?l=popa3d-users&m=104354856516116&w=2
- Extend Documentation
2003-01-28 22:04:19 +00:00
Dirk Meyer
9d0fc5229e Suggested by: marck@woozle.rinet.ru
- Use of /var/empty is it exists.

- Split defines to make portlint happy.
- record installation option SMTP_AFTER_POP3 better
PR:		46802
2003-01-08 06:45:48 +00:00
Dirk Meyer
59aa118e3a - Fix creation of chroot dir again, the packed did not created it. 2002-01-17 21:51:55 +00:00
Dirk Meyer
154e59864e - moved chroot dir from /var/empty to ${PREFIX}/empty
- create chroot dir by default
- bumped PORTREVISION
2002-01-13 10:39:01 +00:00
Dirk Meyer
12423e6cf0 - Update popa3d-0.5
- Cleanup POP_AFTERR_SMTP patches
- honor CFLAGS

- claim maintainership
 no response from previous maintainer since August 2001
2002-01-12 13:04:42 +00:00
Dirk Meyer
77b231c638 Added new functionality:
SMTP_RELAY aftersucessfull POP3 authentification.

Option:
	SMPT_AFTER_POP=yes

Documentation and popauth.m4 is included in this port.

PR:		29906
2001-09-16 09:43:13 +00:00
Michael Haro
3acc3fb9e4 various port fixes
PR:		17180
Submitted by:	maintainer
2000-04-01 03:39:48 +00:00
Chris D. Faulhaber
dc2053998b popa3d is a POP3 server with the following goals:
1. Security (to the extent that is possible with POP3 at all, of course).
2. Reliability (again, as limited by the mailbox format and the protocol).
3. RFC compliance (slightly relaxed to work with real-world POP3 clients).
4. Performance (limited by the more important goals, above).

PR:		16652
Submitted by:	Sergey Samoyloff <techline@hotmail.ru>
2000-02-19 13:21:54 +00:00