On Wed, 26 Mar 2003 16:48:15 -0700, "Jason R. Mastaler" <[EMAIL PROTECTED]> wrote:
> If you use qmail, they don't offer any advantages over .qmail files. > > $ cat ~/.qmail-www-default > ./Maildir/ > > So, I can enter '[EMAIL PROTECTED]', > '[EMAIL PROTECTED]', etc. I thought about this, and yes, it works just fine, but it's not as convenient if you ever have to "close the door" on someone. For example, I signed up for e-mail notification at comics.com in hopes that they would just mail me the slow loading JPGs/GIFs. Instead, it turns out they just mail you links, so it doesn't help any. I had given them a keyword address. I tried to unsubscribe but their crappy site won't let me, so I just put in a "to [EMAIL PROTECTED] bounce" in my filter. Problem solved. Had I been using extensions, then I could add in a ".qmail-www-comics.com" that directs them to the bit bucket. But hopefully by bouncing these things, they may eventually remove me from their list. I suppose I could set up a general TMDA rule that bounces all www addresses and then use links to connect .qmail-www-comics back to .qmail, but that seems kind of weird. Advantage two, I can keep all of this in a few files instead of one file for each closed door. On Wed, 26 Mar 2003 20:13:51 -0800 (PST), David <[EMAIL PROTECTED]> wrote: > Now that's a great idea... and just the kind of feedback I am looking > for. So, using my example, I could do [EMAIL PROTECTED] and > make a link for .qmail-amazon-com pointing to my .qmail file. Then if I > see mail coming in to that address from some other third party, I can > also tell who distributed my e-mail address. Yes, you can, but it's cooler than that. Qmail lets you put in "-default" as the end of any of these .qmail files to catch general cases. In other words, you can set up -default files and continue issuing email addresses without ever monkeying with it again. > But what about just using a keyword address instead to create an > address like [EMAIL PROTECTED] And for that > matter, would it even make a difference? Generally speaking, the effect is the same. If you go with the ext trick, you simply set up (for example) .qmail-www-default and you're done. You can safely give out any [EMAIL PROTECTED] you wish without generating a single keyword. If you use keywords, incoming filtering stays within TMDA. > I mean what purpose does that > 6 character crypted code in a keyword address? The crypto codes are a measure of protection. For example, suppose Jason has a .qmail-www-default file that accepts mail. I could start spamming [EMAIL PROTECTED], [EMAIL PROTECTED], etc. and the only good way he could block me would be to shut down his .qmail-www-default file. The wouldn't work if he was using TMDA because I could never guess the correct crypto codes to put in. What's the chance this would ever happen? Very slim. > Interesting, speaking of tmda-address, it looks like a hyphen in your > keyword gets turned into a question mark in the new address. Huh? > How does > qmail see that. Is it a legal character? Perhaps better to just use a > dot instead of a hyphen. Qmail looks for hyphens specifically and breaks up addresses based on them (colons too, I think). This means that ANY Qmail user can create as many email addresses as s/he need without ever asking for help from the sysadmin! Cool, eh? Gre7g. _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
