Checking for incoming emails on the serverThere are several reasons why an email message that is supposed to have arrived may not be in the user's mailbox. - The message has been blocked by an antispam before arriving on the BlueMind server. In that case, you must check your antispam solution's logs
The message is stuck in the BlueMind server's postfix queue. This typically happens when a user's usage quota is at full capacity. The email will be held in the postfix queue for 3 days. If after 3 days the server hasn't been able to deliver it, a non-delivery message will be sent to the sender. You can check whether the message is in the postfix queue using the command: | Bloc de code |
|---|
[root@bluemind ~]# postqueue -p
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
4E4D83AF8E 943 Thu Mar 2 07:10:58 full@bluemind.net
(host 192.168.124.72[192.168.124.72] said: 452 4.2.2 Over quota SESSIONID=<cyrus-4311-1488438658-1> (in reply to RCPT TO command))
full@bluemind.net |
To release the message, you can either ask the user to delete some emails or increase their quota, then wait for the message to be delivered or force postfix to try to deliver messages again using the postqueue command -f
If the email message is not stuck, you can find tracks of its arrival in the postfix logs (/var/log/maillog ou /var/log/mail.log): | Bloc de code |
|---|
Mar 1 20:45:32 bluemind postfix/lmtp[16928]: C5BF3135FAF: to=<user@bluemind.net>, relay=192.168.124.72[192.168.124.72]:2400, delay=0.32, delays=0.21/0.02/0.01/0.09, dsn=2.1.5, status=sent (250 2.1.5 Ok SESSIONID=<cyrus-12823-1488397532-1> [bluemind.net!user.user.INBOX () 2294]) |
This log line shows that the message with id number C5BF3135FAF has indeed been delivered to the inbox of 'user@bluemind.net' on 1 March at 20:45 hrs. You can find more details about the message, including the sender's address by searching the message-id: | Bloc de code |
|---|
[root@bluemind ~]# grep C5BF3135FAF /var/log/maillog
Mar 1 20:45:32 bluemind postfix/smtpd[16923]: C5BF3135FAF: client=smtp.domain.net[192.168.120.30]
Mar 1 20:45:32 bluemind postfix/cleanup[16927]: C5BF3135FAF: message-id=<AM5PR04MB3219A293B59D96973D338B01D2290>
Mar 1 20:45:32 bluemind postfix/qmgr[364]: C5BF3135FAF: from=<user2@domain.net>, size=8386, nrcpt=1 (queue active)
Mar 1 20:45:32 bluemind postfix/lmtp[16928]: C5BF3135FAF: to=<user@bluemind.net>, relay=192.168.124.72[192.168.124.72]:2400, delay=0.32, delays=0.21/0.02/0.01/0.09, dsn=2.1.5, status=sent (250 2.1.5 Ok SESSIONID=<cyrus-12823-1488397532-1> [bluemind.net!user.user.INBOX () 2294])
Mar 1 20:45:32 bluemind postfix/qmgr[364]: C5BF3135FAF: removed |
In this case, you can see that user2@domain.net is the sender of message AM5PR04MB3219A293B59D96973D338B01D2290 and it has been delivered to this user. The message-id is the identifier for the message only and it is found in the email header. The number at the end of the lmtp line (2294 in this case) corresponds to the email id in the user's INBOX folder, you can therefore find it in /var/spool/cyrus/data/b/bluemind_net/b/bluemind.net/u/user/user/2294. Following email movements/deletionsThe operations performed on an email message can be tracked through the bm-ips IMAP proxy logs: /var/log/bm-ips/ips.log Email movementsYou can find this information by searching the user's log in ID or the email ID | Bloc de code |
|---|
2017-04-28 06:27:46,844 [vert.x-worker-thread-9] n.b.i.m.n.i.ForwardToMQ INFO - [user2@bluemind.net] |
ROUNDCUBE srv: 192.168.150.150, tag A0001 in 47ms.
2017-04-28 |
273 [vert.x-worker-thread- |
7] n.b.i.m.i.MailboxIndexUpdater INFO - [user2@bluemind.net |
] onFlagsChanged:
2017-04-28 |
277 [vert.x-worker-thread- |
i.FlagsChangeRunnable INFO - [user2@bluemind.net][mbox.uid user_entity_23] |
lookup: imap://user/user2@bluemind.net/OTB
2017-04-28 |
284 [vert.x-worker-thread- |
change flags in imap://user/ |
284 [vert.x-worker-thread- |
Bulk START on index mailspool_alias_user_entity_ |
340 [vert.x-worker-thread- |
7] n.b.i.m.MailIndexService INFO - |
In this example, you can see that the user user2@bluemind.net has moved the email 7120 from the INBOX folder to the Trash folder and the email message's ID number in the Trash folder now is 20. Email deletionsSimilarly, bm-ips logs allow you to see an email deletion: | Bloc de code |
|---|
Bulk END (1)
2017-04-28 07:51:15, |
m.MailIndexService INFO - |
updated emails 1
2017-04-28 07:51:15, |
340 [vert.x-worker-thread-7] n.b.i.m.i. |
i.FlagsChangeRunnable INFO - |
Update time is 56ms.
2017-04-28 07:51:15, |
340 [vert.x-worker-thread-7] n.b.i.m.i.i.FlagsChangeRunnable INFO - [user2@bluemind.net][ |
OTB] Reindexing done in 67ms.
2017-04-28 07:51:15, |
[user2@bluemind.net] imap time: 9ms, total time: 83ms, overhead: 73ms.
2017-04-28 07:51:15, |
354 [vert.x-worker-thread- |
MailboxIndexUpdater INFO - |
[OTB] onMailsExpunged: '2818'
2017-04-28 07:51:15, |
359 [vert.x-worker-thread- |
i.UidExpungeRunnable INFO |
[user2@bluemind.net][mbox.uid user_entity_23] folder lookup: imap://user/user2@bluemind.net/OTB
2017-04-28 07:51:15, |
368 [vert.x-worker-thread- |
expunge: imap://user/user2@bluemind.net/OTB 2818
2017-04-28 07:51:15, |
368 [vert.x-worker-thread- |
Bulk START on index mailspool_alias_user_entity_23
2017-04-28 07:51:15, |
Bulk END (1)
2017-04-28 07:51:15, |
376 [vert.x-worker-thread-17] n.b.i.m. |
- expunge imap://user/user2@bluemind.net/OTB (2818) : 1 deleted
2017-04-28 07:51:15, |
376 [vert.x-worker-thread-17] n.b.i.m.i.i.UidExpungeRunnable INFO - [user2@bluemind.net][ |
OTB] Reindexing done in 22ms. |
In the case of multiple deletions, the message ID may not appear on its own but may be part of a range, in which case the logs will show: | Bloc de code |
|---|
2017-07-25 08:22:45,843 [vert.x-worker-thread- |
10] n.b.i.m.MailIndexService INFO - |
change flags in imap://user |
In the case of multiple deletions, the email ID may not appear directly but may be part of a range, in which case the logs will show: | Bloc de code |
|---|
2017-07-25 08:22:45,843 [vert.x-worker-thread-10] n.b.i.m.MailIndexService INFO - change flags in imap://user_entity_209667 29702:1:*You can see deleted IMAP folders with the following log in mail.log – or maillog, depending on your OS: | Bloc de code |
|---|
Apr 16 11:58:38 staging35 cyrus/imap[12116]: Deleted mailbox blue-mind.net!user.john^doe.test.big.big.big2 |
| Remarque |
|---|
Please note that times may differ in different log files, maillog uses system time while BM logs use UTC. |
RestorationFrom version 3.5.11, delayed delete has been set up at the cyrus level. This means that emails are actually deleted from the server after seven days only. In the meantime, they are present on the disk but not visible in IMAP.
This deletion mode is laying the groundwork for an upcoming double-bottom trash feature. To list a user's deleted emails, use this command: | Bloc de code |
|---|
unexpunge -l user/john@domain.net |
To restore an email message: | Bloc de code |
|---|
unexpunge -u -d user/john@domain.net 46908 |
46908 being the message id. To restore all a user's emails: | Bloc de code |
|---|
unexpunge -a -d user/john@domain.net |
For more information about these commands and how to pass them, please refer to the Cyrus documentation: https://www.cyrusimap.org/imap/reference/manpages/systemcommands/unexpunge.html |
