Sorry, I'm still not getting it. The only thing I could see to do
differently was to put the long make makefiles line all on one line without
continuations. Thus,
make tidy \
&& make makefiles CCARGS="-DUSE_TLS -I/usr/local/include/eopenssl
-DUSE_SASL_AUTH -DDEF_SERVER_SASL_TYPE=\"dovecot\
David Benfell:
> make tidy \
> && make makefiles \
> CCARGS="-DUSE_TLS -I/usr/local/include/eopenssl
> -DUSE_SASL_AUTH -DDEF_SERVER_SASL_TYPE=\"dovecot\"" \
> AUXLIBS="-L/usr/local/lib/eopenssl -lssl -lcrypto" \
> && make \
> && sudo sh postfi
Hi,
My saga continues (the earlier thread had to do with linking to openssl
correctly under OpenBSD). As before, this is OpenBSD 5.9 and postfix 3.1.1.
I have built dovecot 2.2.24 from the upstream source and gotten it working
(hello, file descriptor limits! hello, user authentication weirdness!)
On Tue, Aug 23, 2016 at 11:27:39PM +0300, Nikolaos Milas wrote:
> On 20/8/2016 7:56 μμ, Sean Greenslade wrote:
>
> > ...
> > - Enable & configure per-user bayesan filtering
> > - Increase allowed storage space for bayesan databases
> > - Update a particular perl package to make SPF work (CentOS /
On 20/8/2016 7:56 μμ, Sean Greenslade wrote:
...
- Enable & configure per-user bayesan filtering
- Increase allowed storage space for bayesan databases
- Update a particular perl package to make SPF work (CentOS / RHEL
specific bug)
...
- Re-weight a bunch of internal rules, in particular the
> On 23 Aug 2016, at 20:44, David Benfell wrote:
>
> What I have now, which should not be considered complete because the dovecot
> part isn't working
I’d bet money on that being caused by a broken OpenSSL installation too. Check
your OpenSSL setup before you do *anything* else. References to
I'm insufficiently familiar with gmail's web interface (g!) and it
appears I sent my last only to Wietse, not the list.
-- Forwarded message --
From: David Benfell
Date: Tue, Aug 23, 2016 at 12:42 PM
Subject: Re: OpenBSD build 'OPENSSL_VERSION' undeclared
To: Wietse Venema
> On 23 Aug 2016, at 20:16, Wietse Venema wrote:
>
> David Benfell:
>> So now I have:
>>
>> make tidy \
>>&& make makefiles CCARGS="-DUSE_TLS
>> -I/usr/local/include/eopenssl/openssl
>
> Try: -I/usr/local/include/eopenssl
Looks like the OP made a typo when they orginally installed Ope
David Benfell:
> So now I have:
>
> make tidy \
> && make makefiles CCARGS="-DUSE_TLS
> -I/usr/local/include/eopenssl/openssl
Try: -I/usr/local/include/eopenssl
Wietse
I have OpenSSL from the port: openssl-1.0.2fp1. Looking at that packing
list and following the apparently indicated directories seems to yield:
home% ls -al /usr/local/include/eopenssl/openssl
total 3596
drwxr-xr-x 2 root wheel2048 Aug 17 18:50 .
drwxr-xr-x 3 root wheel 512 Aug 17 18:5
On Tue, Aug 23, 2016 at 11:10:38AM -0700, David Benfell wrote:
> Thinking that OpenBSD's packages incorporated assumptions that are
> inapplicable to how I use postfix, I am attempting to build it myself.
>
> Based on what I saw in the READMEs and what I found on the system, I am
> using:
>
> ma
David Benfell:
> tls_misc.c: In function 'tls_run_version':
> tls_misc.c:984: error: 'OPENSSL_VERSION' undeclared (first use in this
> function)
Perhaps that is because OpenBSD does not use OpenSSL?
Wietse
Hi,
Thinking that OpenBSD's packages incorporated assumptions that are
inapplicable to how I use postfix, I am attempting to build it myself.
Based on what I saw in the READMEs and what I found on the system, I am
using:
make tidy \
&& make makefiles CCARGS="-DUSE_TLS -I/usr/include/open
> On Aug 23, 2016, at 12:19 PM, Robert Dahlem wrote:
>
> my $instre = qr{(?x)
>\A # Absolute line start
>(?:\S+ \s+){3} # Timestamp, adjust for other time formats
>\S+ \s+ # Hostname
>(postfix(?:-\S+)?)/ # postfix
Hi,
some days ago Wietse mentioned auxiliary/collate/collate.pl in the
Postfix 3.2 source-code distribution. I did try my luck with it and it
is pretty impressive.
There remains one problem for me: it got this regular expression:
my $instre = qr{(?x)
\A # Absolute li
On Mon, Aug 22, 2016 at 04:14:31PM -0400, Joe Acquisto-j4 wrote:
> Any chance of assistance here with alterMIME?There is a
> need to add disclaimers to outgoing mail.
I looked into altermime a few years ago. It works well with sendmail
(our preferred mta).
In one case, we choose to leave it
Citing the virtual(5) manpage, patterns are tried in the order as
listed below:
user@domain address, address, ...
user address, address, ...
and so on.
Citing the postconf(5) manpage, tables will be searched in the
specified order until a match is found.
So, the first pattern is
>>> On 8/23/2016 at 1:16 AM, in message
<388d98f9-e63e-4d0a-865a-f32814510...@billmail.scconsult.com>, "Bill Cole"
wrote:
> On 22 Aug 2016, at 16:14, Joe Acquisto-j4 wrote:
>
>> Any chance of assistance here with alterMIME?
>
> A slim chance, but it's worth a shot...
>
>> There is a need to add
Hi,
we got a strange issue.
We defined two virtual files. one is for the actual delivery to defined
mailboxes or forward to other mail accounts and the other one is to catch
system mails from cronjobs without mailtto.
virtual_alias_domains = hash:/etc/postfix/virtual,
pcre:/etc/postfix/virtual
19 matches
Mail list logo
