Re: Next Release? When?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Thank you for your reply...

We understand that its just a delivery status and that they may only receive
a Success/Failure notification if anything at all. Our Sales people still
think the internet is FM and they just need a but more info to keep them in
check. (-;

I've confirmed this with MSS and they now have a Fix for it. They said its
in the Next Major Release, though I can call Support (on hold now) and get
it.

As for your code. If you take out your foreach loop and just do the:
smtpMail.Send(msgMail); twice or do:

smtpMail = new SmtpServer("localhost");
smtpMail2 = new SmtpServer("localhost");
smtpMail.Send(msgMail);
smtpMail2.Send(msgMail);

or

MailMessage msgMail = new MailMessage(maFrom, maTo)
MailMessage msgMail2= new MailMessage(maFrom, maTo)
msgMail.Subject = "<Subject Text Here>";
msgMail2Subject = "<Subject Text Here>";
msgMail.Body = "<Body Text Here>";
msgMail2Body = "<Body Text Here>";
msgMail.DeliveryNotificationOptions =
DeliveryNotificationOptions.OnSuccess;
msgMail2DeliveryNotificationOptions =
DeliveryNotificationOptions.OnSuccess;
smtpMail = new SmtpServer("localhost");
smtpMail.Send(msgMail);
smtpMail.Send(msgMail2;

or

MailMessage msgMail = new MailMessage(maFrom, maTo)
MailMessage msgMail2= new MailMessage(maFrom, maTo)
msgMail.Subject = "<Subject Text Here>";
msgMail2Subject = "<Subject Text Here>";
msgMail.Body = "<Body Text Here>";
msgMail2Body = "<Body Text Here>";
msgMail.DeliveryNotificationOptions =
DeliveryNotificationOptions.OnSuccess;
msgMail2DeliveryNotificationOptions =
DeliveryNotificationOptions.OnSuccess;

smtpMail = new SmtpServer("localhost");
smtpMail2 = new SmtpServer("localhost");
smtpMail.Send(msgMail);
smtpMail2.Send(msgMail);


You still just get the delivery receipt for the first connection to
"localhost"

Even though smtpMail goes out of scope, I set it to nothing, I force a
Garbage collection before and after the creation/send the connection to
"localhost" stays active after all of that. If I make any other attempts to
send amil after the initial connection no other delivery receipts are
generated. If after the first email is sent, and you wait several minute for
the SMTP connection to the server to drop, then you can send another message
and get the Delivery Status.

If you set the SmtpServer("<>") to different servers, you get one status per
server per connection.

I could send you my VB.Net app if you would like?

Thank you again for your reply...
Scott<-

"Christopher Reed" <carttu@xxxxxxxxxxxxx> wrote in message
news:uoB1Pw$$FHA.2320@xxxxxxxxxxxxxxxxxxxxxxx
> First of all, not all mail domain return receipts and some only return
> receipts on just successes or just failures.
>
> Okay, a workaround you could consider is to use your list of recipients
> within a foreach loop. For example:
>
> Given a MailAddressCollection macTo and a MailAddress maFrom --
>
> foreach (MailAddress maTo in macTo)
> {
> MailMessage msgMail = new MailMessage(maFrom, maTo)
> msgMail.Subject = "<Subject Text Here>";
> msgMail.Body = "<Body Text Here>";
> msgMail.DeliveryNotificationOptions =
> DeliveryNotificationOptions.OnSuccess;
>
> smtpMail = new SmtpServer("localhost");
> smtpMail.Send(msgMail);
> }
>
> Hope this helps!
>
> "Scott Townsend" <scott-i@.-N0-SPAMplease.enm.com> wrote in message
> news:e3TEGNz$FHA.1600@xxxxxxxxxxxxxxxxxxxxxxx
>> When using a message object and the SMTPClinet - setting the
>> mailMessage.DeliveryNotificationOptions only works once per SMTP
>> Connection. so if you send out 3 emails only the first gets the RCPT
>> TO:<email Address> NOTIFY=SUCCESS in the SMTP protocol. All the rest are
>> just send out as RCPT TO:<email Address>, regardless of the setting of
>> mailMessage.DeliveryNotificationOptions
>>
>>
>>
>> Here is the Bug feedback
>> http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?feedbackid=53d26f3b-e161-4993-93e5-f4d1e62d8754
>>
>> Here is the MSDN Forum Post
>> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=154268&SiteID=1
>>
>> Thanks,
>> Scott<-
>>
>>
>> "Christopher Reed" <carttu@xxxxxxxxxxxxx> wrote in message
>> news:e9EIcmY$FHA.3096@xxxxxxxxxxxxxxxxxxxxxxx
>>> What's the issue?
>>> --
>>> Christopher A. Reed
>>> "The oxen are slow, but the earth is patient."
>>>
>>> "Scott Townsend" <scott-i@.-N0-SPAMplease.enm.com> wrote in message
>>> news:e6mwyJe%23FHA.4028@xxxxxxxxxxxxxxxxxxxxxxx
>>>> I've been told that my SMTPClient issue will be fixed in a Future
>>>> release. How Often is the Framework updated? Is there a place to get
>>>> Beta Versions so I can test my app with the bug Fix?
>>>>
>>>> Thank,
>>>> Scott<-
>>>>
>>>
>>>
>>
>>
>
>


.

Relevant Pages

  • Re: Exchange 2000 denying connection of mail sent from one user
    ... > is failing at my mail server. ... >>>This is the mail delivery agent at messagelabs.com. ... > the message was sent to my server from thier relay and thats where the ... > connection is for about 64 secs to 120, ...
    (microsoft.public.exchange.connectivity)
  • Re: Intentionally slow down queue connections?
    ... The problem is because the connection to this server is so fast theres ... I'm sure if I could tell sendmail to simply pause ... fine and it would go through each message in the queue ... Avoid "at once" delivery attempts - default sendmail's delivery mode ...
    (comp.mail.sendmail)
  • Re: Identify a specific TCP connection
    ... You'd know because your packets are being delivered and you're not getting ... connection unless you kept getting data from your talkative friend. ... any particular timeliness of delivery. ... and just look through all of the TcpConnectionInformation ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: large emails
    ... the Delivery Options tab and check the box "Use different delivery times for ... oversize messages", once you check this you will be able to set the size ... Please do not send mail directly to this alias. ... that killed my INet connection. ...
    (microsoft.public.exchange2000.admin)