Topic: Another post upgrade problem

[toothandnail]

I've just noticed this, though I should have picked it up earlier....

The machine I updated a last week is an internet gateway. As well as that machine, the company has a server-only SME box (also an IBM X series rack). That machine is used purely as a file server, and was updated to SME 8 some months ago.

Normally, that machine forwards admin messages to me. That includes messages that I generate as part of the backup procedure, update messages, etc.

The trouble is, naturally, that those messages are now being rejected by the newly upgraded SME8 gateway machine, since they're not using encrypted connections.

So, my question is, is there any way to get those internal status messages sent? I use synbak (http://www.initzero.it/products/opensource/synbak/) in a script to do normal system backups, as well as my own custom script using rsync to backup the main file data (currently sitting at around 370 GB) to an NFS mounted NAS. Status messages have been sent using things like this in my scripts:

Code: [Select]

cat /root/log/r-run | mail -s "Bantam backup status" paul.marwick@xxxx.com
The status messages are very useful indeed, since they give me a good indication of any problems that occur, so I would hate to lose them. Is there any way in a script to get an encrypted connection to the mail server on the gateway machine?

Paul.

[CharlieBrady]

Change the mail address in the script to admin@your.sme8.box, and then set the email forwarding address for the admin account on your SME8 box (you've probably already done this step).

[toothandnail]

Change the mail address in the script to admin@your.sme8.box, and then set the email forwarding address for the admin account on your SME8 box (you've probably already done this step).

Thanks for the suggestion, Charley. I must be doing something wrong though - not getting very far with it so far.

I've tried setting the email address to admin on the sever only SME8, as well as setting it to admin on the gateway SME8. If the address is set to the gateway machine, I get relaying denied messages. If I set it to admin on the server only machine, I get this:

Code: [Select]

@4000000050a4c4f01eb1b82c info msg 59689468: bytes 3059 from <> qp 18879 uid 101                                                                                                                           
@4000000050a4c4f01ee372a4 starting delivery 262: msg 59689468 to remote gemini@brillcomputers.co.uk                                                                                                       
@4000000050a4c4f01ee37a74 status: local 1/10 remote 1/20                                                                                                                                                   
@4000000050a4c4f01ee37e5c delivery 261: success: did_0+1+1/qp_18879/                                                                                                                                       
@4000000050a4c4f01ee38244 status: local 0/10 remote 1/20                                                                                                                                                   
@4000000050a4c4f01ee3862c end msg 59689484                                                                                                                                                                 
@4000000050a4c4f0203552bc delivery 262: deferral: Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/                                                                                         
@4000000050a4c4f020355a8c status: local 0/10 remote 0/20 
Not sure what to try next....

Paul.

[CharlieBrady]

I've tried setting the email address to admin on the sever only SME8, as well as setting it to admin on the gateway SME8. If the address is set to the gateway machine, I get relaying denied messages. If I set it to admin on the server only machine, I get this:

The serveronly machine needs to be configured to use the gateway machine as its SmartHost. Use smtps, and configure with a username/password for outbound SMTP.

The message you showed has <> as the sender. That's usually a bounce message, and bounce messages are not always delivered by ISPs. Does your NAS really use an empty sender address when it sends status messages?

[CharlieBrady]

The status messages are very useful indeed, since they give me a good indication of any problems that occur, so I would hate to lose them.

Perhaps you can collect them using IMAP from that system. Have that system deliver them locally, and pull them directly from the NAS. You'll need to remember to look.