Arch Linux User Repository

Please, report oama related issues upstream and use this place for AUR related problems only.

After having an expired token, I decided to upgrade mailctl-bin and rerun the authorization process. The authentication in the browser is successful, followed by a 'Something went wrong' in the browser and an error message in the console, see below.

Any hints how to resolve this?

[user@monitor ~]$ mailctl authorize microsoft domain-support
To grant OAuth2 access to domain-support visit the local URL below with your browser.
https://oauth.domain.com/start
Authorization started ... 
Maybe.fromJust: Nothing
CallStack (from HasCallStack):
  error, called at libraries/base/Data/Maybe.hs:150:21 in base:Data.Maybe
  fromJust, called at lib/MailCtl/Authorization.hs:156:56 in mailctl-0.8.4-ed77150bdec61b23cd29a3b1c3fa763235c70531a3279dbd69ed8583eebc5f9a:MailCtl.Authorization

@ptdel, Thank you although I have not received anything.

Anyway, I have just pushed out a new AUR release.

I sent two (sorry) patch emails to what I am guessing is your preferred email address that update the PKGBUILD to point to sourcehut, feel free to apply or tell me to stop emailing you :D

Yes, the canonical repository of mailctl was moved to sourcehut. However, pre-compiled binary is provided there.

I am in the process of adapting PKGBUILD to the new situation, and will release a new AUR bin package asap. Meanwhile the most recent compiled mailctl binary can be downloaded from the link below:

https://git.sr.ht/~petrus/mailctl/refs/download/0.8.3/mailctl-0.8.3.tgz

it looks like the upstream maintainer has moved their code from github to sourcehut. the github links to the binary return a 404. patch sent in email to maintainer.

Finally, I have made progress.

I noticed that the behavior became a bit irregular which made me suspect memory corruption. This triggered me to suspect the Xen Hypervisor being used on this server.

I have installed the Xen hypervisor on my laptop and ran the same mailctl commands in the Dom0 (= privileged Xen VM guest), resulting in the same core dump.

What a pain! :)

I will investigate this further and keep you posted.

In fact, almost all actions crash except --help and --version I have tried a different linux user, which gives the same result. I have tried a new config.yaml and services.yaml, which gives the same result. It seems to crash fairly early in the process, but after --version and --help.

I bet it has something to do with the environment of this server, but I can't pin it down yet. Any suggestion is welcome.

[arthur@xxxx ~]$ mailctl access sdkjflsdjf
Illegal instruction (core dumped)
[arthur@xxxx ~]$ mailctl access sdkjflsdjf --debug
Illegal instruction (core dumped)
[arthur@xxxx ~]$ mailctl --help
mailctl - Provide OAuth2 renewal and authorization capabilities.

Usage: mailctl [--version] [-c|--config-file <config>] [--run-by-cron] [--debug]
               COMMAND

  Mailctl provides IMAP/SMTP clients with the capabilities of renewal and
  authorization of OAuth2 credentials.

Available options:
  -h,--help                Show this help text
  --version                Show version
  -c,--config-file <config>
                           Configuration file
  --run-by-cron            mailctl invoked by cron
  --debug                  Print HTTP traffic to stdout

Available commands:
  password                 Get the password for email
  access                   Get the access token for email
  renew                    Renew the access token of email
  authorize                Authorize OAuth2 for service/email
  fetch                    Get fdm to fetch all or the given accounts
  cron                     Manage running by cron
  list                     List all accounts in fdm's config
  printenv                 Print the current Environment
[arthur@xxxx ~]$ mailctl --version
mailctl version 0.7.4
Copyright (C) Peter Dobsan 2022
[arthur@xxxx ~]$ mailctl fetch
Illegal instruction (core dumped)
[arthur@xxxx ~]$ mailctl authorize sdjlkfdsjkf
Missing: <email>

Usage: mailctl authorize <service> <email>

  Authorize OAuth2 for service/email
[arthur@xxxx ~]$ mailctl authorize microsoft skdjlfsdjlkfdfs
Illegal instruction (core dumped)
[arthur@xxxx ~]$ mailctl list
Illegal instruction (core dumped)
[arthur@xxxx ~]$ mailctl printenv
Illegal instruction (core dumped)

Compiling mailctl on the server results in a working binary (no coredumps).

Source code used https://github.com/pdobsan/mailctl/archive/refs/tags/0.7.4.tar.gz

I have tried to reproduce the issue on my local machine (desktop), which resulted in a working mailctl access xxxxxxxxx.

All packages are up to date on the local machine, so package fdm is not an suspect anymore.

I will do further analysis to find a clue.