The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Fw: OT : New domain provider need - with wildcard email forwarding


  • Subject: Fw: OT : New domain provider need - with wildcard email forwarding
  • From: Gareth Cook <g@xxxxxxxxxx>
  • Date: Thu, 27 Jul 2006 08:55:30 +0100

Not quite what Im after - that means I still get mail - the sender is
a
random address every time from the domain, so that wont directly help

G.

Gareth Cook
IT Architect / Project Manager, SWG Sales
IBM SWG Sales - Lotus Park, Staines, TW18 3AG
Office: +44 (0)1784 445166 - Mobile: +44 (0)7980 445166
email: g@xxxxxxx


----- Forwarded by Gareth Cook/UK/IBM on 27/07/2006 08:41 -----

Discussion
Main Topic

ukha_d@xxxxxxx
Yesterday 22:55

.
Subject:
.
Re: [ukha_d] OT : New domain provider need - with wildcard email
forwarding
.
Category:



Gareth Cook wrote:
> I've started to get a lot of spam from my personal domain - mostly
cause
i
> use a *@domain.com to redirect everything. I then use a unique
identifier
> for each site i use/register with so i know where the mail has
originated
> from. Unfortunately, wkjfhadsiuhflas@xxxxxxx comes through to me.
>
> I use DirectNIC and have for years - but they dont support anything
other
> than a basic wildcard * for email (unless you specify an exact name
such

> as ukha@xxxxxxx forwards to this email account). i can then start
using
> *_mail@xxxxxxx which is generic enough for me to use, but not for the

> spammers.
>
> Anyone use this type of facility ?
>

Yes, Gradwell.

When you get fed up receiving spam on an address, you just redirect it
to <blank> and it gets bounced as an invalid address.

Jim




UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.