cancel
Showing results for 
Search instead for 
Did you mean: 

SMTP Send Timeout

Former Member
0 Kudos

Is it possible to configure a send timeout for outgoing SMTP messages, so that SAP regards the send order as failed if the timeout expires before the remote server accepts the data with "250 OK" ?

I test with a MiniSap 710 system. It seems that when the send timeout (2 min) expires, the message is regarded as successfully sent. At least the recipient list in the SAPConnect outbox says "Recipient .... is valid. Delivery attempted." and no retries are done.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Deepak: Thanks for the response. From the documentation, I assumed that the TIMEOUT value in the profile is only for receiving messages.

I did a quick test and it seems that the timeout also applies to sending.

But, - when the timeout expires, the message is still regarded as sent successfully. It seems that the SMTP node interprets the last positive response from the server (250 OK for the recipient) as a prove of successful delivery - which is not the case, as the end of the DATA has not been acknowledged.

Former Member
0 Kudos

Hi

Please check this link

http://help.sap.com/saphelp_nwpi71/helpdata/en/af/73563c1e734f0fe10000000a114084/content.htm

It would clear the concept of SMTP parameter use in SAP

former_member185954
Active Contributor
0 Kudos

Hello AnneMarie,

You can set the confirmation on reciept setting so that SAP Connect expects a confirmation receipt.

In SAPconnect administration (transaction SCOT), choose Settings -> Confirmation of receipt.

Check this link:

http://help.sap.com/saphelp_nwpi71/helpdata/en/55/609f388b7811d3a33000a0c943858e/frameset.htm

Regards,

Siddhesh

Former Member
0 Kudos

The confirmation on receipt setting is already enabled on my system.

It does not change the behavior of the send job when it encounters a timeout.

former_member185954
Active Contributor
0 Kudos

Hello,

I am not sure why the system is giving status 'sent' when the email is not actually sent.

Can you set a trace and see what is happening, why is the send job picking up the wrong status ?

http://help.sap.com/saphelp_nwpi71/helpdata/en/2b/d926b44b8a11d1894c0000e8323c4f/frameset.htm

Regards,

Siddhesh

Former Member
0 Kudos

Hi Siddhesh,

The trace says:

18.06.2008

10:26:22

SX_PERFORM_SMTPSEND

G

Node Data: localhost 8025

18.06.2008

10:26:22

SX_PERFORM_SMTPSEND

G

CL_SMTP_REQUEST Successfully Created and Filled with Data

18.06.2008

10:26:22

SX_PERFORM_SMTPSEND

G

Send Routine IF_SMTP_CLIENT->SEND Is Now Called.

18.06.2008

10:26:22

CL_SMTP_REQUEST->GENERATE_XSTRIN

G

SMTP-ENVELOPE: S T EX IADR33000000000172 Dcompany2.com Oc2u1@comp

18.06.2008

10:26:22

CL_SMTP_REQUEST->GENERATE_XSTRIN

G

SMTP-ENVELOPE: any2.com Rtest<at>pcfs.topcall.com YS X .... changed by me: cannot post this with an <at> sign...

18.06.2008

10:28:12

SX_PERFORM_SMTPSEND

G

IF_SMTP_CLIENT->SEND Successfully Called

18.06.2008

10:28:12

SX_PERFORM_SMTPSEND

G

Recipient List After Sending (First 50 Characters with Status Code):

18.06.2008

10:28:12

SX_PERFORM_SMTPSEND

G

test<at>pcfs.topcall.com 718 .... changed by me: cannot post this with an <at> sign

18.06.2008

10:28:12

SX_PERFORM_SMTPSEND

G

718 = 250 recipient OK

18.06.2008

10:28:12

SO_SYNCHRON_STATUS_UPDATE

G

Start of synchronous Status Update

18.06.2008

10:28:12

SO_SYNCHRON_STATUS_UPDATE

G

Deleted from Queue: RAW33000000000402 ADR33000000000172

18.06.2008

10:28:12

SO_SYNCHRON_STATUS_UPDATE

G

SOES updated: ADR33000000000172

18.06.2008

10:28:12

SO_SYNCHRON_STATUS_UPDATE

G

Structure: SOES

18.06.2008

10:28:12

SO_SYNCHRON_STATUS_UPDATE

G

No Statusmail/No Event for Status 718

18.06.2008

10:28:12

SO_SYNCHRON_STATUS_UPDATE

G

SOST updated

18.06.2008

10:28:12

SO_SYNCHRON_STATUS_UPDATE

G

End of synchronous Status Update

18.06.2008

10:28:12

SX_PERFORM_SMTPSEND

G

SAPconnect (E)SMTP Outbound Processing Will Now Be Exited

... although the SMTP server has not responded to the end of data....

regards,

Annemarie

former_member185954
Active Contributor
0 Kudos

Hello,

I think i found the root cause:

Note 335310 - SAPconnect: No sending status/'in transit' status

Check the above mentioned note.

Regards,

Siddhesh

Former Member
0 Kudos

Hi

Please try to send the messge without the setting "confirmation on receipt", if you are able to do that, then please try these notes:

Note 997428 - Error during status update

Note 960880 - Error occurs in the case of status mails

Former Member
0 Kudos

Hi

Try this option

icm/server_port_<*> = PROT=SMTP,PORT=<port>

This opens a TCP/IP port for the reception of mails by the SMTP plug-in. <port> specifies the number of the port that is to be used. This port must not be occupied by any other program on this host. If no mails (including status notifications) are to be received in this SAP system, you can set <port> to 0.

You can use TIMEOUT to define an optional maximum time (in seconds) that is to be waited for a response from the mail server

  • is the number like 0, 1 etc

pr_srinivas
Contributor
0 Kudos

Deepak...am i wrong ??

SMTP can be used only sending out mails ? and I beleive receiving mails can happen thru POP3.!

"If no mails (including status notifications) are to be received " - this sentense thrown into confusion

rgds

Former Member
0 Kudos

Hi,

There is no POP3 sort of configuration paramter, its saying if you donot want to receive any mails then you can set the SMTP port as 0 and you will not receive any mails in SAP.

pr_srinivas
Contributor
0 Kudos

Thanks Deepak.

I just got confused as thinking in pace with standard mailing system.

Rgds