Hi Michael, What if I want mutt on "y" (send) to send composed e-mail to my application? > Example: $sendmail -B8BITMIME -f me@xxxxxxxxxxx -- mutt-dev@xxxxxxxx This will not be a great fit, because I want to accomplish the task without need to parse the actual message. Native OWA processes will take care of parsing, all I need to do is to submit mutt composed e-mail. Thank you for quick reply, -- Paul Greenberg PGP key: 0xEF9DE0D8 The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. On Wed, Mar 24, 2010 at 10:06:25AM -0700, Michael Elkins wrote: > On Wed, Mar 24, 2010 at 12:42:27PM -0400, Paul Greenberg wrote: > > Please help integrate msfetch-send with mutt. > > > > right now I have .muttrc > > set sendmail="/path/to/esmtp -v -X /tmp/esmtp.log" > > > > but I want it to be > > set sendmail="/path/to/msfetch-send" > > > > Can you give me an idea of what needs to be done here? > > You need to either create a new script, or make your current script > emulate the minimal sendmail interface that Mutt expects. Mutt invokes > $sendmail with some optional arguments, followed by the recipients. > > Example: $sendmail -B8BITMIME -f me@xxxxxxxxxxx -- mutt-dev@xxxxxxxx > > What you probably need to do is discard all the arguments prior to the > two dashes. If you don't care about BCC, you can probably just ignore > all the arguments and use the recipients listed in the header of the email > delivered to stdin. > > me
Attachment:
pgpyJEypHus8D.pgp
Description: PGP signature