Before today, mailbox.org’s 2FA mechanism was unorthodox. In the login screen, you typed in the TOTP in the password field and then added a 4 digit static pin at the end. This got people confused, as it’s different than the usual login+password then TOTP. Now it’s just like that.

There’s also other goodies, like separate passwords for IMAP and SMTP, WebDAV, CardDAV/CalDAV (one password for both), Exchange Sync. Before today, you’d be using your main mailbox.org password for all of the above. Looks like IMAP access is not even possible without creating a separate password https://kb.mailbox.org/en/private/account-article/how-to-use-two-factor-authentication-2fa/

There doesn’t seem to be support for the YubiKey TOTP anymore. No passkeys or hardware webauthn either for now.

mailbox.org is based on OpenXchange.

  • LWD@lemm.ee
    link
    fedilink
    English
    arrow-up
    12
    ·
    4 days ago

    Okay, so for those of us using third party apps like Thunderbird, everything is done using app specific passwords, which is great

    The new feature for Email App Passwords for external email programmes

    But if this is a new feature, how did third party apps work before? Could people just not use them if they enabled 2FA?

    • Great Blue@infosec.pub
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      3
      ·
      4 days ago

      Basically, yes, they couldn’t use them. The old 2FA had a really weird implementation…

      • 20nat@feddit.it
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 days ago

        This is just wrong, you used the main account password instead of an app password

      • Rogue1633@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        2
        ·
        4 days ago

        You could use third party clients with 2FA enabled in the past (at least I could). I think I used my normal password for the clients, so no real 2FA on that side, but that’s no different from the new app specific passwords. IMAP doesn’t allow 2FA so every mail provider allowing third party clients essentially has a weak point with no 2FA there.

      • Creat@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 days ago

        I’m not sure I quite understand how this would make them unable to support normal 2fa until now.

        Keycloak is one of the most configurable and flexible auth solutions, and there is no way it didn’t support otp based 2fa until recently.

  • Cadende [they/them]@hexbear.net
    link
    fedilink
    English
    arrow-up
    8
    ·
    edit-2
    4 days ago

    Bit of trivia but I think I know why the 4 digit pin thing existed! It’s an out-of-the-box feature on freeRADIUS, I ran across it in a pfsense environment in the past. I thought it was neat (esp. in the absence of passwords, this was primary auth with public keys and then 2fa on top) but ultimately too convoluted for most users

  • CringyMikami@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    2 days ago

    Maybe most people using Mailbox know about this but I’ll still mention that using Mailbox kinda requires having your own domain.

    Reason is the same as Posteo (unless Posteo changed something lately) : mail adresses will get recycled after some time when you stop using the service and close your account.

    Most other providers blacklist adresses so they can’t get reused when an account gets deleted.

  • RiQuY@lemm.ee
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 days ago

    How can I enable it? I received the mail but my login is still using pin+otp and in the settings there is no option to migrate to normal F2A, only the old pin+opt thing.

    • BenchpressMuyDebil
      cake
      OP
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 days ago

      Read the The rollout of Login 2.0 for our customers se tion in the linked post