[exim] Exim acting up after receiving a message

Pàgina inicial
Delete this message
Reply to this message
Autor: Wouter Verhelst
Data:  
A: exim-users
Assumpte: [exim] Exim acting up after receiving a message
Hi,

I've got some problems with two hosts, both running Exim 4.34, that do
not want to talk to eachother as they should.

folk is on my local LAN, is only available to the world through IPv6,
and is where my mail should end up.

Until recently, the primary IPv4 MX was a box running postfix,
administered by my coworker. Just today, I changed that to point to
samba, of which I am the admin, and which runs exim4. Samba is available
through both IPv4 ad IPv6, and sends mail to folk by using IPv6. The
setup there is exactly the same as it used to be -- all that changed is
the box which sends out mails, the software used to do so, and the
kernel (samba runs Linux, the other box runs FreeBSD).

Now, some of my mails don't get delivered anymore.

What happens is that samba connects to folk, sets up everything
(EHLO/MAIL/RCPT/DATA), sends the mail, sends the dot, and waits.

For some reason, folk does not catch the dot. I have been able to
reproduce this by manually connecting to folk's port 25 (by using
telnet), and sending it a mail exactly as it appears in samba's mail
queue; folk will just sit there and wait, until it hits its timeout and
sends a 421 back.

When I tried to run 'exim4 -d -bh <samba's address>' on folk, and did the
same thing, everything worked as it should. I tried to run 'exim4 -bd
-d' on folk, and 'exim4 -qff -d' on samba; the output on folk, right
before the timeout, then ends like this:

4985 grep.be in "@ : @[] : localhost : grep.be : folk : folk.grep.be"? yes (matched "grep.be")
4985 grep.be in "+local_domains"? yes (matched "+local_domains")
4985 accept: condition test succeeded
4985 SMTP>> 250 Accepted
4985 SMTP<< DATA
4985 SMTP>> 354 Enter message, ending with "." on a line by itself
4985 search_tidyup called

There used to be an acl_smtp_data, but I disabled it in an effort to see
whether it had some misconfiguration, and the above issues still exist.
I even commented out the relevant acl block, rather than just the
acl_smtp_data line -- nothing.

At this point, I'm out of ideas. I reran the -bh session inside script,
and put the typescript file up on <http://samba.grep.be/exim-stuff>; any
input would be greatly appreciated. If more information is required to
debug the problem, please ask.

In the mean time, I'm off to reset the MX records...

-- 
         EARTH
     smog  |   bricks
 AIR  --  mud  -- FIRE
soda water |   tequila
         WATER
 -- with thanks to fortune