Thank you for the prompt reply. It is appreciated.
Well, I was sending the E-mails to my own domain.
When I used the -dsn I was not getting any notifications.
When I switched to -d, I started getting only * non delivery * notifications.
Positive deliveries were not generating anything.
My client is asking a very basic question which is 'how do I know if the E-mail was received'. I explained the two types of notifications (delivery and read) and the fact that the read is very unreliable due to user preferences whereas I assumed that the delivery could be trusted.
I am not eager to tell them that the only way that they know that the E-mail was received is that they did not receive a * non delivery * notification.
I am the Exchange Admin for some of our clients and I know that it is very tempting to turn off NDR for incoming E-mails. However, I leave it on.
So, is the bottom line that receiving (or not receiving) a 'delivered notification' or 'non delivered notification' is a completely unreliable method to determine if an E-mail has actually been delivered?
If so, do you have any tricks up your sleeve? :).
Allan Coganovitch, Proven Solutions Inc.
WEB site: http://www.proven-solutions.com
416-227-2290 (phone), 416-227-2295 (fax)
----- Original Message -----
Sent: Friday, December 23, 2005 2:18 PM
Subject: Re: [blat] Version 2.50 Successfull Delivery Notification Not Working
Post by proven_solutions
I am using the '-d' options to obtain delivery notifications.
Non deliveries for unknown domain or unknown recipient at a valid
domain are working fine.
However, I am not receiving delivery notifications for * delivered *
I send a test to chip dot programmer at att dot net as a test and have
not received a valid delivery notice.
The '-r' option seems to be OK.
Thank you in advance for all suggestions.
I am reading and replying to this from my office. My home account shows your message was delivered and waiting for me to get home and download it. Perhaps AT&T does not respond to the delivery notification messages in order to fight spammers. I can tell you that I do not respond to them, personally, for the same reason. I don't want to discourage you from testing Blat, its just that I am anal about my privacy. :-D
Regards your question, why is the -d option not working as expected. I suspect many system adminstrators are disabling this in order to reduce traffic. I have seen cases where a user sent a message, then immediately set their email program to "Out of office", which caused a series of messages to bounce back and forth between users' autoresponders. The admins had to shut down the whole email service to clean up this problem that exploded within minutes.
As an alternative, have you tried using the -dsn option? For example: blat message.txt -t user -dsn s
Community email addresses:
Post message: ***@yahoogroups.com
List owner: firstname.lastname@example.org
Shortcut URL to this page:
Yahoo! Groups Links
[Non-text portions of this message have been removed]
------------------------ Yahoo! Groups Sponsor --------------------~-->
Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life.