Re: OT: offending sig + headers
On Thu, May 17, 2007 at 06:30:26PM -0400, Derek Martin wrote: > And the comment in my sig is anything but glib. A great deal of > thought and effort went into all parts of my spam management scheme, > including weighing any potential irritation of people who might want > to send me mail against the benefits of the scheme. And I mean it > most sincerely. I *am* sorry for the inconvenience; but not sorry > enough to undo it. It comes off pretty glibly. If it works for you, great, but it is definitely a turn-off. Ordinarily I wouldn't care enough about it to tell you, but since you seem very interested in receiving opinions on this subject... The address you see in this "From:" line is public, is posted on a website, is the only email address I use, and has been in use for years, yet SpamAssassin deals with my spam very effectively. Your solution works for you, which is great, but I certainly think it is rude and I doubt it is the only technically viable way for you to deal with spam. As I said, though, I wouldn't ordinarily think you care what my opinion is, so I wouldn't bother to tell you or waste even two seconds thinking about it, but since you seem so interested in opinions...
lists and subscribe commands and the To: header
Hi all, According to the manual, it seems that the lists and subscribe commands only examine the "To:" field of incoming mail. Is that true? Occasionally you get people who Bcc: a list, so then it slips past the lists and subscribe commands. I've set up maildrop to examine messages and change their To: header if it is from a list; is there a better way to deal with this? Thanks, Omari -- A symphony of smiles.
Re: lists and subscribe commands and the To: header
On Wed, Jun 20, 2007 at 07:04:43AM -0600, Kyle Wheeler wrote: > Generally, the lists and subscribe commands just add addresses to an > internal list. This list is then consulted for several things. For > example, it is used for the ~l pattern (which, according to the > manual, matches "messages addressed to a known mailing list"). I must be confused about what those two commands do, then. I thought those commands mark messages as being from a list. I was wondering how to make ~l work for messages that came from a list, but were not addressed to the list. Also I was wondering how to make the "L" flag appear for such messages. Apparently I was asking the wrong question. --Omari
Case insensitive limits not working?
Hi folks, The Mutt manual says that if I do a limit with all lower-case letters, like "l ~f omari", that the limit will be case-insensitive. However this does not seem to be working for me--there are messages that I find if I use the correct case in the pattern, but not if I use all lowercase letters. This is Mutt 1.5.20 on Slackware 13.0 (I compiled it, as Slackware has an older Mutt.) mutt -v shows -USE_GNU_REGEX, if this matters. Anybody else having this problem? Thanks, Omari
Re: Regexps suddenly case-sensitive?
On Fri, Oct 02, 2009 at 02:20:35PM +0200, Joost Kremers wrote: > I recently upgraded from Slackware 12.2 to Slackware 13.0. I installed mutt > 1.5.20 from source both on the old and on the new system. > For some reason, since I did the OS upgrade, mutt's regular expressions are > case-sensitive. I had a similar problem. How did you complile the newer Mutt--did you modify the Slackbuild? See http://dev.mutt.org/trac/ticket/3341 which may nor may not help you... -- You can't lose what you never had.
Re: mutt + imap + gprs
On Fri, Oct 16, 2009 at 04:43:35PM +0100, Toby Cubitt wrote: > Offlineimap claims to be extremely fast at synchronising IMAP folders, so > it might be usable over GPRS. In any case, it can be left to run away in > the background, so it's speed doesn't have much impact on mutt's > responsiveness other than how quickly you see new mails. I have thought about running offlineimap continuously in the background on my laptop, but have been concerned about what would happen if I shutdown the laptop in the middle of a sync. Will killing offlineimap at an arbitrary point result in any mail loss?
Re: Mutt freezes if network lost and regained
On Thu, Nov 12, 2009 at 07:46:04AM +0100, Jeffrey Ratcliffe wrote: > Is there a better way? Can I make mutt more tolerant of patchy network > access? I use offlineimap for this reason. It solves some problems and creates some other ones. -- When it's springtime in Alaska, it's forty below.
Re: How to handle a lot of emails via IMAP
On Mon, Jan 25, 2010 at 10:54:40AM -0500, John Villalovos wrote: > So I have been subscribed to LKML (Linux Kernel Mailing List) for > several years on my gmail account. I decided to try to read that > email using IMAP with Mutt. You might try OfflineIMAP. The disadvantage of that though is that then you'd have to download all the mail. But of OfflineIMAP gets partially done and then the connection dies or something, it will easily pick up again when you restart it.
