Email :fail: message not giving proper message

Just tested it out:

MAIL FROM: xxx@xxx.com
250 OK
RCPT TO: yyy@yyy.com
550-"The recipient cannot be verified. Please check all recipients of this
550 message to verify they are valid."

For yyy.com I have :fail: set with a distinctive response that isn't shown (note: domains changed to protect the guilty).

This would mean that either:

a. The :fail: message never used to work
b. The :fail: message stopped working after verify = recipient
c. The latest exim.conf has broken it

I'd go with c.

As to what's changed - I don't know because I haven't checked yet...

 

...having checked it would actually appear to be have been b. rather than c. as exim.conf doesn't appear to have changed apart from a gramatical correction to that message and that damn split_spool_directory

Id' suggest a bugzilla request for them to lookup the bounce error after the :fail: directive in /etc/valiases/domain and use that as the message to the RCPT failure. Shoudl be emminemtly possible for them to do.

 

Mike,

You definitely won't get any custom message if it fails at the RCPT SMTP stage and it hits verify = recipient, the code simply isn't there in exim.conf at the place it occurs to read the valiases file for the custom message.

 

Yes.

(line added cos of the character limit)

 

Done some extensive testing. Currently you'll have this in the second box of the first triplet in the Exim Configurator:

Code:

  message = "The recipient cannot be verified.  Please check all recipients of this message to verify they are valid."
  verify = recipient

If you get rid of the message line, so that you just have:

Code:

  verify = recipient

then the message in /etc/valiases will be used in the failure error to the sender.

However, if there is no message after the :fail: in /etc/valiases, there will be a blank 550 message in the failure error.

I did play with coding it to cope with this issue through a perl script, which worked, but didn't really complete it.

 

dunno if this helps.. chirpy and squirrel:
=============================
internal_search_find: file="/etc/valiases/xxxxxxxxx.com"
type=lsearch key="*"
file lookup required for *
in /etc/valiases/xxxxxxxxx.com
lookup yielded: :fail:
expanded: :fail:
file is not a filter file
parse_forward_list: :fail:
extract item: :fail:
virtual_aliases router forced address failure
sdgfsd@xxxxxxxx.com is undeliverable:

search_tidyup called
>>>>>>>>>>>>>>>> Exim pid=24960 terminating with rc=2 >>>>>>>>>>>>>>>>
==============================

and when it was set to blackhole it was:
==============================
internal_search_find: file="/etc/valiases/xxxxxxxxxx.com"
type=lsearch key="*"
file lookup required for *
in /etc/valiases/xxxxxxxxxxxxx.com
lookup yielded: :blackhole:
expanded: :blackhole:
file is not a filter file
parse_forward_list: :blackhole:
extract item: :blackhole:
address :blackhole:d
routed by virtual_aliases router
envelope to: sdgfsd@xxxxxxxxxx.com
transport: <none>
mail to sdgfsd@xxxxxxxxxxxx.com is discarded
search_tidyup called
>>>>>>>>>>>>>>>> Exim pid=25185 terminating with rc=0 >>>>>>>>>>>>>>>>
===============================

and also when this was set to :blackhole: .. it just worked.. but :fail: didnt. iam not sure of eventually the process or code... but just tried it out as you guys were serious on this.

the difference i see is at:
======================
virtual_aliases router forced address failure
sdgfsd@xxxxxxxx.com is undeliverable:

and

routed by virtual_aliases router
envelope to: sdgfsd@xxxxxxxxxx.com
transport: <none>
======================

hope this helps.

 

Yup. I know why it works that way, it's just the best way around it. It's straightforward enough to code, but the additional load might be better spent with a daily script to parse the valiases file as squirrel is doing.

 

Done some more digging on this and will suggest this to cPanel:

http://www.exim.org/exim-html-4.40/doc/html/FAQ_7.html#TOC254

If you change this:

Code:

message = "The recipient cannot be verified.  Please check all recipients of this message to verify they are valid."
  verify = recipient

to this:

Code:

  message = "The recipient cannot be verified. $acl_verify_message"
  verify = recipient

You get the best of both worlds