Re: Folder specific TO-Address
On Fri, May 11, 2001 at 08:25:07PM +0200, Wilhelm Wienemann wrote:
I am searching for a way defining a default TO: address depending on
list-reply (default: L)
Reply to the current or tagged message(s) by extracting any addresses
which match the addresses given by the ``lists or subscribe''
commands, but also honor any Mail-Followup-To header(s) if the
``$honor_followup_to'' configuration variable is set. Using this when
replying to messages posted to mailing lists helps avoid duplicate
copies being sent to the author of the message you are replying to.
Is this true solution? I do concur the use of lists or subscribe is
a good thing if used appropriately. But blanket statement makes me
worry. This makes new message linked to previous message which we
sometines do not want when one wish to initiate a thread. This is valid
only for continuing discussion. (I see so many careless posting attached
to unrelated thread.)
L : continue discussion on list (Good thing with lists)
m : start thread.
g : reply to all
So also redefining m with each folder is a good idea which someone
else already posed if m to work as original poster intended. (I
should try...)
One reminder, when you do not want reply to be addressed to you but
should go to ML, set subscribe. Then also change .muttrc
#index format (Collasped)
set index_format=%4C %Z %{%b %d} %-15.15F %?M?(#%03M)(%4l)? %s
to get address displayed sanely. This one took me a while before I
figured out
Osamu
--
~~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~
+ Osamu Aoki [EMAIL PROTECTED], GnuPG-key: 1024D/D5DE453D +
+ My debian quick-reference, http://www.aokiconsulting.com/quick/+
Re: (OT) Help with Spam/Go-Between
On Sun, May 13, 2001 at 07:40:12AM +0530, Suresh Ramasubramanian wrote: Using a large mallet, Horace G. Friend III whacked out: I wrote: Outblaze is a third party email outsourcer. By third party email outsourcer, do you mean it acts as a relay for selected clients such as mail.com? Including spammer's perhaps? See http://www.cp.net or http://www.outblaze.com Such firms take over the hassles of running mailservers for portals and other sites which may not have the expertise / infrastructure to do so. They recently took over mail.com and its dozens of vanity webmail domains Aren't legit mail supposed to have matching forward and reverse DNS to avoid having it thought of (or classified) as spam mail? Definitely not. I read from the RedHat Sendmail HOWTO that the forward and reverse DNS should match. This became necessary due to the proliferation of spam mails on the Net. 1. complain to iname.net regarding the matter or 2. stop using mail.com One last thing, do you know of any clean email forwarding service? They are all clean. If you mean spam free see https://stop.mail-abuse.org - it'll cost you though. I guess by clean, I meant spam free. Honestly, I'm not looking for a 100% spam-free environment because that's next to impossible without blocking other legit mail. I don't even care if outblaze.com takes over all the mail servers in the world. What get's my goat is that someone (and outblaze.com tops the list) intercepts mails and/or pretends to be someone else. Here is the header from the Java Developer Connection Newsletter which I subscribe from. It's even got a Precedence: Junk in it. Can you believe that? I may be wrong because I'm totally unfamiliar with techniques used to forge this and that in spam mails. So where do you folks think the message below came from? sun.com or outblaze.com? From [EMAIL PROTECTED] Sun May 6 14:47:04 2001 Return-Path: [EMAIL PROTECTED] Received: from localhost (IDENT:[EMAIL PROTECTED] [127.0.0.1]) by localhost.localdomain (8.11.0/8.11.0) with ESMTP id f466l3g08310 for hgf3@localhost; Sun, 6 May 2001 14:47:03 +0800 Received: from POP3.skyinet.net [206.101.197.21] by localhost with POP3 (fetchmail-5.5.0) for hgf3@localhost (single-drop); Sun, 06 May 2001 14:47:03 +0800 (PHT) Received: from mx.skyinet.net (int2-mx.skyinet.net [202.78.88.137]) by pop3.skyinet.net (Postfix) with ESMTP id 92D8E281E8 for [EMAIL PROTECTED]; Sat, 5 May 2001 15:14:27 +0800 (PHT) Received: from smv19.iname.net (lmtp08.iname.net [165.251.8.81]) by mx.skyinet.net (Postfix) with SMTP id E4E011B304 for [EMAIL PROTECTED]; Sat, 5 May 2001 15:14:22 +0800 (PHT) Received: from spf8.us4.outblaze.com (205-158-62-35.outblaze.com [205.158.62.35] (may be forged)) by smv19.iname.net (8.9.3/8.9.1SMV2) with ESMTP id DAA20037 for [EMAIL PROTECTED] sent by [EMAIL PROTECTED]; Sat, 5 May 2001 03:14:19 -0400 (EDT) Received: from hermes.java.sun.com (hermes.java.sun.com [204.160.241.85]) by spf8.us4.outblaze.com (8.11.0/8.11.0) with SMTP id f457EHC16692 for [EMAIL PROTECTED]; Sat, 5 May 2001 07:14:17 GMT Message-Id: [EMAIL PROTECTED] Date: Sat, 5 May 2001 00:14:18 PDT To: [EMAIL PROTECTED] From: JDC.C[EMAIL PROTECTED] Subject: JDC CE Technologies Bulletin - May 4, 2001 Precedence: junk X-Mailer: Beyond Email 2.2 Sender: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=iso-8859-1 Status: RO JAVA[SM] WIRELESS DEVELOPER CONNECTION LAUNCH REGISTER NOW! LIMITED SEATING! If you're attending the 2001 JavaOne[SM] Conference, you may want to take this opportunity to learn more about a NEW wireless developer program. The Java[SM] Wireless Developer Connection program is designed to help developers create wireless applications using Sun's Java[TM] 2 Platform, Micro Edition (J2ME[TM]) Connected Limited Device Configuration (CLDC) and Mobile Information Device (MID) profile technologies. Java Wireless Developer Connection Launch - WHAT: EXTREME IMAX Movie WHERE: SONY*IMAX Theatre 101 Fourth Street San Francisco, CA (connected to the Moscone Center) WHEN: June 5, 2001 at 6:30 p.m. Seating is limited. Only the first 600 to register will be able to attend! To register, go to http://servlet.java.sun.com/event-reg/wireless/dev2001/ For additional questions or more information, just send an e-mail to [EMAIL PROTECTED] Thank you. Sun Microsystems, Inc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . - NOTE Sun, Sun Microsystems, Java, Java Developer Connection, JavaOne, and J2ME are trademarks, servicemarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. - COPYRIGHT Copyright 2001
Re: Folder specific TO-Address
Suresh Ramasubramanian wrote: Using a large mallet, Mr. Wade whacked out: folder-hook .'unmy_hdr To:' folder-hook =IN-L-mutt-users 'my_hdr To: [EMAIL PROTECTED]' A problem with this, though, is that list-replies tend to have the list address twice in the To: field. I haven't spent any time determining a method to correct that. Heh, no. Doesnt need to be that way. Trust to mail-followup-to / reply-to set by the list (that takes care of the to) and just set your from header. See my muttrc at http://www.hserus.net/muttrc.html for a list oriented muttrc Well, for one thing, not all lists (this one, for example) modify the Reply-To: header. Also, not all users' MUAs accommodate Mail-Followup-To: headers, but most importantly: not all messages a user sends is a reply to a previous message. Too many users contaminate threads by replying to messages with something that is totally unrelated or break them by not replying where appropriate, beginning new threads. Some are simply too lazy to address an email for themselves, so they just reply, possibly neither understanding nor caring how annoying it is. :) This was an attempt to have Mutt use a default To: address for a mailbox folder, as I understand it. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Folder specific TO-Address
Hello Osamu! On Sat, 12 May 2001, Osamu Aoki wrote: On Fri, May 11, 2001 at 08:25:07PM +0200, Wilhelm Wienemann wrote: I am searching for a way defining a default TO: address depending on list-reply (default: L) Reply to the current or tagged message(s) by extracting any addresses which match the addresses given by the ``lists or subscribe'' commands, but also honor any Mail-Followup-To header(s) if the ``$honor_followup_to'' configuration variable is set. Using this when replying to messages posted to mailing lists helps avoid duplicate copies being sent to the author of the message you are replying to. Is this true solution? Sorry, but I didn't say it's the 'one-and-only' solution. For me it's one of more possible ways to do it which will work here on my box without any problems. :-) Kai Weber [EMAIL PROTECTED] was asking on Fri, 11 May 2001 17:12:34 +0200: --- cut here - [...] Let's say I am in the mutt's Mailinglist folder. If I press m I want a default address [EMAIL PROTECTED] there. [...] --- cut here - If you edit the 'subscribe'-variable in your $HOME/.muttrc then you can get one (possible) solution with the answer which I've quoted above and which is part of the official mutt-manual. I do concur the use of lists or subscribe is a good thing if used appropriately. But blanket statement makes me worry. This makes new message linked to previous message which we sometines do not want when one wish to initiate a thread. IMHO it's a question of the right managing of the tools, especially the configure-tools of mutt. This is valid only for continuing discussion. (I see so many careless posting attached to unrelated thread.) IMHO that's not a question of the managing of the 'L' feature. L : continue discussion on list (Good thing with lists ...and 'subscribe' [!]) m : start thread. g : reply to all Also a possible way but mostly the PM of CC or BCC are enclosed. bye - Wilhelm -- ._. Wilhelm Wienemann [EMAIL PROTECTED] / _,\ | (_./ Debian GNU/Linux Version 2.2 Potato \, To learn more visit = http://www.debian.org/
Re: (OT) Help with Spam/Go-Between
On Sun, May 13, 2001 at 10:24:24AM +0530, Suresh Ramasubramanian wrote: Using a large mallet, Duke Normandin whacked out: You are correct as per the SMTP protocol and the relevant RFCs. However it's my understanding from a very recent thread on the FreeBSD-questions list, that the SMTP 'fact-of-life' is that unless your IP/Doamin name resolve both ways, an increasing number of servers will refuse your mail. Precisely. And this is sad. I would do this myself (reject mail from IPs with no forward / reverse dns - _not_ forward and reverse mismatches like some do) - I take that by mismatches you mean an almost correct match on the RDNS. In this day-and-age, 'almost' _is not_ good enough. The suckers _had_ better resolve. The implications of this whole thread for some Mutt users is important. If a user, like myself, is running Mutt on Cygwin, AND is on a dial-up, AND for some reason needs to run a SMTP server to accept local mail from more one MUA, he cannot run the server end-to-end because given his dyn. IP, his outbound mail will always be rejected because RDNS never resolves. Hence, the need to use the 'From' thing in /etc/muttrc, AND to relay your outbound to your ISP. HELO had better be 'yourISP.whatever' for your outbound to get through -- mismatches don't count. If you're running SMTP as both server and client, i.e., you have an IP and a domain that resolve both ways, then how you handle inbound stuff is up to you. Like I said though, increasingly, your outbound needs to resolve on RDNS --- sad, but a fact. So this second scenario _also_ has implications as to how Mutt is set up. have I missed something obvious here? -- -duke Calgary, Alberta, Canada
Re: (OT) Help with Spam/Go-Between
Using a large mallet, Duke Normandin whacked out: I take that by mismatches you mean an almost correct match on the RDNS. In this day-and-age, 'almost' _is not_ good enough. The suckers _had_ better resolve. The implications of this whole thread for some Mutt users Heck no. Have you ever considered the case of large ISPs and webhosts - and especially virtual server setups? forward dns resolves to my-cat-is-cute.com - but reverse will point to server22.some-web-host.com local mail from more one MUA, he cannot run the server end-to-end because given his dyn. IP, his outbound mail will always be rejected because RDNS never resolves. Hence, the need to use the 'From' thing in You need that as ISPs dont accept mail from unresolvable domains /etc/muttrc, AND to relay your outbound to your ISP. HELO had better be 'yourISP.whatever' for your outbound to get through -- mismatches don't count. No. You _dont_ want to filter on HELO - IIRC there's an RFC against that up to you. Like I said though, increasingly, your outbound needs to resolve on RDNS --- sad, but a fact. So this second scenario _also_ has implications as to how Mutt is set up. rDNS must exist. There is no requirement that it must match forward dns -- Suresh Ramasubramanian + Lumber Cartel India - tinlcI mallet @ cluestick.org + Wallopus Malletus Indigenensis EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
Re: Folder specific TO-Address
Using a large mallet, Mr. Wade whacked out: This was an attempt to have Mutt use a default To: address for a mailbox folder, as I understand it. Yes. And I use procmail with other headers (say Sender: - usually distinctive to the list) to filter each list into a separate mbox -- Suresh Ramasubramanian + Lumber Cartel India - tinlcI mallet @ cluestick.org + Wallopus Malletus Indigenensis EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
Re: Folder specific TO-Address
Hi, I know you quoted manual... But context made me worry. I am not sure we are talking same thing but try explaining what I meant: On Sun, May 13, 2001 at 08:13:28PM +0200, Wilhelm Wienemann wrote: On Fri, May 11, 2001 at 08:25:07PM +0200, Wilhelm Wienemann wrote: I am searching for a way defining a default TO: address depending on ... list-reply (default: L) Reply to the current or tagged message(s) by extracting any addresses which match the addresses given by the ``lists or subscribe'' commands, but also honor any Mail-Followup-To header(s) if the ``$honor_followup_to'' configuration variable is set. Using this when replying to messages posted to mailing lists helps avoid duplicate copies being sent to the author of the message you are replying to. Is this true solution? Sorry, but I didn't say it's the 'one-and-only' solution. For me it's one of more possible ways to do it which will work here on my box without any problems. :-) When L is pressed in place of m, it creates To: correctly as described above but also sets additional one: In-Reply-To: [EMAIL PROTECTED]; from [EMAIL PROTECTED] on Fri, May 11, 2001 at 08:25:07PM +0200S So it becomes part of other thread if used in place of m command. ;-) m will not set above tag. Original posting was about how-to-set To:... for m, I think... Regards, -- ~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ + Osamu Aoki [EMAIL PROTECTED], GnuPG-key: 1024D/D5DE453D + + My debian quick-reference, http://www.aokiconsulting.com/quick/+
Re: Folder specific TO-Address
Suresh Ramasubramanian wrote: Using a large mallet, Mr. Wade whacked out: This was an attempt to have Mutt use a default To: address for a mailbox folder, as I understand it. Yes. And I use procmail with other headers (say Sender: - usually distinctive to the list) to filter each list into a separate mbox I do this as well. I think that perhaps I misunderstood the original question. I was under the impression that the asker wanted to know how to have a default To: [EMAIL PROTECTED] header specified when he loaded his mailing list mailbox folder, so that he wouldn't have to enter that as input. You seem to be discussing sorting incoming mail rather than mail composition. -- Linux: The Choice of the GNU Generation
Re: Folder specific TO-Address
Suresh Ramasubramanian wrote: Using a large mallet, Mr. Wade whacked out: I do this as well. I think that perhaps I misunderstood the original question. I was under the impression that the asker wanted to know how to have a default To: [EMAIL PROTECTED] header specified when he loaded his mailing list mailbox folder, so that he wouldn't have to enter that as input. You seem to be discussing sorting incoming mail rather than mail composition. Well, I sort incoming mail, and then use folder hooks to set my from address. Mutt's L (list reply to) along with subscribe foo in muttrc handles things quite OK. I agree,... but what about messages which are NOT replies? I think that's what the original question was about. If he invokes the mail function, (bound to m by default), he must then specify a To: header address. I think that's what he was trying to automate. -- Linux: The Choice of the GNU Generation
Re: Folder specific TO-Address
Using a large mallet, Mr. Wade whacked out: I agree,... but what about messages which are NOT replies? I think that's what the original question was about. If he invokes the mail function, (bound to m by default), he must then specify a To: header address. I think that's what he was trying to automate. owch. -- Suresh Ramasubramanian + Lumber Cartel India - tinlcI mallet @ cluestick.org + Wallopus Malletus Indigenensis EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
