Attach current email as attachment to current email reply in newer Outlooks












0















I have this code:



Sub Application_ItemSend(ByVal Item As Object, Cancel As Boolean)
Dim strSubject As String

Select Case True
Case (InStr(Item.Subject, "PIR") > 0)
If InStr(Item.Subject, "RE") > 0 Then
strSubject = Replace(Item.Subject, "RE:", "", vbTextCompare)
Else
End If

If InStr(Item.Subject, "FW") > 0 Then
strSubject = Replace(Item.Subject, "FW:", "", vbTextCompare)
Else
End If

If strSubject = "" Then
Else
Set objRecip = Item.Recipients.Add("email.address@domain.com")
objRecip.Type = olBCC
objRecip.Resolve
Item.Subject = Trim(strSubject)
Item.Save
Item.Attachments.Add Item
Item.Save
End If
Case (InStr(Item.Subject, "PIQ") > 0)
If InStr(Item.Subject, "RE") > 0 Then
strSubject = Replace(Item.Subject, "RE:", "", vbTextCompare)
Else
End If

If InStr(Item.Subject, "FW") > 0 Then
strSubject = Replace(Item.Subject, "FW:", "", vbTextCompare)
Else
End If

If strSubject = "" Then
Else
Set objRecip = Item.Recipients.Add("email.address@domain.com")
objRecip.Type = olBCC
objRecip.Resolve
Item.Subject = Trim(strSubject)
Item.Save
Item.Attachments.Add Item
Item.Save
End If
'#### Enable the below to capture more doc types ####
' Case (InStr(Item.Subject, "ABC") > 0)
' If InStr(Item.Subject, "RE") > 0 Then
' strSubject = Replace(Item.Subject, "RE:", "", vbTextCompare)
' Else
' End If
'
' If InStr(Item.Subject, "FW") > 0 Then
' strSubject = Replace(Item.Subject, "FW:", "", vbTextCompare)
' Else
' End If
'
' If strSubject = "" Then
' Else
' Set objRecip = Item.Recipients.Add("email.address@domain.com")
' objRecip.Type = olBCC
' objRecip.Resolve
' Item.Subject = Trim(strSubject)
' Item.Save
' End If
End Select

End Sub


This is in ThisOutlookSession and checks all sent emails for a specific subject.



This code works on my Outlook 2010, but on other Outlooks, it errors at "Item.Attachments.Add Item" saying "a message cannot be attached to itself".



Is there a way round this in newer versions?





On Outlook 2010 the user would hit reply (or forward) to reply to who sent the email to them.



A copy needs to be attached so the added email address (BCC "email.address@domain.com") via the code, gets a copy. This email address is a system email address that strips attachments and saves them into our workflow software under the job (which is in the subject line). That is why we need to send an attachment of the email, so if the user says "Do xyz on this job" then that email message is saved into our workflow system.










share|improve this question

























  • This code doesn't seem to make sense. You clearly can't attach a message to itself. If you want to send the current message, you forward it to another address. Why would you think you need to do this?

    – Ken White
    Nov 15 '18 at 3:28











  • Well it does work flawlessly on Outlook 2010, just not 2013 Basically the user would hit reply (or FW) to reply to who sent the email to them, but a copy needs to be attached so that the added email address (BBC "email.address@domain.com") via the code above, gets a copy. This email address is a system email address that strips attachments and saves them into our workflow software under the job (which is in the subject line). That is why we need to send an attachment of the email, so if the user says "Do xyz on this job" then that email message is saved into our workflow system.

    – Stildawn
    Nov 16 '18 at 1:15


















0















I have this code:



Sub Application_ItemSend(ByVal Item As Object, Cancel As Boolean)
Dim strSubject As String

Select Case True
Case (InStr(Item.Subject, "PIR") > 0)
If InStr(Item.Subject, "RE") > 0 Then
strSubject = Replace(Item.Subject, "RE:", "", vbTextCompare)
Else
End If

If InStr(Item.Subject, "FW") > 0 Then
strSubject = Replace(Item.Subject, "FW:", "", vbTextCompare)
Else
End If

If strSubject = "" Then
Else
Set objRecip = Item.Recipients.Add("email.address@domain.com")
objRecip.Type = olBCC
objRecip.Resolve
Item.Subject = Trim(strSubject)
Item.Save
Item.Attachments.Add Item
Item.Save
End If
Case (InStr(Item.Subject, "PIQ") > 0)
If InStr(Item.Subject, "RE") > 0 Then
strSubject = Replace(Item.Subject, "RE:", "", vbTextCompare)
Else
End If

If InStr(Item.Subject, "FW") > 0 Then
strSubject = Replace(Item.Subject, "FW:", "", vbTextCompare)
Else
End If

If strSubject = "" Then
Else
Set objRecip = Item.Recipients.Add("email.address@domain.com")
objRecip.Type = olBCC
objRecip.Resolve
Item.Subject = Trim(strSubject)
Item.Save
Item.Attachments.Add Item
Item.Save
End If
'#### Enable the below to capture more doc types ####
' Case (InStr(Item.Subject, "ABC") > 0)
' If InStr(Item.Subject, "RE") > 0 Then
' strSubject = Replace(Item.Subject, "RE:", "", vbTextCompare)
' Else
' End If
'
' If InStr(Item.Subject, "FW") > 0 Then
' strSubject = Replace(Item.Subject, "FW:", "", vbTextCompare)
' Else
' End If
'
' If strSubject = "" Then
' Else
' Set objRecip = Item.Recipients.Add("email.address@domain.com")
' objRecip.Type = olBCC
' objRecip.Resolve
' Item.Subject = Trim(strSubject)
' Item.Save
' End If
End Select

End Sub


This is in ThisOutlookSession and checks all sent emails for a specific subject.



This code works on my Outlook 2010, but on other Outlooks, it errors at "Item.Attachments.Add Item" saying "a message cannot be attached to itself".



Is there a way round this in newer versions?





On Outlook 2010 the user would hit reply (or forward) to reply to who sent the email to them.



A copy needs to be attached so the added email address (BCC "email.address@domain.com") via the code, gets a copy. This email address is a system email address that strips attachments and saves them into our workflow software under the job (which is in the subject line). That is why we need to send an attachment of the email, so if the user says "Do xyz on this job" then that email message is saved into our workflow system.










share|improve this question

























  • This code doesn't seem to make sense. You clearly can't attach a message to itself. If you want to send the current message, you forward it to another address. Why would you think you need to do this?

    – Ken White
    Nov 15 '18 at 3:28











  • Well it does work flawlessly on Outlook 2010, just not 2013 Basically the user would hit reply (or FW) to reply to who sent the email to them, but a copy needs to be attached so that the added email address (BBC "email.address@domain.com") via the code above, gets a copy. This email address is a system email address that strips attachments and saves them into our workflow software under the job (which is in the subject line). That is why we need to send an attachment of the email, so if the user says "Do xyz on this job" then that email message is saved into our workflow system.

    – Stildawn
    Nov 16 '18 at 1:15
















0












0








0








I have this code:



Sub Application_ItemSend(ByVal Item As Object, Cancel As Boolean)
Dim strSubject As String

Select Case True
Case (InStr(Item.Subject, "PIR") > 0)
If InStr(Item.Subject, "RE") > 0 Then
strSubject = Replace(Item.Subject, "RE:", "", vbTextCompare)
Else
End If

If InStr(Item.Subject, "FW") > 0 Then
strSubject = Replace(Item.Subject, "FW:", "", vbTextCompare)
Else
End If

If strSubject = "" Then
Else
Set objRecip = Item.Recipients.Add("email.address@domain.com")
objRecip.Type = olBCC
objRecip.Resolve
Item.Subject = Trim(strSubject)
Item.Save
Item.Attachments.Add Item
Item.Save
End If
Case (InStr(Item.Subject, "PIQ") > 0)
If InStr(Item.Subject, "RE") > 0 Then
strSubject = Replace(Item.Subject, "RE:", "", vbTextCompare)
Else
End If

If InStr(Item.Subject, "FW") > 0 Then
strSubject = Replace(Item.Subject, "FW:", "", vbTextCompare)
Else
End If

If strSubject = "" Then
Else
Set objRecip = Item.Recipients.Add("email.address@domain.com")
objRecip.Type = olBCC
objRecip.Resolve
Item.Subject = Trim(strSubject)
Item.Save
Item.Attachments.Add Item
Item.Save
End If
'#### Enable the below to capture more doc types ####
' Case (InStr(Item.Subject, "ABC") > 0)
' If InStr(Item.Subject, "RE") > 0 Then
' strSubject = Replace(Item.Subject, "RE:", "", vbTextCompare)
' Else
' End If
'
' If InStr(Item.Subject, "FW") > 0 Then
' strSubject = Replace(Item.Subject, "FW:", "", vbTextCompare)
' Else
' End If
'
' If strSubject = "" Then
' Else
' Set objRecip = Item.Recipients.Add("email.address@domain.com")
' objRecip.Type = olBCC
' objRecip.Resolve
' Item.Subject = Trim(strSubject)
' Item.Save
' End If
End Select

End Sub


This is in ThisOutlookSession and checks all sent emails for a specific subject.



This code works on my Outlook 2010, but on other Outlooks, it errors at "Item.Attachments.Add Item" saying "a message cannot be attached to itself".



Is there a way round this in newer versions?





On Outlook 2010 the user would hit reply (or forward) to reply to who sent the email to them.



A copy needs to be attached so the added email address (BCC "email.address@domain.com") via the code, gets a copy. This email address is a system email address that strips attachments and saves them into our workflow software under the job (which is in the subject line). That is why we need to send an attachment of the email, so if the user says "Do xyz on this job" then that email message is saved into our workflow system.










share|improve this question
















I have this code:



Sub Application_ItemSend(ByVal Item As Object, Cancel As Boolean)
Dim strSubject As String

Select Case True
Case (InStr(Item.Subject, "PIR") > 0)
If InStr(Item.Subject, "RE") > 0 Then
strSubject = Replace(Item.Subject, "RE:", "", vbTextCompare)
Else
End If

If InStr(Item.Subject, "FW") > 0 Then
strSubject = Replace(Item.Subject, "FW:", "", vbTextCompare)
Else
End If

If strSubject = "" Then
Else
Set objRecip = Item.Recipients.Add("email.address@domain.com")
objRecip.Type = olBCC
objRecip.Resolve
Item.Subject = Trim(strSubject)
Item.Save
Item.Attachments.Add Item
Item.Save
End If
Case (InStr(Item.Subject, "PIQ") > 0)
If InStr(Item.Subject, "RE") > 0 Then
strSubject = Replace(Item.Subject, "RE:", "", vbTextCompare)
Else
End If

If InStr(Item.Subject, "FW") > 0 Then
strSubject = Replace(Item.Subject, "FW:", "", vbTextCompare)
Else
End If

If strSubject = "" Then
Else
Set objRecip = Item.Recipients.Add("email.address@domain.com")
objRecip.Type = olBCC
objRecip.Resolve
Item.Subject = Trim(strSubject)
Item.Save
Item.Attachments.Add Item
Item.Save
End If
'#### Enable the below to capture more doc types ####
' Case (InStr(Item.Subject, "ABC") > 0)
' If InStr(Item.Subject, "RE") > 0 Then
' strSubject = Replace(Item.Subject, "RE:", "", vbTextCompare)
' Else
' End If
'
' If InStr(Item.Subject, "FW") > 0 Then
' strSubject = Replace(Item.Subject, "FW:", "", vbTextCompare)
' Else
' End If
'
' If strSubject = "" Then
' Else
' Set objRecip = Item.Recipients.Add("email.address@domain.com")
' objRecip.Type = olBCC
' objRecip.Resolve
' Item.Subject = Trim(strSubject)
' Item.Save
' End If
End Select

End Sub


This is in ThisOutlookSession and checks all sent emails for a specific subject.



This code works on my Outlook 2010, but on other Outlooks, it errors at "Item.Attachments.Add Item" saying "a message cannot be attached to itself".



Is there a way round this in newer versions?





On Outlook 2010 the user would hit reply (or forward) to reply to who sent the email to them.



A copy needs to be attached so the added email address (BCC "email.address@domain.com") via the code, gets a copy. This email address is a system email address that strips attachments and saves them into our workflow software under the job (which is in the subject line). That is why we need to send an attachment of the email, so if the user says "Do xyz on this job" then that email message is saved into our workflow system.







vba outlook outlook-vba






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 17 '18 at 6:37









Community

11




11










asked Nov 15 '18 at 2:40









StildawnStildawn

11113




11113













  • This code doesn't seem to make sense. You clearly can't attach a message to itself. If you want to send the current message, you forward it to another address. Why would you think you need to do this?

    – Ken White
    Nov 15 '18 at 3:28











  • Well it does work flawlessly on Outlook 2010, just not 2013 Basically the user would hit reply (or FW) to reply to who sent the email to them, but a copy needs to be attached so that the added email address (BBC "email.address@domain.com") via the code above, gets a copy. This email address is a system email address that strips attachments and saves them into our workflow software under the job (which is in the subject line). That is why we need to send an attachment of the email, so if the user says "Do xyz on this job" then that email message is saved into our workflow system.

    – Stildawn
    Nov 16 '18 at 1:15





















  • This code doesn't seem to make sense. You clearly can't attach a message to itself. If you want to send the current message, you forward it to another address. Why would you think you need to do this?

    – Ken White
    Nov 15 '18 at 3:28











  • Well it does work flawlessly on Outlook 2010, just not 2013 Basically the user would hit reply (or FW) to reply to who sent the email to them, but a copy needs to be attached so that the added email address (BBC "email.address@domain.com") via the code above, gets a copy. This email address is a system email address that strips attachments and saves them into our workflow software under the job (which is in the subject line). That is why we need to send an attachment of the email, so if the user says "Do xyz on this job" then that email message is saved into our workflow system.

    – Stildawn
    Nov 16 '18 at 1:15



















This code doesn't seem to make sense. You clearly can't attach a message to itself. If you want to send the current message, you forward it to another address. Why would you think you need to do this?

– Ken White
Nov 15 '18 at 3:28





This code doesn't seem to make sense. You clearly can't attach a message to itself. If you want to send the current message, you forward it to another address. Why would you think you need to do this?

– Ken White
Nov 15 '18 at 3:28













Well it does work flawlessly on Outlook 2010, just not 2013 Basically the user would hit reply (or FW) to reply to who sent the email to them, but a copy needs to be attached so that the added email address (BBC "email.address@domain.com") via the code above, gets a copy. This email address is a system email address that strips attachments and saves them into our workflow software under the job (which is in the subject line). That is why we need to send an attachment of the email, so if the user says "Do xyz on this job" then that email message is saved into our workflow system.

– Stildawn
Nov 16 '18 at 1:15







Well it does work flawlessly on Outlook 2010, just not 2013 Basically the user would hit reply (or FW) to reply to who sent the email to them, but a copy needs to be attached so that the added email address (BBC "email.address@domain.com") via the code above, gets a copy. This email address is a system email address that strips attachments and saves them into our workflow software under the job (which is in the subject line). That is why we need to send an attachment of the email, so if the user says "Do xyz on this job" then that email message is saved into our workflow system.

– Stildawn
Nov 16 '18 at 1:15














1 Answer
1






active

oldest

votes


















0














Why not create a new message and attach the current message to that new message?



You can try to use Redemption for that (it won't try to prevent you from shooting yourself in the foot), but you will most likely end up getting a ghost empty message attachment on the message attached as an embedded attachment since Redemption will copy the embedded attachment just after it was created.






share|improve this answer
























  • I was thinking of doing a saveas on item (the current message) saving it somewhere locally, then attaching that saveas in the code, that might work I think. But that seems a clunky way to do it, and would end up with a folder somewhere full of saved messages, I guess I could code a delete in there after the fact?

    – Stildawn
    Nov 16 '18 at 1:21













  • You could, but, again, why do you need this? If you only care about the embedded message attachment, why not create an empty message with only recipients copied and attach the original object? Why do you need two copies of the same message?

    – Dmitry Streblechenko
    Nov 16 '18 at 5:14











  • The user replies to a email from another user who is asking for information. The original sender needs this information sent to them, hence the reply. However we also need the information sent (in body of email) sent as an attachment to our workflow system, as it saves this information (email) with timestamp against the job. So whatever the user types into the body of the reply, needs to be sent to the coded email address as an attachment.

    – Stildawn
    Nov 18 '18 at 20:21













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53311654%2fattach-current-email-as-attachment-to-current-email-reply-in-newer-outlooks%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Why not create a new message and attach the current message to that new message?



You can try to use Redemption for that (it won't try to prevent you from shooting yourself in the foot), but you will most likely end up getting a ghost empty message attachment on the message attached as an embedded attachment since Redemption will copy the embedded attachment just after it was created.






share|improve this answer
























  • I was thinking of doing a saveas on item (the current message) saving it somewhere locally, then attaching that saveas in the code, that might work I think. But that seems a clunky way to do it, and would end up with a folder somewhere full of saved messages, I guess I could code a delete in there after the fact?

    – Stildawn
    Nov 16 '18 at 1:21













  • You could, but, again, why do you need this? If you only care about the embedded message attachment, why not create an empty message with only recipients copied and attach the original object? Why do you need two copies of the same message?

    – Dmitry Streblechenko
    Nov 16 '18 at 5:14











  • The user replies to a email from another user who is asking for information. The original sender needs this information sent to them, hence the reply. However we also need the information sent (in body of email) sent as an attachment to our workflow system, as it saves this information (email) with timestamp against the job. So whatever the user types into the body of the reply, needs to be sent to the coded email address as an attachment.

    – Stildawn
    Nov 18 '18 at 20:21


















0














Why not create a new message and attach the current message to that new message?



You can try to use Redemption for that (it won't try to prevent you from shooting yourself in the foot), but you will most likely end up getting a ghost empty message attachment on the message attached as an embedded attachment since Redemption will copy the embedded attachment just after it was created.






share|improve this answer
























  • I was thinking of doing a saveas on item (the current message) saving it somewhere locally, then attaching that saveas in the code, that might work I think. But that seems a clunky way to do it, and would end up with a folder somewhere full of saved messages, I guess I could code a delete in there after the fact?

    – Stildawn
    Nov 16 '18 at 1:21













  • You could, but, again, why do you need this? If you only care about the embedded message attachment, why not create an empty message with only recipients copied and attach the original object? Why do you need two copies of the same message?

    – Dmitry Streblechenko
    Nov 16 '18 at 5:14











  • The user replies to a email from another user who is asking for information. The original sender needs this information sent to them, hence the reply. However we also need the information sent (in body of email) sent as an attachment to our workflow system, as it saves this information (email) with timestamp against the job. So whatever the user types into the body of the reply, needs to be sent to the coded email address as an attachment.

    – Stildawn
    Nov 18 '18 at 20:21
















0












0








0







Why not create a new message and attach the current message to that new message?



You can try to use Redemption for that (it won't try to prevent you from shooting yourself in the foot), but you will most likely end up getting a ghost empty message attachment on the message attached as an embedded attachment since Redemption will copy the embedded attachment just after it was created.






share|improve this answer













Why not create a new message and attach the current message to that new message?



You can try to use Redemption for that (it won't try to prevent you from shooting yourself in the foot), but you will most likely end up getting a ghost empty message attachment on the message attached as an embedded attachment since Redemption will copy the embedded attachment just after it was created.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 15 '18 at 3:52









Dmitry StreblechenkoDmitry Streblechenko

43.7k32760




43.7k32760













  • I was thinking of doing a saveas on item (the current message) saving it somewhere locally, then attaching that saveas in the code, that might work I think. But that seems a clunky way to do it, and would end up with a folder somewhere full of saved messages, I guess I could code a delete in there after the fact?

    – Stildawn
    Nov 16 '18 at 1:21













  • You could, but, again, why do you need this? If you only care about the embedded message attachment, why not create an empty message with only recipients copied and attach the original object? Why do you need two copies of the same message?

    – Dmitry Streblechenko
    Nov 16 '18 at 5:14











  • The user replies to a email from another user who is asking for information. The original sender needs this information sent to them, hence the reply. However we also need the information sent (in body of email) sent as an attachment to our workflow system, as it saves this information (email) with timestamp against the job. So whatever the user types into the body of the reply, needs to be sent to the coded email address as an attachment.

    – Stildawn
    Nov 18 '18 at 20:21





















  • I was thinking of doing a saveas on item (the current message) saving it somewhere locally, then attaching that saveas in the code, that might work I think. But that seems a clunky way to do it, and would end up with a folder somewhere full of saved messages, I guess I could code a delete in there after the fact?

    – Stildawn
    Nov 16 '18 at 1:21













  • You could, but, again, why do you need this? If you only care about the embedded message attachment, why not create an empty message with only recipients copied and attach the original object? Why do you need two copies of the same message?

    – Dmitry Streblechenko
    Nov 16 '18 at 5:14











  • The user replies to a email from another user who is asking for information. The original sender needs this information sent to them, hence the reply. However we also need the information sent (in body of email) sent as an attachment to our workflow system, as it saves this information (email) with timestamp against the job. So whatever the user types into the body of the reply, needs to be sent to the coded email address as an attachment.

    – Stildawn
    Nov 18 '18 at 20:21



















I was thinking of doing a saveas on item (the current message) saving it somewhere locally, then attaching that saveas in the code, that might work I think. But that seems a clunky way to do it, and would end up with a folder somewhere full of saved messages, I guess I could code a delete in there after the fact?

– Stildawn
Nov 16 '18 at 1:21







I was thinking of doing a saveas on item (the current message) saving it somewhere locally, then attaching that saveas in the code, that might work I think. But that seems a clunky way to do it, and would end up with a folder somewhere full of saved messages, I guess I could code a delete in there after the fact?

– Stildawn
Nov 16 '18 at 1:21















You could, but, again, why do you need this? If you only care about the embedded message attachment, why not create an empty message with only recipients copied and attach the original object? Why do you need two copies of the same message?

– Dmitry Streblechenko
Nov 16 '18 at 5:14





You could, but, again, why do you need this? If you only care about the embedded message attachment, why not create an empty message with only recipients copied and attach the original object? Why do you need two copies of the same message?

– Dmitry Streblechenko
Nov 16 '18 at 5:14













The user replies to a email from another user who is asking for information. The original sender needs this information sent to them, hence the reply. However we also need the information sent (in body of email) sent as an attachment to our workflow system, as it saves this information (email) with timestamp against the job. So whatever the user types into the body of the reply, needs to be sent to the coded email address as an attachment.

– Stildawn
Nov 18 '18 at 20:21







The user replies to a email from another user who is asking for information. The original sender needs this information sent to them, hence the reply. However we also need the information sent (in body of email) sent as an attachment to our workflow system, as it saves this information (email) with timestamp against the job. So whatever the user types into the body of the reply, needs to be sent to the coded email address as an attachment.

– Stildawn
Nov 18 '18 at 20:21






















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53311654%2fattach-current-email-as-attachment-to-current-email-reply-in-newer-outlooks%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Xamarin.iOS Cant Deploy on Iphone

Glorious Revolution

Dulmage-Mendelsohn matrix decomposition in Python