No incoming mails

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • boris
    Member
    • Apr 2019
    • 35

    #1

    No incoming mails

    I have a strange issue I need some help with:
    I moved my mailserver added the new credentials in ESPO, pushed the test buttons (connection OK, test mail sent out OK). Sending mails works fine, but I don't receive anything.
    A look in the log shows no error
    Tested with 2 other mailclients --> same credentials work here, the folder is present and contains new mails.

    Any ideas?
    Last edited by boris; 05-07-2026, 04:41 PM.
  • boris
    Member
    • Apr 2019
    • 35

    #2
    I found a solution. Made a duplicate of the mailaccount as this worked I deleted the old one. Strange bug in Espo, but simple solution...

    Comment

    • yuri
      EspoCRM product developer
      • Mar 2014
      • 9827

      #3
      This might be related: https://github.com/espocrm/espocrm/issues/3654

      Comment

      • boris
        Member
        • Apr 2019
        • 35

        #4
        It seems to be the same here. Duplicating the current mail account and syncing again is the only way to get ESPO to fetch mails again. At least only 12 accounts with around 100 GB. One nightshift...

        Comment


        • victor
          victor commented
          Editing a comment
          If you have not deleted old emails, they will not be recreated (fetched again). Only emails that did not exist in your instance will be recreated.
      • boris
        Member
        • Apr 2019
        • 35

        #5
        Hi Victor, this is exactly the problem: New mails were not created in ESPO. I tried the files from issue 3654, this didn't solve my problem. As said: Only solution was duplicating the mailaccounts with the same settings...

        Comment

        • yuri
          EspoCRM product developer
          • Mar 2014
          • 9827

          #6
          After moving the server, if the UIDVALIDITY didn't change (e.g. it was 1 and by default was set to 1 with the new server), it may cause such a problem which is expected.

          An additional solution that was implemented yesterday is to reset the account: https://github.com/espocrm/espocrm/issues/3667

          Comment

          Working...