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

protonmail bridge #95

Closed
korzq opened this issue Nov 10, 2018 · 90 comments

Comments

@korzq
Copy link

commented Nov 10, 2018

Hello, Protonmail have a bridge now which give you an IMAP and SMTP addrees at 127.0.0.1 but it doesn't seems to work with the wizard. I filled in all of the info and it seems like the bridge doesn't support ssl.

I use macOS Mojave

λ offlineimap
OfflineIMAP 7.2.1
  Licensed under the GNU GPL v2 or any later version (with an OpenSSL exception)
imaplib2 v2.57 (bundled), Python v2.7.15, OpenSSL 1.0.2p  14 Aug 2018
Account sync proton:
 *** Processing account proton
 Establishing connection to 127.0.0.1:1143 (proton-remote)
 ERROR: Could not connect via SSL to host '127.0.0.1' and non-standard ssl port 1143 configured. Make sure you connect to the correct port. Got: [SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:726)
 *** Finished account 'proton' in 0:00
ERROR: Exceptions occurred during the run!
ERROR: Could not connect via SSL to host '127.0.0.1' and non-standard ssl port 1143 configured. Make sure you connect to the correct port. Got: [SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:726)

Traceback:
  File "/usr/local/Cellar/offlineimap/7.2.1/libexec/offlineimap/accounts.py", line 283, in syncrunner
    self.__sync()
  File "/usr/local/Cellar/offlineimap/7.2.1/libexec/offlineimap/accounts.py", line 359, in __sync
    remoterepos.getfolders()
  File "/usr/local/Cellar/offlineimap/7.2.1/libexec/offlineimap/repository/IMAP.py", line 452, in getfolders
    imapobj = self.imapserver.acquireconnection()
  File "/usr/local/Cellar/offlineimap/7.2.1/libexec/offlineimap/imapserver.py", line 633, in acquireconnection
    exc_info()[2])
  File "/usr/local/Cellar/offlineimap/7.2.1/libexec/offlineimap/imapserver.py", line 547, in acquireconnection
    af=self.af,
  File "/usr/local/Cellar/offlineimap/7.2.1/libexec/offlineimap/imaplibutil.py", line 194, in __init__
    super(WrappedIMAP4_SSL, self).__init__(*args, **kwargs)
  File "/usr/local/Cellar/offlineimap/7.2.1/libexec/offlineimap/bundled_imaplib2.py", line 2183, in __init__
    IMAP4.__init__(self, host, port, debug, debug_file, identifier, timeout, debug_buf_lvl)
  File "/usr/local/Cellar/offlineimap/7.2.1/libexec/offlineimap/bundled_imaplib2.py", line 361, in __init__
    self.open(host, port)
  File "/usr/local/Cellar/offlineimap/7.2.1/libexec/offlineimap/imaplibutil.py", line 202, in open
    super(WrappedIMAP4_SSL, self).open(host, port)
  File "/usr/local/Cellar/offlineimap/7.2.1/libexec/offlineimap/bundled_imaplib2.py", line 2196, in open
    self.ssl_wrap_socket()
  File "/usr/local/Cellar/offlineimap/7.2.1/libexec/offlineimap/bundled_imaplib2.py", line 548, in ssl_wrap_socket
    self.sock = ssl.wrap_socket(self.sock, self.keyfile, self.certfile, ca_certs=self.ca_certs, cert_reqs=cert_reqs, ssl_version=ssl_version)
  File "/usr/local/Cellar/python@2/2.7.15_1/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 949, in wrap_socket
    ciphers=ciphers)
  File "/usr/local/Cellar/python@2/2.7.15_1/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 617, in __init__
    self.do_handshake()
  File "/usr/local/Cellar/python@2/2.7.15_1/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 846, in do_handshake
    self._sslobj.do_handshake()
@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented Nov 12, 2018

I don't have a Protonmail account and it seems like Bridge is still in beta (AUR build didn't work for me).

So I can't personally debug this immediately. If anyone else has a PM account and has figured out getting it working with mutt, please share your configs and I'll add it to the wizard!

@einveru

This comment has been minimized.

Copy link

commented Nov 13, 2018

This works for me using neomutt + Protonmail bridge on Arch.

set imap_user =
set imap_pass =
set folder = imap://127.0.0.1:1143
set spoolfile = imap://127.0.0.1:1143
set ssl_starttls = yes
set ssl_force_tls = yes
set imap_authenticators = login

The only issue recently is that the 'bridge' changes the issues password frequently forcing me to edit the configs more than I would like. This might be an issue on my end. I haven't spent any time troubleshooting.

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented Nov 13, 2018

Okay, thanks for the info. Are the ssl_starttls, ssl_force_tls and imap_authenticators variables necessary in this case? I can probably make a special face for ProtonMail if that's the case.

@einveru

This comment has been minimized.

Copy link

commented Nov 14, 2018

Just did a quick test with those options commented out and was able to retrieve/send without issue. Don't remember why I added those lines, but after the frustrating hours setting up neomutt with bridge and etc etc, just left it all 'as is' once got it working. Probably time I revisit my config files.

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented Nov 14, 2018

Okay. So I'm going to make the assumption that @korzq 's problem is either Mac specific or has something to do with his setup in bridge. Since theoretically mutt-wizard is ideally Mac compatible, hopefully we can figure out what's up.

I'll probably try getting a Protonmail account and testing it myself, but I think I might go ahead and add the IMAP address to the servers file.

@korzq

This comment has been minimized.

Copy link
Author

commented Nov 14, 2018

Thanks! I'll also do some research and see whats up.

@bepolymathe

This comment has been minimized.

Copy link

commented Dec 9, 2018

I'am very interessed to...
@einveru can you explain a little bit more your config... i have this

image

@bepolymathe

This comment has been minimized.

Copy link

commented Dec 9, 2018

Little progress

image

@bepolymathe

This comment has been minimized.

Copy link

commented Dec 17, 2018

always blocked at the same stage...

@bepolymathe

This comment has been minimized.

Copy link

commented Dec 17, 2018

@einveru are your config files accessible somewhere?

@einveru

This comment has been minimized.

Copy link

commented Dec 17, 2018

@bepolymathe For offlineIMAP? As it seems that's the program you are running from the error logs above. Here's the settings I use. I have protonmail setup in mutt using IMAP settings, but do also have offlineimap working with protonmail (bridge) to archieve some folders. Here's my settings in offlineIMAP.

(I believe from the shots above the issue is with ssl. Try 'ssl=no' and make sure you are using the bridge password.)

[general]
accounts = protonmail

[Account protonmail]
localrepository = Local-Protonmail
remoterepository = Remote-Protonmail

[Repository Local-Protonmail]
type = Maildir
localfolders = ~/Mail/protonmail
sync_deletes = yes

[Repository Remote-Protonmail]
type = IMAP
remoteport = 1143
remotehost = 127.0.0.1
remoteuser =
remotepass = <BRIDGE PASSWORD!!>
expunge =yes
ssl = no
folderfilter = lambda foldername: foldername not in ['All Mail']

@bepolymathe

This comment has been minimized.

Copy link

commented Dec 17, 2018

Ok, thanks. But you leave the password in plain text ? Without remoteuser ?
I test it...

@hakova

This comment has been minimized.

Copy link

commented Jan 3, 2019

I confirm that @einveru's solution (specifically speaking "ssl=no" setting works with the protonmail bridge.

Do sync_deletes=yes and expunge=yes settings delete and expunge messages locally and remotely, repsectively? I don't seem to have those settings in my .offlineimaprc file, which was generated by the mutt-wizard.

@hakova

This comment has been minimized.

Copy link

commented Jan 3, 2019

Ok, thanks. But you leave the password in plain text ? Without remoteuser ?

In my .offlineimaprc file, which was generated by mutt-wizard, that line reads as follows:
remotepasseval = mailpasswd("protonmail")

@bepolymathe

This comment has been minimized.

Copy link

commented Jan 3, 2019

Ok. Thanks. I'll try again today.

@bepolymathe

This comment has been minimized.

Copy link

commented Jan 3, 2019

Excellent, guys, it seems to be working. It's synchronizing right now !
I let the import process finish and I tell you.
Thank you.

@bepolymathe

This comment has been minimized.

Copy link

commented Jan 3, 2019

I managed to synchronize the emails but I have a problem with the GPG key. Is it possible to change the key without deleting the account? @LukeSmithxyz

@bepolymathe

This comment has been minimized.

Copy link

commented Jan 3, 2019

Well, I can synchronize the emails, delete them... but it doesn't want to decrypt the key when I try to send an email.

capture d ecran de 2019-01-03 16-09-30

@bepolymathe

This comment has been minimized.

Copy link

commented Jan 3, 2019

If I try to pass the password in full text... I get an error message too (which must be quite logical)...

inability to use a secure authentication method

@bepolymathe

This comment has been minimized.

Copy link

commented Jan 3, 2019

Maybe I'm making progress? I edited the.msmtprc file to change the argument from "gpg" to "gpg2"... I have a new error message but not the same one.

image

@bepolymathe

This comment has been minimized.

Copy link

commented Jan 3, 2019

Well, I just managed to send an email but it's not very clean... I had to disable TLS and the password in plain text in ".msmtprc" file. However, the following configuration works.


defaults
auth on
tls on
tls_certcheck off
logfile ~/.msmtp.log


account proton
host 127.0.0.0.1.1
port 1025
from name@mail.net
user name@mail.net
password <PASSWORD>
@hakova

This comment has been minimized.

Copy link

commented Jan 4, 2019

Well, I can synchronize the emails, delete them... but it doesn't want to decrypt the key when I try to send an email.

capture d ecran de 2019-01-03 16-09-30

I confirm this behavior for protonmail AND hotmail. I get the same error message when I try to send emails from either of these accounts. It is as if either the decrypted smtp password cannot be read by msmtp or it gets corrupted during decryption process (my interpretation, which may be off). Interestingly, when I use offlineimap to synch these same accounts, I get a prompt for password entry on the console, even if I just entered the main PGP passphrase on pinentry dialog. I believe there may be a disconnect between the gpg and mutt. Perhaps the ~/.config/mutt/credentials/getmuttpass script needs some attention (again, I may be off)?

Gmail works as expected though...

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented Jan 4, 2019

@bepolymathe If you need to replace your GPG key for some reason, do so manually, then in the wizard select the "change an account's password" option. This should overwrite the previous password encrypted for your old gpg key.

@hakova Is this a new problem for you? You make it sound like it was working before. If you don't have gpg and only have gpg2, be sure to either symlink gpg to gpg2 or change the wizard-generated command to say gpg2. Try running that command manually and it should return your password (with no newline). Say if it does anything else.

Also, if you're getting continually prompted for your gpg password, you may want to change your cache settings or use pam-gnupg.

@hakova

This comment has been minimized.

Copy link

commented Jan 4, 2019

...

@hakova Is this a new problem for you? You make it sound like it was working before. If you don't have gpg and only have gpg2, be sure to either symlink gpg to gpg2 or change the wizard-generated command to say gpg2. Try running that command manually and it should return your password (with no newline). Say if it does anything else.

Thanks for your prompt response @LukeSmithxyz! I have both (/usr/bin/gpg and /usr/bin/gpg2). I tried the manual command gpg -d hotmail.gpg before reading your response and saw that it wasn't returning my password at all. What I did then was to manually encrypt my password gpg -e -r account-to-encrypt hotmail.pass and moved files around (hotmail.gpg > hotmail.old, hotmail.new > hotmail.gpg). When I tried again, it worked for hotmail. I did the same thing for my protonmail account afterwards. It looked like it was going to work, protonmail definitely received my decrypted password, however quit with the following error:

"msmtp: TLS certificate verification failed: the certificate hasn't got a known issuer". I bet that is why disabling TLS worked for @bepolymathe . I am now trying to figure out how to overcome this next hurdle :).

Also, if you're getting continually prompted for your gpg password, you may want to change your cache settings or use pam-gnupg.

I actually wasn't getting continually prompted for my gpg password. It was more like even when I was within cache period, I was getting prompted to enter the individual imap account passwords. That has now been resolved by re-creating the gpg files manually.

@hakova

This comment has been minimized.

Copy link

commented Jan 4, 2019

I got it to work :).

First I commented the line in ~/.msmtprc starting with tls_trust_file and saved it. Then, I manually issued the following command to learn about server's certificate:
msmtp --serverinfo --tls --tls-certcheck=off -a protonmail
From the output, I copied the SHA256 fingerprint for the server certificate, re-edited the ~/.msmtprc file, removed comment from the line starting with tls_trust_file. Under protonmail account settings, I added the following lines:
tls_trust_file <Tab>
tls_fingerprint -pasted SHA256 fingerprint here-
The first line with blank tls_trust_file specification is needed to unset the trusted file. The fingerprint on the second line is then used for tls_handshake instead.
I confirm now that I can send email via neomutt from my protonmail account. I hope this helps others dealing with this problem.
@LukeSmithxyz : Please see my previous message above. I believe the wizard messes up while creating some gpg files that contain individual account passwords. Manually re-creating them works.

@bepolymathe

This comment has been minimized.

Copy link

commented Jan 4, 2019

@hakova You don't mean instead that you edited ".msmtprc" for this ? I don't have any tls_trust_file option in .muttrc

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented Jan 4, 2019

@hakova As I said, it password encyption works on a fresh install for me. Do you, by any chance, have any particularly strange characters in your password? Maybe quotation marks if that's possible? The script might be mangling some particular characters.

@hakova

This comment has been minimized.

Copy link

commented Jan 4, 2019

@hakova You don't mean instead that you edited ".msmtprc" for this ? I don't have any tls_trust_file option in .muttrc

Yes @bepolymathe , ~/.msmtprc was what I meant. I edited the post above for future. I am sorry for the silly mistake.

@hakova As I said, it password encyption works on a fresh install for me. Do you, by any chance, have any particularly strange characters in your password? Maybe quotation marks if that's possible? The script might be mangling some particular characters.

I only have letters, numbers and dashes in my passwords, but looking back I remember how I entered them to the mutt-wizard, and perhaps that created the problem. I selected the password with the mouse and middle-clicked to the mutt-wizard password prompt field. I thought I did a good job, but maybe not good enough. For protonmail, I think the bridge has a problem with the trust_file and therefore the need to authenticate using something else...

@bepolymathe

This comment has been minimized.

Copy link

commented Jan 5, 2019

@hakova Okay great, that's clearer.
I'll try your method....

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented Apr 26, 2019

Would you mind sharing your working msmtp and mbsync config files or sending them to me?

I've already pushed a change to make sure the SSLType is right for Protonmail, so mbsync might work out of the box now.

@hakova

This comment has been minimized.

Copy link

commented Apr 26, 2019

@bepolymathe

This comment has been minimized.

Copy link

commented Apr 26, 2019

Hi,

My msmtp config ( in /home/me/.config/msmtp/config ) with the new wizard.

defaults
auth	on
tls	on
tls_trust_file	/etc/pki/tls/certs/ca-bundle.crt
logfile	~/.config/msmtp/msmtp.log

account protonmail
host 127.0.0.1
port 1025
from my@email.com
user my@email.com
tls_trust_file	
tls_fingerprint <MY FINGERPRINT>
passwordeval "pass mutt-wizard-protonmail"

It works, i can send mails....
Enjoy ;-)

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented Apr 26, 2019

Now where do you get this tls_fingerprint? Is it supplied by Protonmail?

@bepolymathe

This comment has been minimized.

Copy link

commented Apr 26, 2019

I use this command :

msmtp --serverinfo --tls --tls-certcheck=off -a protonmail

And get the TLS Certificate SHA256 Fingerprint

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented Apr 26, 2019

So is it different for each user though? I don't know.

@RealAestan

This comment has been minimized.

Copy link

commented Apr 26, 2019

I don't have this in my config and it's working. Default from mutt-wizard is perfect for me 👍

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented Apr 27, 2019

Really? That's good news. It'll be nice to close this issue. Are there other PM users who can report the newest version working seamlessly without needing manual dotfile changes?

@bepolymathe

This comment has been minimized.

Copy link

commented Apr 27, 2019

Hi,

It's strange. We have been forced to use this fingerprinting workaround for months now with @hakova . And I don't see what the mutt-wizard changes in this case.

I think we need to deepen the diagnosis.

Which version of the protonmail-bridge? Which distribution?
On my side, protonmail-bridge V 1.1.3 and fedora 29.

@RealAestan Were you using the mutt-wizard in its previous version? What is your configuration (only one proton account / several)? You don't have an SSL error message by default ?

It would be necessary to do tests with fresh installation in VM but I don't have the possibility to do it now.

@RealAestan

This comment has been minimized.

Copy link

commented Apr 27, 2019

Protonmail bridge (1.1.4) and mutt-wizard both from the AUR, Im running this on Manjaro with modified dotfiles from Luke. I was not using mutt-wizard in previous version and I only have my protonmail account configured. I don't have any SSL error by default. Hope it helps

@RealAestan

This comment has been minimized.

Copy link

commented Apr 27, 2019

Oh you was probably right after boot this morning its giving me an error about my tls certificate. :/ Then I should do like you have in your config file with tls_fingerprint ?

@RealAestan

This comment has been minimized.

Copy link

commented Apr 27, 2019

Ok I added tls_fingerprint to .msmtprc and it's working now, I also had to change path to .gpg file for password from wizard mutt dir to password-store dir (probably settings of pass on my end idk)

@j0ma

This comment has been minimized.

Copy link

commented Apr 30, 2019

Hi everyone,

Really? That's good news. It'll be nice to close this issue. Are there other PM users who can report the newest version working seamlessly without needing manual dotfile changes?

I can report that something is not working in the newest version for me out-of-the-box. I'm also not using Arch, but PureOS -- not sure if that would make a difference.

Here are my specs:

Operating System: PureOS GNU/Linux 8 x86_64 
Protonmail Bridge Version: 1.1.4 (also tried with 1.1.3 without any luck)

I haven't tried the dotfile changes yet -- just wanted to document that not everything is working after simply installing mutt-wizard and its dependencies.

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented May 2, 2019

Okay I want to ask some things to figure this out. I can't test anything since I don't have PM or especially a paid account:

  • I assume this "fingerprint" is specific to each computer? I.e. PM Bridge is local on your machine, right?
  • So as @bepolymathe showed this command:
msmtp --serverinfo --tls --tls-certcheck=off -a protonmail

will give you the fingerprint, but is it in the proper format, or does it come with more output? That is, if I just have the above command output to a file, would it work if that file were given as the argument to tls_fingerprint? If not, how should the output be grepped to be what we want?

@hakova

This comment has been minimized.

Copy link

commented May 2, 2019

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented May 2, 2019

So the SHA256 fingerprint is what we want? The whole big long thing? That you pasted into the msmtp config file?

@hakova

This comment has been minimized.

Copy link

commented May 2, 2019

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented May 2, 2019

Okay. I've pushed a change that tries to automatically add the fingerprint. I expect that I missed something since I'm necessarily writing blind here.

If anyone wants to try it out, please tell me what happens. Back up your old configs first, I want a fresh test.

@j0ma

This comment has been minimized.

Copy link

commented May 2, 2019

After running mw purge, I was able to set it up with my @protonmail.com domain, but not the @pm.me version. Using the latter still throws the following:

It seems that either you inputted the wrong password or server settings, or there are other requirements for your account out of the control of mutt-wizard.

FWIW, I also tried to give mw my PM username without a domain, and with @protonmail.com when setting up @pm.me, sadly without any luck.

Could this be a matter of simply adding another case after the following?

+       case "$service" in
+               protonmail.*) protonfinger || return 1 ;;
+       esac

Thanks anyways for the quick update @LukeSmithxyz !

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented May 2, 2019

So you didn't have to add the fingerprint manually? Everything worked fine including sending mail?

Yeah, that case statement would be the issue, I'll be sure to amend it for pm.me.

@j0ma

This comment has been minimized.

Copy link

commented May 3, 2019

Nope didn't add anything manually. Thanks also for adding @pm.me to the case statement, my address creation ended up working now after trying with a fresh install.

However, to answer your 2nd question, everything didn't work fine unfortunately.
I am right now encountering a bug after I run mbsync protonmail, and see the following message:

C: 0/1  B: 0/0  M: +0/0 *0/0 #0/0  S: +0/0 *0/0 #0/0gpg: decryption failed: No secret key

Skipping account protonmail-remote, password command exited with status 2

Is this to be expected? When I try to simply open neomutt, I see the following:

/home/<my_username>/.local/share/mail/protonmail/INBOX is not a mailbox.

Not quite sure what's going wrong? FWIW I'm using a PGP smart card and it's plugged in normally. I don't the card is the issue since decryption has been working normally otherwise, but i thought I'd just throw it out there.

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented May 3, 2019

Uh, okay, well if you can neither download or access your mail, what did you originally mean by it working?

Show me the output of ls ~/.local/share/mail/protonmail/.

Also, show me the output of mbsync -l protonmail.

@j0ma

This comment has been minimized.

Copy link

commented May 3, 2019

I was referring to simply getting the acount creation to go through -- sorry for the n00b confusion. :)

However I think it might've actually been the PGP smart card that's the issue.
I created a bogus PGP key and ran pass init again, and now mbsync protonmail works, and i am able to download mail.

mbsync -l protonmail gave this when using the smart card:

gpg: decryption failed: No secret key
Skipping account protonmail-remote, password command exited with status 2

and now gives

INBOX
All Mail
Archive
Folders/Utilities
Folders/financial
Folders/grad_school
... [ omitted a bunch of folders here for privacy reasons ]
Folders/travel
Sent
Spam
Trash

as it should.

ls ~/.local/share/mail/protonmail similarly shows all folders of my protonmail account.

I can now also open and download mail fine. However, when I try to

msmtp: TLS certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown.

msmtp: could not send mail (account protonmail from /home/<username>/.msmtprc)
msmtp: cannot log to /home/<username>/.config/msmtp/msmtp.log: cannot open: Permission denied
msmtp: log info was: host=127.0.0.1 tls=on auth=on user=<my_username> from=<from_address> recipients=<to_address> errormsg='TLS certificate verification failed: The certificate is NOT trusted. The certificate issuer is unknown. ' exitcode=EX_UNAVAILABLE

After adding the tls_fingerprint line via @bepolymathe 's workaround above using msmtp --serverinfo --tls --tls-certcheck=off -a protonmail, both sending and downloading mail now seem to work.

So TL;DR:

  • "it was working" = account creation was working
  • PGP smartcard seemed to be the issue => using a regular PGP keypair fixed ability to download mail
  • tls_fingerprint manual workaround was still needed to be able to send mail
@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented May 3, 2019

Can you show me what the msmtp config looked like before you manually edited it?

That was suppose to have been what I just added, but something isn't working right.

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented May 3, 2019

Did you have to add tls_trust_file as well?

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented May 20, 2019

Well, I've added in the tls_trust_file to PM accounts as well.

Should I close this issue? I'm pretty sure that's about everything, so mutt-wizard should be as compatible as possible with Protonmail Bridge and shouldn't require the user to change any other config files.

@hakova

This comment has been minimized.

Copy link

commented May 20, 2019

@LukeSmithxyz

This comment has been minimized.

Copy link
Owner

commented May 20, 2019

Okay great, thanks!

Yeah I think I'll close this. There might be some issues in the future, but I think this thread is a little big and mostly related to the original version anyway.

I'm pretty sure that PM should be working out of the box now so I'll let it be.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants
You can’t perform that action at this time.