Astaro Notifications in SMTP Spool - Page 2

stevenhemelaere · #11 (**permalink**) 06-09-2009, 05:08 PM

OK,

Let's go over it from the start.

First the sender address was put as the standard do-not-reply@fw-notify.net

Then i changed it to my emailaddress@gmail.com

Afterwards, i thought better of that, and changed it to emailaddress@myisp.be

I cleaned out (deleted) everything in the smtp pool to start over

As smarthost i picked the host address of my ip, of which i'm certain, with the authorization put as in my emailclient.

Now, when i retry in the smtp pool, i get the following:

Code:

2009:06:09-18:02:17 hemelaere exim[3199]: 2009-06-09 18:02:17 10Vnhq-0003cN-1J alt2.gmail-smtp-in.l.google.com [209.85.217.70]:25 Connection timed out 
2009:06:09-18:02:18 hemelaere exim[3326]: 2009-06-09 18:02:18 10GgPR-0007JT-1x alt2.gmail-smtp-in.l.google.com [209.85.217.24]:25 Connection timed out 
2009:06:09-18:02:18 hemelaere exim[3325]: 2009-06-09 18:02:18 10GgPR-0007JT-1x == emailaddress@gmail.com R=dnslookup T=remote_smtp defer (110): Connection timed out 
2009:06:09-18:02:18 hemelaere exim[3506]: 2009-06-09 18:02:18 1MDrzR-0004CN-1D == do-not-reply@fw-notify.net R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

Why is he still trying to connect to gmail, and looking up the do-not-reply address?

BAlfson · #12 (**permalink**) 06-09-2009, 08:12 PM

If I understand your situation correctly, I believe that those are emails already in a queue over which you no longer have control in Mail Manager. The easiest way to get rid of the problem is to do a factory reset.

Before that, back up your configuration in an unencrypted file and put it on a USB memory stick. After the factory reset, do a reboot with the memory stick in place and the Astaro will restore the configuration automatically from the backup file.

Cheers - Bob

stevenhemelaere · #13 (**permalink**) 06-11-2009, 05:52 PM

OK,

i wanted to try your suggestion out tonight, checked my mails first, and ... there they were........

Somehow, i don't know why, he just got rid of the problem mails or something, and went on with the latest stuff in the spool.

I'll keep on monitoring to see if it continues to work, however...

BAlfson · #14 (**permalink**) 06-11-2009, 07:08 PM

That's good news. That means the PostgreSQL databases are doing a better job of policing themselves - hio-hip-hooray for the developers!

Cheers - Bob