#3136 new
Gareth King

Inbox Connection Issue

Reported by Gareth King | October 12th, 2022 @ 10:32 AM

I've recently updated to the latest beta of MailMate (v5918) from the previous beta (v5895) and have an issue with delays to receiving email. In particular I receive email on my other devices (iPad and iPhone using Outlook) much faster than on my Mac (using MailMate).

If I send an email from another account / device it's not received by MailMate for 5-6 minutes whereas it appears quickly on other devices.

I'm using MailMate with Office365 and when checking settings on MailMate it shows the Synchronization Schedule for the INBOX to be 'Connected'.

If I select the Mailbox and 'Synchronize INBOX' the email shows up straight away.

Therefore it seems to me that the INBOX isn't really 'Connected' to MailMate but is being synchronized every 5 minutes.

I have updated to the latest Test Build (5921) that also has the issue.

MailMate v5918 didn't have this issue (not sure if it's possible to 'downgrade' to check it's an issue with MailMate and not the server?).

I'm using macOS Ventura (beta 11 / 22A537b) so wasn't sure whether to report this issue given it may be a problem with the OS and not MailMate. However given that MailMate v5918 was working fine on Ventura I think it's an issue with the latest builds of MailMate.

Comments and changes to this ticket

  • benny

    benny November 1st, 2022 @ 02:43 PM

    Nothing changed in the related code. Has something changed in your network setup? There might be something which cuts network connections without MailMate being able to detect it (iPad/Mail works differently). MailMate will then only be able to detect new messages whenever it explicitly checks for new messages.

    You can try opening the Activity Viewer to see what happens for the Connected connection (so-called IDLE state). New messages should show up immediately. Wait to see what happens on the connection when it does show up (without manually synchronizing it).

  • Gareth King

    Gareth King November 1st, 2022 @ 03:18 PM

    Thanks Benny

    I haven't changed anything in my network set up - although I could reboot everything to see if that helped?

    I did get something in the Activity Viewer - not sure if this helps?

    15:13:56 Response after idling (900/900): timeout (9)
    15:13:56 C: DONE
    15:13:56 S: * 1 RECENT
    15:13:56 S: * 12 EXISTS
    15:13:56 S: * 2 RECENT
    15:13:56 S: * 13 EXISTS
    15:13:56 S: * 3 RECENT
    15:13:56 S: * 14 EXISTS
    15:13:56 S: S34 OK IDLE completed.
    15:13:56 C: S35 FETCH 12:* (UID)
    15:13:56 S: * 12 FETCH (UID 293010)
    15:13:56 S: * 13 FETCH (UID 293012)
    15:13:56 S: * 14 FETCH (UID 293014)
    15:13:56 S: S35 OK FETCH completed.
    15:13:56 C: S36 FETCH 12:* (INTERNALDATE)
    15:13:56 S: * 12 FETCH (INTERNALDATE "01-Nov-2022 15:01:52 +0000")
    15:13:56 S: * 13 FETCH (INTERNALDATE "01-Nov-2022 15:02:57 +0000")
    15:13:56 S: * 14 FETCH (INTERNALDATE "01-Nov-2022 15:03:21 +0000")
    15:13:56 S: S36 OK FETCH completed.
    15:13:56 Completed IDLE (4). Reset observed read/write timeouts: 8/8

    15:13:56 Handling reply
    15:13:56 Running action
    15:13:56 Handling request
    15:13:56 Ready to run action (type: 1006, retry count: 0)
    15:13:56 Fetching bodies for mailbox: INBOX
    15:13:56 C: G37 NOOP
    15:13:56 S: G37 OK NOOP completed.
    15:13:56 C: G38 UID FETCH 293010:293014 (UID BODY.PEEK[] RFC822.SIZE)
    15:13:57 S: * 12 FETCH (UID 293010 BODY[] {110747}
    15:13:57 S: Received: from AS2PR03MB9989.eurprd03.prod.outlook.com (2603:10a6:20b:649::8)
    15:13:57 S: by DB3 ...
    15:13:57 <108774 bytes>
    15:13:57 S: ... t;">

    =
    15:13:57 S:
    15:13:57 S: --9f97227075f7e9acf905d4b0cc484f57330e5dfacf228e8cb8eb333ce56d--
    15:13:57 S: RFC822.SIZE 361314)
    15:13:57 S: * 13 FETCH (UID 293012 BODY[] {85826}
    15:13:57 S: Received: from AS4PR03MB8177.eurprd03.prod.outlook.com (2603:10a6:20b:4e0::20)
    15:13:57 S: by DB ...
    15:13:57 <84122 bytes>
    15:13:57 S: ... _185314229_82810460.1667314914294--
    15:13:57 S:
    15:13:57 S: ------=_Part_185314228_708969232.1667314914294--
    15:13:57 S: RFC822.SIZE 234837)
    15:13:57 S: * 14 FETCH (UID 293014 BODY[] {7460}
    15:13:57 S: Received: from AS2PR03MB9743.eurprd03.prod.outlook.com (2603:10a6:20b:60c::22)
    15:13:57 S: by DB ...
    15:13:57 <7341 bytes>
    15:13:57 S: ... Hh+1QyxqDCeVbV+fM7R0?=
    15:13:57 S: =?us-ascii?Q?grzBZqYYJDo=3D?=
    15:13:57 S: MIME-Version: 1.0
    15:13:57 S:
    15:13:57 S: Test of idle
    15:13:57 S: RFC822.SIZE 46116)
    15:13:57 S: G38 OK FETCH completed.
    15:13:57 C: G39 UID FETCH 293010:293014 (FLAGS)
    15:13:57 S: * 12 FETCH (FLAGS (\Recent) UID 293010)
    15:13:57 S: * 13 FETCH (FLAGS (\Recent) UID 293012)
    15:13:57 S: * 14 FETCH (FLAGS (\Recent) UID 293014)
    15:13:57 S: G39 OK FETCH completed.
    15:13:57 Completed action (1006). Observed read/write timeouts: 8/8

    15:13:57 Handling reply
    15:13:59 Running action
    15:13:59 Handling request
    15:13:59 Ready to run action (type: 1009, retry count: 0)
    15:13:59 Copying 1 message(s)
    15:13:59 C: J40 NOOP
    15:13:59 S: J40 OK NOOP completed.
    15:13:59 C: J41 NOOP
    15:13:59 S: J41 OK NOOP completed.
    15:13:59 C: J42 UID MOVE 293010 "Junk Email"
    15:13:59 S: * OK [COPYUID 1266 293010 18262]
    15:13:59 S: * 12 EXPUNGE
    15:13:59 S: * 13 EXISTS
    15:13:59 Warning: Unnecessary EXISTS response received.
    15:13:59 S: J42 OK MOVE completed.
    15:13:59 Completed action (1009). Observed read/write timeouts: 8/8

    15:13:59 Handling reply
    15:13:59 Running action
    15:13:59 Handling request
    15:13:59 Ready to run action (type: 1007, retry count: 0)
    15:13:59 C: H43 NOOP
    15:13:59 S: H43 OK NOOP completed.
    15:13:59 Storing flags (enable: '$NotJunk', disable: '')
    15:13:59 C: H44 UID FETCH 293012:293014 (FLAGS)
    15:13:59 S: * 12 FETCH (FLAGS (\Recent) UID 293012)
    15:13:59 S: * 13 FETCH (FLAGS (\Recent) UID 293014)
    15:13:59 S: H44 OK FETCH completed.
    15:13:59 Completed action (1007). Observed read/write timeouts: 8/8

    15:13:59 Handling reply
    15:13:59 Running action
    15:13:59 Handling request
    15:13:59 Ready to run action (type: 4, retry count: 0)
    15:13:59 C: S45 NOOP
    15:13:59 S: S45 OK NOOP completed.
    15:13:59 Running IDLE (still alive checks every 15 minutes)
    15:13:59 C: S46 IDLE
    15:13:59 S: + IDLE accepted, awaiting DONE command.

  • benny

    benny November 2nd, 2022 @ 12:56 PM

    Well, the output does not look like it includes the delay of an incoming message. It just shows a message arriving and then being fetched (no broken connection). Was the incoming message delayed?

  • Gareth King

    Gareth King November 3rd, 2022 @ 05:40 PM

    Yes the incoming message seems to be delayed by about 14 minutes if I don't do anything else in MailMate (e.g. the message will appear on my iPad from my Office365 account but not in MailMate until 14 mins later). If I send or delete a message from the Inbox the new message appears.

  • benny

    benny November 5th, 2022 @ 04:13 PM

    Ok, I cannot really see that delay in the activity log above. Please try this:

    • Open the Activity Viewer in the Window menu (this enables logging).
    • Relaunch MailMate.
    • Wait until you have seen a message arrive late.
    • Use “Help > Send Server Logs”.

    Then I'll review the logs to see if the server or the network connection is the cause of the delay.

  • Gareth King

    Gareth King November 5th, 2022 @ 05:26 PM

    Many thanks - server logs sent by email as requested.

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

Mac OS X email client.

Shared Ticket Bins

People watching this ticket

Pages