Re: mutt can't send mail (Interrupted system call)
On Thu, Jul 31, 2014 at 06:09:12PM -0600, Bob Proulx wrote: Brian wrote: Tony Baldwin wrote: I have copied the muttrc for this account to http://tonyb.myownsite.me/pages/muttrc.txt (password removed, of course). Same muttrc on both the server and desktop. mutt works perfectly with both accounts from the server, not from the desktop. Same version of mutt on both machines? Or different versions of mutt? If different which version is in which place? For this reason, I don't think the rc file is significant, since it works on one machine fine, but what the heck...worth a shot. I haven't heard that this was solved for you yet. Has it been? I have been away from the computer for a week. At the very least it allows us to see that the line set smtp_url = smtp://to...@myownsite.me:passwordh...@mail.myownsite.me:25 looks sensible and correct. Hmm... The doc on smtp_url says: 3.265. smtp_url Type: string Default: (empty) Defines the SMTP smarthost where sent messages should relayed for delivery. This should take the form of an SMTP URL, e.g.: smtp[s]://[user[:pass]@]host[:port] where [...] denotes an optional part. Setting this variable overrides the value of the $sendmail variable. But the above has two '@' parts in it. If you tell me that the username is to...@myownsite.me then I will ask how is the parser supposed to know this and not split it at the first '@' sign? Maybe that is the problem. Note that I haven't ever used smtp_url before. Can't be the problem, because the exact same .muttrc is working on my remote server (which I'm using now to send this message). You have an account with gmx.com; a mail sent to that account with the line above unaltered might be expected to be recorded in postfix's logs. Is it? I' ll have to look at the remainder of your suggestions later. Pressed for time at the moment. Thanks for your input. Tony -- http://www.myownsite.me web design, development and hosting -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140801155017.ga23...@myownsite.me
Re: mutt can't send mail (Interrupted system call)
Brian wrote: Tony Baldwin wrote: I have copied the muttrc for this account to http://tonyb.myownsite.me/pages/muttrc.txt (password removed, of course). Same muttrc on both the server and desktop. mutt works perfectly with both accounts from the server, not from the desktop. Same version of mutt on both machines? Or different versions of mutt? If different which version is in which place? For this reason, I don't think the rc file is significant, since it works on one machine fine, but what the heck...worth a shot. I haven't heard that this was solved for you yet. Has it been? I have been away from the computer for a week. At the very least it allows us to see that the line set smtp_url = smtp://to...@myownsite.me:passwordh...@mail.myownsite.me:25 looks sensible and correct. Hmm... The doc on smtp_url says: 3.265. smtp_url Type: string Default: (empty) Defines the SMTP smarthost where sent messages should relayed for delivery. This should take the form of an SMTP URL, e.g.: smtp[s]://[user[:pass]@]host[:port] where [...] denotes an optional part. Setting this variable overrides the value of the $sendmail variable. But the above has two '@' parts in it. If you tell me that the username is to...@myownsite.me then I will ask how is the parser supposed to know this and not split it at the first '@' sign? Maybe that is the problem. Note that I haven't ever used smtp_url before. It also confirms that on the desktop you are not using exim as the MTA but the MTA built into mutt. This MTA will contact the MTA on myownsite.me (postfix), which will relay the mail. I also wonder if local machine mail makes it out. It would be interesting to know if echo test | mailx -s test to...@myownsite.me works. I suspect it isn't configured to work. If that were configured to work then none of the above would be needed and you could just use the /usr/sbin/sendmail default for sending email and everything else would work too. In any case the Postfix logs should say something about the problem. It should log that the mail was attempted and if rejected why it was rejected. You have an account with gmx.com; a mail sent to that account with the line above unaltered might be expected to be recorded in postfix's logs. Is it? For debugging SMTP things I find swaks (Swiss Army Knife SMTP) to be useful. I would try it. Not sure I can get your exact case going on the first try but I think it would be something like this: swaks --to to...@myownsite.me --server mail.myownsite.me --auth-user=tonyb --auth-password=PASS That will show something like this: 220 myownsite.me ESMTP Postfix (Debian/GNU) EHLO joseki.proulx.com 250-myownsite.me 250-PIPELINING 250-SIZE 3072 250-VRFY 250-ETRN 250-STARTTLS 250-AUTH PLAIN LOGIN 250-AUTH=PLAIN LOGIN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN And then it will try to authenticate. I personally disable PLAIN authentication. I don't like to enable a sniff-able protocol. But in any case you should see an SMTP exchange. That should help debug the problem. The Postfix logs will also log this exchange. Comparing the problem case to the working case to the debug case should show some type of clue as to the problem. Bob signature.asc Description: Digital signature
Re: mutt can't send mail (Interrupted system call)
Moin mitnanner, moin Anthony. I remember having had similar problems with my mutt/wheezy on my laptop. (My mails are handled by my provider; I use fetchmail to get them.) As Interrupt reactions of your mail system could be due to missing files or directories, I put an excerpt of my own exim4/mutt configuration here running under Wheezy in order to assist you in evaluating your entries. (my local login name = wwf) ~/.muttrc (mode= 0640, owner =wwf:mail) --- ... my_hdr From:wfok...@web.de (my email address at my email provider) ... set realname=Wilko Fokken set editor=vim (make sure vim is found by mutt!) set charset=UTF-8 ... set folder=~/Mail # Where my mail folders go set postponed=~/Mail/mutt/postponed # Where to put postponed messages set tmpdir=/tmp - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Make sure to install directories according to .muttrc contents: mkdir -p ~/Mail/archive cd ~/Mail/archive touch now mkdir -p ~/Mail/mutt cd ~/Mail/mutt touch postponed - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - check for entry in /etc/email-addresses: wwf:wfok...@web.de relating local login name to my mail name at my provider - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - my mail files (mode= 0660, owner= wwf:mail) are located in directory: /var/mail (mode= 2775, owner= root:mail) ~ in directory /etc/exim4/ (0755, root:root), I modified 3 files: /etc/exim4/update-exim4.conf.conf: -- (active entries = my alterations) # dc_eximconfig_configtype='local' dc_eximconfig_configtype='smarthost' # # dc_other_hostnames='my local mailname' dc_other_hostnames='' # # dc_local_interfaces='127.0.0.1' dc_local_interfaces='127.0.0.1 ; ::1' # # dc_readhost='' dc_readhost='fok02.laje.edewe.de' (=my local mailname) # dc_relay_domains='' # # dc_minimaldns='false' dc_minimaldns='true' # dc_relay_nets='' # # dc_smarthost='' dc_smarthost='smtp.web.de' (my provider's smtp address) # CFILEMODE='644' # # dc_use_split_config='false' dc_use_split_config='true' # # dc_hide_mailname='' dc_hide_mailname='true' # dc_mailname_in_oh='true' # dc_localdelivery='mail_spool' - - - - - - - - - - - - - - - - - - - - - - - - - - - - - /etc/exim4/passwd.client: - # Example: # target.mail.server.example:login:password # smtp.web.de:my smtp login:my smtp passwd - - - - - - - - - - - - - - - - - - - - - - - - - - - - - /etc/exim4/conf.d/router/800_exim4-config_maildrop: --- # check_local_user (ORIG: this entry was activated) ~ ~ (in order to keep my original configuration, I save my original files in an added subdir: ./ORIG/) Good luck! Wilko -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140723091521.ga5...@fok02.laje.edewe.de
Re: mutt can't send mail (Interrupted system call)
On Mon, Jul 21, 2014 at 02:33:50PM +0100, Brian wrote: On Sun 20 Jul 2014 at 16:08:25 +0200, Tony Baldwin wrote: On Sun, Jul 20, 2014 at 12:55:09PM +, Curt wrote: I understood that he is using Mutt's native smtp support and the default exim configuration, which only handles local mail, I believe. Maybe an attempt to send mail to a remote location with Mutt from the command line would result in some useful warning/error messages. I did that, now, and got no error msgs (but got a bounce message in mail declaring that mail to remote domains was not supported...this being without my .muttrc, when mailing with my .muttrc, I get that interrupted system call error). I'm persuaded by Curt and what you write to believe that your smtp transport is provided by mutt and not exim. Furthermore, you say that your desktop and myownsite.me have identical mutts and mutt configs. Wouldn't this imply the problem on the desktop lies outside mutt and in some other machine configuration? Probably the biggest differences is the myownsite.me has postfix/dovecot and the desktop has exim, but I don't know if mutt is using exim or postfix anyway, as mentioned. I think it's just the native support on both. There is probably a good reason for you to use mutt's native smtp support but you could consider using exim to sidestep the issue. How would I change from one to the other? tony -- http://www.myownsite.me web design, development and hosting -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140722110539.ga16...@myownsite.me
Re: mutt can't send mail (Interrupted system call)
On 2014-07-22, Tony Baldwin to...@myownsite.me wrote: There is probably a good reason for you to use mutt's native smtp support but you could consider using exim to sidestep the issue. How would I change from one to the other? I'm all for sidestepping your issue if only I knew what the heck your issue was. To reconfigure exim4, you would issue the following command: dpkg-reconfigure exim4-config then answer the questions correctly. ;-) (for gmx? probably a setup similar to gmail as per this wiki (smarthost): https://wiki.debian.org/GmailAndExim4) Of course, you'd have to tell mutt to hand off the mail locally rather than contacting the remote smtp server itself. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnlssmpi.2b9.cu...@einstein.electron.org
Re: mutt can't send mail (Interrupted system call)
On Tue, Jul 22, 2014 at 12:38:10PM +, Curt wrote: On 2014-07-22, Tony Baldwin to...@myownsite.me wrote: There is probably a good reason for you to use mutt's native smtp support but you could consider using exim to sidestep the issue. How would I change from one to the other? I'm all for sidestepping your issue if only I knew what the heck your issue was. Ultimately, that's what I'd like to determine, but have so far not been able to. The error is too vague (Interrupted System Call), and all the googling and duckgoing and ixquicking has produced nothing useful. To reconfigure exim4, you would issue the following command: dpkg-reconfigure exim4-config then answer the questions correctly. ;-) (for gmx? probably a setup similar to gmail as per this wiki (smarthost): https://wiki.debian.org/GmailAndExim4) Of course, you'd have to tell mutt to hand off the mail locally rather than contacting the remote smtp server itself. -- http://www.myownsite.me web design, development and hosting -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140722125721.ga18...@myownsite.me
Re: mutt can't send mail (Interrupted system call)
On 2014-07-22, Tony Baldwin to...@myownsite.me wrote: Ultimately, that's what I'd like to determine, but have so far not been able to. The error is too vague (Interrupted System Call), and all the googling and duckgoing and ixquicking has produced nothing useful. We need to see your config. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnlssr0l.2b9.cu...@einstein.electron.org
Re: mutt can't send mail (Interrupted system call)
On Tue 22 Jul 2014 at 13:50:13 +, Curt wrote: On 2014-07-22, Tony Baldwin to...@myownsite.me wrote: Ultimately, that's what I'd like to determine, but have so far not been able to. The error is too vague (Interrupted System Call), and all the googling and duckgoing and ixquicking has produced nothing useful. We need to see your config. Thirded. (Because the request has been made twice already). I'm loath to move someone on to exim if there is a fixable mutt config. Not that there is any wrong with exim but if mutt is using 'smtp_url' the OP must have a reason for it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140722175053.ga27...@copernicus.demon.co.uk
Re: mutt can't send mail (Interrupted system call)
On Tue, Jul 22, 2014 at 06:50:54PM +0100, Brian wrote: On Tue 22 Jul 2014 at 13:50:13 +, Curt wrote: On 2014-07-22, Tony Baldwin to...@myownsite.me wrote: Ultimately, that's what I'd like to determine, but have so far not been able to. The error is too vague (Interrupted System Call), and all the googling and duckgoing and ixquicking has produced nothing useful. We need to see your config. Thirded. (Because the request has been made twice already). I'm loath to move someone on to exim if there is a fixable mutt config. Not that there is any wrong with exim but if mutt is using 'smtp_url' the OP must have a reason for it. Okay, but keep in mind, I have mutt on two machines, my desktop, and my server. Both are running wheezy, and both are using the same muttrc files (I have two because I use it with two different accounts, using mutt -F otherconfig to access the second account). I have copied the muttrc for this account to http://tonyb.myownsite.me/pages/muttrc.txt (password removed, of course). Same muttrc on both the server and desktop. mutt works perfectly with both accounts from the server, not from the desktop. For this reason, I don't think the rc file is significant, since it works on one machine fine, but what the heck...worth a shot. Tony -- http://www.myownsite.me web design, development and hosting -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140722204130.ga25...@myownsite.me
Re: mutt can't send mail (Interrupted system call)
On Tue 22 Jul 2014 at 22:41:31 +0200, Tony Baldwin wrote: On Tue, Jul 22, 2014 at 06:50:54PM +0100, Brian wrote: On Tue 22 Jul 2014 at 13:50:13 +, Curt wrote: On 2014-07-22, Tony Baldwin to...@myownsite.me wrote: Ultimately, that's what I'd like to determine, but have so far not been able to. The error is too vague (Interrupted System Call), and all the googling and duckgoing and ixquicking has produced nothing useful. We need to see your config. Thirded. (Because the request has been made twice already). I'm loath to move someone on to exim if there is a fixable mutt config. Not that there is any wrong with exim but if mutt is using 'smtp_url' the OP must have a reason for it. Okay, but keep in mind, I have mutt on two machines, my desktop, and my server. Both are running wheezy, and both are using the same muttrc files (I have two because I use it with two different accounts, using mutt -F otherconfig to access the second account). I have copied the muttrc for this account to http://tonyb.myownsite.me/pages/muttrc.txt (password removed, of course). Same muttrc on both the server and desktop. mutt works perfectly with both accounts from the server, not from the desktop. For this reason, I don't think the rc file is significant, since it works on one machine fine, but what the heck...worth a shot. At the very least it allows us to see that the line set smtp_url = smtp://to...@myownsite.me:passwordh...@mail.myownsite.me:25 looks sensible and correct. It also confirms that on the desktop you are not using exim as the MTA but the MTA built into mutt. This MTA will contact the MTA on myownsite.me (postfix), which will relay the mail. You have an account with gmx.com; a mail sent to that account with the line above unaltered might be expected to be recorded in postfix's logs. Is it? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140723011200.gb27...@copernicus.demon.co.uk
Re: mutt can't send mail (Interrupted system call)
On Sun 20 Jul 2014 at 16:08:25 +0200, Tony Baldwin wrote: On Sun, Jul 20, 2014 at 12:55:09PM +, Curt wrote: I understood that he is using Mutt's native smtp support and the default exim configuration, which only handles local mail, I believe. Maybe an attempt to send mail to a remote location with Mutt from the command line would result in some useful warning/error messages. I did that, now, and got no error msgs (but got a bounce message in mail declaring that mail to remote domains was not supported...this being without my .muttrc, when mailing with my .muttrc, I get that interrupted system call error). I'm persuaded by Curt and what you write to believe that your smtp transport is provided by mutt and not exim. Furthermore, you say that your desktop and myownsite.me have identical mutts and mutt configs. Wouldn't this imply the problem on the desktop lies outside mutt and in some other machine configuration? There is probably a good reason for you to use mutt's native smtp support but you could consider using exim to sidestep the issue. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140721133350.ga24...@copernicus.demon.co.uk
Re: mutt can't send mail (Interrupted system call)
On Mon, Jul 21, 2014 at 02:33:50PM +0100, Brian wrote: On Sun 20 Jul 2014 at 16:08:25 +0200, Tony Baldwin wrote: On Sun, Jul 20, 2014 at 12:55:09PM +, Curt wrote: I understood that he is using Mutt's native smtp support and the default exim configuration, which only handles local mail, I believe. Maybe an attempt to send mail to a remote location with Mutt from the command line would result in some useful warning/error messages. I did that, now, and got no error msgs (but got a bounce message in mail declaring that mail to remote domains was not supported...this being without my .muttrc, when mailing with my .muttrc, I get that interrupted system call error). I'm persuaded by Curt and what you write to believe that your smtp transport is provided by mutt and not exim. Furthermore, you say that your desktop and myownsite.me have identical mutts and mutt configs. Wouldn't this imply the problem on the desktop lies outside mutt and in some other machine configuration? There is probably a good reason for you to use mutt's native smtp support but you could consider using exim to sidestep the issue. Or ask the mutt experts on mutt-us...@mutt.org. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140721163258.GA14377@tal
Re: mutt can't send mail (Interrupted system call)
On Jo, 17 iul 14, 23:41:20, Anthony Baldwin wrote: Hi, I am unable to send mail with mutt from my home desktop, either through one of my own domains (this one, myownsite.me), or through gmx.com's SMTP server. Please attach your .muttrc, just take care to replace passwords with XXX or so. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: mutt can't send mail (Interrupted system call)
On Sun 20 Jul 2014 at 02:06:31 +0200, Tony Baldwin wrote: On Fri, Jul 18, 2014 at 03:45:27PM +0100, Brian wrote: Assuming a valid username is tony, mainlog should show a record of mail -s TEST tony@localhost being sent. Yeah, it does. But that doesn't tell me anything about why mutt is faiilng. It shows me that mail works for local users. Does 'mail' also work with remote users? Does mutt work with local and remote users? Can we rule out a problem with exim? Move any mutt config files in $HOME out of the way. You've not altered any in /etc? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20072014124737.0cfe62887...@desktop.copernicus.demon.co.uk
Re: mutt can't send mail (Interrupted system call)
On 2014-07-20, Brian a...@cityscape.co.uk wrote: Yeah, it does. But that doesn't tell me anything about why mutt is faiilng. It shows me that mail works for local users. Does 'mail' also work with remote users? Does mutt work with local and remote users? Can we rule out a problem with exim? I understood that he is using Mutt's native smtp support and the default exim configuration, which only handles local mail, I believe. Maybe an attempt to send mail to a remote location with Mutt from the command line would result in some useful warning/error messages. Move any mutt config files in $HOME out of the way. You've not altered any in /etc? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnlsnf1d.21v.cu...@einstein.electron.org
Re: mutt can't send mail (Interrupted system call)
On Sun, Jul 20, 2014 at 12:55:55PM +0100, Brian wrote: On Sun 20 Jul 2014 at 02:06:31 +0200, Tony Baldwin wrote: On Fri, Jul 18, 2014 at 03:45:27PM +0100, Brian wrote: Assuming a valid username is tony, mainlog should show a record of mail -s TEST tony@localhost being sent. Yeah, it does. But that doesn't tell me anything about why mutt is faiilng. It shows me that mail works for local users. Does 'mail' also work with remote users? Does mutt work with local and remote users? Can we rule out a problem with exim? I can not use 'mail' to send to remote users, now. mutt isn't working with local or remote, but even sending to a local user, it's got to go through the remote SMTP server, no? and that's the problem, at least, somewhere in getting mail to/through a remote SMTP server (and I've ruled out problem at the remote SMTP server end, definitely at my end). Move any mutt config files in $HOME out of the way. You've not altered any in /etc? User mutt without my .muttrc? Ah, okay, I did that, and I CAN mail to a local user, but mailing to a remote user without my rc file does not work: A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: to...@myownsite.me Mailing to remote domains not supported tony -- http://www.myownsite.me web design, development and hosting -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140720140318.ga24...@myownsite.me
Re: mutt can't send mail (Interrupted system call)
On Sun, Jul 20, 2014 at 12:55:09PM +, Curt wrote: On 2014-07-20, Brian a...@cityscape.co.uk wrote: Yeah, it does. But that doesn't tell me anything about why mutt is faiilng. It shows me that mail works for local users. Does 'mail' also work with remote users? Does mutt work with local and remote users? Can we rule out a problem with exim? I understood that he is using Mutt's native smtp support and the default exim configuration, which only handles local mail, I believe. Maybe an attempt to send mail to a remote location with Mutt from the command line would result in some useful warning/error messages. I did that, now, and got no error msgs (but got a bounce message in mail declaring that mail to remote domains was not supported...this being without my .muttrc, when mailing with my .muttrc, I get that interrupted system call error). Move any mutt config files in $HOME out of the way. You've not altered any in /etc? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnlsnf1d.21v.cu...@einstein.electron.org -- http://www.myownsite.me web design, development and hosting -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140720140825.gb24...@myownsite.me
Re: mutt can't send mail (Interrupted system call)
On Fri, Jul 18, 2014 at 03:45:27PM +0100, Brian wrote:
On Fri 18 Jul 2014 at 15:26:50 +0200, Tony Baldwin wrote:
/var/log/exim4/mainlog shows nothing I deem useful.
Lots of stuff like:
2014-07-18 07:53:14 Start queue run: pid=13117
2014-07-18 07:53:14 End queue run: pid=13117
2014-07-18 08:23:14 Start queue run: pid=14426
2014-07-18 08:23:14 End queue run: pid=14426
This shows exim behaving normally.
/var/log/mail.{log,warn,info,error} are all empty, and the older files
(mail.*.1) show nothing since Nov 5 of last year.
Exim doesn't use these files.
So, the logs aren't proving particularly helpful.
Assuming a valid username is tony, mainlog should show a record of
mail -s TEST tony@localhost
being sent.
Yeah, it does.
But that doesn't tell me anything about why mutt is faiilng.
It shows me that mail works for local users.
tony
--
http://www.myownsite.me
web design, development and hosting
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/2014072631.ga7...@myownsite.me
Re: mutt can't send mail (Interrupted system call)
On Thu, Jul 17, 2014 at 08:52:15PM -0600, Bob Proulx wrote: Tony Baldwin wrote: What else can I do to diagnose this issue and/or, of course, resolve it? I think this must be something other than mutt. In your description you didn't mention how you were sending email and therefore I know you weren't looking at that part of things. I suspect it is in the MTA side of things. Of course these days many people are using IMAP to read messages and often using SMTP on the submission port with SASL or various for sending mail. Hard to say what you are using. Well I know almost nothing about gmx's SMTP server, other than the requisite knowledge to send mail through it from a MUA, which I can do from icedove and mutt (but not mutt here, currently. Can with mutt on my remote server). My remote server (myownsite.me, from which I am sending this mail) has postfix and dovecot, but clearly, the problem is on my local machine (and affecting mutt, but not icedove). If you have not customized it then you are using /usr/sbin/sendmail and the message is handed off to your system MTA for delivery. If so then the system MTA will log all of these actions to the system log. Please look in /var/log/mail.log (Postfix logs there) or possibly other location and see what it says. I forget where Exim logs to and exim4 is the default MTA unless you select another. A common thing for me to do is to run tail -f /var/log/mail.log in one terminal window while sending mail in another terminal window. yes, not customized, exim4 installed, so I assume that's sending the mail Run mailq and see what mailq says. If I run that as a regular user, I just get exim: permission denied. If I run it as root, no message appears. I don't know what, if anything, it is doing in that case. If the message is undeliverable but still in the queue the reason will be shown there. Most messages will queue for five days (configurable, maximal_queue_lifetime = 5d for postfix) until it times out. At that point it will generate a bounce message back to the sender. A side note but a useful SMTP debug tool is swaks. It will show the SMTP handshake and is a useful debug tool. Bob -- http://www.myownsite.me web design, development and hosting -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140718131409.gb19...@myownsite.me
Re: mutt can't send mail (Interrupted system call)
On Fri, Jul 18, 2014 at 03:14:09PM +0200, Tony Baldwin wrote:
On Thu, Jul 17, 2014 at 08:52:15PM -0600, Bob Proulx wrote:
If you have not customized it then you are using /usr/sbin/sendmail
and the message is handed off to your system MTA for delivery. If so
then the system MTA will log all of these actions to the system log.
Please look in /var/log/mail.log (Postfix logs there) or possibly
other location and see what it says. I forget where Exim logs to and
exim4 is the default MTA unless you select another. A common thing
for me to do is to run tail -f /var/log/mail.log in one terminal
window while sending mail in another terminal window.
yes, not customized, exim4 installed, so I assume that's sending the
mail
/var/log/exim4/mainlog shows nothing I deem useful.
Lots of stuff like:
2014-07-18 07:53:14 Start queue run: pid=13117
2014-07-18 07:53:14 End queue run: pid=13117
2014-07-18 08:23:14 Start queue run: pid=14426
2014-07-18 08:23:14 End queue run: pid=14426
/var/log/mail.{log,warn,info,error} are all empty, and the older files
(mail.*.1) show nothing since Nov 5 of last year.
So, the logs aren't proving particularly helpful.
Tony
--
http://www.myownsite.me
web design, development and hosting
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140718132650.gc19...@myownsite.me
Re: mutt can't send mail (Interrupted system call)
Am 18.07.2014 15:26, schrieb Tony Baldwin:
On Fri, Jul 18, 2014 at 03:14:09PM +0200, Tony Baldwin wrote:
On Thu, Jul 17, 2014 at 08:52:15PM -0600, Bob Proulx wrote:
If you have not customized it then you are using /usr/sbin/sendmail
and the message is handed off to your system MTA for delivery. If so
then the system MTA will log all of these actions to the system log.
Please look in /var/log/mail.log (Postfix logs there) or possibly
other location and see what it says. I forget where Exim logs to and
exim4 is the default MTA unless you select another. A common thing
for me to do is to run tail -f /var/log/mail.log in one terminal
window while sending mail in another terminal window.
yes, not customized, exim4 installed, so I assume that's sending the
mail
/var/log/exim4/mainlog shows nothing I deem useful.
Lots of stuff like:
2014-07-18 07:53:14 Start queue run: pid=13117
2014-07-18 07:53:14 End queue run: pid=13117
2014-07-18 08:23:14 Start queue run: pid=14426
2014-07-18 08:23:14 End queue run: pid=14426
/var/log/mail.{log,warn,info,error} are all empty, and the older files
(mail.*.1) show nothing since Nov 5 of last year.
So, the logs aren't proving particularly helpful.
Tony
According to wiki.debian.org Mutt has it's own SMTP implementation since
1.5.15. Exim should therefore not be necessary.
Starting Mutt with debug level 1 or higher enabled should provide you
with some useful information.
--
Alex JOST
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53c9265f.90...@dimejo.at
Re: mutt can't send mail (Interrupted system call)
On Fri 18 Jul 2014 at 15:26:50 +0200, Tony Baldwin wrote:
/var/log/exim4/mainlog shows nothing I deem useful.
Lots of stuff like:
2014-07-18 07:53:14 Start queue run: pid=13117
2014-07-18 07:53:14 End queue run: pid=13117
2014-07-18 08:23:14 Start queue run: pid=14426
2014-07-18 08:23:14 End queue run: pid=14426
This shows exim behaving normally.
/var/log/mail.{log,warn,info,error} are all empty, and the older files
(mail.*.1) show nothing since Nov 5 of last year.
Exim doesn't use these files.
So, the logs aren't proving particularly helpful.
Assuming a valid username is tony, mainlog should show a record of
mail -s TEST tony@localhost
being sent.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/18072014153934.3bdd3be61...@desktop.copernicus.demon.co.uk
Re: mutt can't send mail (Interrupted system call)
On Thu, 17 Jul 2014 20:52:15 -0600 Bob Proulx b...@proulx.com wrote: Tony Baldwin wrote: What else can I do to diagnose this issue and/or, of course, resolve it? I think this must be something other than mutt. In your description you didn't mention how you were sending email and therefore I know you weren't looking at that part of things. I suspect it is in the MTA side of things. Normally (and I say normally in the traditional sense knowing that many people do things differently now) the MUA (mail user agent). The MUA is mutt, mailx, pine, or other. Those MUAs send the message to /usr/sbin/sendmail. The /usr/sbin/sendmail binary is one of Postfix, Exim, Sendmail or other MTA (mail transfer agent). OR, one of those SMTP on-ramp things like nullmailer. If you feel strongly that you don't want a full fledged MTA on your machine, you can use an on-ramp to replace /usr/sbin/sendmail and the send executable. If you're using an on-ramp, I recommend nullmailer because it employs a queue, whereas some of its competitors just block until messages are sent. Here's some stuff I wrote on nullmailer: * http://www.troubleshooters.com/linux/nullmailer/index.htm * http://www.troubleshooters.com/linux/nullmailer/landmines.htm SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140718111749.4ad1b...@mydesq2.domain.cxm
Re: mutt can't send mail (Interrupted system call)
On 2014-07-18, Tony Baldwin to...@myownsite.me wrote: yes, not customized, exim4 installed, so I assume that's sending the mail I believe by default exim is configured only to handle email local to the system. That's how it works here (squeeze). I use alpine to send directly to my ISP's smtp server (not handing the mail to exim/sendmail--as outlined by Bob in his message). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnlsif0k.2f6.cu...@einstein.electron.org
mutt can't send mail (Interrupted system call)
Hi, I am unable to send mail with mutt from my home desktop, either through one of my own domains (this one, myownsite.me), or through gmx.com's SMTP server. Furthermore, I can send through both with mutt when I login into the myownsite server (hosted in Germany by contabo.com) just fine. So, I have determined that the problem must be with mutt, here, not with either SMTP server. I can receive mail just fine from both servers on either machine. I did some searching (duckgoing, ixquicking, etc.), and all I could come up with was to clear the header cache and check the rc files. Well, I vimdiffed the rc files from the remote server and here, and there were absolutely no difference (indeed, I did not expect there to be any, since I scp-ed them from here to there and haven't altered them since), and I deleted the header cache here, and still no joy. I can not send mail with mutt from home (sending this with squirrelmail on the remote server in my browser, at the moment). What else can I do to diagnose this issue and/or, of course, resolve it? thanks, tony -- http://www.myownsite.me web design, development and hosting -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/0c9db5f869098cadf984beb91ffe3950.squir...@webmail.myownsite.me
Re: mutt can't send mail (Interrupted system call)
On Thu, Jul 17, 2014 at 11:41:20PM +0200, Anthony Baldwin wrote: Hi, I am unable to send mail with mutt from my home desktop, either through one of my own domains (this one, myownsite.me), or through gmx.com's SMTP server. Furthermore, I can send through both with mutt when I login into the myownsite server (hosted in Germany by contabo.com) just fine. So, I have determined that the problem must be with mutt, here, not with either SMTP server. I can receive mail just fine from both servers on either machine. I did some searching (duckgoing, ixquicking, etc.), and all I could come up with was to clear the header cache and check the rc files. Well, I vimdiffed the rc files from the remote server and here, and there were absolutely no difference (indeed, I did not expect there to be any, since I scp-ed them from here to there and haven't altered them since), and I deleted the header cache here, and still no joy. I can not send mail with mutt from home (sending this with squirrelmail on the remote server in my browser, at the moment). What else can I do to diagnose this issue and/or, of course, resolve it? Oh, I should probably have mentioned that both machines, the home desktop and the remote server, are running Wheezy, both updated about a week ago. Mutt seems to have stopped sending shortly after this last update. tony -- http://www.myownsite.me web design, development and hosting -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140717223237.ga6...@myownsite.me
Re: mutt can't send mail (Interrupted system call)
Tony Baldwin wrote: What else can I do to diagnose this issue and/or, of course, resolve it? I think this must be something other than mutt. In your description you didn't mention how you were sending email and therefore I know you weren't looking at that part of things. I suspect it is in the MTA side of things. Normally (and I say normally in the traditional sense knowing that many people do things differently now) the MUA (mail user agent). The MUA is mutt, mailx, pine, or other. Those MUAs send the message to /usr/sbin/sendmail. The /usr/sbin/sendmail binary is one of Postfix, Exim, Sendmail or other MTA (mail transfer agent). The MTA delivers the message to the next hop in the route to the destination. The next hop is usually controlled by MX DNS records. Of course these days many people are using IMAP to read messages and often using SMTP on the submission port with SASL or various for sending mail. Hard to say what you are using. If you have not customized it then you are using /usr/sbin/sendmail and the message is handed off to your system MTA for delivery. If so then the system MTA will log all of these actions to the system log. Please look in /var/log/mail.log (Postfix logs there) or possibly other location and see what it says. I forget where Exim logs to and exim4 is the default MTA unless you select another. A common thing for me to do is to run tail -f /var/log/mail.log in one terminal window while sending mail in another terminal window. Run mailq and see what mailq says. If the message is undeliverable but still in the queue the reason will be shown there. Most messages will queue for five days (configurable, maximal_queue_lifetime = 5d for postfix) until it times out. At that point it will generate a bounce message back to the sender. A side note but a useful SMTP debug tool is swaks. It will show the SMTP handshake and is a useful debug tool. Bob signature.asc Description: Digital signature
