New answers tagged ubuntu-13.04
Unfortunately, ssmtp does not read ~/.forward. Here is a quote from the ssmtp manpage: It does not do aliasing, which must be done either in the user agent or on the mailhub. Nor does it honor .forwards, which have to be done on the recieving host. It especially does not deliver to pipelines.
Since you asked for suggestions - We recently faced this problem and if like me you don't want to run a OS which is not supported any more, we decided to switch to Debian all together, this might appear over kill to someone but "to each his own". Whole purpose is not to worry about OS not being supported after every 1 year. Ubuntu 13.10 is supported for 9 ...
Someone here could tell you you'll be fine but how will they know for sure ? Surely the correct thing to do here is to test the upgrade for each of your server types. You know, for each $ServerType Spin up a new instance configure it as per $ServerType, run your test suite do the upgrade run test suite analyze the results
The best option would be to do a graceful restart (service apache2 reload) in order to have the config become active without downtime (the new process takes over the listener while the old process completes any active requests). To automate this you'd need something watching the files then restarting the service.. probably not worth the effort if you're ...
Top 50 recent answers are included