Retrospect Unable To Send Email Out

[abb668b8-e67d-45d2-8fe4-b2a87dc2831e]

In the past Retrospect has been able to send out emails. However, now when I send a test email, no email arrives.

 

If I look in the console I see the error message:

 

6/9/11 10:52:25 AM Retrospect[2402] PreferencesEmailController::sendTestEmail exception: E-mail notification failed: error -519 ( network communication failed)

 

I can ping the mail server from the same computer.

I can send out emails using Apple Mail using the same settings that I've entered into Retrospect.

 

Is there a way to see more details about this error so I can figure out why Retrospect can't send emails out?

[Lennart_T]

I think there is a bug when sending test emails.

The "real" ones should work fine regardless.

[Mayoff]

Try including the port number after the server name or IP

 

server:port

[abb668b8-e67d-45d2-8fe4-b2a87dc2831e]

The send test email has worked for me in the past, and I am still not getting emails during normal operation.

 

I tried entering in the port after the IP of the SMTP server, when I did, Retrospect became unresponsive and I force quit the application. While it was hung I took a sample of the process.

Edited June 13, 2011 by backup zen

[fb8af8c4-dd0f-470e-99c8-1c13979512b6]

Some additional information on this as I've discovered the same issue.

 

My mail server only has port 25/SMTP open. And entering my SMTP server as "mail.servername.com", I see the following behavior:

 

• When I click the send test email button, retrospect tries to connect via port 587 (SMTP submission port). Because my server doesn't allow that port, it fails. Unfortunately, Retrospect immediately freezes, displays the BBOD (Beach Ball Of Death), doesn't make any further network connections, and requires a force quit. I DO NOT receive the test email.
   
  
• When I click the send test email button and block the outgoing port 587 request using my reverse firewall, Retrospect immediately attempts a second connection over the old port 25. Retrospect still freezes, displays the BBOD, and requires a force quit. However, I *DO* receive the test email.
   
  
• When I then relaunch Retrospect after a force quit, I'm seeing that "smtp://" has been added to the mail server address! It doesn't do this if I remove it and quit normally however.
   
  
• When I then click the send test email button with the "smtp://" included, Retrospect acts like it sends the message, but in reality it doesn't attempt to make any outgoing connections and I don't receive the test email.
  

 

To summarize, it appears that:

 

1. If I prefix the mail server with the protocol "smtp://" Retrospect does not send out the test message or make any network connections at all
   
2. If I omit the protocol in the server name and block the initial outgoing 587 SMTP port request at the computer, the test email is delivered over port 25 and received
   
3. Adding the port number to the server setting (eg. mail.servername.com:25) doesn't appear to have any effect
   

 

I have not yet tested the actual notification email because I was concerned that it might cause the Retrospect daemon to freeze. From the other posts here, it sounds like it may be fine however.

 

 

Edit: I can now confirm that although I have problems sending the test email, mail from actual script execution appears to be working fine

Edited July 19, 2011 by Thanehand

[iGary]

Unfortunately, Retrospect immediately freezes, displays the BBOD (Beach Ball Of Death), doesn't make any further network connections, and requires a force quit. I DO NOT receive the test email.

 

[*]When I click the send test email button and block the outgoing port 587 request using my reverse firewall, Retrospect immediately attempts a second connection over the old port 25. Retrospect still freezes, displays the BBOD, and requires a force quit. However, I *DO* receive the test email.

 

 

I'm wrangling with getting an-mail to go out through a corporate firewall. Haven't figured it out yet. But in the process I did discover that Retrospect is not crashed when you send the test e-mail. Be patient and it will come back without having to force quit.

Edited July 20, 2011 by gskibum

[f30e6e60-a263-4d69-8f60-c92703669308]

The test function is broken. The actual mail function works fine, with some limitations depending on your SMTP server.