Re: Mutt hangs, Network Issue?
On Tue, May 20, 2008 at 05:09:07PM -0500, David Champion wrote: > > What should a functional control-z tell me? > > If control-Z works, your transport (ssh) and terminal are still > fundamentally intact, and responsive to low-level traffic and > out-of-band signals. (It means that mutt is responsive to signals too, > for that matter -- once it receives them.) Does mutt work again once > you bring it back to foreground, or does it remain hung? If it hangs, > and you type a bunch of stuff followed by control-Z, and then foreground > mutt, does all the stuff you typed suddenly appear to execute at once? > Does it appear to have already executed long ago? Or is it ignored? I'll have to dig more into this later ... The two occasions I've done this, there was some delay with mutt responding. But once it did, it acted perfectly normal. There have been times when mutt doesn't respond, I'll hit a few keys, and after a while maybe it comes back to life, and maybe it doesn't. But, because I'm hugely impatient, I typically just kill the mutt process, and wait for that to bring back a prompt. BTW, I'm at home now. Looks like mutt died. The ssh session is still up. The last 30 or 40 lines of the debug log are like mutt_index_menu[613]: Got op -1 mutt_index_menu[613]: Got op -1 mutt_index_menu[613]: Got op -1 mutt_index_menu[613]: Got op -1 mutt_index_menu[613]: Got op -1 mutt_index_menu[613]: Got op -1 mutt_index_menu[613]: Got op -1 It just occurred to me, that when I ssh in from home, I don't seem to have this problem. Obviously same version of mutt. Same configs. But I tend not to leave the home sessions open all the time so a little hard to tell. > at an exact moment that it appears hung, but it's quite possible that > it's just waiting for input that's simply not arriving. The logs > will tell what it *has* been doing up until that, but it might not be > anything special. Thanks, I may get into this more. > Honestly this has the feel of an ordinary session timeout at the network > level, which wouldn't be surprising. But you said that it happens only > with mutt, and not even with an idle shell. That's what seems strange > to me. My feeling all along is that it is more network related than anything. But mutt is somehow triggering something screwy. I am still convinced the router change is one of the pieces of the puzzle. And I never have a problem with other terminals that are opened to the same server. Thanks for the help! -- Hal Burgiss
Re: Mutt hangs, Network Issue?
On Tue, May 20, 2008 at 02:05:28PM -0700, Gary Johnson wrote: > > I should have mentioned this before, but something you can do to > help associate the contents of the debug file with mutt's actions is > to open another terminal and in it run > >tail -f ~/.muttdebug0 Excellent! Its going now. Thanks. -- Hal Burgiss DBS>Interactive Technical Services
Re: Mutt hangs, Network Issue?
On Tue, May 20, 2008 at 01:46:59PM -0700, Gary Johnson wrote: > > The debug output is sent to a file, not to your terminal. The > latest debug file will have the name ~/.muttdebug0. Ach! Thanks. Wasn't expecting that. Now have 5 different ones, and its a little hard to see where the problem might have been. I'll know better next time. -- Hal Burgiss
Re: Mutt hangs, Network Issue?
On Tue, May 20, 2008 at 12:06:28PM -0500, David Champion wrote: > > So you regain control of mutt's session when mutt dies to a kill signal? > Can you also suspend mutt (control-Z) from within the same session, or > only from outside? I've had two opportunites to try control-z. Both times it worked, though there was a delay. On the second attempt, I had tried Control-c a couple of times first, and its possible there was a delayed thing going on. What should a functional control-z tell me? -- Hal Burgiss DBS>Interactive Technical Services
Re: Mutt hangs, Network Issue?
On Tue, May 20, 2008 at 12:26:54PM -0500, Kyle Wheeler wrote: > Try running mutt in debug mode; with luck, we can see what mutt's > doing when it dies. All I get is ... Caught signal 15... Exiting. That is from killing the mutt process after its hung. -- Hal Burgiss DBS>Interactive Technical Services
Re: Mutt hangs, Network Issue?
On Tue, May 20, 2008 at 06:01:10PM +, Jussi Peltola wrote: > Try enabling SSH keepalives. Thanks. I have keepalives enabled on the server end already. -- Hal Burgiss DBS>Interactive Technical Services
Re: Mutt hangs, Network Issue?
On Tue, May 20, 2008 at 12:26:54PM -0500, Kyle Wheeler wrote: > > Try running mutt in debug mode; with luck, we can see what mutt's > doing when it dies. Thanks! I wasn't aware of debug mode, but I'm game. Rebuilt now and running -d 5 now. -- Hal Burgiss DBS>Interactive Technical Services
Re: Mutt hangs, Network Issue?
On Tue, May 20, 2008 at 12:06:28PM -0500, David Champion wrote: > > So you regain control of mutt's session when mutt dies to a kill > signal? Yes. Sometimes quickly. Sometimes after more than 30 seconds or so. > Can you also suspend mutt (control-Z) from within the same session, > or only from outside? I have not tried suspending. I will next time. > Does mutt freeze while you're actively using it, or only while > you're idling? Or both? Idling only. And only on the index screen. I use vim as both pager and composer, so maybe that means something. In fact, I have accidently left a partially composed mail open for many hours, and mutt is always functional once I close out the vim/compose aspect. > Is it at all possible that the freezes are related to software flow > control signals (normally control-S = stop; control-Q = start; but see > `stty`)? This seems unlikely since you said the problem started with > the installation of a NATting router, but it's sometimes worth asking. I wouldn't think so either. I guess I could dig into that a little more. This is the same system (hardware + software) that worked flawlessly until the new router. The router thing might be co-incidence and a red-herring, but that is when the problem started. Thanks. -- Hal Burgiss
Re: Mutt hangs, Network Issue?
On Tue, May 20, 2008 at 12:13:34PM -0400, Hal Burgiss wrote: > On Tue, May 20, 2008 at 05:45:47PM +0200, Rado S wrote: > > a) try 1.5.18 > > OK, good idea. I am running that now, and should know within an hour > or two. No go. Still hanging. :( -- Hal Burgiss
Re: Mutt hangs, Network Issue?
On Tue, May 20, 2008 at 05:45:47PM +0200, Rado S wrote: > a) try 1.5.18 OK, good idea. I am running that now, and should know within an hour or two. > b) I only know of stale NFS handles freezing mutt beyond recovery. > Try with local filesys folder open in mutt all day. If it doesn't > hang, it's NFS. I don't think thats it. There are no nfs mounts involved here. Thanks! -- Hal Burgiss
Mutt hangs, Network Issue?
Hello, I have a strange problem that is driving me nuts. Sorry if this is long. Background: I am a long time mutt user. I use it at home. I use it at work. I get a lot of email. I love mutt. The problem is at work. I routinely interact with several servers (Linux and *BSD). I keep terminals with ssh sessions open to all these. On one of these, I keep my personal mail spool (mbox). This is a CentOS Linux server. The mutt version is mutt-1.4.1-12.0.3.el4. So I connect from my Ubuntu Desktop via ssh to the server, and mutt runs locally on the server. I do not use mutt for retrieving mail, just reading mail from the spool. This Mutt hangs/freezes probably 10-15 times a day. It is completely unresponsive. If I open a second ssh session, and kill the mutt process, it generally takes maybe 30 seconds for mutt to let go, and to get a shell prompt back. If I don't manually kill mutt, and just let nature take its course, the ssh session itself will eventually time out and die, and I am dropped back to my local desktop. The aggravation is killing me! I have approximately 12 ssh session opens now, and three to this same server where I use mutt. Many of these stay open for weeks, and sometimes months without issue. The only one that is problematic is the one with mutt. And only when mutt is running. The other ssh sessions to this same server are 100% problem free. This problem only started after we changed our local office router that does NAT, DHCP, packet filtering, etc a few months ago. Other than this one issue, the router is problem free, with approx 20 users connected to it, using it all day long. My suspicion is that there is some background network related stuff that mutt is doing, that is breaking statefulness on the router, and the network connection just hangs. But that is a wild guess. It may turn out to be a network issue, but if so, mutt is the only thing triggering it. I am at a loss of how to troubleshoot this. Any ideas would be hugely appreciated! -- Hal Burgiss
Re: Dependency problem: OpenSSL and Mutt 1.3.18i-2
On Fri, Jun 08, 2001 at 09:58:36PM -0400, John P. Verel wrote: > I'm attempting to upgrade to Mutt mutt-1.3.18i-2, using an rpm. I get > these failed dependencies messages: > > libcrypto.so.0.9.6.1 is needed by mutt-1.3.18i-2 > libssl.so.0.9.6.1 is needed by mutt-1.3.18i-2 > libtinfo.so.5 is needed by mutt-1.3.18i-2 > > Search at rpmfind says that openssl-0.9.6a-4 provides these objects. Just curious where you got this? It looks like the rawhide version. > When I attempt an rpm -Uvh on mutt and openssl, I get a slew of > dependency errors relating to libssl.so.1 and libcrypto.so.1 being > needed by a few dozen packages. I am, of course, reluctant to do a > --nodeps force on such an important package as openssl. > > I have openssl-0.9.6-3 installed, running a stock Red Hat 7.1 > installation. > > Can anyone suggest a solution? Thanks. I just went through this about an hour ago, for different reasons. The rawhide rpm has libssl.so.2 and libcrypto.so.2, no *so.1. Not sure if this is by design, or an oversight. I recreated the symlink that I think should be there, and everything seems to work. I don't like doing that kind of thing, but, hey, I needed it since something is broken in the 7.1 version. The only thing I ran afoul of was so far ssh not wanting to run. Rebuilding that from src.rpm worked. -- Hal B [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Spamtrap: [EMAIL PROTECTED] and [EMAIL PROTECTED] --
Re: Send hook question
On Tue, Oct 10, 2000 at 03:52:49PM +0200, Ulf Erikson wrote: > >mostly I think the autoedit is a bit easier > > (ie I am lazy :), especially when replying. The 'To' and 'Subject' > > normally have already been decided in this case. I rarely change To or > > Subject on a reply. Now, for a new mail, it makes perfect sense. > > Perhaps you are searching for > set autoedit = no > set fast_reply = yes Yes, I am ;) You are a good man Ulf. Thanks. Life is good again. -- Hal B [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] --
Re: Send hook question
On Tue, Oct 10, 2000 at 12:51:31AM -0400, David T-G wrote: > Hal -- > > ...and then Hal Burgiss said... > % > % Yea, it works fine with autoedit off, but I like autoedit too :( > > What does autoedit get you that you can't have otherwise? Do you have > edit_hdrs set, maybe, and like to play with your headers there? Yes, I do have it set. But mostly I think the autoedit is a bit easier (ie I am lazy :), especially when replying. The 'To' and 'Subject' normally have already been decided in this case. I rarely change To or Subject on a reply. Now, for a new mail, it makes perfect sense. > I find that edit_hdrs lets me muck around to my heart's content, but I > leave autoedit off so that I can specify a To: entry so that hooks work. > I also have $askbcc and $askcc turned off; I do that in the editor... Same here. Maybe this just takes some getting used to. I guess I want my cake and to eat it too as they say. -- Hal B [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] --
Re: Send hook question
On Fri, Oct 06, 2000 at 07:27:38PM +0200, Michael Tatge wrote: > Hal Burgiss muttered: > I don't have a clue how combine autoedit and send-hooks. Harold says > it is possible so maybe you should start a new muttrc from scratch > and you'll see which line confuses mutt. Sounds challenging. Would have to take a few options at a time. If I did a new one with all the features I like/want in one fell swoop, I would have the exact same muttrc ;) I'll play with this this weekend. Also, either I am suffering premature senile dementia, or this was working not too long ago. Oh well ... > P.S. Check your Mail-Followup-To: Thanks. Was wondering why I was getting duplicates. You just gotta love mutt for all the configuration options. -- Hal B [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] --
Re: Send hook question
On Thu, Oct 05, 2000 at 08:08:48PM +0200, Hal Burgiss wrote: > Peter Jaques muttered: > > > > > Please post your whole muttrc. > > > http://feenix.eyep.net/xstuff/muttrc > > do you have 'autoedit' set? > > He does. And that's why the send-hooks do not work. So, Hal the solution is > obvious - give up that autoedit stuff. > Yea, it works fine with autoedit off, but I like autoedit too :( You confuse me with your from header for a minute ;) -- Hal B [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] --
Re: Send hook question
Peter Jaques muttered: > > > Please post your whole muttrc. > > http://feenix.eyep.net/xstuff/muttrc > do you have 'autoedit' set? He does. And that's why the send-hooks do not work. So, Hal the solution is obvious - give up that autoedit stuff. HTH, Michael -- Our informal mission is to improve the love life of operators worldwide. -- Peter Behrendt, president of Exabyte PGP-fingerprint: DECA E9D2 EBDD 0FE0 0A65 40FA 5967 ACA1 0B57 7C13
Re: Send hook question
On Thu, Oct 05, 2000 at 11:45:33AM +0200, Michael Tatge wrote: > Hal Burgiss muttered: > > > > unset use_from > > Don't know why you do that, but according to the docs it shouldn't > hurt. It might be worth testing without this line, though. Still no go. -- Hal B [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] --
Re: Send hook question
On Thu, Oct 05, 2000 at 11:45:33AM +0200, Michael Tatge wrote: > Hal Burgiss muttered: > > Should the below not work? I could swear it used to ;) Recently even. > > Despite much playing with this, I cannot get the header to handle the > > exceptions. > > > > > > unset use_from > > Don't know why you do that, but according to the docs it shouldn't > hurt. It might be worth testing without this line, though. I'll try that. That came from an example in the original Muttrc when I first installed a couple of years ago. > > send-hook . 'my_hdr From: Hal Burgiss <[EMAIL PROTECTED]>' > > send-hook redhat-list 'my_hdr From: Hal Burgiss <[EMAIL PROTECTED]>' > > These _have_ to work. If they don't, I'd suspect that there is > something else disturbing. Just copy / pasted your send-hooks into my > mutt - they work. Please post your whole muttrc. http://feenix.eyep.net/xstuff/muttrc -- Hal B [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] --
Re: Send hook question
On Thu, Oct 05, 2000 at 01:30:40AM -0600, Harold Oga wrote: > On Wed, Oct 04, 2000 at 11:29:30PM -0400, Hal Burgiss wrote: > >On Wed, Oct 04, 2000 at 06:25:47PM -0600, Harold Oga wrote: > >> > >> send-hook . 'my_hdr From: Hal Burgiss <[EMAIL PROTECTED]>' > >> send-hook '~C redhat-list' 'my_hdr From: Hal Burgiss <[EMAIL PROTECTED]>' > > > >No, sorry, it does not work. Neither does '~t'. ??? > Hi, >Hmm, strange. I just tried it here, and it works fine for me. Not sure > why it doesn't work for you. Just to be clear, what exactly is happening? > Is the From: always being set to From: Hal Burgiss <[EMAIL PROTECTED]>, > or is something else happening? Yes, Hal Burgiss <[EMAIL PROTECTED]> is it. Despite many variations. Unless I am going crazy, this was working fine not too long ago. I suspect something else upgraded is messing with things. But I can't think what that would be. Thanks. -- Hal B [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] --
Re: Send hook question
On Wed, Oct 04, 2000 at 06:25:47PM -0600, Harold Oga wrote: > On Wed, Oct 04, 2000 at 07:58:13PM -0400, Hal Burgiss wrote: > >Should the below not work? I could swear it used to ;) Recently > >even. Despite much playing with this, I cannot get the header to > >handle the exceptions. > > > >unset use_from > >send-hook . 'my_hdr From: Hal Burgiss <[EMAIL PROTECTED]>' > >send-hook redhat-list 'my_hdr From: Hal Burgiss <[EMAIL PROTECTED]>' > Hi, >I think send-hook is expecting a pattern where you have redhat-list. > Does the following work better for you? > > send-hook . 'my_hdr From: Hal Burgiss <[EMAIL PROTECTED]>' > send-hook '~C redhat-list' 'my_hdr From: Hal Burgiss <[EMAIL PROTECTED]>' No, sorry, it does not work. Neither does '~t'. ??? -- Hal B [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] --
Send hook question
Should the below not work? I could swear it used to ;) Recently even. Despite much playing with this, I cannot get the header to handle the exceptions. unset use_from send-hook . 'my_hdr From: Hal Burgiss <[EMAIL PROTECTED]>' send-hook redhat-list 'my_hdr From: Hal Burgiss <[EMAIL PROTECTED]>' Mutt 1.2i (2000-05-09) Copyright (C) 1996-2000 Michael R. Elkins and others. System: Linux 2.2.16pre3 [using slang 10202] Updated RH6.2 from src.rpm. TIA -- Hal B [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] --
Error: Warning changing readonly file
I just rebuilt linux kernel (2.2.12), and all of a sudden I get this error anytime I try to look at any mail -- new or stored. Ctrl-C seems to be the only to get past this message. After that all seems well. I am using vim as pager (vim -R). I used the identical config on the kernel build as previous. Mutt is mutt-1.0pre3i-1 as shipped with Redhat 6.1. The problem is that there is an "me>" being inserted at the cursor position. I find that this is caused by my pager statement in .muttrc: set pager="vim -R -c 'normal! 1L'" The line is getting truncated at the , leaving just the 'me>'. This was not a problem previously. Any linux users have any idea what in a kernel rebuild might cause this? TIA -- Hal B [EMAIL PROTECTED] -- Linux helps those who help themselves
Re: wmaker and mutt
On Sun, Sep 12, 1999 at 08:08:40PM +0200, finnegan wrote: > Hi, > this mutt is pretty enigmatic, at least for such a beginner like me; > I run windowmaker and would like to put an appicon on my desktop; > perhaps there is here somebody who prefers this combination of a mailer > and window manager and could help me a bit; any practical suggestions? > Thanx > There are probably any number of ways to do this. My solution is that I use wmmail as one of my dockapps. One feature of wmmail is that it watches your mailbox and will notify you of new mail. When I doubleclick on wmmail it fires up mutt. I also use mutt with Eterm (rxvt variation). Eterm has a mutt 'theme' which incorporates menus. All this looks pretty good and very functional -- at least from my standpoint. -- Hal B [EMAIL PROTECTED] -- Linux helps those who help themselves
Re: message width in vim?
On Sun, Aug 29, 1999 at 03:59:15PM -0230, Chris Gushue wrote: > I *know* I saw how to do this recently on a mailing list but I couldn't > find it. I need to know how to set the message width when using vim as > my editor. I didn't see anything helpful in the vim docs for this, but > I might have missed something. > Many ways to do this probably. One easy way is start vim: set editor="vim +'set tw=xx'" in .muttrc. -- Hal B [EMAIL PROTECTED] -- Linux helps those who help themselves
Re: Sending mail ?? HA
On Mon, Jul 26, 1999 at 11:02:41PM +0200, Niels Rasmussen wrote: > > Hi all > > As a newbie I must say that I am getting exstremely frustrated at the moment !! > > Mutt is a wonderfull mailclient with all the features that I always wanted! > > But why in the H... cant I send mail with it ?? > > In the last 12 hours I have tried to make it work, is it at all possible ?? > > sendmail: > DSsmtp.ISP.dk > And ?? > > muttrc: > set sendmail="/usr/lib/sendmail -oi -oem" > And ?? > On linux, this is typically '/usr/sbin/sendmail ' Typo ??? > Any suggestions will be greeted with a abnormally high optimism !! > > Thanks in advance :-( > -- Hal B [EMAIL PROTECTED] -- Linux helps those who help themselves
Re: Email client poll
On Fri, Jul 16, 1999 at 12:37:13PM +0200, Alexander Langer wrote: > Thus spake Mark Mielke ([EMAIL PROTECTED]): > > > Also many of them wouldn't know how to use a non "impressing" view of > > their mailbox. It's so much cooler to have messages fade and titles > > Standard-Mutt is b/w for me without my config files. > Maybe in a further version themes could be added. That would make it a > mutt-newbie easy to make it well-looking and have nice key-bindings. > Maybe also a folder-configure-program, that lets you add folders by a > GUI. > You can use a *term to do this. Eterm, for one, supports themes and works with Mutt. As a matter fact, one of themes in the package is one for mutt, but pretty easy to create your own. -- Hal B [EMAIL PROTECTED] -- Linux helps those who help themselves
Re: Email client poll
On Thu, Jul 15, 1999 at 12:26:02AM +0200, J Horacio MG wrote: > Jeremy Blosser dixit: > > > Uh, we do, and even crashed netscape when I tried a second time (just to > check if I had done it right the first time, of course). > > Notice though, that netscape was by far the widiest voted mailreader. > That's surely due to mutt being command line based. > When ignorance is bliss ... -- Hal B [EMAIL PROTECTED] -- Linux helps those who help themselves
Re: HTML Mail -> no temp file
On Wed, Jul 07, 1999 at 10:12:01AM +1100, Brian Salter-Duke wrote: > On Tue, Jul 06, 1999 at 08:10:36PM -0400, Hal Burgiss wrote: > > Trying to view html mail and I get a NS message to the effect of: > > > > No Such File: /tmp/mutt > > > > Correct there is no such file -- anywhere. I have tmpdir set to /tmp in > > .muttrc. I don't see that mutt is creating any temp files in this > > situation? > > I have experienced a similar situation and was waiting to find time > for more extensive tests before asking mutt-users. On some tries > I get the "No such file" error. On others I get part of the document > appearing. I think mutt fires of the document from the tmp directory > and then moves on, deleting the file. It gets deleted before the > transfer is complete. At least that is my hypothesis at present. I > was going to try putting the call of netscape in a wrapper script > whose name appears in the mailcap file, but I am busy with other > stuff. > You would seem to be correct. I just tried 'watch ls' in /tmp and there is a temp file created very briefly -- and then it's gone. -- Hal B [EMAIL PROTECTED] -- Linux helps those who help themselves
HTML Mail -> no temp file
Trying to view html mail and I get a NS message to the effect of: No Such File: /tmp/mutt Correct there is no such file -- anywhere. I have tmpdir set to /tmp in .muttrc. I don't see that mutt is creating any temp files in this situation? I've changed mailcap to '-remote openFile(%s)', since openURL() seemed to always want a http:// URL. This works fine as long as it points to a valid file. Using with RH6.0: Mutt 0.95.4us (1999-03-03) Copyright (C) 1996-8 Michael R. Elkins and others. System: Linux 2.2.5-22 [using slang 9938] Compile options: -DOMAIN -HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_IMAP +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/spool/mail" SHAREDIR="/etc" SYSCONFDIR="/etc" ISPELL="/usr/bin/ispell" TIA -- Hal B [EMAIL PROTECTED] -- Linux helps those who help themselves
Re: Return Address problem
On Fri, Apr 23, 1999 at 06:42:47PM +0200, Claus Assmann wrote: > > Maybe this discussion should be done in a sendmail related list/group? My original query was whether this situation is addressable with Mutt ... > > Well I am starting sendmail as : sendmail -bd -f [EMAIL PROTECTED] I > > thought this might help, but doesn't seem to. > > The daemon ignores the -f option for obvious reasons: you don't > want all mail going through it to be from that address... Perhaps obvious to some. I would at least like it to appear as if outbound mail is coming from that address. But now that I think about it, I see the problem with it. Thanks for replying ... -- Hal B [EMAIL PROTECTED]
Re: Return Address problem
On Fri, Apr 23, 1999 at 10:23:06AM -0400, David Shaw wrote: > > Hhere is no such domain as "hals.box" and some (but, as you found out, not > all) systems won't talk to you because of it. This is generally done as a > spam protection technique (all those mails coming from "[EMAIL PROTECTED]" and > such nonsense). > > Some sites bounce it immediately, like the example above, and some give a > temporary error which causes your system (or relay) to try again later. > The temporary error makes more sense to me, as if the receiving site's DNS > is either down or having problems it can come up with false positives, so > retrying later prevents valid mail from being bounced. On the other hand, > if a name is completely bogus, it'll sit in the queue for potentially days > before the user who sent it knows what happened. > > Either way, what you need to do is arrange for your envelope sender to be > something valid. Probably the most elegant way to do this is to use > sendmail's genericstable feature to rewrite '[EMAIL PROTECTED]' to > '[EMAIL PROTECTED]'. A less elegant, but simpler, way would be to change your > $sendmail variable to something like: > > set sendmail="/usr/sbin/sendmail -oem -oi [EMAIL PROTECTED]" > Well I am starting sendmail as : sendmail -bd -f [EMAIL PROTECTED] I thought this might help, but doesn't seem to. > That should work in most setups, but it might (again, depending on your > configuration) add a header to your mail saying: > > X-Authentication-Warning: hals.box: hal set sender to hdb using -f > > If that bothers you, either add yourself to the "trusted user" section of > /etc/sendmail.cf or just use genericstable. :) > > David > I've got several good suggestions now. I apprecitate your time and help. Thanks again David! -- Hal B [EMAIL PROTECTED]
Re: Return Address problem
On Fri, Apr 23, 1999 at 11:23:06AM +0200, Wouter Hanegraaff wrote: > This is not a mutt problem but a sendmail problem. > You can fix this using the genericstable. I wrote a sort of mini howto on offline >mailing that fixes this problem, and posted the address a while ago. > You may have missed it, so here it is again... > > http://www.cysonet.com/~wouter/offline_mailing.html > > This _fixes_ the problem while hacking your muttrc might at best result in > a (bad) workaround. > > Wouter... > -- > Ieder voordeel heeft ook een nadeel. > -Johan Cruijff, Europees voetballer van de eeuw I was suspecting sendmail. Was hoping to solve it with Mutt though, since mutt config is snap compared to what I know about sendmail. Thanks for takiing time to help! and I will check out http://www.cysonet.com/~wouter/offline_mailing.html. -- Hal B [EMAIL PROTECTED]
Re: Return Address problem
On Fri, Apr 23, 1999 at 07:37:33AM +0300, Liviu Daia wrote: > > Yes. Assuming "lou-ts3-23.iglou.com" is (one of) the address(es) > you get when you dial your ISP, change the domain definition in your > sendmail.cf (the "Dj" thing) to look like > > Djlou-ts3-23.iglou.com Thanks Liviu for the detailed, informative response!!! Sounds like what I needed to know. I had tried '[EMAIL PROTECTED]`, but it bombed. > > my_hdr From: Hal Burgiss <[EMAIL PROTECTED]> > > to your .muttrc . It doesn't have to be your real address at the time > you dial in, a fixed "lou-ts3-23" should be ok. The remote peer will be > happy if it can resolve it, and find that it points inside your ISP's > domain. > > Alternatively, if your ISP allows relaying messages from dialup > users (normally they should), get the address of the main mail hub and > relay your outgoing messages there. Assuming "mail.iglou.com" is the > address of the relay host, you can do that with the "DS" entry in your > sendmail.cf: > > DSmail.iglou.com I believe it is indeed 'mail.iglou.com'. > > On a related topic: > > (1) Don't mess with "Reply-To:" if you don't need to (that is if it > points to the same as "From:"); My ISP has been using the Reply-to field to resolve return address problems. At least on my own tests where I am emailing myself. > > (2) You seem to be using a very old version of sendmail, which is known > to have a lot of security-sensitive bugs; not a big problem if > you're online only a few minutes a day, but watch your steps if you > do things like IRC; :-) > > (3) You might want to forget about sendmail altogether, and take a look > at postfix: > > http://www.postfix.org/ > > It's much easier to configure than sendmail, and at least 10x > faster. > I've been struggling with sendmail since it seems to be the 'standard' by which others are measured. I hate to quit on something till I get it solved. Once it get this straightened out, I will try postfix as you suggest. Thanks again for being such a big help ! -- Hal B [EMAIL PROTECTED]
Re: Return Address problem
On Thu, Apr 22, 1999 at 09:52:08PM -0500, Ray or Donna Menke wrote: > I've been chasing this problem for weeks, and will be watching the list > for a solution. I have been sending the message (to queue) using Mutt, > then chasing it to /var/spool/mqueue, and using an editor to remove > the name of my computer. Then my header looks like this: > HReceived: (from root@localhost) > by lockhart.net (8.8.7/8.8.7) id . > (The words just prior to lockhart.net were [EMAIL PROTECTED]) > or [EMAIL PROTECTED] (won't work at all!) > > Seems to be affected by line 112 in my /etc/sendmail.cf (in my RH5.2) Intel > version: Dj$w. I'm a new user, too, and really like to use Mutt, so > I hope to find a solution. Thanks for posting, and I'll be watching for > a fix. If you fix this by some other method, other than the Mutt list, > would you please tell me too. Ray Menke Assuming this gets to you ... actually almost all my mail is getting through. I have only had a couple bounced back. I'm sure there is a simple answer, I just haven't found it. sendmail.cf is an enigma wrapped in a riddle to me so far. I've toyed with editing by hand, but not sure what all the symbols are, and don't really have time to learn sendmail at this point just to solve this problem. Likewise, if you solve your problem, please post back -- Hal B [EMAIL PROTECTED]
Re: Return Address problem
On Thu, Apr 22, 1999 at 07:08:51PM -0500, Ronny Haryanto wrote: > On 22-Apr-1999 07:40PM, Hal Burgiss wrote: > > Using mutt .95 with sendmail on a standalone home box. My mail headers are > > apparently showing 'sender' as $user@$HOSTNAME. Some mail servers ignore this, > > but others complain -- 'BadReturnPath' or '(mail may be forged)' -- and some are > > bouncing mail back to me undelivered. > > This is more-less what I use in my .muttrc: > > unset use_from > send-hook . 'my_hdr From: Yours Truly <[EMAIL PROTECTED]>' > send-hook '^honey@girlfriend\.com$' 'my_hdr From: Honey Bunny <[EMAIL PROTECTED]>' Well, I tried that now, and it doesn't seem to solve my problem. Perhaps I am botching it somehow. I've included header of one that was kicked back below. Sorry if this is excessively long. My username is 'hal', the hostname here is 'hals.box'. My email address is '[EMAIL PROTECTED]' (of course). I get a 'BadReturnPath' in the header if I try emailing myself as a test. The 'From' field seems correct to me. : From hal Thu Apr 22 12:08:56 1999 : Return-Path: : Received: from localhost (localhost) : by hals.box (8.8.7/8.8.7) with internal id MAA08477; : Thu, 22 Apr 1999 12:08:56 -0400 : From: Mail Delivery Subsystem <[EMAIL PROTECTED]> : Message-Id: <[EMAIL PROTECTED]> : To: [EMAIL PROTECTED] : Content-Type: multipart/report; report-type=delivery-status; : boundary="MAA08477.924797336/hals.box" : Subject: Returned mail: Data format error : Auto-Submitted: auto-generated (failure) : Status: RO : Content-Length: 2676 : Lines: 82 : : This is a MIME-encapsulated message : : --MAA08477.924797336/hals.box : : The original message was received at Thu, 22 Apr 1999 12:08:47 -0400 : from hal@localhost : :- The following addresses had permanent fatal errors - : [EMAIL PROTECTED] : :- Transcript of session follows - : ... while talking to jonesy.conman.ugg.edu.: : >>> MAIL From:<[EMAIL PROTECTED]> SIZE=1620 : <<< 501 <[EMAIL PROTECTED]>... Sender domain must exist : 501 [EMAIL PROTECTED] Data format error : : --MAA08477.924797336/hals.box : Content-Type: message/delivery-status : : Reporting-MTA: dns; hals.box : Arrival-Date: Thu, 22 Apr 1999 12:08:47 -0400 : : Final-Recipient: RFC822; [EMAIL PROTECTED] : Action: failed : Status: 5.5.2 : Remote-MTA: DNS; jonesy.conman.ugg.edu : : : /* This is where the problem is !!!*/ : : Diagnostic-Code: SMTP; 501 <[EMAIL PROTECTED]>... Sender domain must exist : ^ : : : --MAA08477.924797336/hals.box : Content-Type: message/rfc822 : : Return-Path: : Received: (from hal@localhost) : by hals.box (8.8.7/8.8.7) id MAA08475; : Thu, 22 Apr 1999 12:08:47 -0400 : : : Date: Thu, 22 Apr 1999 12:08:46 -0400 : From: Hal Burgiss <[EMAIL PROTECTED]> : To: Barry Hooty <[EMAIL PROTECTED]> : Cc: [EMAIL PROTECTED] : Subject: Re: [wm-user] WM 0.53 : Message-ID: <[EMAIL PROTECTED]> : Reply-To: [EMAIL PROTECTED] : References: <19990422063335.A11132@mordo> <[EMAIL PROTECTED]> : Content-Type: text/plain; charset=us-ascii : X-Mailer: Mutt 0.95.4us : In-Reply-To: <[EMAIL PROTECTED]>; from Barry Hooty on Thu, Apr :22, 1999 at 09:36:13AM -0400 : TIA -- Hal B [EMAIL PROTECTED]
Return Address problem
New user, stupid question probably ... Using mutt .95 with sendmail on a standalone home box. My mail headers are apparently showing 'sender' as $user@$HOSTNAME. Some mail servers ignore this, but others complain -- 'BadReturnPath' or '(mail may be forged)' -- and some are bouncing mail back to me undelivered. I've scoured the docs and tried various things in .muttrc, but nothing seems to change this behavior. I suspect this is perhaps something in sendmail configuration, but it seems sendmail is not something that one can learn only a little something about . Anyone have an 'easy' answer? TIA -- Hal B [EMAIL PROTECTED]
