Sending mail
Dear all, As a newbie, I tried to configure mutt. Partially successful if you don't consider that I can not send mails :) . I can get mail but can not send. My incoming mail server is an IMAP and outgoing server is an SMTP. I guess there is a problem with my .muttrc. I pasted that (relatively short for a beginner :) ) #mailboxes imap://mail.mech.kuleuven.be set imap_user=username #your IMAP user name or login set imap_pass=password #your IMAP password set spoolfile=imap://mail.mech.kuleuven.be set folder=imap://mail.mech.kuleuven.be/INBOX set folder=/home/utab/Mail set sendmail=/usr/sbin/ssmtp [EMAIL PROTECTED] -appassword #set sendmail=/usr/sbin/sendmail set editor=vim Thanks in advance. Umut Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
Re: Sending mail
* Umut Tabak [EMAIL PROTECTED] [03-14-07 03:19]: As a newbie, I tried to configure mutt. Partially successful if you don't consider that I can not send mails :) . I can get mail but can not send. My incoming mail server is an IMAP and outgoing server is an SMTP. I guess there is a problem with my .muttrc. I pasted that (relatively short for a beginner :) ) #mailboxes imap://mail.mech.kuleuven.be set imap_user=username #your IMAP user name or login set imap_pass=password #your IMAP password set spoolfile=imap://mail.mech.kuleuven.be set folder=imap://mail.mech.kuleuven.be/INBOX set folder=/home/utab/Mail set sendmail=/usr/sbin/ssmtp [EMAIL PROTECTED] -appassword #set sendmail=/usr/sbin/sendmail set editor=vim account-hook imap://username@mech.huleuven.be -- Patrick ShanahanRegistered Linux User #207535 http://wahoo.no-ip.org@ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/
Re: Sending mail
Patrick Shanahan wrote: * Umut Tabak [EMAIL PROTECTED] [03-14-07 03:19]: As a newbie, I tried to configure mutt. Partially successful if you don't consider that I can not send mails :) . I can get mail but can not send. My incoming mail server is an IMAP and outgoing server is an SMTP. I guess there is a problem with my .muttrc. I pasted that (relatively short for a beginner :) ) #mailboxes imap://mail.mech.kuleuven.be set imap_user=username #your IMAP user name or login set imap_pass=password #your IMAP password set spoolfile=imap://mail.mech.kuleuven.be set folder=imap://mail.mech.kuleuven.be/INBOX set folder=/home/utab/Mail set sendmail=/usr/sbin/ssmtp [EMAIL PROTECTED] -appassword #set sendmail=/usr/sbin/sendmail set editor=vim account-hook imap://username@mech.huleuven.be Thanks for the reply but this command is not recognized by bash. bash: account-hook: command not found My mutt version is Mutt 1.5.13 (2006-08-11) (dont know if it is necessary) Best regards, Umut Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
Re: Sending mail
On 3/14/07, Umut Tabak [EMAIL PROTECTED] wrote: Patrick Shanahan wrote: * Umut Tabak [EMAIL PROTECTED] [03-14-07 03:19]: As a newbie, I tried to configure mutt. Partially successful if you don't consider that I can not send mails :) . I can get mail but can not send. My incoming mail server is an IMAP and outgoing server is an SMTP. I guess there is a problem with my .muttrc. I pasted that (relatively short for a beginner :) ) #mailboxes imap://mail.mech.kuleuven.be set imap_user=username #your IMAP user name or login set imap_pass=password #your IMAP password set spoolfile=imap://mail.mech.kuleuven.be set folder=imap://mail.mech.kuleuven.be/INBOX set folder=/home/utab/Mail set sendmail=/usr/sbin/ssmtp [EMAIL PROTECTED] -appassword #set sendmail=/usr/sbin/sendmail set editor=vim account-hook imap://username@mech.huleuven.be Thanks for the reply but this command is not recognized by bash. bash: account-hook: command not found My mutt version is Mutt 1.5.13 (2006-08-11) (dont know if it is necessary) Best regards, I think he wanted you to add that line to your .muttrc file.
Re: Sending mail
Ken Brush wrote: On 3/14/07, Umut Tabak [EMAIL PROTECTED] wrote: Patrick Shanahan wrote: * Umut Tabak [EMAIL PROTECTED] [03-14-07 03:19]: As a newbie, I tried to configure mutt. Partially successful if you don't consider that I can not send mails :) . I can get mail but can not send. My incoming mail server is an IMAP and outgoing server is an SMTP. I guess there is a problem with my .muttrc. I pasted that (relatively short for a beginner :) ) #mailboxes imap://mail.mech.kuleuven.be set imap_user=username #your IMAP user name or login set imap_pass=password #your IMAP password set spoolfile=imap://mail.mech.kuleuven.be set folder=imap://mail.mech.kuleuven.be/INBOX set folder=/home/utab/Mail set sendmail=/usr/sbin/ssmtp [EMAIL PROTECTED] -appassword #set sendmail=/usr/sbin/sendmail set editor=vim account-hook imap://username@mech.huleuven.be Thanks for the reply but this command is not recognized by bash. bash: account-hook: command not found My mutt version is Mutt 1.5.13 (2006-08-11) (dont know if it is necessary) Best regards, I think he wanted you to add that line to your .muttrc file. Thanks, Yes that is the case when I try to source .muttrc by typing . .muttrc I got this error. My best, Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
Re: Sending mail
On Wed, Mar 14, 2007 at 04:35:57PM +0100, Umut Tabak wrote: Ken Brush wrote: On 3/14/07, Umut Tabak [EMAIL PROTECTED] wrote: Patrick Shanahan wrote: * Umut Tabak [EMAIL PROTECTED] [03-14-07 03:19]: As a newbie, I tried to configure mutt. Partially successful if you don't consider that I can not send mails :) . I can get mail but can not send. My incoming mail server is an IMAP and outgoing server is an SMTP. I guess there is a problem with my .muttrc. I pasted that (relatively short for a beginner :) ) #mailboxes imap://mail.mech.kuleuven.be set imap_user=username #your IMAP user name or login set imap_pass=password #your IMAP password set spoolfile=imap://mail.mech.kuleuven.be set folder=imap://mail.mech.kuleuven.be/INBOX set folder=/home/utab/Mail set sendmail=/usr/sbin/ssmtp [EMAIL PROTECTED] -appassword #set sendmail=/usr/sbin/sendmail set editor=vim account-hook imap://username@mech.huleuven.be Thanks for the reply but this command is not recognized by bash. bash: account-hook: command not found My mutt version is Mutt 1.5.13 (2006-08-11) (dont know if it is necessary) Best regards, I think he wanted you to add that line to your .muttrc file. Thanks, Yes that is the case when I try to source .muttrc by typing . .muttrc I got this error. You source your .muttrc from within mutt, it reads it automatically at startup so you only need to explicitly source it if you have changed it and don't want to exit/restart mutt. To source the .muttrc from within mutt you use the 'source' command, see the documentation/help. -- Chris Green
Re: Sending mail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, March 14 at 04:35 PM, quoth Umut Tabak: As a newbie, I tried to configure mutt. Partially successful if you don't consider that I can not send mails :) . I can get mail but can not send. My incoming mail server is an IMAP and outgoing server is an SMTP. I guess there is a problem with my .muttrc. I pasted that (relatively short for a beginner :) ) Your configuration looks correct. What error do you get when you attempt to send mail? account-hook imap://username@mech.huleuven.be Two things: 1. How would that help? 2. That's incomplete syntax. The form is account-hook thing-to-match thing-to-do and you're missing the thing to do section. OP: probably best to ignore that. Thanks for the reply but this command is not recognized by bash. That's because it's not a bash (or shell) command, it's something that goes in mutt's config file (i.e. ~/.muttrc). Yes that is the case when I try to source .muttrc by typing . .muttrc Umm... I don't think you're quite grasping the concept of that being MUTT's config file. This may be your original problem. Put it this way: every program likes storing it's configuration settings somewhere, usually in a file. These configuration settings are virtually NEVER in a form that your shell will (or *should*) understand. Take the standard car analogy. Your car starts because you put the key in the ignition and turn. That doesn't mean that your new car radio will turn on when you stick your car key in the tape player and turn. The way you turn on the radio is NOT the same way you turn on the car. Similarly, mutt's config files are NOT your shell's config files. The fact that they use set something=somethingelse syntax may *look* like shell syntax, and may mean that your shell will interpret them as valid shell commands (though they won't do anything relevant to mutt in that case), but that doesn't mean that it's something that your shell *should* interpret. Your ~/.muttrc is a file that needs ONLY make sense to mutt; if your shell thinks it can understand some of it, that is purely coincidence and if your shell objects that it cannot understand all of it, that's irrelevant because your shell shouldn't be reading it in the first place. Now you may be asking yourself okay, so, if that's a mutt-only file, how does mutt find it to read it? One of two ways. The first, and most common, is to put that file in a known location. Mutt always checks your home directory ($HOME or ~) for a file named .muttrc to read its configuration settings out of. The second way mutt can find the file is by telling mutt where it is when you launch mutt. For example: mutt -F ./.muttrc That command launches mutt and tells it to read its configuration data out of the .muttrc that is in the current directory. The -F is a flag that tells mutt that the next word is the name of the config file it should read. Does that make sense? ~Kyle - -- That it is better 100 guilty Persons should escape than that one innocent Person should suffer, is a Maxim that has been long and generally approved. -- Benjamin Franklin -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFF+B54BkIOoMqOI14RAlJPAKCXp5yR6DgZR9H08UqGW37UWkgHigCgqrd1 /Uz2KCHYDL3V3iTlzJaS2x0= =iRyK -END PGP SIGNATURE-
Re: Sending mail
Kyle Wheeler wrote: Your configuration looks correct. What error do you get when you attempt to send mail? I still get a ssmtp: Cannot open mail:25 I made a search after I got some replies, I changed my .muttrc file to account-hook imap://mech.kuleuven.be/ 'set imap_user=user imap_pass=password' #mailboxes imap://mail.mech.kuleuven.be set imap_user=user #your IMAP user name or login set imap_pass=pass #your IMAP password set spoolfile=imap://mail.mech.kuleuven.be set folder=imap://mail.mech.kuleuven.be/INBOX set folder=/home/utab/Mail set sendmail=/usr/sbin/ssmtp [EMAIL PROTECTED] -appassword #set sendmail=/usr/sbin/sendmail set editor=vim After this change the error is the same. a . That's because it's not a bash (or shell) command, it's something that goes in mutt's config file (i.e. ~/.muttrc). Yes, right, also a beginner and learner of linux. Step by step :) Take the standard car analogy. Your car starts because you put the key in the ignition and turn. That doesn't mean that your new car radio will turn on when you stick your car key in the tape player and turn. The way you turn on the radio is NOT the same way you turn on the car. Similarly, mutt's config files are NOT your shell's config files. The fact that they use set something=somethingelse syntax may *look* like shell syntax, and may mean that your shell will interpret them as valid shell commands (though they won't do anything relevant to mutt in that case), but that doesn't mean that it's something that your shell *should* interpret. Your ~/.muttrc is a file that needs ONLY make sense to mutt; if your shell thinks it can understand some of it, that is purely coincidence and if your shell objects that it cannot understand all of it, that's irrelevant because your shell shouldn't be reading it in the first place. Now you may be asking yourself okay, so, if that's a mutt-only file, how does mutt find it to read it? One of two ways. The first, and most common, is to put that file in a known location. Mutt always checks your home directory ($HOME or ~) for a file named .muttrc to read its configuration settings out of. The second way mutt can find the file is by telling mutt where it is when you launch mutt. For example: mutt -F ./.muttrc That command launches mutt and tells it to read its configuration data out of the .muttrc that is in the current directory. The -F is a flag that tells mutt that the next word is the name of the config file it should read. Does that make sense? ~Kyle - -- That it is better 100 guilty Persons should escape than that one innocent Person should suffer, is a Maxim that has been long and generally approved. -- Benjamin Franklin -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFF+B54BkIOoMqOI14RAlJPAKCXp5yR6DgZR9H08UqGW37UWkgHigCgqrd1 /Uz2KCHYDL3V3iTlzJaS2x0= =iRyK -END PGP SIGNATURE- Thanks for this clarification, it helped :). My best, Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
Re: Sending mail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, March 14 at 05:25 PM, quoth Umut Tabak: I still get a ssmtp: Cannot open mail:25 Alright, now we're getting somewhere. set sendmail=/usr/sbin/ssmtp [EMAIL PROTECTED] -appassword Okay, it appears that the real problem is not with your mutt setup, but with your ssmtp setup. I don't know much about ssmtp, but I do know that it has more-or-less been abandoned. You may be able to find information about how to configure ssmtp on the web... I know some people use and love ssmtp, but I'm personally not a fan (for many reasons, many having to do with it being abandon-ware). I would recommend using a different package: msmtp. It has a web page (http://msmtp.sf.net) and a lot of documentation and active development. I would suggest installing that, setting it up, and telling mutt to use that instead of ssmtp. That being said, some folks get a lot of mileage out of ssmtp and may be able to help you set it up. I am not one of them. :) That's because it's not a bash (or shell) command, it's something that goes in mutt's config file (i.e. ~/.muttrc). Yes, right, also a beginner and learner of linux. Step by step :) We're all beginners at some point. :) Thanks for this clarification, it helped :). Happy to help. ~Kyle - -- Man cannot live by bread alone. He must have peanut butter. -- Bill Cosby -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iD8DBQFF+CelBkIOoMqOI14RAoQiAJ91KlaThupBm7XYyJMnmXfTlApbpgCfUKYd cBzzvzmkx/huZlpj9opiTz8= =VSfx -END PGP SIGNATURE-
Re: Sending mail
On Wed, Mar 14, 2007 at 09:49:41AM -0700, Kyle Wheeler wrote: On Wednesday, March 14 at 05:25 PM, quoth Umut Tabak: I still get a ssmtp: Cannot open mail:25 Alright, now we're getting somewhere. set sendmail=/usr/sbin/ssmtp [EMAIL PROTECTED] -appassword Okay, it appears that the real problem is not with your mutt setup, but with your ssmtp setup. I don't know much about ssmtp, but I do know that it has more-or-less been abandoned. You may be able to find information about how to configure ssmtp on the web... I know some people use and love ssmtp, but I'm personally not a fan (for many reasons, many having to do with it being abandon-ware). I would recommend using a different package: msmtp. It has a web page (http://msmtp.sf.net) and a lot of documentation and active development. I would suggest installing that, setting it up, and telling mutt to use that instead of ssmtp. That being said, some folks get a lot of mileage out of ssmtp and may be able to help you set it up. I am not one of them. :) Some of us rely on ssmtp for Windows machines because it's traditionally been provided with Cygwin. I guess you could call that mileage. To help out the poster for the moment, he can configure ssmtp by editing /etc/ssmtp/ssmtp.conf (or wherever the appropriate configuration file located on his system) to define, at minimum, the following: mailhub=smtp.myISP.net and replacing the mailhub value with whatever is applicable. For everything else, there's the manpage. Or as you suggested, install msmtp and use it instead, and then read through the ~/.msmtp.log file to diagnose any further problems. The msmtp manpage provides mutt-specific configuration directives so it should be relatively easy to set things up correctly. -- George
Re: Changing c's reponse
Tom [EMAIL PROTECTED] wrote:
| On Mon, Mar 12, 2007 at 05:58:50PM +0100, mess-mate wrote:
| Kyle Wheeler [EMAIL PROTECTED] wrote:
| | On Friday, March 9 at 08:49 PM, quoth [EMAIL PROTECTED]:
| | I am asking myself whether it would be possible to change this
| | response to a simple:
| |
| | Open mailbox ('?' for list); =
| |
| | macro index c 'change-folder='
| |
| And to get my /home/mess-mate/ ??
| ( not the mailbox)
| best regards
| mess-mate
| --
|
| When I hit c then ? in the list that shows up is a ../ if I high light that
and
| hit enter then the stuff in my home directory is listed. Is this what your
| asking ?
|
| Tom
|
Yes, that is what i asked, and when i highlight it + enter, what i
see is only
.INBOX
INBOX
entering on one of this do not display my ~/ directory.
Can't access my $HOME at all :(
The $HOME dir very usefull to attach files with an email.
best rgards
mess-mate
--
Q: What's tan and black and looks great on a lawyer?
A: A doberman.
forwarding messages with attachments
Please read carefully before you reply. I already know about mime_forward, forward_decode, mime_forward_decode, and mime_forward_rest... I've played with these vars quite a bit, and no combination of these appears to do what I want them to do. [Though, FWIW, the manual documentation on some of these could stand to be a lot clearer... i.e. what the hell does Controls the decoding of complex MIME messages into text/plain when forwarding a message actually mean, exactly?] Anyway... The problem is this: Often, I have mail which consists of a body, and several text attachments. The attachments very often are scripts or source code of some sort, attached with a type of text/plain. What I want to do is to be able to forward (or reply to) these messages to someone else, with the original body included in-line in my body, so I can comment on it. However, I *DO NOT* want the attachments included in-line, because this makes them very difficult to save separately (remember, they're individual programs -- albeit in plain text format). Is there a way to make Mutt deal with this properly? I can't imagine that the audience of Mutt (largely sysadmins and programmers and such) hasn't run into this problem before... The normal way I handle this is to save the original body to a text file, mime_forward the message components *excluding* the body, and then while composing my own body, read the original body into my editor, manually marking it up to distinguish it from what I've written. This is a solution, but it's a pretty sucky one. It was workable when I did this a lot less often, but in my new role, I find it happening a lot. It's giving me major headaches. I believe, based on perusing the manual, that mutt does not provide a way to do this. But I'm hoping that I've just missed something... and perhaps also that me mentioning it will encourage some ambitious young soul to fix it if it's not there. :) I'm getting too old to spend time hacking on my mailer... -- Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail. Sorry for the inconvenience. Thank the spammers. pgp37w3qkWc4e.pgp Description: PGP signature
Re: forwarding messages with attachments
On Wed, Mar 14, 2007 at 06:55:48PM -0400, Derek Martin wrote: Is there a way to make Mutt deal with this properly? I can't imagine that the audience of Mutt (largely sysadmins and programmers and such) hasn't run into this problem before... The normal way I handle this is to save the original body to a text file, mime_forward the message components *excluding* the body, and then while composing my own body, read the original body into my editor, manually marking it up to distinguish it from what I've written. Definitely interested in hearing the discussion on this one as well.. in the past I've relied on 'b' to bounce the message on to someone when I needed to preserve the attachments as-is, but this obviously doesn't allow you to (easily) edit the contents of the message first. At least not in a way compareable to how other mailers do it. Ray
Re: forwarding messages with attachments
On Wed, Mar 14, 2007 at 04:03:00PM -0700, Ray Van Dolson wrote: On Wed, Mar 14, 2007 at 06:55:48PM -0400, Derek Martin wrote: Is there a way to make Mutt deal with this properly? I can't imagine that the audience of Mutt (largely sysadmins and programmers and such) hasn't run into this problem before... The normal way I handle this is to save the original body to a text file, mime_forward the message components *excluding* the body, and then while composing my own body, read the original body into my editor, manually marking it up to distinguish it from what I've written. Definitely interested in hearing the discussion on this one as well.. in the past I've relied on 'b' to bounce the message on to someone when I needed to preserve the attachments as-is, but this obviously doesn't allow you to (easily) edit the contents of the message first. At least not in a way compareable to how other mailers do it. If bouncing is enough for you, then probably it will be enough for you to add this to your muttrc (or make a macro to do it when you need it, or something): set mime_forward But again, this does not (AFAICT) allow you to easily edit the original body. In fact, it's really annoying in another way: it includes the *headers* from the original message in-line in the body, but not the original body itself... But then the entire message is included (with headers) in the first attachment. I consider this to be utterly and completely broken, and I'm considering reporting it as a bug, but I'm waiting to see what other people think. It's shocking to me that people have not previously complained loudly enough about this to get it changed; but that just leads me to think that some people actually *like* this behavior, which boggles my mind. It might even bottle my mind. ;-) -- Derek D. Martinhttp://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail. Sorry for the inconvenience. Thank the spammers. pgpgBhPYfP8w4.pgp Description: PGP signature
Re: forwarding messages with attachments
On 2007-03-14, Derek Martin [EMAIL PROTECTED] wrote: On Wed, Mar 14, 2007 at 04:03:00PM -0700, Ray Van Dolson wrote: On Wed, Mar 14, 2007 at 06:55:48PM -0400, Derek Martin wrote: Is there a way to make Mutt deal with this properly? I can't imagine that the audience of Mutt (largely sysadmins and programmers and such) hasn't run into this problem before... The normal way I handle this is to save the original body to a text file, mime_forward the message components *excluding* the body, and then while composing my own body, read the original body into my editor, manually marking it up to distinguish it from what I've written. Definitely interested in hearing the discussion on this one as well.. in the past I've relied on 'b' to bounce the message on to someone when I needed to preserve the attachments as-is, but this obviously doesn't allow you to (easily) edit the contents of the message first. At least not in a way compareable to how other mailers do it. If bouncing is enough for you, then probably it will be enough for you to add this to your muttrc (or make a macro to do it when you need it, or something): set mime_forward But again, this does not (AFAICT) allow you to easily edit the original body. In fact, it's really annoying in another way: it includes the *headers* from the original message in-line in the body, but not the original body itself... But then the entire message is included (with headers) in the first attachment. I consider this to be utterly and completely broken, and I'm considering reporting it as a bug, but I'm waiting to see what other people think. It's shocking to me that people have not previously complained loudly enough about this to get it changed; but that just leads me to think that some people actually *like* this behavior, which boggles my mind. It might even bottle my mind. ;-) I think it works to: 1. go to the attachment menu; 2. tag all the message parts; 3. type ;f (without quotes) to forward everything; 4. answer yes to Forward as attachments? ([no]/yes):; 5. save away the stuff that appears in your editor; 6. exit editor; 7. delete first attachment; 8. edit what was the second attachment; 9. insert stuff saved away previously. Never mind. Yuck! I've thought about fixing this on several occasions, but the gap between thinking about fixing it and actually fixing it has always been too great. One of my excuses has been that I thought I should first understand what all the mime forward settings do, and their behavior depends on the content-type and the associated mailcap rules, so the set of all combinations of settings and rules was discouragingly large. Also, I have a solution for forwarding messages with non-text attachments and I don't forward text attachments often enough to become irritated enough with the current behavior to find the time to fix it. As far as complaining about it goes: I figured that everyone else who works on the mutt code is just as busy as I am and if I couldn't find the time to do it, I couldn't expect anyone else to. I don't think it's really a bug, either, but a missing feature. Regards, Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Mobile Broadband Division http://www.spocom.com/users/gjohnson/mutt/ | Spokane, Washington, USA
