RE: SMTP troubles (AGAIN!)

You will probably need to get some sort of native 400 mail progam such as
"MailTool" from Brad Stone .... works great.

You will probably also need to get a Reverse Dns address for your 400
... Aol, Comcast, others will not accept your mail for that reason.
... Some will not accept your mail because it is relayed, which is what's
happening now. The bigger players make life difficult.

I certainly can't answer all your ?'s, but we have our mail hosted outside.
.... you are paying for it to be protected and out of harms ways.
.... such as spam and viruses
.... and you have no maintenance to speak of

These are the things we did when we started having our mail hosted outside
... it works fine and relieves us of a lot of burden


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H H Lampert
Sent: Wednesday, April 12, 2006 2:57 PM
To: Midrange Systems Technical Discussion
Subject: Re: SMTP troubles (AGAIN!)

"Tom Jedrzejewicz" <tomjedrz@xxxxxxxxx> wrote:
> This is not a good practice; the mail server should be 
> protected by the firewall, particularly as it is a Windows
> server.  I am kind of curious to
> find out why it was done, if indded it is the case.

Confirmed: the mail server is outside. This was done so 
that the web-mail interface would work, as port 80 is 
being routed elsewhere by the firewall.

Sending email from the Java application on the 400 to an 
address on the mail server works fine; sending it from the 
email server itself (through the web-mail interface) to my 
personal email address works fine.

Sending it from the Java application on the 400 to my 
personal email address produces the bounce message I 
reported previously. The curious thing about the bounce 
message is that it purports to be from 
QGATE@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx On the CHGTCPDMN 
screen for that 400, the host name is given as "sirius," 
and the domain as "private.touchtonecorp.com," but I can't 
imagine how a bounce message could be coming from the 
origin point of the original message.

Can anybody point me in the direction of docs and/or 
previous List traffic on how to get the OS/400-native SMTP 
sending email directly, without relaying through our mail 
server? Obviously, it's getting through the firewall, 
since it's getting to the mail server, so avoiding the 
relay should be fairly straightforward.

--
JHHL

--
JHHL