2013/3/6 Andre Klärner <kan...@ak-online.be>: > Hi Kunszt, > > On Tue, Mar 05, 2013 at 09:05:06AM +0100, Kunszt Árpád wrote: >> When I'm using the interactive user-interface everything works fine, >> but from the command line it doesn't work. I tried a lot of things, >> googled half of the day, but I didn't found any working solution. >> >> Is it possible anyhow? Why Mutt acts differently when invoked from >> command-line parameters? It's very frustrating... > > Maybe it's another environment from cron? Thats quite usual, so maybe > something is not set that you require to work.
I'm still testing from the command-line, I'm going to use cron after this. > > Also you might want to write a special muttrc for the automated sending > than mentions only the really required stuff. You might also want to use > "--passin" option to openssl so that your smime-key can be decrypted > properly. I'm only encrypting the message (no signing) so I only use the public certificate which isn't encrypted, of course. I checked the .muttdebugX files and there isn't any reference to S/MIME/encryption in the non-interactive case. It looks like it doesn't even try to do this. Thanks, for any advice! Arpad Kunszt
