roundcube/rainloop missing lots of sent emails... dovecot problem?

Discussion in 'ISPConfig 3 Priority Support' started by craig baker, Mar 15, 2023.

  1. craig baker

    craig baker Member HowtoForge Supporter

    I've got a customer with a LOT of emails. and I can go into the Maildir and see (grepping) that lots of emails from an address are infact there.
    but under the sent mail almost nothing shows up!

    I suspect dovecot indices are messed up. but its not a linux user (ispconfig3 of course) so how do I get dovecot to reindex all her emails?
    I read a force-resync but the -u user would surely refer to a linux user and she is only an ispconfig mailbox.

    any other ideas as to why sent emails would not be showing up under webmail? (they DO appear under outlook as well - so the emails clearly SHOULD be showing!)
    thanks. once again.
    oh - one other small items - ONE domain is getting a certbot warning that the cert will expire. I assume just uncheck-recheck the letsencrypt box should fix it? or anything else I need to look at first?
    thanks once again. again.

    and one other small thing. My server spontaneously rebooted at 11am this morning. never happened before. Dont see anything in /var/log/messages that might give me a clue as to why??
    any thoughts?

    thanks once again. again. again.
     
  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    The -u option of doveadm refers to a email user, e.g. [email protected].

    Maybe the sent folder is not configured correctly in the webmail?
     
  3. craig baker

    craig baker Member HowtoForge Supporter

    It used to work properly. And slme emails do show up right lots in fact. Its just missing a bunch!
    Whats right command to resync all boxes for the user?
    Yikes! Server just rebooted again. What the heck???
     
  4. pyte

    pyte Well-Known Member HowtoForge Supporter

    Check the last reboots or shutdowns with:
    Code:
    last -xF reboot shutdown | head
    Then check /var/log/syslog for that timestamp. Or check the journalctl with something like
    Code:
    journalctl | egrep  '(shutdown|reboot)'
     
  5. craig baker

    craig baker Member HowtoForge Supporter

    alas:
    [root@ns10 etc]# last -xF reboot shutdown | head
    reboot system boot 4.18.0-193.19.1. Wed Mar 15 12:41:02 2023 still running
    reboot system boot 4.18.0-193.19.1. Wed Mar 15 11:05:04 2023 still running
    reboot system boot 4.18.0-193.19.1. Thu Jul 28 21:08:20 2022 still running
    [root@ns10 etc]# journalctl | egrep '(shutdown|reboot)'
    [root@ns10 etc]#
    nothing interesting!
     

Share This Page