Hi,

This is a minor issue. If I schedule a mail with an attachment and then delete the file that is supposed to be attached before the mail is sent, then every time the timer runs I get a dialogue saying "Buffer temp modified; kill anyway?". Perhaps we could add an informative error message?

Cheers,
Ben

currently it retains the initial schedule time, but that is incorrectly interpreted. # Creating issue for mu4e-send-delay. # # Write a message for this issue. The first block of # text is the title and the rest is the description.

I have this custom code:

(setq mu4e-send-delay-default-delay "2h")
(setq mu4e-send-delay-timer 3600)

It is now 11:35pm and I have dozens of emails in my drafts folder all scheduled to before this date, from 1.30pm to 10pm. The value of mu4e-send-delay-send-queue-timer is:

[t 24058 22377 101966 3600 mu4e-send-delay-send-queue nil nil 0]

I don't know enough LISP to debug it. Can someone help?

I have submitted two pull requests for issues. It seems that this repo has had no activity for a long time. Please add me as a contributor.

this should be worked around or requested upstream # Creating issue for mu4e-send-delay. # # Write a message for this issue. The first block of # text is the title and the rest is the description.

Maybe it is possible to add an org-mode like function to schedule mails to a specific date/time when pressing C-c C-s.

mu4e-send-strip-header-before-send is not being honored # Creating issue for mu4e-send-delay. # # Write a message for this issue. The first block of # text is the title and the rest is the description.

I have been using send-delay and it works most of the time. Sometimes, the emails is only sent much later. For example, yesterday I drafted an email at 7pm scheduled for 5 minutes later. I may have closed the computer and changed locations in the 5-10 minutes after (I am not sure). Then I reopened, reconnected, left running for 2 hours, and restarted, and the email was only sent this morning when I launched Emacs again.

I often get a message in the mini-buffer saying "Stopping call to process with quit inhibited", or something like that. Could that be the reason?

wasn't an issue before the fix for #5 and the move to message-mode to handle attachments # Creating issue for mu4e-send-delay. # # Write a message for this issue. The first block of # text is the title and the rest is the description.

Let's say I a message at t0 with a delay, scheduled for t1, and then go back to edit the message. The original message is still scheduled for sending. If I send the edited message after t1, then I will be sending two separate messages.

Can I remove the message from the send queue when I edit it?

I send emails with delay using mu4e-send-delay. The repo seems out of date with the last commit 2 years ago.

I often find that emails I sent with delay are sent twice, for example a pair sent within 1 minute of each other:

Date: Mon 29 Apr 16:05:09 2019
Date: Mon 29 Apr 16:04:17 2019

an another pair within 1 second of each other:

Date: Tue 30 Apr 12:51:22 2019
Date: Tue 30 Apr 12:51:21 2019

And some pairs have exactly the same timestamp.

Nevertheless, some recipients I contacted only receive one of them.

In addition, attachments show differently, for example one email in the pair has:

Date: Mon 29 Apr 11:56:01 2019
Maildir: /Sent Items
[...body of email...]
<#part type="application/pdf" filename="/var/folders/zx/j_gjm0ld081b_mcqmg3gp9l1zp59y6/T//mu-2137171910/9ca95bbc/3/SS Programme 2019.pdf" disposition=attachment>
<#/part>

and another in the pair has:

Date: Mon 29 Apr 11:55:41 2019
Maildir: /Sent Items
Attachments: [1]SS Programme 2019.pdf(1.1M)
[...body of email...]

I have 3 accounts, 2 gmails and one exchange server. I can not seem to make mu4e-send-delay work and this is what I am getting.

If I try to schedule an email from exchange account, I got following message.
Saving file /.../mail/Drafts/cur/1489718313.3ed505347ccd2a4a.sagittarius:2,DS...
Wrote /.../mail/Drafts/cur/1489718313.3ed505347ccd2a4a.sagittarius:2,DS
[mu4e] Saved (5 lines)
mu4e-send-delay: (error [mu4e] unsupported type for ("/Exchange/Sent"))
[mu4e] Mail scheduled for sending at: mu4e-send-delay: (error [mu4e] unsupported type for ("/Exchange/Sent"))
If I try to schedule from Gmail account, I got this:
Saving file /.../mail/Drafts/cur/1489718675.87ee579c4f98342c.sagittarius:2,DS...
Wrote /.../mail/Drafts/cur/1489718675.87ee579c4f98342c.sagittarius:2,DS
[mu4e] Saved (5 lines)
mu4e-send-delay: (error [mu4e] Cannot set folder mu4e-sent-folder, account for MSG nil not detected)
[mu4e] Mail scheduled for sending at: mu4e-send-delay: (error [mu4e] Cannot set folder mu4e-sent-folder, account for MSG nil not detected)

Text by Ben Maughen: " I may have found a small bug. If I save a message as a draft and then send a message with delay so that it also ends up in my drafts folder waiting to be sent, then the timer fails with the following:

Error running timer `mu4e-send-delay-send-queue': (wrong-type-argument integerp nil)

and the delayed message is not sent until I delete or send the draft message. "

to quickly detect and jump to entries in the Drafts that are scheduled for sending # Creating issue for mu4e-send-delay. # # Write a message for this issue. The first block of # text is the title and the rest is the description.

long waited feature, thanks! A few questions:
Can I set delay with 3d, 1w etc?
I can not seems to edit the emails after scheduling. any hits?
Another question is how to send the email right away? set the X-delay to 0min?

When I send a message immediately and don't have an internet connection, I see this message in the mini-buffer:

smtp.domain.tld/25 nodename nor servname provided, or not known

The message remains open in the Emacs frame with some changes such as the FCC header with the destination filepath and is saved to Drafts.

When I delay sending mail with mu4e-send-delay, at the time of sending, the mini-buffer shows Sending via mail.... If I have no internet connection at the time of sending, a pop-up appears in Emacs:

Emacs-x86_64-10_14

Buffer *temp* modified; kill anyway?

[Yes] [No]

If I click Yes, the mini-buffer changes to Buffer *temp* modified; kill anyway? y. If I click No, the mini-buffer changes to Buffer *temp* modified; kill anyway? n and I get a file similar to *message*-20190627-105554 saved in the home directory with the content of the message:

User-agent: mu4e 1.2.0; emacs 26.2
From: ...
To: ...
Subject: ...
Fcc: /path/to/maildir/Sent Items/cur/1561629089.e6e765d7b4ad6364.hostname:2,S
Date: Thu, 27 Jun 2019 11:01:54 +0100
Message-ID: <[email protected]>
--text follows this line--
...

Annoyingly, I get a new saved message with the same content every time I click No in the Emacs pop-up.

I fiddled with the code and I get this upon exit

Save file /path/to/maildir/Drafts/cur/some-id.hostname:2,DS? (y, n !, ...)

Playing with the code, the issue is in function mu4e-send-delay-send-if-due, which calls (message-send-mail). The help for this last function shows:

message-send-mail is a compiled Lisp function in ‘message.el’.

and its source code modifies the buffer and then calls kill-buffer without options for confirmation.

(defun message-send-mail (&optional _)
	...
    (kill-buffer tembuf))
	...
	)

So I can either remove the confirmation default before calling it, and then putting it back, which is ugly, or I can check for an internet connection before trying to send. I will propose a pull request with this fix.

If I reply to a mail using mu4e-send-delay-send-and-exit, the "replied to" flag is not set when the mail is finally sent.

I had this working in mu4e-delay by using
(mu4e~compose-set-parent-flag f)
before sending the mail. I tried this quickly with mu4e-send-delay bit it didn't appear to work, but I have not had time to look at it in any detail.

Cheers,
Ben