Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proper error handling #1

Open
zachlatta opened this issue May 1, 2014 · 5 comments
Open

Proper error handling #1

zachlatta opened this issue May 1, 2014 · 5 comments

Comments

@zachlatta
Copy link
Owner

Right now the program just fails and exits if it encounters errors. Ideally it'd print out recipients that it failed on. Maybe write them to a CSV?

Might also be a good idea to parse templates before sending.

@zachlatta zachlatta reopened this May 2, 2014
@zachlatta
Copy link
Owner Author

Reminder to self to take care of this.

@maxandersen
Copy link

I just bumped into this.

Emailed recipient 24 of 67...
Error sending email: Error sending email: 550 5.1.1 <[email protected]>... User unknown

Worst of all - that user is at line 32, but it says it sent 24 emails...

So did those from line 24 to 32 get the email or not ?

Would be great to fix this - at least by printing out who succesfully received the mail so I could remove them from the list.

@zachlatta
Copy link
Owner Author

Would it be more useful to have the output look something like the following?

So you can grep the response and parse with other unix utilities?

@maxandersen
Copy link

Yes :)

@zachlatta
Copy link
Owner Author

Alright, cool. I'll try to take some time in the near future to
update Postman to V2, which'll play nicer with other unix utilities
and allow proper error checking. I have a flight this weekend, maybe
I can do it then.

Zach Latta http://zachlatta.com https://github.com/zachlatta
https://twitter.com/zachlatta

On Tue, Oct 28, 2014, at 05:51 AM, Max Rydahl Andersen wrote:

Yes :)

— Reply to this email directly or view it on GitHub[1].

Links:

  1. Proper error handling #1 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants