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
Adding Auth-User for imapsync #1495
Conversation
Thanks. Can you add an explanation below the auth user field? Use |
The description is not useful. People will not understand what this is for. This will lead to questions like "When do I need to use this field? Should I leave it blank? Should I enter just anything?" |
OK, I'll retry it ;-) |
How about that? |
What about the password? Does it need to be the password for the user or the "auth user"? What is an "auth user account" anyway? Is it a master user? What is "username" used for, when we specify the auth user? You see, this is frustrating for users. You know what you need it for, but not everyone will understand this. What will be read when using an "auth user" to determine the correct mails to fetch? Will it read the "To:" header? |
Hm .. You're right with the password! Because it has to be the password of the Login name - if set. Should I make a help-text to the password or describe it at the authuser anyway? But it doesn't change anything in the behavior of imapsync. It's "just" to login if you don't own the user account. I don't think that I should explain what it doesn't change (determine correct mails to fetch, read "To:" , ...) What about naming it "Auth User" with the description: |
One more try ;-) .. btw it's not that easy in ANY case. IMAP is different in exchange 2003/2007/2010/2013 and 2016. It took me hours to find the right imapsync-configuration for Exchange 2016 (even with the normal imapsync ;-) ). |
For example I found out (with the help of imapsync/imapsync#136 (comment) ) that Exchange is blocking the administrator account for IMAP at all (no login, no sync, ...) ;-) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
From my part, I would be ready for merge :-) .. Just say if I have to change something |
We added a custom parameter field, which should be used for that. 👍 Only a very few fields are hard-coded now. I hope you understand. |
I'm currently migrating user mailboxes from exchange 2016 to mailcow.
Because I don't want to create separated *.pst files, I'm using the admin account as "authuser" and now I can sync every mailbox with mailcow :-).
This PR should enable it for everybody