Re: directly sending from postponed menu
> This workflow completely obviates any need to use "postponed" for a message > which is complete. I like it! No need for a separate outbox with postfix being the outbox itself. That's the fire-and-forget workflow I'm looking for. > All you really need to make this work in concert with an > ISP's SMTP service is to add a relayhost to /etc/posfix/main.cf. Here's > mine: > > relayhost = [service.l]:1025 I looked a bit around and also found instructions for GMail [1]. What irks me though is that it requires putting a plain-text password into /etc/postfix/sasl/sasl_passwd. Ideally I'd use my OSX keychain and put in the password on demand via 'security find-generic-password'. How do you handle SMTP server authentication? Matthias [1] https://gist.github.com/joech4n/d59e7bc9f99273fbda31
Re: directly sending from postponed menu
> Try adding your postpone directory as a mailbox and directly access it, or > just access the // regular mail file. (it really is a regular mail file). Yeah, I noticed that I can access the mailbox like any other. Simply piping the message through sendmail should then do the trick then. The remaining I have (see the other sub-thread) is setting up the local MTA on OSX so that it relays mail through an authenticated and encrypted SMTP session. But that's not a mutt problem anymore. Matthias
