https://bugs.exim.org/show_bug.cgi?id=2903

Dean Brooks <d...@iglou.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |d...@iglou.com
         Resolution|FIXED                       |---

--- Comment #10 from Dean Brooks <d...@iglou.com> ---
I'm reopening out of an abundance of caution. We ran into this same problem
with global rewrites after upgrading to 4.96 yesterday. However, our problem is
occurring for some addresses even if *none* of the rewrite rules match. It
would immediately log an error and the smtp connection would drop.

The rewrite rule we have in the format of:

^(.*)@ourdomain.net $1...@ourdomain.com hE

To reproduce, in a manual smtp transaction we used the following commands:
-----------------------------------------------------------------------
EHLO ourdomain.com
MAIL FROM:<john...@ourdomain.com>
RCPT TO:<john...@ourdomain.com>
DATA
From: john...@ourdomain.com <john...@ourdomain.com>
To: john...@ourdomain.com
Subject: test

test message
.
-----------------------------------------------------------------------

Immediately upon encountering the blank line after the headers, the smtp
transaction would drop. Debug shows:

end of ACL "check_rcpt": ACCEPT
250 Accepted
data
354 Enter message, ending with "." on a line by itself
From: john...@ourdomain.com <john...@ourdomain.com>
To: john...@ourdomain.com
Subject: test
host in ignore_fromline_hosts? no (option unset)

john...@ourdomain.com in "^(.*)@ourdomain.net"? no (end of list)
LOG: MAIN
  rewrite: malformed address: <john...@ourdomain.com>
 may not follow john...@ourdomain.com

** Note that the address did *not* actually match the rewrite rule, but it
still threw an error and disconnected the smtp transaction. I don't know if
this commit fixes this issue as well, but wanted to be sure someone saw this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##

Reply via email to