[LINK] BigPond goes Static
nospam at crm911.com
Wed Jan 21 13:44:45 EST 2004
> From: Craig Sanders (or someone using his machine and account, that is)
Thanks for an impressive but unnecessary detail there, but I'll comment below.
> On Tue, Jan 20, 2004 at 03:54:53PM +1100, Ash Nallawalla wrote:
> > I have located people with fixed IP addresses because their email
> > headers over time are unchanged.
> people don't have fixed IP addresses. machines do.
I know. The ones I referred to are companies whose networking regime is known to
me (fixed IP addresses). While that CEO's secretary or wife may well surf the web
from his PC and know his password, I don't think she would visit my site from his
> also, how do you tell the difference between a fixed IP
> address and a long-held dynamic IP address? you can't,
> unless you know the structure of the remote network - which,
> generally, you don't unless you work there as some kind of
> network engineer.
See above. I have worked on their premises (thankfully not as an employee but as
a customer), I have visited my site from the CEO's PC, I have spoken to their
network manager when I needed an address on their network, etc.
I try not to list the full history of every situation, perhaps hoping that others
know that I have been a reasonably hands-on Internet user for 17 years with more
than a nodding acquaintance with networks.
> it's more likely that the remote site was rejecting the mail
> when outlook tried to deliver it. it is then outlook's job
> to bounce it back to you.
Looks like it. See below.
> with a dynamic IP address you shouldn't be sending email
> directly. you should be relaying your mail via your ISP's
> mail server (or, by agreement, through some other mail server
> which has a static IP - there are ways of doing that securely
> without being an open relay, e.g. using SMTP AUTH or TLS
> crypto-certificate based relaying, or even uucp over tcp).
Yeah, yeah, etc. I use 3-4 SMTPs including my ISP and some web host sites in
every email pass. I didn't say I was running a mail server on my PC.
> at the very least, you should understand the limitations of
> what you are doing and not be surprised - or upset - when
> your mail gets rejected because it is coming from a dynamic
> IP address....because it WILL get rejected for that reason.
> there is just too much spam and too many viruses coming
Why shouldn't I be surprised? I am *trying* to understand Outlook 2003 and its
"limitations", (oh woe is me, it is not Open Source). The above test suggests
that it checked the DNS and didn't bother to send it to my SMTP gateway.
To use a supposedly cooler mail client, Agent, doing the same results in a popup
stating a 450 error, not a bounce email. I can't replicate the error with the
Using a lousy client, Outlook Express, I also see a more informative (raw) 450
error from Netspace - a popup, not a bounce email.
So, to extrapolate, Netspace did such a good job by using the black list to manage
its outbound mail, that it blocked me from sending an email to its own Helpdesk.
Outlook had nothing to do with it - it just happened to be the client I used when
I acquired a blacklisted address. I am no longer surprised, just better informed.
More information about the Link