[Bug 232134] mail/pop3proxy: Fix OpenSSL build

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232134

Kai <freebsd_ports at k-worx.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |freebsd_ports at k-worx.org
 Attachment #200241|                            |maintainer-approval+
              Flags|                            |

--- Comment #11 from Kai <freebsd_ports at k-worx.org> ---
Created attachment 200241
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=200241&action=edit
pop3proxy-fix-build-with-openssl111.patch

This is another try to fix the build with OpenSSL 1.11+. The patch also does
following items:

- fix the wrong default location for the configuration file which prevented the
start via rc script (was "/docsis/etc/pop3proxyd.conf", now:
$PREFIX/etc/pop3proxyd.conf"). This resided probably a very long time in the
port.

- pet portlint a bit (not all items were covered, see further below for a
reason)

- fix the installation of the configuration files which were installed with the
execute bit set

- improve pkg-descr a bit to inform about pop3proxy's origin

Because mail/pop3proxy is derived from an earlier version of mail/up-imapproxy
the SSL patch was taken from there with some small modifications. I assume the
origin of the patch would be still Debian in that case.

I also went through the code and did some runtime tests after the issue with
the wrong configuration path was fixed. Interestingly pop3proxy doesn't seem to
support and initiate any SSL/TLS connections, it only worked properly when the
traffic was unencrypted.

Given those facts the port isn't really useful for actual use-cases because
there are more modern and secure solutions to setup a POP3 proxy if required.


QA:
~~~
poudriere (11.2-, 12.-RELEASE, 13.0-CURRENT at r341993 amd64 + i386) -> OK
portlint -> OK (with some warnings)

-- 
You are receiving this mail because:
You are the assignee for the bug.