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
Syncing Imap Sync from Imap account to Mail Plus ? #442
Comments
Have you read Do you know what is an SSL certificate? |
I've read that page, although I'm having problems with how to get the IMAP account to sync to Mail Plus an email client on my NAS. As well I understand creating the folders but what is the purpose if imapsync.tk and privkey.pem ?
|
What happened?
You don't have to.
They are examples. imapsync.tk is a domain name, privkey.pem is a secret file certificate. What is your need? An online imapsync? the basic imapsync command line? transferring imap accounts? |
The first issue is why after installing IMAPSYNC by means of a Docker Manager in my NAS the container always starts and stops and I cannot figure out why; the logs don't explain anything ? |
I don't know what you did. Can you explain in more detail?
Do you mean imapsync always starts and stops?
The logs of what? Please, help me to help you:
|
I downloaded from my Synology NAS Container Manager the IMAPSYNC container, it installed successfully although when its started, within two minutes it stops; then it repeats this every two minutes. Within the Container Manager which is almost identical to Docker Compose there are logs but those logs don't tell me what the issue at hand is. That is all the information I have regarding getting this container to run without any issues, I know it's not that detailed but that is all I can say about the issue. |
My context: I don't know Container Manager and I don't know Docker Compose. What happens when you run the following:
|
|
Your imapsync works well. What imapsync command fails? |
The container which is identical to docker compose, always starts and stops ? How can I use if the container is always starting and stopping ? |
If the container doesn't work, don't start it. What gives the following command:
And then what happens when you open a browser on the host address running the previous command? |
The command returns nothing but; docker: Error response from daemon: driver failed programming external connectivity on endpoint elated_joliot (8b1dc5350aae78c6153013b185a9f0c0cf49608d85acd64f96eba7657dc83516): Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use. |
Do you have a web server running on port 80? And this one:
|
Followed by the command not returning to a prompt, I have to terminate the command to get back to a prompt at the last line posted above. |
Is it possible that there is an error for the container ? |
Thanks for the report.
It's the normal behavior, it is a command working in the foreground.
Yes, that's the way to end it.
I don't know. What you showed me tells that imapsync and the online service are running well when you run them. |
Why does the container in and equivalent to docker compose consistently start and stop every two minutes; a container is suppose to continuously run ? |
I don't know Container Manager and I don't know Docker Compose but now I know they are equivalent. Why do you use something not working when there is no problem without it? |
Alright I figured out what was the problem; I wasn't aware that this container is not a service. As my second question to this issue; what arguments must I use to direct mail to a specific email client whether on a network or on a drive ? |
Congratulations!
I don't know what that means but I let it to you :-)
There is no option for that, imapsync can't sync directly on a disk. Imapsync can't sync either to an email client because imapsync is an email client itself, it talks to email imap servers. |
How can I get Imapsync to be incorporated into an email client so that I can download the emails from IMAP to the client ? |
You could ask the email client developer. |
So what exactly did you change? I was looking for a way to run imapsync on a synology NAS and figured that Docker should be the easiest option. When I just install imapsync via the Synology Docker GUI and start it, it just stops again. The same as you reported. But what does "I wasn't aware that this container is not a service." mean? What did you change to fix it and keep it running? |
He didn't run imapsync as a service, but just in a command line session. |
I'm new to docker and containers and I'm having some issues with setting up this container.
What is a privkey.pem & imapsync.tik ?
From what I understand I must create a folder called
letsencrypt/live
but what is a docker.imapsync.tk/privkey.pem ?The text was updated successfully, but these errors were encountered: