-
Notifications
You must be signed in to change notification settings - Fork 12
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
Cant sync mail #546
Comments
@nzola is stuck likewise? In any case, he just wrote:
|
@nzola Please email privately me the contents of /lokole/state/settings.env from the 0.6.10 machine please. |
@jvonau I rushed to catch the bus. I will send it late at midnight when I am home |
The piece of code where the error was being thrown was a new(well not so new anymore) piece that was added as part of the IIAB integration funny enough, discussion here. check_connection() basically checks for an existing connection before attempting to dial up via a USB modem. In short, as @jvonau pointed out, the OPWEN_REMOTE_ACCOUNT_HOST variable is not set. This should also probably be returned in the register UI. That being said, @nzola is using the install script so it is definitely odd that this variable would not be set. |
Looking at the install script, it does not even mention or set the OPWEN_REMOTE_ACCOUNT_HOST variable. Maybe this should be 'mailserver.lokole.ca'. Maybe I should just change it it 'OPWEN_EMAIL_SERVER_HOSTNAME'? |
Noticed 3 vwdial files and a directory are missing in the state directory of the new client install compared to ver 0.6.10 install Folder for victest1 client ver 0.6.10: pi@raspberrypi: Folder for victest9 client ver 0.6.14: pi@raspberrypi: |
I don't know why those crossing lines? |
Thanks @nzola for having shared:
@jvonau requests you post the contents of this file:
|
@nzola use triple backticks ``` before and after any code block — to make it easier to read: https://docs.github.com/en/github/writing-on-github/creating-and-highlighting-code-blocks |
Folder for victest1 client ver 0.6.10:
Folder for victest9 client ver 0.6.14:
|
Lets get some timestamps |
Replaced the contents of /lokole/venv/lib/python3.7/site-packages/opwen_email_client/util/network.py on jv-rpi-stock with this complete hack
that would be network.py here, that is enough for check_connection to work and email starts to flow but needs polishing. @nzola what is a valid address on vic1test that you know works? |
✅ Triple backticks: ``` ...before and after any code block. Make sure triple-backticks are on their own separate line: |
@nzola to find the backtick key (same as accent grave in French) on your keyboard, take a close look at these photos: https://google.com/search?q=backtick&tbm=isch (Very different from the single-quote / apostrophe!) |
Lokole on IIAB install (RPI B+ 0S Buster Lite had been failing since last night at this spot.
|
Re-open this issue, the sync issue will be uncovered once you register any new machine and is unresolved. |
Think the above is because there is a space in the attachment filename
These are 2 emails are outside world <-> remote lokole, the emails are sent and received on the the remote's end to the outside world and back, this looks like a copy of the email are kept somewhere else, for the web-portal maybe? |
Looks like the sent_at field is missing when the email was created. I'll look into this one as well. Should be a relatively easy fix. Thanks so much, these logs help big time |
Yes. That is correct. Any email received in gmail is missing @
…On Sat, May 22, 2021 at 4:24 PM Adam Sclafani ***@***.***> wrote:
Looks like the sent_at field is missing when the email was created. I'll
look into this one as well. Should be a relatively easy fix. Thanks so
much, these logs help big time
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#546 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEH5MMYBZMBEPFA3JWRIF3TTPA4KZANCNFSM442ZO3VA>
.
|
The top error was victest's test client. the second one was definitionally me outside <> client, but lets just keep an eye on the server, could be resolved over the last 2 weeks with the client side refinements.
Agreed, so I'm not sure if this is a client side issue when the email was created or on the server when a email is stored before forwarding, just have to eyeball the all logs for a awhile. |
Installed via curl install.py
fished this out of /lokole/logs/lokole_celery_worker.stderr.log
pi@raspberrypi:~ $ cat /lokole/state/settings.env
Only the server has this variable passed to the running processes. Think this would need to be embedded in the registration reply info.
The text was updated successfully, but these errors were encountered: