Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mailpile contacts SMTP server on the wrong port? #1169

Closed
albertocottica opened this issue Dec 29, 2014 · 7 comments
Closed

Mailpile contacts SMTP server on the wrong port? #1169

albertocottica opened this issue Dec 29, 2014 · 7 comments

Comments

@albertocottica
Copy link

Hello all, we are trying to run Mailpile on our own self-hosted email addresses. IMAP works, SMTP does not. I am no expert, but it seems that Mailpile contacts the SMTP server on the wrong port (my settings are correctly set to 587):
SMTP connection to: mail.edgeryders.eu:143 as alberto@edgeryders.eu
If I try the same thing with Gmail, I get instead
SMTP connection to: smtp.gmail.com:587 as alberto.cottica@gmail.com

Below I paste the whole logged error message:

SendMail: from alberto.cottica@gmail.com  (), to [u'alberto.cottica@gmail.com ', 'test@mailpile.is'] via smtp.gmail.com:587
SMTP connection to: smtp.gmail.com:587 as alberto.cottica@gmail.com
connect: (u'smtp.gmail.com', 587)
reply: '220 mx.google.com ESMTP l9sm40919136wic.21 - gsmtp\r\n'
reply: retcode (220); Msg: mx.google.com ESMTP l9sm40919136wic.21 - gsmtp
connect: mx.google.com ESMTP l9sm40919136wic.21 - gsmtp
send: 'ehlo mailpile.local\r\n'
reply: '250-mx.google.com at your service, [151.217.212.176]\r\n'
reply: '250-SIZE 35882577\r\n'
reply: '250-8BITMIME\r\n'
reply: '250-STARTTLS\r\n'
reply: '250-ENHANCEDSTATUSCODES\r\n'
reply: '250-PIPELINING\r\n'
reply: '250-CHUNKING\r\n'
reply: '250 SMTPUTF8\r\n'
reply: retcode (250); Msg: mx.google.com at your service, [151.217.212.176]
SIZE 35882577
8BITMIME
STARTTLS
ENHANCEDSTATUSCODES
PIPELINING
CHUNKING
SMTPUTF8
send: 'STARTTLS\r\n'
reply: '220 2.0.0 Ready to start TLS\r\n'
reply: retcode (220); Msg: 2.0.0 Ready to start TLS
send: 'ehlo mailpile.local\r\n'
reply: '250-mx.google.com at your service, [151.217.212.176]\r\n'
reply: '250-SIZE 35882577\r\n'
reply: '250-8BITMIME\r\n'
reply: '250-AUTH LOGIN PLAIN XOAUTH XOAUTH2 PLAIN-CLIENTTOKEN\r\n'
reply: '250-ENHANCEDSTATUSCODES\r\n'
reply: '250-PIPELINING\r\n'
reply: '250-CHUNKING\r\n'
reply: '250 SMTPUTF8\r\n'
reply: retcode (250); Msg: mx.google.com at your service, [151.217.212.176]
SIZE 35882577
8BITMIME
AUTH LOGIN PLAIN XOAUTH XOAUTH2 PLAIN-CLIENTTOKEN
ENHANCEDSTATUSCODES
PIPELINING
CHUNKING
SMTPUTF8
send: 'AUTH PLAIN AGFsYmVydG8uY290dGljYUBnbWFpbC5jb20gAGJwZndoZnZoeXplcXRscXM=\r\n'
reply: '235 2.7.0 Accepted\r\n'
reply: retcode (235); Msg: 2.7.0 Accepted
send: u'mail FROM:<alberto.cottica@gmail.com>\r\n'
reply: '250 2.1.0 OK l9sm40919136wic.21 - gsmtp\r\n'
reply: retcode (250); Msg: 2.1.0 OK l9sm40919136wic.21 - gsmtp
send: u'rcpt TO:<alberto.cottica@gmail.com>\r\n'
reply: '250 2.1.5 OK l9sm40919136wic.21 - gsmtp\r\n'
reply: retcode (250); Msg: 2.1.5 OK l9sm40919136wic.21 - gsmtp
send: 'rcpt TO:<test@mailpile.is>\r\n'
reply: '250 2.1.5 OK l9sm40919136wic.21 - gsmtp\r\n'
reply: retcode (250); Msg: 2.1.5 OK l9sm40919136wic.21 - gsmtp
send: 'DATA\r\n'
reply: '354  Go ahead l9sm40919136wic.21 - gsmtp\r\n'
reply: retcode (354); Msg: Go ahead l9sm40919136wic.21 - gsmtp
SendMail: from alberto@edgeryders.eu (ugrazyd_xfa6mcsvx36pwasaamq), to ['alberto@edgeryders.eu', 'alberto.cottica@gmail.com'] via mail.edgeryders.eu:143
@BjarniRunar
Copy link
Member

It really looks like you had 143 as your SMTP port:

SMTP connection to: mail.edgeryders.eu:143 as alberto@edgeryders.eu

That's not expected to work, unless you have an SMTP server listening on port 143.

@albertocottica
Copy link
Author

Thanks, @BjarniRunar, but that's precisely my point: I set it at 587 through the GUI, but the program calls 143. I have no idea why :-(
screen shot 2015-01-19 at 17 58 19

@almereyda
Copy link

  • What happens when you click the "test route" button?
  • How did you set up Mailpile?

Taken from the Edgerydes forum. @BjarniRunar according to @albertocottica, he double checked the settings, so the flaw is somewhere.

SMTP connection to: mail.edgeryders.eu:143 as alberto@edgeryders.eu
connect: (u'mail.edgeryders.eu', 143)
reply: '* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot (Ubuntu) ready.\r\n'
reply: retcode (-1); Msg: [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot (Ubuntu) ready.
connect: [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot (Ubuntu) ready.
send: 'ehlo mailpile.local\r\n'
reply: 'ehlo BAD Error in IMAP command received by server.\r\n'
reply: retcode (-1); Msg: BAD Error in IMAP command received by server.
send: 'helo mailpile.local\r\n'
reply: 'helo BAD Error in IMAP command received by server.\r\n'
reply: retcode (-1); Msg: BAD Error in IMAP command received by server.
SendMail: from alberto@edgeryders.eu (ugrazyd_xfa6mcsvx36pwasaamq), to ['alberto@edgeryders.eu', 'alberto.cottica@gmail.com'] via mail.edgeryders.eu:143

@albertocottica
Copy link
Author

Hello @almereyda, thanks for your interest.

  • When I clock the "test route" button I get the "error connecting" message.
  • Do you mean "how did I install Mailpile"? I simply downloaded the beta (for Mac: I am running OSX 10.10.1), and followed the instructions. But maybe I don't understand the question, sorry!

@albertocottica
Copy link
Author

@almereyda, any word on this? My installation of Mailpile now has also stopped receiving from Edgeryders. I can try to correct for the problem, but it is pointless if I can't send. Should I just default to Thunderbird + Enigmail for my Community Crypto project?

@almereyda
Copy link

Yes, you may be right here. Sorry for not having been responsive.

For deployment I would never install it on a system, but use Docker containers instead. To be able to serve multiple accounts.

Unfortunately I didn't look into the current Dockerfile and its performance under production environments lately. Issues for a v1.0 Milestone should definately account for this, too.

I will have to look into #962 again, to provide meaningful feedback. But according to @BjarniRunar in #962 (comment) , this still seems to be a low hanging fruit.

@albertocottica
Copy link
Author

This is beyond me, @almereyda – but then I imagine it will be beyond most users, and "normal" users like me will not need multiple accounts. All I can do is volunteer to retry the installation from scratch and test again. But that does not make sense unless the send problem is solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants