Exim 4.93.0.4 has been released

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
9,051
Hello,

Exim 4.93.0.4 has been released:

and the SPF "A/AAAA" lookup issue from 4.93.0 appears to have been resolved.

I have tested the sending TXT spf with just
Code:
"v=spf1 a mx -all"
and seems ok now.

To update:
Code:
cd /usr/local/directadmin/custombuild
./build update
./build exim
If anyone runs into any related issues, please let us know as soon as possible.

As usual, the update is now on files1, and all of our own mirrors.
Other mirrors may take up to 24 hours to sync.

John
 

nmb

Verified User
Joined
Sep 13, 2008
Messages
213
Already tested. I don't see any problem with SPF anymore.

Thanks
 

Tazmanian79

Verified User
Joined
Jul 24, 2010
Messages
89
Version 4.93.0.4 is still giving me problems. Mails are not going out.
As soon as I go back to 4.92.3 all mails are send without any problem.

Errorlogs:
Code:
2020-01-08 16:24:45 Received from root@server.com U=root P=local S=979 T="lfd on srv: blocked 175.6.133.182 (CN/China/-)"
2020-01-08 16:24:45 mail@mail.net R=lookuphost T=remote_smtp defer (-53): retry time not reached for any host for 'mail.net'
2020-01-08 16:25:21 H=aspmx.l.google.com [108.177.119.27] Broken pipe
2020-01-08 16:25:21 H=alt1.aspmx.l.google.com [142.250.4.27] Broken pipe
2020-01-08 16:25:21 H=alt2.aspmx.l.google.com [108.177.97.27] Broken pipe
2020-01-08 16:25:21 mail@mail.net R=lookuphost T=remote_smtp defer (32): Broken pipe
Code:
2020-01-08 16:22:08 Received from planning@server.com H=(SAMCLOUD01.server.be) [1.1.1.1] P=esmtpa A=login:planning@server.com S=136152 T="Ordre de transport "
2020-01-08 16:22:08 H=hotmail-com.olc.protection.outlook.com [104.47.70.33] Broken pipe
2020-01-08 16:22:08 H=hotmail-com.olc.protection.outlook.com [104.47.55.33] Broken pipe
2020-01-08 16:22:08 H=aspmx.l.google.com [108.177.126.26] Broken pipe
2020-01-08 16:22:08 H=alt1.aspmx.l.google.com [142.250.4.26] Broken pipe
2020-01-08 16:22:08 H=alt2.aspmx.l.google.com [108.177.97.27] Broken pipe
2020-01-08 16:22:08 H=aspmx2.googlemail.com [142.250.4.27] Broken pipe
2020-01-08 16:22:08 mail@hotmail.com R=lookuphost T=remote_smtp defer (32): Broken pipe
2020-01-08 16:22:08 planning@mail.com R=lookuphost T=remote_smtp defer (32): Broken pipe
2020-01-08 16:23:24 H=hotmail-com.olc.protection.outlook.com [104.47.12.33] Broken pipe
2020-01-08 16:23:24 H=hotmail-com.olc.protection.outlook.com [104.47.14.33] Broken pipe
2020-01-08 16:23:24 H=aspmx.l.google.com [108.177.119.27] Broken pipe
2020-01-08 16:23:24 H=alt1.aspmx.l.google.com [142.250.4.27] Broken pipe
2020-01-08 16:23:24 H=alt2.aspmx.l.google.com [108.177.97.27] Broken pipe
2020-01-08 16:23:24 mail@hotmail.com R=lookuphost T=remote_smtp defer (32): Broken pipe
2020-01-08 16:23:24 planning@mail.com R=lookuphost T=remote_smtp defer (32): Broken pipe
Code:
2020-01-08 16:23:00 Received from nasserver@server.com H=d54c4e40b.access.telenet.be (NAS01) [1.1.1.1] P=esmtpsa X=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256 CV=no A=login:nasserver@server.com S=1045 T="NAS-01 - Testbericht van NAS01"
2020-01-08 16:23:00 H=aspmx.l.google.com [108.177.119.27] Broken pipe
2020-01-08 16:23:00 H=alt1.aspmx.l.google.com [142.250.4.27] Broken pipe
2020-01-08 16:23:00 mail@server.com R=lookuphost T=remote_smtp defer (32): Broken pipe
2020-01-08 16:23:24 H=aspmx.l.google.com [108.177.119.27] Broken pipe
2020-01-08 16:23:24 H=alt1.aspmx.l.google.com [142.250.4.27] Broken pipe
2020-01-08 16:23:24 H=alt2.aspmx.l.google.com [108.177.97.27] Broken pipe
2020-01-08 16:23:24 mail@server.com R=lookuphost T=remote_smtp defer (32): Broken pipe
 

annc

Verified User
Joined
Jun 10, 2008
Messages
44
Broken pipe is not the SPF related error.
It's something with network traffic (connection to other mail server is closed/broken)

As far, I don't have such of this problems on my machines.
 

wouterdt

New member
Joined
Jan 8, 2020
Messages
3
I have the same issue, mails are stuck in the mail queue and the log contains broken pipe errors.

Reverting back to 4.92 and retrying the items in the queue fixes it but I would like to know what the issue is. I have no idea how to debug this further at this point.
 

ikkeben

Verified User
Joined
May 22, 2014
Messages
807
Location
Netherlands Germany
OK for those who are reading is a link to howto / wiki go back to older version ( reverting) in this case handy? ;)

So not only replies with i did go back , reverting back to 4.92 but also a link how to do that?
 

Tazmanian79

Verified User
Joined
Jul 24, 2010
Messages
89
I know it's not an SPF issue. But broken pipe only occured when 4.93 came out, I also posted it on the topic of 4.93 release.
On all upgrades before I did not have any problem.

So I reverted back to 4.92.3. Hope someone can fix this problem.

If you use custombuild then it's easy to downgrade:
Go to Customize versions, search for EXIM and change 4.93.0.3 to 4.92.3 leave MD5 empty.
Then go back to update software tap and click on downgrade exim
 
Last edited:

wouterdt

New member
Joined
Jan 8, 2020
Messages
3
Is there any way to find out why there's a broken pipe? Maybe a log file somewhere or setting a debug/verbose level?
 

DanR

Verified User
Joined
Sep 1, 2019
Messages
20
Hey!

I am having major issues with this and emails not sending... How do I roll back to the previous version please?

Thanks
Dan
 

DanR

Verified User
Joined
Sep 1, 2019
Messages
20
I updated exim and eximconf today and now emails arent sending at all...
 

DanR

Verified User
Joined
Sep 1, 2019
Messages
20
Managed to fix the issue... Port 587 seemed to have closed randomly...
 

Anne

Verified User
Joined
Dec 3, 2015
Messages
18
Same problems here on CentOS 7 machine after update to 4.93.0.4. All mail stuck in queue. Revert back to 4.92, all send right away. Errors same as above, broken pipe...
 

smtalk

Administrator
Staff member
Joined
Aug 22, 2006
Messages
9,355
Location
LT, EU
Same problems here on CentOS 7 machine after update to 4.93.0.4. All mail stuck in queue. Revert back to 4.92, all send right away. Errors same as above, broken pipe...
Are you using a smarthost?
 
Top