Reason behind this that with abuse@127.0.0.1, the MTA will try to get MX records for the 'dns name' 127.0.0.1. (Although, I hope all MTA's are smart enough to just reject such an address) With [172.0.0.1] it bypasses MX checks and uses the default A or CNAME DNS record or, in case of an IP address, the IP.


On Thu, Aug 23, 2012 at 8:20 PM, Benny Pedersen <me@junc.org> wrote:
Den 2012-08-23 20:15, A.L.E.C skrev:

On 08/23/2012 07:43 PM, Benny Pedersen wrote:
Den 2012-08-23 08:06, A.L.E.C skrev:

Doesn't work with current version too. It looks like javascript method
for address validation doesn't handle this case. Please, open a ticket
in bugtracker, so we could fix this issue in next version.

I've fixed this issue in commit ff805351cae78676927f76a1960b8e688558fe95.

also here i forget to say that abuse@127.0.0.1 is invalid, but abuse@[127.0.0.1] is valid

test it on mta such as postfix to prove it :=)

thanks for all that resolve this




_______________________________________________
Roundcube Development discussion mailing list
dev@lists.roundcube.net
http://lists.roundcube.net/mailman/listinfo/dev