to get right the folders names for imap_mail_move/imap_mail_copy, do not guess, instead use imap_list
(PHP 4, PHP 5, PHP 7, PHP 8)
imap_mail_move — Move mensagens especificadas para uma caixa de correio
Move mensagens de correio especificadas por message_nums para a
caixa especificada em mailbox.
Observe que as mensagens de correio são, na verdade, copiadas para a
caixa mailbox, e as mensagens originais são sinalizadas para exclusão.
Isso implica que as mensagens em mailbox recebem novos UIDs.
imapUma instância de IMAP\Connection.
message_nums
message_nums é um intervalo e não só números de mensagens
(como descrito em » RFC2060).
mailboxO nome da caixa de correio, consulte imap_open() para mais informação.
Passar dados não confiáveis para este parâmetro é inseguro, a menos que imap.enable_insecure_rsh esteja desabilitado.
flags
flags é uma máscara de bits e pode conter esta única opção:
CP_UID - os números de sequência contêm UIDS
| Versão | Descrição |
|---|---|
| 8.1.0 |
O parâmetro imap agora espera uma instância de IMAP\Connection;
anteriormente, um resource imap válido era esperado.
|
Nota:
imap_mail_move() irá sinalizar a mensagem original com a marca de exclusão. Para excluí-la, é necessário chamar a função imap_expunge().
to get right the folders names for imap_mail_move/imap_mail_copy, do not guess, instead use imap_listAfter using imap_mail_move, imap_mail_copy or imap_delete it is necesary to call imap_expunge() function.The imap_mail_move() function's second parameter (message_nums parameter) accept two valid values:
Individual message number:
47
or
Array:
47,58,112
Remember four key things in combination!
1. This move function does not move anything, internally it creates a copy and then deletes the original!
2. You should be tracking the Message-Id header (that should be set!) internally to confirm the unique IMAP id.
3. Because when a message is pseudo-"moved" the original message and unique IMAP id are lost! That means after the internal copy (or to us, having been moved) is created you will then have to create a new connection to the second mailbox folder, list or search and verify by internal message identifiers to keep your mail shell synchronized with the external server. Which then in turn means...
4. You will have to track the copied message after it is destroyed in the first mailbox folder. That gives you two logical approaches to use:
4.1 Individually move the message then simply get an index of the destination folder (e.g. moving from inbox to trash), "move" the message using this command, getting the index of the trash mailbox folder and comparing the arrays to determine the oddball out.
4.2 But in reality we're moving multiple messages in a single go so you can scan the mailbox folder for each message however this presumes that the header (e.g. Message-Id) exists.
Example search:
$result = imap_search($mail_connection_folder_trash, "TEXT \"<24322757.12578452.2416351620568@domain.tld>\"", SE_UID);
In my limited experience of a few thousand emails only spammers or devastatingly underpaid developers have not set the Message-Id. You can not presume however that the missing header implies spam as my original system never set it. Hence why it may be necessary to search by a secondary or tertiary means in more non-common scenarios with oddball messages. This may occur in one-in-several thousand instances.
Hopefully this logic will spare a few people the time spent on conceptual work.