eliashussary / mail-confirm Goto Github PK

I have been trying to install your package. I am facing one problem... exactly the problem you mentioned in the doc, with port 25 not accessible I think. So when I launch

const check = async (email) => {  
  try{
      const emailResponse = new MailConfirm({
          emailAddress: email,
          timeout: 5000,
          mailFrom: '[email protected]',
          invalidMailboxKeywords: ['noreply', 'noemail']
      });
      const result = await emailResponse.check()
      return result
  }catch(err){   throw new Error(err)    }
}

 check('[email protected]');

Here is the log error:
Error: Mailbox check failed.

However, I have been trying different things to fix this, but no success yet. I would love your word on how you manage it !!!

My config: using a mac IOS 10.12
I have been trying to sudo launchctl start org.postfix.master to enable port 25, so now i see 25 open:

Host is up (0.000098s latency).
Other addresses for localhost (not scanned): ::1
Not shown: 1989 closed ports
PORT      STATE         SERVICE
25/tcp    open          smtp
587/tcp   open          submission
631/tcp   open          ipp
3000/tcp  open          ppp
3001/tcp  open          nessus
49152/tcp open          unknown
49153/tcp open          unknown
123/udp   open          ntp
137/udp   open|filtered netbios-ns
138/udp   open|filtered netbios-dgm
5353/udp  open|filtered zeroconf`

But still the issue persits.

I noticed that the simple telnet example.com 25 is hanging without answer, so it is definitly
related to port 25. I also tried to set up s server on digitalocean to try on ubuntu servers, but same thing, telnet example.com 25 is hanging.

I know it is not an issue related to your package, but I won't be the only one having this problem I suppose.
So @eliashussary : any ideas on how to make port 25 available on Mac or ubuntu in order to get your package to work ?
Any possibilities to make this package work on different port ?

thanks

does not work with google mx servers because their initial message messes up the result parsing.