Let's just suppose you are running an OpenSource project. Do you have money to patent your invention, or do you have to wait until that someone else does it for you (microsoft for example) and they sue you?
I got spam bounces from unknown domains, and since I don't control DNS for backup MX, I think about doing a procmail rule to forward it to Veri$ign:
:0
* ^From: Mail Delivery Subsystem \<MAILER-DAEMON@sundog\.phear\.org\>$
* ^To: postmaster@sundog\.phear\.org$
* ^Subject: Postmaster notify: see transcript for details$
{ :0Bc
* ^... 550 User domain does not exist
| ( formail -rk | head -25 ; \
echo ; \
echo "We dont want to receive bounce e-mails from unexistant domains" ; \
echo "So we forward them back to you." ; \
echo ; \
echo -- ; \ /usr/games/fortune ; \
) | $SENDMAIL -f dev.null@phear.org info@verisign-grs.com
:0
sundog-bounces
}
I am wondering if something like that done by many postmasters would be nice for them. If you try, adapt to your domain/hostnames.
PS: I'm pretty sure that's not the best way to do it, but at least it seems to work.
*nasty* *nasty* (but still pissed off by VeriSign)
I spend two hours overtime fixing my company's caching name servers.
I am wondering how disturbing it would be for their finance department if they got invoices from anyone who had to change their DNS setup.
Slashdot Mirror
Let's just suppose you are running an OpenSource project. Do you have money to patent your invention, or do you have to wait until that someone else does it for you (microsoft for example) and they sue you?
No, there was one missing detail... DMCA.
But, it seems that it's not going to be the case soon: Europe heading down DMCA route, warns think tank
Welcome to One World.
Hello,
:0
:0Bc
/usr/games/fortune ; \
:0
I got spam bounces from unknown domains, and since I don't control DNS for backup MX, I think about doing a procmail rule to forward it to Veri$ign:
* ^From: Mail Delivery Subsystem \<MAILER-DAEMON@sundog\.phear\.org\>$
* ^To: postmaster@sundog\.phear\.org$
* ^Subject: Postmaster notify: see transcript for details$
{
* ^... 550 User domain does not exist
| ( formail -rk | head -25 ; \
echo ; \
echo "We dont want to receive bounce e-mails from unexistant domains" ; \
echo "So we forward them back to you." ; \
echo ; \
echo -- ; \
) | $SENDMAIL -f dev.null@phear.org info@verisign-grs.com
sundog-bounces
}
I am wondering if something like that done by many postmasters would be nice for them. If you try, adapt to your domain/hostnames.
PS: I'm pretty sure that's not the best way to do it, but at least it seems to work. *nasty* *nasty* (but still pissed off by VeriSign)
I spend two hours overtime fixing my company's caching name servers. I am wondering how disturbing it would be for their finance department if they got invoices from anyone who had to change their DNS setup.