Advantages of small companies: No 327

NNTP traffic isn't blocked on the company firewall

 

Pint of Tea

 

A very large Talisker, ta.

 

Peppermint tea please.

So who did the "Emperors New Clothes" interview technique work on this
time?

 

<suspicious> Did you see my CV?

 

It's invisible. Isn't that the whole point?

 

Too late. I've still got pictures of naked interviewing in my head.

 

Get back to work, you skiving fecker. :O

 

So there is an opening going for a competent network admin jobsworth
then?

 

Could you explain the difference between "competent" and "permits NNTP",
with reference to Champ's employer's corporate security policy?

 

No, **** off.

 

Not only that, but I can connect my corporate laptop to my personal
pop3 email account, no problem. Fantastic! Tho, for some reason, my
attempts to send personal email out to a certain SMTP server with
which you might have a passing acquaintance is met with a " 550 5.7.1
<>... Relaying denied. IP name lookup failed
[194.143.169.189]". Any ideas?

 

champ wrote:
reference to Champ's employer's corporate security policy?

Yes, it looks like the SMTP server has been set up properly, so that
it' won't relay messages from just any tom dick or harry. That IP
address doesn't even have a matching reverse DNS entry, does it?

Get your employer to fix their DNS, for starters.

 

From the above, I'd guess that your IP is 194.143.169.189 and you're trying
to send mail out through a relay that only permits relaying to known domains
or from known IPs.
I'd suggest dropping the server admin a mail with that and any other IPs you
may appear to come from and have him open it up.

 

Yeah. I know you're a techo-biff so I'll try keep it simple.

It could be that the SMTP server is trying to obtain a hostname for the IP
address that you're connecting from. This 194... bit is all it has, and
it could be making the assumption that as the IP address doesn't resolve
to a hostname, that you must be some thieving scum bucket spammer, and is
telling you to **** off.

Alternatively, if you really are using the sender address of
<>, it's saying that it doesn't know you, so **** off.
Entering your real email addy might fix that right up if the server knows
you and likes you. Of course, you could have altered that for anti-spam
reasons but it's so not you.

 

You've not got server authentication on, so it doesn't
know who you are and thinks you're trying to relay spam.
Remember that POP3 and SMTP are (usually) different servers
so unless you've entered a username/password for the SMTP
then chances are that's the problem.

Most of the time it works on your home connection because
it can resolve your connected IP address to that of one of
it's own customers, so it doesn't need to authenticate you.
It only becomes a problem when you're away from your home
network and try to send.

Anyway, to resolve it in Outlook (most common in this because
it doesn't set the server auth on by default) you need to
goto Tools > Accounts and select the account you use to send
email with, then click the Properties button. This will open
that email account dialog. On the Servers tab of that dialog
there is a "My Server Requires Authentication" checkbox which
you need to tick. If you use a different username/password
to send email then you can set this under the Settings...
button, otherwise it will use the same details as your
POP3 server settings. Click the OKs to close the dialogs and
try it again. If you're not using Outlook then you'll have
to hunt for the same setting, but you get the idea.

 

PS. The server admin is off for dinner in 5, so it'll have to wait til
tomorrow.

 

You missed the "jobsworth", and I missed out the smiley. Here you go

 

wrote in message

Get on with the job you're paid to do and manage your social life at
home?

 

Which, of course, only works if the server supports authentication.

Which it doesn't. Probably.