Re: Line wrapping with mutt/emacs (was Re: Problems: mutt to Outlook (Express))
* Richard Cobbe ([EMAIL PROTECTED]) [020516 18:05]: > Lo, on Thursday, May 16, Cam Ellison did write: > > set editor="emacs '+/^$' \"set textwidth=70\"" > I'm not entirely sure what the '+/^$' means---is this perhaps a Mutt > thing? No, it's a vim thing. > The `set textwidth=70' is almost certainly incorrect. In Emacs, the Again, a vim thing. I'm guessing OP saw a muttrc saying "here's how to make vim wrap your text at 70 columns and start you at the first blank line (the line after the headers)." Then OP said "I like emacs, not vim" and so changed vim to emacs in the muttrc, but left the rest of the vim commandline intact. good times, Vineet -- Currently seeking opportunities in the SF Bay Area Please see http://www.doorstop.net/resume.shtml pgpj83gXxaym5.pgp Description: PGP signature
Re: Problems: mutt to Outlook (Express)
On Thu, May 16, 2002 at 10:32:05AM -0400, Hall Stevenson wrote: > Many times, people using mutt, for example, do PGP signatures > which will often cause their messages to show up to OE users > as a blank e-mail (1) with two attachments. One attachment is > a text file containing their message. The other is a .dat file > (???). This isn't the case with your message either. > > (1) I'm not interested in how OE is "broken" or who/what is > doing what wrong or against some RFC... ;-) LOL, yesterday and the day before I had some troubles with this. I started to sign my mail... and indeed I got a bunch of comments on the mailinglist of my year. The people who complained where outlook express and opera users. Some people never listen! You can say it hundred times there mailclient sucks, but the keep on winning their client is the best. In the end I gave up... I did have a laught when someone claimend XP is at least even stable as any Linux distribution. Wahaha :) Cheers, -- Rudy Gevaert - [EMAIL PROTECTED] - http://www.zeus.rug.ac.be keyserverID=24DC49C6 - http://www.webworm.org I'm a GNU/Linux advocate. Every action against my beliefs is useless University politics are vicious precisely because the stakes are so small. - Henry Kissinger (1923-) pgpvTxhJlkYfo.pgp Description: PGP signature
Re: Problems: mutt to Outlook (Express)
Hi Cam, Ok, set up a POP server on your own box, and create accounts for these people. Get them to log into your POP server with emails that you've sent there from mutt. Hopefully they'll be rejected and then you can see from the logs which you'll now have access to what the error responces are. Matthew On Thu, May 16, 2002 at 12:59:34PM -0700, Cam Ellison wrote: > * Matthew Sackman ([EMAIL PROTECTED]) wrote: > > On Thu, May 16, 2002 at 09:55:33AM -0700, Cam Ellison wrote: > > > * Grant Edwards ([EMAIL PROTECTED]) wrote: > > > > In muc.lists.debian.user, you wrote: > > > > > > > Hmm. Do the emails even arrive? How are they getting them: is it > > download from POP or IMAP server (in which case see if the email is even > > being downloaded) or is it from an Exchange server? (in which case see > > if you can track the logs). > > > To the best of my knowledge, they do not. It is difficult for me to actually > get into each of the machines in question and play around, since they are > some distance away (anywhere from 40 km across a large body of water to 600 > km over the mountains). The headers do not appear in the respective Inbox > displays, and I must assume that they are either rejected (given a 554 code, > perhaps) or sent to /dev/null after retrieval. > > > Seeing as you mention Eudora is fine, I take it this implies download > > from POP/IMAP as Eudora doesn't know Exchange. This I therefore find > > really odd: the emails must be arriving, so why doesn't O/OE show them? > > Could you see if you can find out whether they're even downloaded? > > > See above -- I am not sure they are arriving. As an earlier post of mine > states, the problem does not occur with build 10 of Outlook or with OE 6. > Sounds very much like a bug (such a surprise!) in Outlook. Curious, though, > that it doesn't happen with the Mac version of OE (comes with Mac Office 98). > > Cam > > -- > Cam Ellison Ph.D. R.Psych. > >From Roberts Creek on B.C.'s incomparable Sunshine Coast > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- Matthew Sackman Nottingham England BOFH Excuse Board: Root name servers corrupted. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17 May 2002, Grant Edwards wrote: > You're describing a different bug in OE. There are so many > from which to choose... And as demonstrated here, they all have similar effects with many different causes... - -- Baloo -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE85b21NtWkM9Ny9xURAqYZAKCW8EnwudCMrjQjP1BsmSgbzA12UQCfcrFX A45Zh4CT75sa/K4L0wJmK1U= =ptmy -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
On Thu, May 16, 2002 at 11:43:21PM -0700, Paul 'Baloo' Johnson wrote: [snip] | The bug you describe is caused when it recieves a message that | starts with "begin " and isn't starting a uuencoded file. OE users | will attest to this as this particular post will trigger that bug. Oh, yeah, that bug. I read about it recently. It's a great bug. Rather than following the spec regarding uuencode data MS assumes that any text beginning with 'begin' is uuencode. Take a look at their recommended workaround. They first claim that the problem is in the standards (not in their non-conformance) and then tell everybody not to use the word 'begin' in an email! | > The Usenet group comp.mail.mutt is probably the definitive | > place to ask for help, since I doubt there's anything | > Debian-specific going on. | | I've been thinking about moving away from pine in favor of either mutt | or elm. Choose mutt over elm. | I use tin, but elm doesn't work *exactly* like I would expect coming | from tin, and mutt is just counterintuitive. How do you find elm (mostly) ok and mutt wholly not ok? Their UI is very similar, except that mutt uses screen real-estate better and has more features. mutt's author, Michael Elkins, is a former part of the elm development group. I used to use elm when I didn't have a GUI available because it was the first UNIX mailer I was introduced to. One of my big complaints with it was that it didn't understand new mail in a non-inbox folder. That didn't mesh well with my sorting of list mail. Someone recommended mutt to me, and I found I could jump right in and use it naturally (because the keybindings are nearly the same). mutt has no problem with new messages being in any folder (not just the INBOX). | I wish pine would go free so people actually have an incentive to | hack the code a bit and make it more featureful; my estimation is | UWash's semi-braindead license is what's keeping more people from | hacking on it. Could be. I'll provide an FYI here instead of in the message it's more related to. The way you/pine is signing your messages is the "old" style called 'clearsign'. The problem with it is that the client must parse the message body to find the PGP stuff to verify the signature. The mutt-gpg howto has some macros and scripts to automate it, but I haven't set that up yet. Mutt uses the newer style which is to transfer the body and the signature as separate MIME parts with proper Content-Types. I think mutt has a switch to use the old style too. MS Outhouse "works" with the clearsign format and misbehaves with the PGP/MIME format. (it doesn't verify the sig in either case) This is just FYI since your pine plugin is behaving according to the (superceded) RFC. -D -- I can do all things through Christ who strengthens me. Philippians 4:13 GnuPG key : http://dman.ddts.net/~dman/public_key.gpg pgpSUy25u0o0G.pgp Description: PGP signature
Re: Problems: mutt to Outlook (Express)
Paul 'Baloo' Johnson <[EMAIL PROTECTED]> wrote: >> The symptoms of the gpg thing are that the Outlook user gets >> the e-mail, but instead of treating it as a signed message, it >> treats it as an empty message with an attachment (or something >> like that). > > I think you're getting your bugs mixed up. No, I'm not. Here is the entry from the mutt FAQ: > Some user complained that my PGP messages are attachments! > > That user is using obsolete and broken software. PGP/MIME is > the only way to use PGP with email that is actually specified > (RFC 2015) and not some proprietary ad-hoc crap. Tell that > other user to get rid of his legacy crap mail software and > install standards compliant software. RFC 2015 is from 1996, > by the way, so no mail software author can say he didn't have > enough time to implement this. The "legacy crap mail software" to which the FAQ refers includes programs such as Outlook Express. This has been discussed ad-nauseum in comp.mail.mutt. Here is one of many threads: http://groups.google.com/groups?hl=en&lr=&th=f4bc5007a180da94 > The bug you describe is caused when it recieves a message that > starts with "begin " and isn't starting a uuencoded file. Wrong. The bug I'm describing is triggered by messages signed w/ PGP or GPG according to the RFC. Outlook treats them as attachments. > OE users will attest to this as this particular post will > trigger that bug. You're describing a different bug in OE. There are so many from which to choose... -- Grant Edwards grante Yow! Is something VIOLENT at going to happen to a visi.comGARBAGE CAN? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Line wrapping with mutt/emacs (was Re: Problems: mutt to Outlook (Express))
> On Thu, 16 May 2002, "cam" == Cam Ellison wrote: cam> set editor="emacs '+/^$' \"set textwidth=70\"" Nope. On my system this tells emacs to edit a file named (something like) "textwidth=70". Look at your list of buffers when you use this command string. cam> What should I do differently? There's always more than one way to skin any unix cat; here's mine, based on the fact that the default fill-column in emacs is 70. Force emacs into text mode, and tell it to always use automatic fill in any text mode. Do all this neat stuff by putting these lines in your ~/.emacs: (setq default-major-mode 'text-mode) (add-hook 'text-mode-hook '(lambda () (auto-fill-mode 1))) Now, in .muttrc just say: editor="emacs" Works here -- Bob Bernstein at http://www.ruptured-duck.com Esmond, Rhode Island USA cam> Cam cam> -- Cam Ellison Ph.D. R.Psych. From Roberts Creek on B.C.'s incomparable cam> Sunshine Coast [EMAIL PROTECTED] [EMAIL PROTECTED] cam> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a cam> subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
I have had my suspicions about the existence of some such thing, but being no expert on M$ (I was an OS/2 user before Linux), I have not been sure where to look. I shall go looking for it (my kids' machine will run Win98 for up to an hour before it GPFs). :-) Thank you, sir Cam * Paul 'Baloo' Johnson ([EMAIL PROTECTED]) wrote: > Hash: SHA1 > > On Thu, 16 May 2002, Cam Ellison wrote: > > > To the best of my knowledge, they do not. It is difficult for me to > > actually get into each of the machines in question and play around, > > since they are some distance away (anywhere from 40 km across a large > > body of water to 600 km over the mountains). The headers do not > > appear in the respective Inbox displays, and I must assume that they > > are either rejected (given a 554 code, perhaps) or sent to /dev/null > > after retrieval. > > Back from my tech support days, I vaguely remember an option in OE that > allows OE to silently drop "potentially harmful" attachments and is on > by default...curious what happens if the recipient shuts this feature > off? This shouldn't make a difference in the security of the box, as > they're running an up to date virus package (right?). > > - -- > Baloo > > > Version: GnuPG v1.0.7 (GNU/Linux) > > iD8DBQE85KiuNtWkM9Ny9xURAmleAKCUbUNPIEqpHVyNQEYVbhFofWXDoQCfUQHI > 1bxCI9cCToCv5p3oOsHa9pg= > =ypyb > > -- Cam Ellison Ph.D. R.Psych. From Roberts Creek on B.C.'s incomparable Sunshine Coast [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Line wrapping with mutt/emacs (was Re: Problems: mutt to Outlook (Express))
On Thu, May 16, 2002 at 07:10:30PM -0700, Cam Ellison wrote: > Thank you, Richard. I don't know about the '+/^$' bit either - I > cribbed my .muttrc from someone else, and dutifully copied that bit. Looks like both that and the textwidth setting came from a vim user. '+/^$' will tell vim to go to the first line matching the regular expression /^$/ (i.e. the first blank line) on starting up. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 16 May 2002, Cam Ellison wrote: > To the best of my knowledge, they do not. It is difficult for me to > actually get into each of the machines in question and play around, > since they are some distance away (anywhere from 40 km across a large > body of water to 600 km over the mountains). The headers do not > appear in the respective Inbox displays, and I must assume that they > are either rejected (given a 554 code, perhaps) or sent to /dev/null > after retrieval. Back from my tech support days, I vaguely remember an option in OE that allows OE to silently drop "potentially harmful" attachments and is on by default...curious what happens if the recipient shuts this feature off? This shouldn't make a difference in the security of the box, as they're running an up to date virus package (right?). - -- Baloo -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE85KiuNtWkM9Ny9xURAmleAKCUbUNPIEqpHVyNQEYVbhFofWXDoQCfUQHI 1bxCI9cCToCv5p3oOsHa9pg= =ypyb -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 begin On 16 May 2002, Grant Edwards wrote: > The symptoms of the gpg thing are that the Outlook user gets > the e-mail, but instead of treating it as a signed message, it > treats it as an empty message with an attachment (or something > like that). I think you're getting your bugs mixed up. The bug you describe is caused when it recieves a message that starts with "begin " and isn't starting a uuencoded file. OE users will attest to this as this particular post will trigger that bug. > The Usenet group comp.mail.mutt is probably the definitive > place to ask for help, since I doubt there's anything > Debian-specific going on. I've been thinking about moving away from pine in favor of either mutt or elm. I use tin, but elm doesn't work *exactly* like I would expect coming from tin, and mutt is just counterintuitive. I wish pine would go free so people actually have an incentive to hack the code a bit and make it more featureful; my estimation is UWash's semi-braindead license is what's keeping more people from hacking on it. - -- Baloo -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE85KaMNtWkM9Ny9xURArQMAKCrrLVvx2W91oHahrDr4bv/i9M+aQCePxpI l8/384tfxi505D7V1fkUZIE= =xeOa -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Line wrapping with mutt/emacs (was Re: Problems: mutt to Outlook (Express))
Similar advice from two of you -- Alan and yourself. I have tried your route, and I see that is is finally wrapping as I write. This is a great relief. Thank you, all, very much. Now, I just need to straighten out my problems with a couple of service providers. Thanks again Cam * Bob Bernstein ([EMAIL PROTECTED]) wrote: > > > On Thu, 16 May 2002, "cam" == Cam Ellison wrote: > > cam> set editor="emacs '+/^$' \"set textwidth=70\"" > > Nope. On my system this tells emacs to edit a file named (something like) > "textwidth=70". Look at your list of buffers when you use this command string. > > cam> What should I do differently? > > There's always more than one way to skin any unix cat; here's mine, based on > the fact that the default fill-column in emacs is 70. Force emacs into text > mode, and tell it to always use automatic fill in any text mode. Do all this > neat stuff by putting these lines in your ~/.emacs: > > (setq default-major-mode 'text-mode) > (add-hook 'text-mode-hook > '(lambda () (auto-fill-mode 1))) > > Now, in .muttrc just say: > > editor="emacs" > > Works here > > -- Cam Ellison Ph.D. R.Psych. From Roberts Creek on B.C.'s incomparable Sunshine Coast [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Line wrapping with mutt/emacs (was Re: Problems: mutt to Outlook (Express))
> On Thu, 16 May 2002, "cam" == Cam Ellison wrote: cam> set editor="emacs '+/^$' \"set textwidth=70\"" Nope. On my system this tells emacs to edit a file named (something like) "textwidth=70". Look at your list of buffers when you use this command string. cam> What should I do differently? There's always more than one way to skin any unix cat; here's mine, based on the fact that the default fill-column in emacs is 70. Force emacs into text mode, and tell it to always use automatic fill in any text mode. Do all this neat stuff by putting these lines in your ~/.emacs: (setq default-major-mode 'text-mode) (add-hook 'text-mode-hook '(lambda () (auto-fill-mode 1))) Now, in .muttrc just say: editor="emacs" Works here -- Bob Bernstein at http://www.ruptured-duck.com Esmond, Rhode Island USA cam> Cam cam> -- Cam Ellison Ph.D. R.Psych. From Roberts Creek on B.C.'s incomparable cam> Sunshine Coast [EMAIL PROTECTED] [EMAIL PROTECTED] cam> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a cam> subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Line wrapping with mutt/emacs (was Re: Problems: mutt to Outlook (Express))
On 0, Cam Ellison <[EMAIL PROTECTED]> wrote: > I hate replying to my own posts, but I see that it did not work. But then, I > forgot to restart mutt, which wasn't very clever. Sorry to take the > bandwidth, but I need to test this so I can quit annoying everyone. Evidently not. Since you seem to be using emacs, this is what Worked For Me (TM): apt-get install post-el editor="emacs -nw -f post-mode" -nw means no X even if its available, and -f post-mode means execute the function post-mode when starting up, which mode automagically includes auto-fill-mode. Tom -- Tom Cook Information Technology Services, The University of Adelaide Classifications of inanimate objects: Those that don't work, those that break down, and those that get lost. Get my GPG public key: https://pinky.its.adelaide.edu.au/~tkcook/tom.cook-at-adelaide.edu.au pgpuDdd9olWeN.pgp Description: PGP signature
Re: Line wrapping with mutt/emacs (was Re: Problems: mutt to Outlook (Express))
Cam Ellison <[EMAIL PROTECTED]> writes: > set editor="emacs '+/^$' \"set textwidth=70\"" Put this in your .emacs: (setq default-major-mode 'text-mode) (add-hook 'text-mode-hook 'turn-on-auto-fill) -- Alan Shutko <[EMAIL PROTECTED]> - In a variety of flavors! Tact is the art of making a point without making an enemy. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Line wrapping with mutt/emacs (was Re: Problems: mutt to Outlook (Express))
I hate replying to my own posts, but I see that it did not work. But then, I forgot to restart mutt, which wasn't very clever. Sorry to take the bandwidth, but I need to test this so I can quit annoying everyone. * Cam Ellison ([EMAIL PROTECTED]) wrote: > Thank you, Richard. I don't know about the '+/^$' bit either - I cribbed my > .muttrc from someone else, and dutifully copied that bit. > > So I have followed your advice, andmade the changes. I had not set up > xemacs, and of course it has done its own thing, so we shall see the results > now. I am deliberately running my lines long to see if it works. > > Cam > > > * Richard Cobbe ([EMAIL PROTECTED]) wrote: > > Lo, on Thursday, May 16, Cam Ellison did write: > > > > > * Gary Hennigan ([EMAIL PROTECTED]) wrote: > > > > > > > > > > > And, *please*, for the love of God and country, can you wrap your > > > > lines at 70 characters or so?! > > > > > > > > > > I would love to, but every attempt seems to go nowhere. Not everyone > > > complains, but I see the litle red markers coming back indicating that > > > mutt is wrapping them for me. > > > > > > So, here's another problem. I have this in .muttrc: > > > > > > set editor="emacs '+/^$' \"set textwidth=70\"" > > > > > > > > > (Let's not have a flamewar about emacs vs vi, please.) The > > > information I have to date is that this should work. It obviously > > > doesn't. > > > > > > What should I do differently? > > > > I'm not entirely sure what the '+/^$' means---is this perhaps a Mutt > > thing? > > > > The `set textwidth=70' is almost certainly incorrect. In Emacs, the > > relevant variable is fill-column, which is 70 by default. However, this > > only applies if you manually fill each paragraph (M-q) or turn on > > auto-fill-mode. To do the latter, add the following to your ~/.emacs > > file: > > > > (add-hook 'FOO-mode-hook 'turn-on-auto-fill) > > > > where FOO is the major mode in which you edit your mail messages. And, > > if you're using XEmacs, > > > > (require 'filladapt) > > (add-hook 'FOO-mode-hook 'turn-on-filladapt-mode) > > > > So, for instance, I've got > > > > (require 'filladapt) > > (add-hook 'mail-mode-hook 'turn-on-auto-fill) > > (add-hook 'mail-mode-hook 'turn-on-filladapt-mode) > > > > You shouldn't need to do this, but while we're at it, to change a > > variable's contents, use something like the following: > > > > (setq fill-column 72) > > > > HTH, > > > > Richard > > > > > > -- > > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > -- > Cam Ellison Ph.D. R.Psych. > From Roberts Creek on B.C.'s incomparable Sunshine Coast > [EMAIL PROTECTED] > [EMAIL PROTECTED] > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- Cam Ellison Ph.D. R.Psych. From Roberts Creek on B.C.'s incomparable Sunshine Coast [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Line wrapping with mutt/emacs (was Re: Problems: mutt to Outlook (Express))
Thank you, Richard. I don't know about the '+/^$' bit either - I cribbed my .muttrc from someone else, and dutifully copied that bit. So I have followed your advice, andmade the changes. I had not set up xemacs, and of course it has done its own thing, so we shall see the results now. I am deliberately running my lines long to see if it works. Cam * Richard Cobbe ([EMAIL PROTECTED]) wrote: > Lo, on Thursday, May 16, Cam Ellison did write: > > > * Gary Hennigan ([EMAIL PROTECTED]) wrote: > > > > > > > > And, *please*, for the love of God and country, can you wrap your > > > lines at 70 characters or so?! > > > > > > > I would love to, but every attempt seems to go nowhere. Not everyone > > complains, but I see the litle red markers coming back indicating that > > mutt is wrapping them for me. > > > > So, here's another problem. I have this in .muttrc: > > > > set editor="emacs '+/^$' \"set textwidth=70\"" > > > > > > (Let's not have a flamewar about emacs vs vi, please.) The > > information I have to date is that this should work. It obviously > > doesn't. > > > > What should I do differently? > > I'm not entirely sure what the '+/^$' means---is this perhaps a Mutt > thing? > > The `set textwidth=70' is almost certainly incorrect. In Emacs, the > relevant variable is fill-column, which is 70 by default. However, this > only applies if you manually fill each paragraph (M-q) or turn on > auto-fill-mode. To do the latter, add the following to your ~/.emacs > file: > > (add-hook 'FOO-mode-hook 'turn-on-auto-fill) > > where FOO is the major mode in which you edit your mail messages. And, > if you're using XEmacs, > > (require 'filladapt) > (add-hook 'FOO-mode-hook 'turn-on-filladapt-mode) > > So, for instance, I've got > > (require 'filladapt) > (add-hook 'mail-mode-hook 'turn-on-auto-fill) > (add-hook 'mail-mode-hook 'turn-on-filladapt-mode) > > You shouldn't need to do this, but while we're at it, to change a > variable's contents, use something like the following: > > (setq fill-column 72) > > HTH, > > Richard > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- Cam Ellison Ph.D. R.Psych. From Roberts Creek on B.C.'s incomparable Sunshine Coast [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Line wrapping with mutt/emacs (was Re: Problems: mutt to Outlook (Express))
Lo, on Thursday, May 16, Cam Ellison did write: > * Gary Hennigan ([EMAIL PROTECTED]) wrote: > > > > > And, *please*, for the love of God and country, can you wrap your > > lines at 70 characters or so?! > > > > I would love to, but every attempt seems to go nowhere. Not everyone > complains, but I see the litle red markers coming back indicating that > mutt is wrapping them for me. > > So, here's another problem. I have this in .muttrc: > > set editor="emacs '+/^$' \"set textwidth=70\"" > > > (Let's not have a flamewar about emacs vs vi, please.) The > information I have to date is that this should work. It obviously > doesn't. > > What should I do differently? I'm not entirely sure what the '+/^$' means---is this perhaps a Mutt thing? The `set textwidth=70' is almost certainly incorrect. In Emacs, the relevant variable is fill-column, which is 70 by default. However, this only applies if you manually fill each paragraph (M-q) or turn on auto-fill-mode. To do the latter, add the following to your ~/.emacs file: (add-hook 'FOO-mode-hook 'turn-on-auto-fill) where FOO is the major mode in which you edit your mail messages. And, if you're using XEmacs, (require 'filladapt) (add-hook 'FOO-mode-hook 'turn-on-filladapt-mode) So, for instance, I've got (require 'filladapt) (add-hook 'mail-mode-hook 'turn-on-auto-fill) (add-hook 'mail-mode-hook 'turn-on-filladapt-mode) You shouldn't need to do this, but while we're at it, to change a variable's contents, use something like the following: (setq fill-column 72) HTH, Richard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Line wrapping with mutt/emacs (was Re: Problems: mutt to Outlook (Express))
* Gary Hennigan ([EMAIL PROTECTED]) wrote: > > And, *please*, for the love of God and country, can you wrap your > lines at 70 characters or so?! > I would love to, but every attempt seems to go nowhere. Not everyone complains, but I see the litle red markers coming back indicating that mutt is wrapping them for me. So, here's another problem. I have this in .muttrc: set editor="emacs '+/^$' \"set textwidth=70\"" (Let's not have a flamewar about emacs vs vi, please.) The information I have to date is that this should work. It obviously doesn't. What should I do differently? Cam -- Cam Ellison Ph.D. R.Psych. From Roberts Creek on B.C.'s incomparable Sunshine Coast [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
"Cam Ellison" <[EMAIL PROTECTED]> writes: > I guess alittle more information is in order. Some of this is > repeated elsewhere in this thread. I have a cable hookup, and am > using exim (3.35) as my MTA. Messages I send from mutt go to just > about everyone, but there are at least three exceptions, all using > an ISP other than my own. > > Case 1: Correspondent uses Outlook Express 5.00.2615.200 on a > dialup connection to a telco. > Case 2: Correspondent uses the same version on a dialup connection > to an independent ISP. > Case 3: Correspondent uses Outlook 2000 (9.0.2416) and has DSL > (same telco as above). > Case 4: Correspondent uses OE for the Mac (5.02.2022), receives the > mail via a 24/7 link to a mail company. This one always works. > > The mail for the first three never arrives. I do not know whether > it is left on the server, or goes to /dev/null. A number of > possibilities suggest themselves, but the most likely to my mind is > that Outlook thinks it is malformed and assigns a 5xx code, thus > killing it. > > Very strange, and it does nothing to endear me to M$. Personally I don't think the trouble is on your end. You'll more than likely have to bring their ISPs into this to solve the problem. One other thing they can try is to use Netscape mail and see if they can access the mail. And, *please*, for the love of God and country, can you wrap your lines at 70 characters or so?! Gary -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
I guess alittle more information is in order. Some of this is repeated elsewhere in this thread. I have a cable hookup, and am using exim (3.35) as my MTA. Messages I send from mutt go to just about everyone, but there are at least three exceptions, all using an ISP other than my own. Case 1: Correspondent uses Outlook Express 5.00.2615.200 on a dialup connection to a telco. Case 2: Correspondent uses the same version on a dialup connection to an independent ISP. Case 3: Correspondent uses Outlook 2000 (9.0.2416) and has DSL (same telco as above). Case 4: Correspondent uses OE for the Mac (5.02.2022), receives the mail via a 24/7 link to a mail company. This one always works. The mail for the first three never arrives. I do not know whether it is left on the server, or goes to /dev/null. A number of possibilities suggest themselves, but the most likely to my mind is that Outlook thinks it is malformed and assigns a 5xx code, thus killing it. Very strange, and it does nothing to endear me to M$. Cam * Joachim Fahnenmueller ([EMAIL PROTECTED]) wrote: > On Thu, May 16, 2002 at 07:15:48AM -0700, Cam Ellison wrote: > > I use mutt as my MUA, and am happy as a clam with it, with one exception: > > anyone who runs Outlook or Outlook Express on a PC cannot receive mail from > > me. This does not apply to Outlook Express running on a Mac. > > Hi Cam, > > I've never had problems with that, though many of my colleagues use Outlook, > too. Can you be more specific: > Do you communicate via intranet or internet (provider)? > Which MTA do you use (exim)? > What exactly is the problem: mail does not arrive, can't be read, ...? > Any error messages? > > Reagrds, Joachim > > -- > Joachim Fahnenmüller > Lehrer für Mathematik und Physik > > Herder-Gymnasium > Kattowitzer Straße 52 > 51065 Köln > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- Cam Ellison Ph.D. R.Psych. From Roberts Creek on B.C.'s incomparable Sunshine Coast [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
I think that the presence of Exchange has some influence here. It certainly is not in use in the other cases. Well, this does help to narrow the inquiry. A little more digging reveals that the culprit versions of OE and Outlook are apparently R1 (5.00.2615.200, and 9.0.2416, respectively). Quasi-beta software. :-( Cam * Jamin Collins ([EMAIL PROTECTED]) wrote: > Yea, I'm using Outlook, but as a client to an Exchange 5.5 SP4 system. So, > all mail from this account is sent to the Exchange server for processing > (which is where the Internet Mail Service 5.5.2653.19 comes from). > -- Cam Ellison Ph.D. R.Psych. From Roberts Creek on B.C.'s incomparable Sunshine Coast [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
Interestingly, your mailer shows as Internet Mail Service 5.5.2653.19, not Outlook. In the situations that don't work, Outlook is fetching (or failing to fetch) the message from the ISP. One of the ISPs uses Unix, as far as I can tell. I am uncertain about the other. * Jamin Collins ([EMAIL PROTECTED]) wrote: > Received no problem > > > -Original Message- > > From: Cam Ellison [mailto:[EMAIL PROTECTED] > > Sent: Thursday, May 16, 2002 3:53 PM > > To: Jamin Collins > > Cc: Jamin W. Collins > > Subject: Re: Problems: mutt to Outlook (Express) > > -- Cam Ellison Ph.D. R.Psych. From Roberts Creek on B.C.'s incomparable Sunshine Coast [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
On Thu, May 16, 2002 at 07:15:48AM -0700, Cam Ellison wrote: > I use mutt as my MUA, and am happy as a clam with it, with one exception: > anyone who runs Outlook or Outlook Express on a PC cannot receive mail from > me. This does not apply to Outlook Express running on a Mac. Hi Cam, I've never had problems with that, though many of my colleagues use Outlook, too. Can you be more specific: Do you communicate via intranet or internet (provider)? Which MTA do you use (exim)? What exactly is the problem: mail does not arrive, can't be read, ...? Any error messages? Reagrds, Joachim -- Joachim Fahnenmüller Lehrer für Mathematik und Physik Herder-Gymnasium Kattowitzer Straße 52 51065 Köln -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
* Matthew Sackman ([EMAIL PROTECTED]) wrote: > On Thu, May 16, 2002 at 09:55:33AM -0700, Cam Ellison wrote: > > * Grant Edwards ([EMAIL PROTECTED]) wrote: > > > In muc.lists.debian.user, you wrote: > > > > Hmm. Do the emails even arrive? How are they getting them: is it > download from POP or IMAP server (in which case see if the email is even > being downloaded) or is it from an Exchange server? (in which case see > if you can track the logs). > To the best of my knowledge, they do not. It is difficult for me to actually get into each of the machines in question and play around, since they are some distance away (anywhere from 40 km across a large body of water to 600 km over the mountains). The headers do not appear in the respective Inbox displays, and I must assume that they are either rejected (given a 554 code, perhaps) or sent to /dev/null after retrieval. > Seeing as you mention Eudora is fine, I take it this implies download > from POP/IMAP as Eudora doesn't know Exchange. This I therefore find > really odd: the emails must be arriving, so why doesn't O/OE show them? > Could you see if you can find out whether they're even downloaded? > See above -- I am not sure they are arriving. As an earlier post of mine states, the problem does not occur with build 10 of Outlook or with OE 6. Sounds very much like a bug (such a surprise!) in Outlook. Curious, though, that it doesn't happen with the Mac version of OE (comes with Mac Office 98). Cam -- Cam Ellison Ph.D. R.Psych. From Roberts Creek on B.C.'s incomparable Sunshine Coast [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
On Thu, May 16, 2002 at 02:06:15PM -0400, Hall Stevenson wrote: > Find an OE user who can access their e-mail via some sort of > "webmail". Send them a message. Have them check to see if they > get the message via "webmail". If it's not there, this isn't > an OE problem (nor Debian) and possibly not a mutt problem. If > it is there, then have them get their e-mail with OE and see > if it mysteriously has disappeared. Or even better, with some social engineering, find their POP box username and password, telnet into it, and check that the email has arrived. Check that it's retriveable. If Outlook still refuses to believe that the message exists then find the LART...[1] telnet session would as follows: telnet mail.blah.blah 110 > [welcome message] < USER username > [OK] < PASS password > [OK or ERR Bad Pass] < STAT > [number of messages, size in octets of all messages] hopefully there's only 1: yours! < RETR 1 text of your email will be shown a '.' terminates the email < QUIT where > is text sent from server and < is text sent to server. [1] LART: Luser Attitude Re-adjustment Tool $> dict LART for more info Matthew -- Matthew Sackman Nottingham England BOFH Excuse Board: Root name servers corrupted. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
On Thu, May 16, 2002 at 09:55:33AM -0700, Cam Ellison wrote:
> * Grant Edwards ([EMAIL PROTECTED]) wrote:
> > In muc.lists.debian.user, you wrote:
> >
> > > I use mutt as my MUA, and am happy as a clam with it,
> > Me too.
> > > with one exception: anyone who runs Outlook or Outlook Express
> > > on a PC cannot receive mail from me. This does not apply to
> > > Outlook Express running on a Mac.
> >
> > I send mail every day to people running Outlook and Outlook
> > Express. I've never had a problem.
> > What is the failure mode?
> >
> I have no idea. The messages simply fail to show up. Baloo suggests I
> should get out the strong arm, but your experience suggests that I need to
> set something {differently, or unset it}. I do not use gpg (yet), as Hall
> Stevenson asked. I'm reluctant to post my .muttrc file because of the
> bandwidth, but will do so if that will help.
Hmm. Do the emails even arrive? How are they getting them: is it
download from POP or IMAP server (in which case see if the email is even
being downloaded) or is it from an Exchange server? (in which case see
if you can track the logs).
Seeing as you mention Eudora is fine, I take it this implies download
from POP/IMAP as Eudora doesn't know Exchange. This I therefore find
really odd: the emails must be arriving, so why doesn't O/OE show them?
Could you see if you can find out whether they're even downloaded?
Matthew
--
Matthew Sackman
Nottingham
England
BOFH Excuse Board:
Root name servers corrupted.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Fw: Problems: mutt to Outlook (Express)
I have suspected as much, all along, but needed to be sure. I note some interesting differences: The peole that do not receive have either Outlook Express 5 or Outlook build 9. Those that seem to work (yours included) have either OE 6 or Outlook build 10. M$ has done it again! Thanks for the help, all of you. Cam * Hall Stevenson ([EMAIL PROTECTED]) wrote: > This is now your friends problems, not you or your mutt... ;-) > > -- Cam Ellison Ph.D. R.Psych. From Roberts Creek on B.C.'s incomparable Sunshine Coast [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Fw: Problems: mutt to Outlook (Express)
This is now your friends problems, not you or your mutt... ;-)
- Original Message -
From: "Cam Ellison" <[EMAIL PROTECTED]>
To: "Hall Stevenson" <[EMAIL PROTECTED]>
Cc: "Debian-User"
Sent: Thursday, May 16, 2002 2:17 PM
Subject: Re: Problems: mutt to Outlook (Express)
OK. Here you are.
* Hall Stevenson ([EMAIL PROTECTED]) wrote:
> > I have no idea. The messages simply fail to show up.
> > Baloo suggests I should get out the strong arm, but
> > your experience suggests that I need to set something
> > {differently, or unset it}. I do not use gpg (yet), as
Hall
> > Stevenson asked. I'm reluctant to post my .muttrc file
> > because of the bandwidth, but will do so if that will
help.
>
> Send a message directly to me... cc: the list so I know you
> sent it (in case it really doesn't show up !)
>
>
> --
> To UNSUBSCRIBE, email to
[EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
>
--
Cam Ellison Ph.D. R.Psych.
>From Roberts Creek on B.C.'s incomparable Sunshine Coast
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
OK. Here you are.
* Hall Stevenson ([EMAIL PROTECTED]) wrote:
> > I have no idea. The messages simply fail to show up.
> > Baloo suggests I should get out the strong arm, but
> > your experience suggests that I need to set something
> > {differently, or unset it}. I do not use gpg (yet), as Hall
> > Stevenson asked. I'm reluctant to post my .muttrc file
> > because of the bandwidth, but will do so if that will help.
>
> Send a message directly to me... cc: the list so I know you
> sent it (in case it really doesn't show up !)
>
>
> --
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
--
Cam Ellison Ph.D. R.Psych.
From Roberts Creek on B.C.'s incomparable Sunshine Coast
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
> ... I do not use gpg (yet), as Hall Stevenson asked. I'm > reluctant to post my .muttrc file because of the > bandwidth, but will do so if that will help. No, even if you use PGP signing, Outlook Express users still get the message. It's just that the actual message you wrote is turned into an (text) attachment by OE. This is *not* the problem you're seeing. The fact that the messages "simply fail to show up" doesn't seem to be a problem related to OE. Here's a far-fetched idea: Find an OE user who can access their e-mail via some sort of "webmail". Send them a message. Have them check to see if they get the message via "webmail". If it's not there, this isn't an OE problem (nor Debian) and possibly not a mutt problem. If it is there, then have them get their e-mail with OE and see if it mysteriously has disappeared. Hall -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
In article <[EMAIL PROTECTED]>, Cam Ellison wrote:
>> > with one exception: anyone who runs Outlook or Outlook Express
>> > on a PC cannot receive mail from me. This does not apply to
>> > Outlook Express running on a Mac.
>> I send mail every day to people running Outlook and Outlook
>> Express. I've never had a problem.
>> What is the failure mode?
>
> I have no idea. The messages simply fail to show up. Baloo
> suggests I should get out the strong arm, but your experience
> suggests that I need to set something {differently, or unset
> it}. I do not use gpg (yet), as Hall Stevenson asked.
The symptoms of the gpg thing are that the Outlook user gets
the e-mail, but instead of treating it as a signed message, it
treats it as an empty message with an attachment (or something
like that).
> I'm reluctant to post my .muttrc file because of the bandwidth,
> but will do so if that will help.
The Usenet group comp.mail.mutt is probably the definitive
place to ask for help, since I doubt there's anything
Debian-specific going on.
If you have no other way to access Usenet, you can use Google:
http://groups.google.com/groups?hl=en&lr=&group=comp.mail.mutt
--
Grant Edwards grante Yow! If I pull this SWITCH
at I'll be RITA HAYWORTH!! Or
visi.coma SCIENTOLOGIST!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
> I have no idea. The messages simply fail to show up.
> Baloo suggests I should get out the strong arm, but
> your experience suggests that I need to set something
> {differently, or unset it}. I do not use gpg (yet), as Hall
> Stevenson asked. I'm reluctant to post my .muttrc file
> because of the bandwidth, but will do so if that will help.
Send a message directly to me... cc: the list so I know you
sent it (in case it really doesn't show up !)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
* Grant Edwards ([EMAIL PROTECTED]) wrote:
> In muc.lists.debian.user, you wrote:
>
> > I use mutt as my MUA, and am happy as a clam with it,
>
> Me too.
>
> > with one exception: anyone who runs Outlook or Outlook Express
> > on a PC cannot receive mail from me. This does not apply to
> > Outlook Express running on a Mac.
>
> I send mail every day to people running Outlook and Outlook
> Express. I've never had a problem.
>
> > Is there a setting I am missing, or do I have to strong-arm
> > them all to use Eudora (which also works fine)? Getting them
> > onto Linux is another step, but one thing at a time...
>
> What is the failure mode?
>
>
I have no idea. The messages simply fail to show up. Baloo suggests I should
get out the strong arm, but your experience suggests that I need to set
something {differently, or unset it}. I do not use gpg (yet), as Hall
Stevenson asked. I'm reluctant to post my .muttrc file because of the
bandwidth, but will do so if that will help.
Cam
--
Cam Ellison Ph.D. R.Psych.
From Roberts Creek on B.C.'s incomparable Sunshine Coast
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
In muc.lists.debian.user, you wrote: > I use mutt as my MUA, and am happy as a clam with it, Me too. > with one exception: anyone who runs Outlook or Outlook Express > on a PC cannot receive mail from me. This does not apply to > Outlook Express running on a Mac. I send mail every day to people running Outlook and Outlook Express. I've never had a problem. > Is there a setting I am missing, or do I have to strong-arm > them all to use Eudora (which also works fine)? Getting them > onto Linux is another step, but one thing at a time... What is the failure mode? -- Grant Edwards grante Yow! I invented skydiving at in 1989! visi.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Turn your line wraps on to 72 columns, please. On Thu, 16 May 2002, Cam Ellison wrote: > Is there a setting I am missing, or do I have to strong-arm them all > to use Eudora (which also works fine)? Getting them onto Linux is > another step, but one thing at a time... This would most likely be an Outlook/OE bug then. Whip out the strong arm. - -- Baloo -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE848MxNtWkM9Ny9xURAoWJAJ4jK2oZDBHHKcYfXOtCEFajYSiyRQCfeJWr bHxnT5K/uUM9dG1Ce7uQVho= =4fC6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problems: mutt to Outlook (Express)
> I use mutt as my MUA, and am happy as a clam with it, > with one exception: anyone who runs Outlook or Outlook > Express on a PC cannot receive mail from me. This does > not apply to Outlook Express running on a Mac. I'm at work, running Outlook Express, and I rec'd this message fine. Then again, you didn't send it directly to me... > Is there a setting I am missing, or do I have to strong-arm > them all to use Eudora (which also works fine)? Getting > them onto Linux is another step, but one thing at a time... Many times, people using mutt, for example, do PGP signatures which will often cause their messages to show up to OE users as a blank e-mail (1) with two attachments. One attachment is a text file containing their message. The other is a .dat file (???). This isn't the case with your message either. (1) I'm not interested in how OE is "broken" or who/what is doing what wrong or against some RFC... ;-) Regards Hall -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Problems: mutt to Outlook (Express)
I use mutt as my MUA, and am happy as a clam with it, with one exception: anyone who runs Outlook or Outlook Express on a PC cannot receive mail from me. This does not apply to Outlook Express running on a Mac. Is there a setting I am missing, or do I have to strong-arm them all to use Eudora (which also works fine)? Getting them onto Linux is another step, but one thing at a time... TIA Cam -- Cam Ellison Ph.D. R.Psych. From Roberts Creek on B.C.'s incomparable Sunshine Coast [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
