I can´t get the email function to work...
I have set up Mail with SMTP server (I can successfully send mail from the Mail application)
I have selected "Automatically send emails for overdue borrowed entries in DVDpedia Preferences.
Outgoing mails will show up in the Outgoing Emails list, but it can´t send it.. if I try to click Send now button, nothing happens, I looks like it is trying, because of the spinning progress-thingy to the left for the "Send now" button... but the minutes will go negative and nothing is sent.
I have tried to have mail application closed and open, no difference.. If I select "Email Borrower" it will open Mail and I can send the email successfully.
What am I missing?
Outgoing Emails....
Re: Outgoing Emails....
Thank you for the bug report. Seems the latest release of Snow Leopard changed the way they store default port information for the mail accounts. DVDpedia was failing to connect to the mail server with the missing information. Please download the latest DVDpedia beta 38 where the issue is fixed. With this version after the progress spinning indicator is done the email messages should have been sent and due date should be moved forward (14 days by default).
Re: Outgoing Emails....
Oki doki, but I´m not running 10.6...
I am on 10.5.8 and I am up to date with DVDpedia, but still no outgoing emails... Do I have to downgrade DVDpedia to get "outgoing emails" to play with 10.5.8?
I am on 10.5.8 and I am up to date with DVDpedia, but still no outgoing emails... Do I have to downgrade DVDpedia to get "outgoing emails" to play with 10.5.8?
Re: Outgoing Emails....
Download the latest beta, the outgoing emails should work for you without trouble. If not, please let us know.
Re: Outgoing Emails....
I have similar issues with sending due emails to borrowers. I'm running Bookpedia 4.6.5 on OS X 10.6.7.
E-mails are not sent and when sending manually the wheel just keeps spinning; at the same time following error is logged:
Bookpedia has asked permissions to use keychain and I've granted 'always allow' permissions.
E-mails are not sent and when sending manually the wheel just keeps spinning; at the same time following error is logged:
Code: Select all
2011-06-02 11:49:23 Bookpedia[9265] Call stack: (
0 Pediabase 0xc0f89f4f -[NSException(NSExceptionExtensions) printStackTrace] + 100
1 Pediabase 0xc0f34829 -[MyControllerShared(ApplicationNotifications) exceptionHandler:shouldHandleException:mask:] + 126
2 ExceptionHandling 0x922b9260 -[NSExceptionHandler _handleException:mask:] + 1264
3 ExceptionHandling 0x922b8d52 NSExceptionHandlerExceptionRaiser + 228
4 libobjc.A.dylib 0x98a28509 objc_exception_throw + 56
5 CoreFoundation 0x93428a21 -[NSException raise] + 17
6 EDMessage 0x3500c4ea -[EDMailAgent _getStream] + 906
7 EDMessage 0x3500cbb0 -[EDMailAgent sendMailWithHeaders:body:andAttachments:] + 753
8 EDMessage 0x3500bc59 -[EDMailAgent sendMailWithHeaders:andBody:] + 56
9 Pediabase 0xc0f035e8 -[JBMailer sendMailsAutomatic:] + 2199
10 Foundation 0x962e6ad0 -[NSThread main] + 45
11 Foundation 0x962e6a80 __NSThread__main__ + 1499
12 libSystem.B.dylib 0x936f47fd _pthread_start + 345
13 libSystem.B.dylib 0x936f4682 thread_start + 34
)
2011-06-02 11:49:23 Bookpedia[9265] An uncaught exception was raised
2011-06-02 11:49:23 Bookpedia[9265] Authentication failed.
2011-06-02 11:49:23 Bookpedia[9265] Call stack: (
0 Pediabase 0xc0f89f4f -[NSException(NSExceptionExtensions) printStackTrace] + 100
1 Pediabase 0xc0f34829 -[MyControllerShared(ApplicationNotifications) exceptionHandler:shouldHandleException:mask:] + 126
2 ExceptionHandling 0x922b9260 -[NSExceptionHandler _handleException:mask:] + 1264
3 ExceptionHandling 0x922b8b36 NSExceptionHandlerUncaughtExceptionHandler + 328
4 CoreFoundation 0x933dd7c9 __raiseError + 681
5 libobjc.A.dylib 0x98a28509 objc_exception_throw + 56
6 Pediabase 0xc0f036cc -[JBMailer sendMailsAutomatic:] + 2427
7 Foundation 0x962e6ad0 -[NSThread main] + 45
8 Foundation 0x962e6a80 __NSThread__main__ + 1499
9 libSystem.B.dylib 0x936f47fd _pthread_start + 345
10 libSystem.B.dylib 0x936f4682 thread_start + 34
)
Re: Outgoing Emails....
Try out the Bookpedia beta if it's the same issue as above it will be resolved. Otherwise, this version of the beta will print out the email account it's trying to use to your console log, so that you may verify both in Mail and the Keychain that you have the correct password saved for the the account that is trying to send. It will be in your keychain under "internet password" with the name being the host name.
Re: Outgoing Emails....
Problem solved -- thanks for help.
It appears there were two entries for smtp.gmail.com in Keychain, one with current password and one with old password. Apparently Bookpedia was using the old version. After deleting the old one everything worked smoothly.
I reckon I wouldn't have noticed the issue without the extra debugging information. And on a sidenote, I think there is a actual SW defect in Bookpedia since it did not catch the (authentication) exception..
It appears there were two entries for smtp.gmail.com in Keychain, one with current password and one with old password. Apparently Bookpedia was using the old version. After deleting the old one everything worked smoothly.
I reckon I wouldn't have noticed the issue without the extra debugging information. And on a sidenote, I think there is a actual SW defect in Bookpedia since it did not catch the (authentication) exception..
Re: Outgoing Emails....
Glad you where able to get rid of the extra entry in the keychain with the wrong password. Bookpedia asks the Mac to supply the password and there is no reference to what criteria the keychain would use to select a unique item when there are several with the same host and account name.
The exception comes from an open source messaging framework we use called EDMessage. I agree that Bookpedia should gracefully log the error and continue running than honor the exception. I have changed that for the next version and also added the host information from the debug version into the error message to make it more useful.
The exception comes from an open source messaging framework we use called EDMessage. I agree that Bookpedia should gracefully log the error and continue running than honor the exception. I have changed that for the next version and also added the host information from the debug version into the error message to make it more useful.