SQL Anywhere database replication - Rejected SMTP Messages and Resend requests are being queued log entries

Author

Rejected SMTP Messages and Resend requests are being queued log entries

Jim Diaz

2005-07-20, 1:23 pm

Using ASA 6.0.3.2747

It seems as if a dbRemote log entry of "Resend requests are being queued"
indicates there was an error sending a message. Can you verify that this is
true? What else will cause this log entry?

Here is some detail on what we see occurring

We changed one of our remote users addresses from a local mail server
address to another internet address. After doing so our dbRemote log
indicated that resend requests for this remote user were being queued
(snippet below)

I. 07/13 14:31:37. Sending message to "XXXRemoteUser" (0-046219866434-0)
I. 07/13 14:31:37. Resend requests are being queued

After setting remote SMTP option debug to "Yes" we realized the messages
being sent to this user were rejected by our mail server because of relay
configuration (snippet below)

I. 07/13 17:58:23. MAIL FROM:< ConsPubAddress@Local
DomainName.com>
I. 07/13 17:58:23. 250 OK - mail from < ConsPubAddress@Local
DomainName.com>
I. 07/13 17:58:23. RCPT TO:< NewRemoteAddress@Rem
oteDomainName.xxx>
I. 07/13 17:58:23. 550 Relaying is prohibited
I. 07/13 17:58:23. RSET
I. 07/13 17:58:23. 250 OK - Reset
I. 07/13 17:58:23. Resend requests are being queued

After reconfiguring our mail server to prevent this error the message was
sent and the Resend requests are being queued log entry went away.

I. 07/13 18:42:07. MAIL FROM:< ConsPubAddress@Local
DomainName.com>
I. 07/13 18:42:07. 250 OK - mail from < ConsPubAddress@Local
DomainName.com>
I. 07/13 18:42:07. RCPT TO:< NewRemoteAddress@Rem
oteDomainName.xxx>
I. 07/13 18:42:07. 250 OK - Recipient
< NewRemoteAddress@Rem
oteDomainName.xxx>
I. 07/13 18:42:07. DATA
I. 07/13 18:42:07. 354 Send data. End with CRLF.CRLF
I. 07/13 18:42:07. 250 OK

Thanks

Jim

Rob Waywell

2005-07-20, 1:23 pm

Here is the response I provided on the earlier thread (which I understand
isn't showing up for you):

No problem, this would be perfectly normal. Take a look at the -ru switch
for dbremote.

Here is the response Reg provided:

No, this message indicates that during the receive stage, that there was a
missing message detected. If you are running in continuous mode, a resend
request is not automatically satisifed right away. The speed at which
resend requests are as processed can be changed with the -ru switch.

--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional

Sybase's iAnywhere Solutions

Please respond ONLY to newsgroup

EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all

To Submit Bug Reports:
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug

SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288

Whitepapers, TechDocs, and bug fixes are all available through the iAnywhere
Developer Community at www.ianywhere.com/developer
"Jim Diaz" < jimdiazatemprisecorp
orationdotcom> wrote in message
news:42de857e$1@foru
ms-2-dub...
> Using ASA 6.0.3.2747
>
> It seems as if a dbRemote log entry of "Resend requests are being queued"
> indicates there was an error sending a message. Can you verify that this
> is true? What else will cause this log entry?
>
> Here is some detail on what we see occurring
>
> We changed one of our remote users addresses from a local mail server
> address to another internet address. After doing so our dbRemote log
> indicated that resend requests for this remote user were being queued
> (snippet below)
>
> I. 07/13 14:31:37. Sending message to "XXXRemoteUser" (0-046219866434-0)
> I. 07/13 14:31:37. Resend requests are being queued
>
> After setting remote SMTP option debug to "Yes" we realized the messages
> being sent to this user were rejected by our mail server because of relay
> configuration (snippet below)
>
> I. 07/13 17:58:23. MAIL FROM:< ConsPubAddress@Local
DomainName.com>
> I. 07/13 17:58:23. 250 OK - mail from < ConsPubAddress@Local
DomainName.com>
> I. 07/13 17:58:23. RCPT TO:< NewRemoteAddress@Rem
oteDomainName.xxx>
> I. 07/13 17:58:23. 550 Relaying is prohibited
> I. 07/13 17:58:23. RSET
> I. 07/13 17:58:23. 250 OK - Reset
> I. 07/13 17:58:23. Resend requests are being queued
>
> After reconfiguring our mail server to prevent this error the message was
> sent and the Resend requests are being queued log entry went away.
>
> I. 07/13 18:42:07. MAIL FROM:< ConsPubAddress@Local
DomainName.com>
> I. 07/13 18:42:07. 250 OK - mail from < ConsPubAddress@Local
DomainName.com>
> I. 07/13 18:42:07. RCPT TO:< NewRemoteAddress@Rem
oteDomainName.xxx>
> I. 07/13 18:42:07. 250 OK - Recipient
> < NewRemoteAddress@Rem
oteDomainName.xxx>
> I. 07/13 18:42:07. DATA
> I. 07/13 18:42:07. 354 Send data. End with CRLF.CRLF
> I. 07/13 18:42:07. 250 OK
>
> Thanks
>
> Jim
>
>
>
>

Jim Diaz

2005-07-20, 8:23 pm

Thanks and sorry for the duplicate post. Shouldn't dbRemote indicate there
was an error when trying to send the message? Does dbRemote record the
error in the log file in the latest version?

Jim

"Rob Waywell" <rwaywell@no_spam.ianywhere.com> wrote in message
news:42de9545$1@foru
ms-2-dub...
> Here is the response I provided on the earlier thread (which I understand
> isn't showing up for you):
>
> No problem, this would be perfectly normal. Take a look at the -ru switch
> for dbremote.
>
> Here is the response Reg provided:
>
> No, this message indicates that during the receive stage, that there was a
> missing message detected. If you are running in continuous mode, a resend
> request is not automatically satisifed right away. The speed at which
> resend requests are as processed can be changed with the -ru switch.
>
>
> --
> -----------------------------------------------
> Robert Waywell
> Sybase Adaptive Server Anywhere Developer - Version 8
> Sybase Certified Professional
>
> Sybase's iAnywhere Solutions
>
> Please respond ONLY to newsgroup
>
> EBF's and Patches: http://downloads.sybase.com
> choose SQL Anywhere Studio >> change 'time frame' to all
>
> To Submit Bug Reports:
> http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
>
> SQL Anywhere Studio Supported Platforms and Support Status
> http://my.sybase.com/detail?id=1002288
>
> Whitepapers, TechDocs, and bug fixes are all available through the
> iAnywhere
> Developer Community at www.ianywhere.com/developer
> "Jim Diaz" < jimdiazatemprisecorp
orationdotcom> wrote in message
> news:42de857e$1@foru
ms-2-dub...
>
>

Rob Waywell

2005-07-21, 8:23 pm

I often refer the messaging system that is required between the dbremote at
the sending node and the dbremote at the receiving node as the "Magical
Mystical Messaging Cloud" to emphasize that SQL Remote has no knowledge and
no control over what happens there. In your case you are using SMTP. If
dbremote did encounter an error in building and sending the SMTP message
then it would report it. However, we have no control over the message once
it is handed off to the SMTP server. Delivery of the message to the
receiving mailbox relies entirely on your mail system. If the system was
down and a message was lost, then dbremote will not know that other than by
detecting the missing message. We detect missing messages based on the log
offset info included in the header of each message file. When we detect a
missing message we request a resend - ensuring guaranteed message delivery.

--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional

Sybase's iAnywhere Solutions

Please respond ONLY to newsgroup

EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all

To Submit Bug Reports:
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug

SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288

Whitepapers, TechDocs, and bug fixes are all available through the iAnywhere
Developer Community at www.ianywhere.com/developer
"Jim Diaz" < jimdiazatemprisecorp
orationdotcom> wrote in message
news:42dea280@forums
-2-dub...
> Thanks and sorry for the duplicate post. Shouldn't dbRemote indicate
> there was an error when trying to send the message? Does dbRemote record
> the error in the log file in the latest version?
>
> Jim
>
> "Rob Waywell" <rwaywell@no_spam.ianywhere.com> wrote in message
> news:42de9545$1@foru
ms-2-dub...
>
>

Jim Diaz

2005-07-29, 9:23 am

In this case dbRemote did encounter an error in building and sending the
message dbRemote received a notice from the SMTP server
"550 Relaying is prohibited" 550 is a standard as defined in the RFC reply
which indicate an error has occurred. This is analogous to writing a file
and the directory not existing and not reporting an error. I'm not
complaining mind you I think this would improve the product.

Thanks

Jim Diaz

"Rob Waywell" <rwaywell@no_spam.ianywhere.com> wrote in message
news:42dff692$1@foru
ms-2-dub...
>I often refer the messaging system that is required between the dbremote at
>the sending node and the dbremote at the receiving node as the "Magical
>Mystical Messaging Cloud" to emphasize that SQL Remote has no knowledge and
>no control over what happens there. In your case you are using SMTP. If
>dbremote did encounter an error in building and sending the SMTP message
>then it would report it. However, we have no control over the message once
>it is handed off to the SMTP server. Delivery of the message to the
>receiving mailbox relies entirely on your mail system. If the system was
>down and a message was lost, then dbremote will not know that other than by
>detecting the missing message. We detect missing messages based on the log
>offset info included in the header of each message file. When we detect a
>missing message we request a resend - ensuring guaranteed message delivery.
>
> --
> -----------------------------------------------
> Robert Waywell
> Sybase Adaptive Server Anywhere Developer - Version 8
> Sybase Certified Professional
>
> Sybase's iAnywhere Solutions
>
> Please respond ONLY to newsgroup
>
> EBF's and Patches: http://downloads.sybase.com
> choose SQL Anywhere Studio >> change 'time frame' to all
>
> To Submit Bug Reports:
> http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug
>
> SQL Anywhere Studio Supported Platforms and Support Status
> http://my.sybase.com/detail?id=1002288
>
> Whitepapers, TechDocs, and bug fixes are all available through the
> iAnywhere
> Developer Community at www.ianywhere.com/developer
> "Jim Diaz" < jimdiazatemprisecorp
orationdotcom> wrote in message
> news:42dea280@forums
-2-dub...
>
>

Rob Waywell

2005-07-29, 8:23 pm

There are a few things here:

1) If dbremote fails in sending a message, that will not result in a missing
message being reported at the other end. The reason it will not result in a
missing message being detected is because the next time you run dbremote in
send mode it will have to send the failed message before it can send the
next message.

2) DBRemote should report an error when failing to send a message. If you
can see that DBRemote received the error back from the SMTP server then this
would confirm that it reported the failure to send the message, is this
correct? If so, can you post the dbremote output from running with the SMTP
message control DEBUG parameter set to YES?

SQL Remote User's Guide

SQL Remote Administration

Using message types

The SMTP message system
....
Debug When set to YES, displays all SMTP and POP3 commands and responses.
This is useful for troubleshooting SMTP/POP support problems. Default is NO.

3) If DBRemote reports the error but then continues on sending the next
message from a later offset, then it would explain the missing message
scenario. However, that would seem to be unlikely since if the SMTP server
is reporting that "Relaying is prohibited" for one message, it would be
expected to report "Relaying is prohibited" for the very next message being
sent within seconds of the first one.

--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional

Sybase's iAnywhere Solutions

Please respond ONLY to newsgroup

EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all

To Submit Bug Reports:
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug

SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288

Whitepapers, TechDocs, and bug fixes are all available through the iAnywhere
Developer Community at www.ianywhere.com/developer
"Jim Diaz" < jimdiazatemprisecorp
orationdotcom> wrote in message
news:42ea3c32$1@foru
ms-1-dub...
> In this case dbRemote did encounter an error in building and sending the
> message dbRemote received a notice from the SMTP server
> "550 Relaying is prohibited" 550 is a standard as defined in the RFC
> reply which indicate an error has occurred. This is analogous to writing
> a file and the directory not existing and not reporting an error. I'm not
> complaining mind you I think this would improve the product.
>
> Thanks
>
> Jim Diaz
>
> "Rob Waywell" <rwaywell@no_spam.ianywhere.com> wrote in message
> news:42dff692$1@foru
ms-2-dub...
>
>

Sponsored Links