markd@macports.org wrote:

Jay Chandler <lists@sequestered.net> writes:

...

So I've built Postfix on my MacBook Pro, and it starts correctly.

However, when I try to relay mail via 587 submission to my colocated server, I get:

warning: run-time library vs. compile-time header version mismatch: OpenSSL 0.9.8 may not be compatible with OpenSSL 0.9.7

Followed quickly by a network error from the server: Sep 17 14:08:20 kwisatz postfix/smtpd[7902]: warning: network_biopair_interop: error reading 5 bytes from the network: Connection reset by peer Sep 17 14:08:20 kwisatz postfix/smtpd[7902]: lost connection after EHLO

from pool-MyIP.lsanca.dsl-w.verizon.net[MyIP]

...

I suspect the problem is that the port builds with one OpenSSL, but runs with another; the issue is I require TLS encryption for my 587 submissions, so this is kind of a showstopper until I can get this resolved...

And though it should go without saying, the colocated server is patched, current, and has no issues from other locations...

I'd be grateful for any assistance anyone can lend...

I see this has been reported before.

http://lists.macosforge.org/pipermail/macports-dev/2006-September/000070.htm...

Perhaps the answer is here. See the next 2-3 messages in the thread.

http://www.aet.tu-cottbus.de/pipermail/postfix_tls/2002/000314.html

If someone can use this information to make a fix to the portfile we can commit it. The postfix port needs a maintainer; it is a little bit out-of-date now that 2.4 is out.

Mark

If no one else wants it, I'll do it. It's apparent to me that it's a genuine bug-- I found that reference during my preliminary Google, and it doesn't appear anyone did anything with it after that. -- Jay Chandler / KB1JWQ Living Legend / Systems Exorcist Today's Excuse: SCSI Chain overterminated

Daniel J. Luke wrote:

On Sep 17, 2007, at 8:34 PM, Jay Chandler wrote:

...

If no one else wants it, I'll do it. It's apparent to me that it's a genuine bug-- I found that reference during my preliminary Google, and it doesn't appear anyone did anything with it after that.

I know that a past maintainer had a hard time figuring out why the bug appeared (ie, he/she was unable to reproduce it).

From a cursory look at the portfile, it doesn't look like it's doing anything different than my non-macports postfix install (which successfully builds/links against the macports openssl), so I'm not sure what's wrong.

Thanks for being willing to maintain the port and work to get this fixed!

No worries. The bug only manifests itself when using TLS-- unfortunately, since I'm a paranoid type I require TLS on my private stuff, so getting it working is going to definitely be a challenge. I'm afraid I'll have to deconstruct the port and go line by line through the source to figure out where it's making OpenSSL calls... -- Jay Chandler / KB1JWQ Living Legend / Systems Exorcist Today's Excuse: Plasma conduit breach