Disposable email adresses, procmail & clients

Hey there,

I was wondering if there would be a good tutorial on the use of
disposable email addresses using a *@domain.tld approach.

Ok so what I want is this:
- incoming email is filtered to different folders depending on the To:
header.
This is impossible for mail that used Bcc: to get to me.
Then, some providers insert custom headers like: X-Envelope-To: to let
this information pass through to the reader.
Otherwise, procmail would not be able to do this, or so it was said.
The MTA should do this, it was said.

However, on my email, when I look at all the headers, I see "Received:"
headers. If I scan those headers from oldest to newest for the pattern
"for name@domain" I always can retrieve the 'original to'.

Software could do this. Procmail could. Any mail reader could. It could
be done to IMAP folders, or in a custom 'dynamic view' program like
Opera M2.

What I really want is this:
: reply to the sender using the 'original to'.

It seems Mutt is very well able to do this. In other programs like
Outlook, Opera M2 or Thunderbird, it seems quite a hassle. What are
others' results in this?

The only requirement is this:
- retrieve the 'original to' from the list of "Received" headers
- on replying, put the 'original to' of the received email in the
"From" header.

That is all. Is this anywhere implemented? Or is my suggestion, to
search the "Received" headers, not workable? If not, being able to
reply using to received email's "To" and "Cc" headers is also an
option. This would require a pattern to identify the address in the
"To" and "Cc" headers that belong to me. For example, the pattern
"*@mydomain.com" would suffice. The only drawback would be, that I
couldn't reply this way to BCC'd mails. This is only a minor drawback,
usually I have no need to reply to those emails. And might the need
arise, I could fall back to another disposable address, like
"spam@domain.com", or just use my main address. Or choose any.

Greetings, Bart

Re: Disposable email adresses, procmail & clients

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--=_mimegpg-commodore.email-scan.com-26947-1128553260-0007
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

xen writes:

> Hey there,
>
> I was wondering if there would be a good tutorial on the use of
> disposable email addresses using a *@domain.tld approach.

Don't.

A few years from now, your domain is going to be pummeled with random crap,
to random addresses, 24 hours a day.


--=_mimegpg-commodore.email-scan.com-26947-1128553260-0007
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQBDRFssx9p3GYHlUOIRAlIFAJ9jyGiVGYio/nqFfOVJPpbQqqMjCACd FpdH
5lnohxTD1baKO4WyNsTOKfU=
=lUut
-----END PGP SIGNATURE-----

--=_mimegpg-commodore.email-scan.com-26947-1128553260-0007--

Re: Disposable email adresses, procmail & clients

=A8A few years from now, your domain is going to be pummeled with random
crap, to random addresses, 24 hours a day.=A8

If not my domain, then someone elses. It=B4s not as if I=B4m going to be
sharing those addresses with all to see. I get little spam anyway; my
provider filters out almost all spam. But when spam arrives, I will
know the history of my getting spam at that particular address. I like
the control I have over what email address is public. Regardless of the
issue of spam. I am now the one that tells others how to contact me.
This is for me as important as being able to know what address has made
it to what spamlist. This is the same in the snailmail world. Some
while ago, I suddenly started getting spam from charity orgs and =A8you
have won =80 50.000,-=A8 homeshopping companies. I=B4d like to know who
was responsible for that. What org passed on my details?

Greetings, Bart

Re: Disposable email adresses, procmail & clients

On Wed, 5 Oct 2005, xen wrote:

x> However, on my email, when I look at all the headers, I see "Received:"
x> headers. If I scan those headers from oldest to newest for the pattern
x> "for name@domain" I always can retrieve the 'original to'.
x>

You only have control over one received line and that is the one put there
by your own mail server. So you make sure that the "for
" is always put there.


x>
x> The only requirement is this:
x> - retrieve the 'original to' from the list of "Received" headers
x> - on replying, put the 'original to' of the received email in the
x> "From" header.
x>
x> That is all.


formail -u will extract the topmost header. The man page says -u gives
the first occurrence but to my logic, it is is the last occurrance so I
was a bit confused when I used it's corollary -U in a procmail recipe. But
I digress.

--
Alan

( If replying by mail, please note that all "sardines" are canned.
There is also a password autoresponder but, unless this a very
old message, a "tuna" will swim right through. )

Re: Disposable email adresses, procmail & clients

: You only have control over one received line and that is the one put
there
: by your own mail server. So you make sure that the "for
: " is always put there.

I don't need in any way to control the received line; I just need to
retrieve the first received line that was put there by the first
server to process my mail.

You write about formail - I checked its manpage but can't test it yet,
am on windows now - and I see that it would allow me to extract the
header I'd need and another filter could get me the "for" field. I see
that I could use it to change the "from" field in my own reply.

Ok so what would be the recommended setup then?

When I reply to a mail (call it: ORIG), I need just 1 piece of
information and a filter. The information is: the list of received
headers of ORIG. The filter is: a filter that extracts the original
"for" from this headerlist and substitutes the found email address into
the "from" field of the outgoing reply (call it REPLY). Only my mailer
knows the relationship between ORIG and REPLY. Only my mailer can call
any scripts and have the information be passed along from ORIG to
REPLY. It will need to do it, normally, whenever I press the "Reply"
button. It needs to be an event handler that executes a filter and
immediately imports the result as the new raw outgoing mail.

A filter that receives perhaps only ORIG and outputs REPLY for use by
the mailer to be edited by the user. Then there need be no concecutive
steps. Of course, such a scheme would also allow any custom formatting
of REPLY to take place based on the contents of ORIG, such as the way
you present the contents of ORIG in your reply. Or fill in a signature,
or add the contact to your addressbook. Of course, most mailers support
these notions internally but I would greatly enhance the
custamizability.

What mailers support this?

greetings,

Bart

Re: Disposable email adresses, procmail & clients

: You only have control over one received line and that is the one put
there
: by your own mail server. So you make sure that the "for
: " is always put there.


I don't need in any way to control the received line; I just need to
retrieve the first received line that was put there by the first
server to process my mail.


You write about formail - I checked its manpage but can't test it yet,
am on windows now - and I see that it would allow me to extract the
header I'd need and another filter could get me the "for" field. I see

that I could use it to change the "from" field in my own reply.


Ok so what would be the recommended setup then?


When I reply to a mail (call it: ORIG), I need just 1 piece of
information and a filter. The information is: the list of received
headers of ORIG. The filter is: a filter that extracts the original
"for" from this headerlist and substitutes the found email address into

the "from" field of the outgoing reply (call it REPLY). Only my MUA
(Mail User Agent; the program you use for reading & writing email; this
for new users)
knows the relationship between ORIG and REPLY. Only my MUA can call
any scripts and have the information be passed along from ORIG to
REPLY. It will need to do it, normally, whenever I press the "Reply"
button. It needs to be an event handler that executes a filter and
immediately imports the result as the new raw outgoing mail.


A filter that receives perhaps only ORIG and outputs REPLY for use by
the MUA to be edited by the user. Then there need be no concecutive
steps. Of course, such a scheme would also allow any custom formatting
of REPLY to take place based on the contents of ORIG, such as the way
you present the contents of ORIG in your reply. Or fill in a signature,

or add the contact to your addressbook. Of course, most MUAs support
these notions internally but I would greatly enhance the
custamizability.


What MUAs support this?


greetings,


Bart

Re: Disposable email adresses, procmail & clients

On 11 Oct 2005 09:56:02 -0700, "xen" wrote:

>: You only have control over one received line and that is the one put
>there
>: by your own mail server. So you make sure that the "for
>: " is always put there.
>
>I don't need in any way to control the received line; I just need to
>retrieve the first received line that was put there by the first
>server to process my mail.

You can't rely on finding that "for" clause. Most mailers just don't
create it, and even the ones that do create it only do so when there is
only one recipient per message.

Steve Baker

Re: Disposable email adresses, procmail & clients

Ah...that's what I suspected...somehow. For if it were reliable, I
would figure it would be widely used....

So now we have three possible sources for the original to. The "To"
header(s), The "CC" headers(s) and the for clause, and none of them
reliable...well, I have check some of my emails, including mailinlists,
and all show the "for" clause. I have yet to see one that doesn't. Even
hotmail adds it. The mailing list daemons that I work with do. My own
mail server (ISP) does. Ok, I've now found one postfix mailer for a
mailinglist post that didn't...

Reliable or not, if there is no information, you can always fall back
to the default, and you can use other information (such as the
to-address in the face of mailinglist posts) to figure out what "From"
address you should use.

Meanwhile, I think it provides a nice way to auto-fill in the "From
address".And at the same time, it would be a good feature of any MUA to
provide such a scripting mechanism as described in the prev. post.

Anyone have any notion of MUAs implementing such a scripting feature?

gr, Bart