Provide a new code when the client is blacklisted

[chrisvoo]

Hi,
I was testing your library and unfortunately, our production AWS server got blacklisted by Microsoft ([email protected] it's mine)

ubuntu@ip-172-31-66-205:~$ email-verify [email protected]
INFO: DEBUG
INFO: OPTIONS: {"port":25,"sender":"[email protected]","fqdn":"mail.example.org","concurrency":1,"debug":true}
INFO: # Veryfing [email protected]
INFO: Resolving DNS... hotmail.it
INFO: MX Records {"exchange":"eur.olc.protection.outlook.com","priority":10}
INFO: Choosing eur.olc.protection.outlook.com for connection
INFO: Creating connection...
INFO: Connected
SERVER: 220 DB3EUR04FT014.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Wed, 5 Aug 2020 14:03:14 +0000
SERVER: 
CLIENT: EHLO mail.example.org
CLIENT: 
SERVER: 250-DB3EUR04FT014.mail.protection.outlook.com Hello [35.181.159.81]
SERVER: 250-SIZE 49283072
SERVER: 250-PIPELINING
SERVER: 250-DSN
SERVER: 250-ENHANCEDSTATUSCODES
SERVER: 250-8BITMIME
SERVER: 250-BINARYMIME
SERVER: 250-CHUNKING
SERVER: 250 SMTPUTF8
SERVER: 
CLIENT: MAIL FROM:<[email protected]>
CLIENT: 
SERVER: 550 5.7.1 Unfortunately, messages from [<OUR_IP>] weren't sent. Please contact your Internet service provider since part of their network is on our block list (S3140). You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors. [DB3EUR04FT014.eop-eur04.prod.protection.outlook.com]
SERVER: 
INFO: Closing connection
{
  success: false,
  info: '[email protected] is an invalid address',
  addr: '[email protected]',
  code: 1,
  tryagain: false,
  banner: '220 DB3EUR04FT014.mail.protection.outlook.com Microsoft ESMTP MAIL Service ready at Wed, 5 Aug 2020 14:03:14 +0000\r\n'
}

In this case, it's wrong saying that [email protected] is an invalid address since when I try it locally it's perfectly valid. Maybe it could really help to parse the server's message or just blindly reporting it, even if it's a bit long. I had to enable the debugging option by modifying the module inside node_modules (I wasn't able to find a param for the CLI to enable debugging) to spot this message.
Thanks.