550 5.7.1 Error

Hi All
Ok I am a newbe, not just here but with the Linux family. I have a number of boxes, ok a lot with various OS variants on, Smoothwall, Fedora 5 and CentOS. I can build boxes do basic setup in GUI mode, unfortunately my son is the technical authority (command line) and he is away on holiday so I am at the coal face. So KIS (Keep it simple (stupid) (KISS))

My problem is the laptop can't send mail, incoming is OK WIN XPP & Outlook Express. The laptop gets its I/P from Smoothwall via a wireless accesspoint. The mail server is I think a Centos 3 IMAP on the 2nd URL's I/P while the Web server is on the 3rd I/P. Ok there are 2 VPN links to sister locatations. The mail server has a map of the smoothwall DHCP range and some names have been allocated, to correct this problem only it didn't!

So am I looking at an Outlook problem or a Server problem or do I need to run some test scripts? If so what please.

I have seen this about Outlook Express
Quote:
In the EMAIL settings, if you set 'Relay Status' to "Authorization is NOT required to relay through this domain", you are actually turning on POP before SMTP.

Kind of miseleading verbage; but at least it works...
Un Quote

I didn't think I would need POP with an IMAP server? so have discounted this option.

Could my problem be the WIFI Access point's I/P is not mapped?

Your advice please.
Alan

Mmm, talk about making life difficult for yourself (!)

Start with this;

Look in your mail program settings for "outgoing mail server (smtp)"
Start a terminal session and do;

And see if you get a response ...

If you do try;

And see if you get a response like this;

If you do, try this;

This should give you a detailed error (or work) ..

1st thanks for getting back.

Oh Pooh, Wally strikes again!

I am not positive I fully understand what constitutes a "terminal session", I seem to recall it is an application included in Linux but not MS Win XPP?

But I can ping the mail server from a command line prompt C:> from the Laptop in XPP.

--------------------------------
On my practice system (almost identical) fully working.

As I expected - telnet [server name or address] 25 - from a command line fails to connect. I was not expecting telnet to be an executable command.

I started HyperTerminal and set up a session - [server name or address] and changed the default port setting from 23 to 25.
The system connected 220 (server) ESMTP (....)(Date & time).

HyperTerminal wanted me to attach a file, there seemed no way to input
EHLO world .....

Do I need redirecting?

-------------------------------------
Problem system, surfing works fine.

The networked PC again XPP (another email) works fine. The laptop via the WIFI has ERROR 550 5.7.1 on send, receive is fine.

Thanks again Alan

Oh Pooh, Wally strikes again! As I said above!

Ok I now have PuTTY a name I had know but what it was for. Have a while to wait for the download.

Ok, are you asking for help with a Windows or Linux system ?

"terminal session" is the linux equivalent of a command line or "dos box"

"telnet" is standard Linux, if you don't have it installed, your system is very badly broken ...

If as it sounds like you're trying to run "telnet" from a windows box, then it's not going to work, and indeed you're on the wrong forum!

Hi Gareth,

Both the Email and Web servers are Linux based servers as is the firewall.
The laptop has MS Win XPP....I/P via DCHP range x.x.x.160 to 192
The PC has MS Win XPP........fixed I/P

The reason I am here is I believe the Win guys don't know the first thing about mixed systems of Win & Linux.

So I did get the basics about right.

I did try and outline the system fully in my original post. My first question tried to get help on where the problem might lay in the Laptop or the email server and what tests I could run.

I do understand if this is not your scene and I have to wait for my son to return.

Thanks
Alan

Well, the first problem (apart from the fact you're using Windows) is that you say you can't send email. You don't say why, or more specifically, what happens when you try. [an error message would 'probably' tell us immediately what the problem is]

This is where my first set of instructions come in.

Try again;

click start, run, enter "cmd" into the box, then click Ok.

If at that point you don't get a black "dos" box opening on the screen, you're stuffed. If the system then doesn't recognise the "ping" or "telnet" commands, you're also stuffed.

Not being a Windows person, when I said "telnet isn't going to work from a DOS box", I was talking through my hat - it does of course work fine.
(now I've tried it myself)

Given all this works, the commands after 'telnet' will either work (in which case you shouldn't be having a problem) OR, will produce an error message which will tell you what the problem is, probably fairly explicitly and almost certainly to a point where we can tell you [probably] how to fix it.