krosenstiel at comcast.net
krosenstiel at comcast.net
Mon Sep 22 17:03:59 CDT 2008
Well, that's when Jesus died for your sins and redeemed you :-))) (I could NOT resist!) -- Karen Rosenstiel Seattle WA USA -------------- Original message ---------------------- From: "Rocky Smolin at Beach Access Software" <rockysmolin at bchacc.com> > Correct. What's Redemption? > > > Rocky Smolin > Beach Access Software > 858-259-4334 > www.e-z-mrp.com > www.bchacc.com > > > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust > Sent: Monday, September 22, 2008 1:29 PM > To: Access Developers discussion and problem solving > Subject: Re: [AccessD] Email Problem > > We always used Redemption with our Access apps (and still use it with > .Net) and trapped the errors on individual email addresses. It sounds like > you're set up to send a single email to multiple addresses, correct? > > Charlotte Foust > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at > Beach Access Software > Sent: Monday, September 22, 2008 1:17 PM > To: 'Access Developers discussion and problem solving' > Subject: [AccessD] Email Problem > > Dear List: > > My day for questions. I'm sending emails automatically, unattended, from > this app - scheduled to run at night. When the email contains an invalid > address it generates an error "-21472220977 - the server rejected one or > more recipient addresses. The server response was 550 > 5.1.1 User Unknown. > Possible bad email address" > > then it lists all of the addresses in the To: CC: and BCC: fields, and the > process stops until the user comes in, sees the message and clicks OK. At > which point they don't really know what address was bad. > > I suppose I could use On Error Resume Next at the line which calls the email > send routine. Of course, that way the user will never know that there was a > bad address and that the report didn't go out. So I think that's not a good > solution. > > However, is there a way to verify addresses before sending an email? Or is > there a better approach to this problem? > > MTIA > > Rocky Smolin > > Beach Access Software > > 858-259-4334 > > www.e-z-mrp.com <http://www.e-z-mrp.com/> > > www.bchacc.com <http://www.bchacc.com/> > > > > > > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com