From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] pipefrom fun
Date: Fri, 21 Aug 2009 08:33:44 -0400 [thread overview]
Message-ID: <b3a1e2db525ca9c6846791ba9a2e4650@quanstro.net> (raw)
In-Reply-To: <4A8E4CB9.8070205@maht0x0r.net>
> >one thing i've thought would be useful since people mail from
> >many places with many names is a translation from a set of from
> >addresses to a mailbox name so that, e.g. the ned f command doesn't
> >end up creating a bunch of folders for the same person.
> >
> >
> I'll consider that when I get round to pipeto
that has nothing to do with pipeto. it would be a big mistake
to modify the sender in an email! the dread libcommon needs
modification.
little known fact: mail quanstro/folder will deliver directly to
folder rather than inbox. many email gateways dislike this,
so you can rewrite
\l\.quanstro.net!([^+]+)\+([^+]+) alias \1/\2
if you're using nupas, which is a good idea if you have an internet-
facing smtpd, i'll consider patches. but i'm a little leery of adding
yet more complicated rules for frobnication of the sent message.
does your script work with mail sent through the imap server?
since you set upasname, marshal already tries to add
/mail/box/upasname/headers, this already solves all of your problem
except setting upasname automaticly.
finally, the reason your To: address did get rewritten is that send, which
is invoked by marshal does yet more rewriting of the from,
- erik
next prev parent reply other threads:[~2009-08-21 12:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 23:47 maht-9fans
2009-08-21 0:58 ` erik quanstrom
2009-08-21 7:28 ` matt
2009-08-21 12:33 ` erik quanstrom [this message]
2009-08-21 4:39 ` Russ Cox
2009-08-21 7:59 ` matt
2009-08-21 13:48 ` Russ Cox
2009-08-21 14:55 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b3a1e2db525ca9c6846791ba9a2e4650@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).