%Net.SMTP

[Chris Bonnici]

Hi,

I am using the above class to send emails from with Caché. When I send an
email to someone within our domain (gasanmamo.com) it gets delivered, but if
an email is sent to someone outside our domain exchange returns with an
error :"Unknown Recipient".

Does anyone know a solution to the problem.

Thanks
Chris Bonnici

[Rob Tweed]

Chris

I was just wondering - does the WLD ^%wldsmtp routine have the same
problem?

Rob

---
Rob Tweed
M/Gateway Developments Ltd : http://www.mgateway.com
IM&T Consulting Ltd
---

[Chris Bonnici]

Hi Rob,

I just checked it. Yes it does.

[Bernd Mueller]

Hey Chris,
YES, i think that's a configuration problem of your mail server!
The IP-Adress from your Cache'-Server which delivers the mail to
your mail server via SMTP is not allowed sending mails to recipients
outside your domain!

Hope i could help ... i still had this problem long ago ;-)

Bernd Mueller
-SHD-

[Peter Cooper]

Chris & all

>Hey Chris,
>YES, i think that's a configuration problem of your mail server!
>The IP-Adress from your Cache'-Server which delivers the mail to
>your mail server via SMTP is not allowed sending mails to recipients
>outside your domain!
>
>Hope i could help ... i still had this problem long ago ;-)

I believe this is correct
Depends on the mail server - the one I use you can set it to accept
mail from specific IP addresses
this is what I do setting the mail Server to accept mail from the IP
of the Cache server

Peter

[Gordon Philip]

Just to add to the fray

It does sound like your email server has the "Do not Relay Foreign Mail"
option turned on, which is there specifically to stop spamming.

If your email server is exchange that the incoming email must be from a
validated user I haven't found out how to validate a user at the command
line). Some other email servers require you to have a known email account as
the SMTPsender so look at this parameter.

Hope this helps

"Peter Cooper" <p...@xisltd.demon.co.uk> wrote in message
news:g8fagtga41qbvj4aj...@4ax.com...

[Peter Cooper]

And to add a bit more

the Cache %Net.SMTP does not have facilities for username/password to
log on (the POP3 does)

perhaps this will rectified in some future release

Peter

[Timur Safin]

There is no need on it. SMTP protocol doesn't use username/password (Check your
preferred mail-client Outlook, Outlook Express, Eudora, The Bat!, etc.) there is
username/password edit boxes only for INCOMING Mail Servers. Security policy for
outcoming mail server belong to firewall domain..

Regards,
Timur Safin

"Peter Cooper" <p...@xisltd.demon.co.uk> wrote in message

news:3lgigtktvt0hed1ta...@4ax.com...
: And to add a bit more

: >>
: >
:

[Peter Cooper]

Timur

>There is no need on it. SMTP protocol doesn't use username/password (Check your
>preferred mail-client Outlook, Outlook Express, Eudora, The Bat!, etc.) there is
>username/password edit boxes only for INCOMING Mail Servers. Security policy for
>outcoming mail server belong to firewall domain..

I think you ae incorrect
take a look in Outlook Express v 5
Tools | Accounts | Mail Account

On the servers tab at the bottom there is
"My Server Requires Authentication"
and some settings on the Advanced Button

Peter

[Bill McCormick]

You trust Microsoft?? I am shocked. The SMTP standard does not require a
username/password. MS in their infinite wisdom probably added this as a feature to MS
Exchange servers so they provide the option in Outlook...It is definitely not part of
the standard.

--
Bill McCormick
Web/Objects Support Manager
InterSystems Corporation
bmc...@intersys.com

[Mark Sires]

"Bill McCormick" <wmccor...@snet.net> wrote in message
news:3B0A63A1...@snet.net...

> You trust Microsoft?? I am shocked.

Almost as shocking as trusting Intersystems......
particularly for security issues...... :-)
Mark

[Bill McCormick]

Hehe ..... ;) Point taken...

[Markus DeFreitas]

<quote>
SMTP AUTH is " ..an SMTP service extension [ESMTP] whereby an SMTP client
may indicate an authentication mechanism to the server, perform an
authentication protocol exchange, and optionally negotiate a security layer
for subsequent protocol interactions. This extension is a profile of the
Simple Authentication and Security Layer [SASL]. "

This is what RFC 2554 says.
(http://members.elysium.pl/brush/smtp-auth/rfc/rfc2554.txt)

For mere mortals this means that we now have a way to authenticate smtp
client before we accept mail from him. If you are an ISP this is one of the
most important things on a big mail server. Without this and with a lot of
roaming customers, you end up being an open relay (because of your customers
needs) and sooner or later spamers will use you and you will be banned on
ORBS and other spam fighting list.

With SMTP AUTH you can add a layer of security to you SMTP server. While
allowing legitimate customers to send e-mail from any place (IP) in the
world you are preventing spamers and unauthorised people from using you SMTP
server.

</quote>

"Bill McCormick" <wmccor...@snet.net> wrote in message
news:3B0A63A1...@snet.net...

[Bill McCormick]

Markus,

Thank you for finding this information regarding this extension to SMTP. I
have forwarded the relevent data to development and expect this will be
supported in 4.2 at the latest if not sooner.

[Gordon Philip]

Ah yes but you try and get a MS Exchange box to recognise SMTP AUTH commands
;-)

"Bill McCormick" <bmc...@intersys.com> wrote in message
news:3B1324FD...@intersys.com...

[Markus De Freitas]

Bleh. All i know is my mail server supports CRAM-MD5 and LOGIN. Whatever
the hell that means.

"Gordon Philip" <gph...@fortuneplus.co.uk> wrote in message
news:3b165...@info2.kinich.com...

[Peter Cooper]

Markus

>Bleh. All i know is my mail server supports CRAM-MD5 and LOGIN. Whatever
>the hell that means.

After doing a bit of resaerch on Google
CRAM-MD5 is the encryption algorithm to encrypt the Username/password
pair

LOGIN is the conversation type (there seems to be two LOGIN and AUTH)

Probably the simplist way to do this if you really have to is
a) get a mail server that supports these facilities
b) send the mail from Cache to this mail server - no PW facilities
c) get this mailserver to relay the mail to the one that does the
CRAM-MD5 stuff - let this mailserver do the secure logon

Peter

[PANDIYAN]

Hi, 

Good Morning!!!,

 

I need some clarification for sending mail using SMTP,Actually we run the code in Cache, we are getting the error (ERROR #6029: Timed out waiting for response.1) while run the below code.

Whenever I tried to connect my SMTP server via Telnet (Unix Server),Its working fine and mail also sent successfully which I mentioned the mail id ,Please find the attached screen shot for the mail sent via Telnet

 

I have checked the GetResponse Method in %Net.SMTP class,  it timeout at below code

read response:timeout
                else  do ..SetStatus($$$ERROR($$$SMTPTimeout)) set response="" 

 

We don’t  know why it’s not fetching the response code. Please provide your suggestion.

 

There is no firewall setting and we are able send mail using Unix Command using the same SMTP and Port number 25 but not from Cache.

 

Code :

 

new auth,m,s,status
 set s=##class(%Net.SMTP).%New()
 set s.smtpserver="xx.xx.xx.xx"
 set s.port=25
 set auth=##class(%Net.Authenticator).%New() ; use default authentication list
 set auth.UserName="pandiyan@xxx.com"
 set auth.Password="xxxx@"
 set s.authenticator=auth
 set m=##class(%Net.MailMessage).%New()
 set m.From="pand...@xxx.com"
 do m.To.Insert("skumara@xxx.com")
 set m.Subject="Sent by Cache' mail"
 do m.TextData.Write("This message has been sent using an SMTP server with Authemtication.")
 set status=s.Send(m)
 w !,$system.OBJ.DisplayError(status)
 quit

 

Thanks & Regards,

Pandiyan