Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EWS, OWA, Acts: Save sent copy in specific folder #425

Open
benbucksch opened this issue Jan 30, 2025 · 2 comments · May be fixed by #427
Open

EWS, OWA, Acts: Save sent copy in specific folder #425

benbucksch opened this issue Jan 30, 2025 · 2 comments · May be fixed by #427
Assignees
Labels

Comments

@benbucksch
Copy link
Collaborator

benbucksch commented Jan 30, 2025

Reproduction

  • Reply to a message in a normal folder (not Inbox or any other special folder)
  • Send it

Actual result

  • Message is saved in the Sent folder

Expected

  • Message is saved in the folder where the replied-to message is

Code

  • MailAccount.send() should send the message and save it in the folder email.folder, if set, otherwise in the Sent folder.

Caveats

  • If the protocol does not support it, please note here.
  • In this case: Consider moving the message after sending and saving to Sent folder
  • If email.folder?.specialFolder == SpecialFolder.Sent, then ignore it and use the server default.
@NeilRashbrook
Copy link
Collaborator

MailAccount.send() should send the message and save it in the folder email.folder, if set, otherwise in the Sent folder.

Did you not read my comment in #413 as to why this doesn't work?

  • If the protocol does not support it, please note here.
  • In this case: Consider moving the message after sending and saving to Sent folder

Unfortunately ActiveSync won't even tell you the id of the sent item, so there's no way to move it.

@NeilRashbrook
Copy link
Collaborator

Looks like that part of #413 was fixed by 3ac31fb, so I can actually fix this.

@NeilRashbrook NeilRashbrook linked a pull request Jan 30, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants