-->
Select the message that you want to permanently delete. To permanently delete a folder in Outlook, go to the Folders pane and select the folder. Press Shift + Del. Or, go to the Home tab, press and hold Shift, and select Delete. A dialog box opens and warns you that the message will be permanently deleted. Here's how to set up Outlook to immediately and permanently delete messages marked to be expunged in IMAP email accounts: For Outlook 2019, 2016, 2013, and 2010 Go to Folder. In the Clean Up group, select Purge. Open Outlook application click 'Send/Receive', go to 'Send/Receive groups' and then select the Define Send/Receive Groups. Another pop-up will open, click New and under 'Send/Receive Group Name' box give a name to the group. Under this new pop-up, choose the Accounts for which you want to create this group.
[IIMAPTransport::Expunge is available for use in the operating systems specified in the Requirements section. It may be altered or unavailable in subsequent versions.]
Sends the EXPUNGE command to the Internet Message Access Protocol (IMAP) server.
Syntax
Parameters
wParam [in]
Type: WPARAM
Specifies a WPARAM that together with lParam forms a unique transaction ID assigned by the caller to this IMAP command and its responses. The value can be anything except zero, which is reserved for unsolicited responses.
lParam [in]
Type: LPARAM
Specifies an LPARAM that together with wParam forms a unique transaction ID assigned by the caller to this IMAP command and its responses. The value can be anything except zero, which is reserved for unsolicited responses.
pCBHandler [in]
Type: IIMAPCallback*
Specifies a pointer to the IIMAPCallback interface to use to process the responses for this command. If this parameter is NULL, then the default callback interface is used. The default callback interface is specified in the IIMAPTransport::InitNew method, which initialized this IIMAPTransport object.
Return value
Type: HRESULT
Returns one of the following values.
| Return code | Description |
|---|---|
| Indicates success. |
| Indicates that an unknown error has occurred. |
| Indicates that an attempt to allocate memory failed. |
| Indicates that the server is not in an authenticated state and cannot accept this command. |
Requirements
| Minimum supported client | Windows XP [desktop apps only] |
| Minimum supported server | Windows Server 2003 [desktop apps only] |
| Product | Outlook Express 6.0 |
| Header |
|
| IDL |
|
| DLL |
|
Microsoft has fixed an Outlook bug that blocked users from forwarding or replying to emails containing embedded hyperlinks pointing to long URLs.
Outlook for PC users experiencing this issue are seeing 'Cannot send this item' errors according to customers' reports on Microsoft's community website.
Others have also pointed out on Reddit that these errors have also started showing up on long email threads beginning with February.
The issue appears when replying to emails with long links in the body when processed with SafeLinks or when the 2084th character in a link is an escaped character.
Microsoft has fixed the known issue in Outlook for PC build 13913.10000, which should roll out in production Current Channel during late April.
Workaround available until fix goes live
Microsoft also provides a workaround for users affected by this bug until the fix will roll out.
To get rid of 'Cannot send this item' errors when replying or forwarding emails in Outlook, you have to do one of the following:
- Change the email format from HTML to Rich text. Go here for more information and detailed steps: Change the message format to HTML, Rich Text Format, or plain text - Outlook (microsoft.com)
Remove any long links in the body of the email before replying.
Reply to the email using Outlook Web App (OWA)
Switch Office to Semi Annual Channel where the bug is not introduced. To do this, follow the steps here: Change the Microsoft 365 Apps update channel for devices in your organization
Microsoft is also currently investigating issues where the follow-up flag status is displayed in sent messages incorrectly and error messages being displayed when sharing a calendar in Microsoft 365.
Last year, Redmond addressed a major issue affecting Microsoft Outlook worldwide with the application immediately crashing on launch with 0xc0000005 errors displayed in the Windows Event Viewer.