If people want qmail-dk (ssl) and have already installed the update
(qmail version 1.03-1.3.24) you can do the following to get qmail-dk
working with ssl/crypto:
(i686)
# rpm -Uvh
ftp://ftp.qmailtoaster.org/pub/repo/qmt/CentOS/5/testing/i386/libdomainkeys-toaster-0.68-1.3.7.i686.rpm
# rpm -
FWIW, I did not update my qmail-dk binary. I was hypothesizing it was
only used to sign, not to communicate, and therefore the version of
openssl didn't matter. I might be wrong, but I'm still sending mail?
Brian
On 7/5/18 06:38, South Computers wrote:
Interestingly, this broke DKIM.
I
Thanks!
An oversight on my part, I'll probably have to recompile and link
domainkeys with openssl101e if anyone's interested. I'm not sure how
much it's in use these days being replaced by dkim.
On 7/5/2018 7:38 AM, South Computers wrote:
Interestingly, this broke DKIM.
I don't have the ti
Interestingly, this broke DKIM.
I don't have the time to look further right now, but disabled dk for the
time being, and it's working.
Was getting this in smtp/current when trying to send mail:
@40005b3e1a821e069b7c qmail-dk:[3870]: Dying due to a POSSIBLE BUG!
etc...
South Computers
Also mostly a lurker these days, but wanted to chime in and give a big
thanks as well Eric.
Much appreciate all your work to keep this going.
Scott
Also, if anyone else has neglected to keep their toaster up to date and
needs to manually install the epel repo, at least for x86 on COS5:
wget
h
ation is starting to fail! LOL
Dan McAllister
QMT DNS Admin
-Original Message-
From: Eric Broch [mailto:ebr...@whitehorsetc.com]
Sent: Wednesday, June 27, 2018 12:09 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Upgrading openssl in an old Qmailtoaster install
H
Even though this iteration of qmail is compiled and linked with
openssl101e the only affected packages are qmail-smtpd, qmail-remote,
and qmail-dk. Everything else should be the same.
On 7/3/2018 12:32 PM, Sean Murphy wrote:
Just performed this procedure on a test machine, and everything
insta
Just performed this procedure on a test machine, and everything
installed properly.
epel-release was already installed, the newer openssl package installed
in /usr/lib as expected, and the toaster rpm installed with no
complaints. A quick stop/start of qmail later and we have an updated
toas
riginal Message-
From: Eric Broch [mailto:ebr...@whitehorsetc.com]
Sent: Wednesday, June 27, 2018 12:09 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] Upgrading openssl in an old Qmailtoaster install
Have a look at this thread:
https://www.mail-archive.com/qmailtoas
Yes, CNAME lookup removed.
On 7/2/2018 12:47 PM, Peter Peltonen wrote:
Thanks Eric, does this rpm have also the cname lookup remove patch?
Best,
Peter
On Sat, Jun 30, 2018 at 9:06 PM, Eric Broch wrote:
Instructions for setting up greater than openssl-0.9.8 CentOS 5, minimal
testing done. Th
Thanks Eric, does this rpm have also the cname lookup remove patch?
Best,
Peter
On Sat, Jun 30, 2018 at 9:06 PM, Eric Broch wrote:
> Instructions for setting up greater than openssl-0.9.8 CentOS 5, minimal
> testing done. This is done with openssl-1.01e
>
> https://www.qmailtoaster.org/newopenss
Instructions for setting up greater than openssl-0.9.8 CentOS 5, minimal
testing done. This is done with openssl-1.01e
https://www.qmailtoaster.org/newopensslcnt50.html
Eric
On 6/29/2018 4:51 AM, Peter Peltonen wrote:
Great, thanks for sharing!
One question:
Eric had produced an RPM for qm
It removes cname lookups from qmail-remote, specifically in dns.c per
DJB (https://lists.gt.net/qmail/users/138190).
On 6/29/2018 9:49 AM, Brian Ghidinelli wrote:
What does this patch do? I never heard about 1.3.23.
On 6/29/18 08:45, Eric Broch wrote:
Here's the patch:
diff -rNu qmailq
Here's the patch:
diff -rNu qmailqmt/dns.c qmailqmt-new/dns.c
--- qmailqmt/dns.c 2018-01-21 09:03:56.201694493 -0700
+++ qmailqmt-new/dns.c 2018-01-21 09:06:40.696619489 -0700
@@ -249,32 +249,7 @@
int dns_cname(sa)
stralloc *sa;
{
- int r;
- int loop;
- for (loop = 0;loop < 10;++loop)
My guess is: get both source RPMs, extract both spec files, diff my spec
against .22 and then apply those changes to .23 and follow the rest of the
steps?
I don’t remember what I changed in the spec file, or if that even mattered, but
that would give you what is needed to replicate for .23 I
Great, thanks for sharing!
One question:
Eric had produced an RPM for qmail 1.03-1.3.23.i386 with the CNAME
lookups removed.
Yours is 1.03-1.3.22 and with CNAME lookups enabled I assume.
How would one migrate the changes you did to Eric's version, as I
would like to have both: newer TLS support
Thanks, Brian!!!
On 6/29/2018 1:32 AM, Brian Ghidinelli wrote:
Good news - I seemed to have solved this. It's a combo of these old notes from
2011 and an upgraded openssl:
http://www.ghidinelli.com/2011/10/20/october-qmail-follow-up
I'm attaching my modified qmail-toaster.spec from 1.3.21. I
Good news - I seemed to have solved this. It's a combo of these old notes from
2011 and an upgraded openssl:
http://www.ghidinelli.com/2011/10/20/october-qmail-follow-up
I'm attaching my modified qmail-toaster.spec from 1.3.21. I installed
openssl-1.0.2o from source on CentOS 5 and linked:
/u
Have a look at this thread:
https://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg41029.html
IMHO, there were to many packages that were dependent on openssl-9.8 on
the CentOS 5 box to make this practical.
On 6/26/2018 11:44 PM, Brian Ghidinelli wrote:
I'm running into the sam
I would be interested in this solution as well.
How did you upgrade openssl? Did you follow this tutorial
https://miteshshah.github.io/linux/centos/how-to-enable-openssl-1-0-2-a-tlsv1-1-and-tlsv1-2-on-centos-5-and-rhel5/
or something else?
Best,
Peter
On Wed, Jun 27, 2018 at 8:44 AM, Brian Ghi
I'm running into the same SMTP TLS connection errors as reported by Sean
Murphy in this email here:
https://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg41115.html
Same scenario: old, reliable CentOS 5 box. We need a few more months to
transition off this box and we're getting
21 matches
Mail list logo
