On Tue, 2016-02-16 at 22:25 +, Johnson, Brett E (HP Cloud Linux R&D) wrote:
> I've noticed that, using evolution-ews, evolution almost always base64-encodes
> the body of my messages. Yet, if I send the same message via SMTP, it is not
> encoded.
If anyone else is interested, I figured out an
On 03/07/2016 09:26 AM, Patrick O'Callaghan wrote:
> A quick way to check on DNS lookups is to specify the server directly,
> e.g.:
>
> % dig @8.8.8.8 foo.bar.com
And something I always do to check what the system thinks the IP is: use
ping. For example:
$ ping core-01
PING core-01 (172.17.8.101
On Mon, 2016-03-07 at 15:59 +0100, Milan Crha wrote:
> On Mon, 2016-03-07 at 13:26 +, Denny wrote:
> >
> > >
> > > Can it be that you have cached the DNS resolution in the system,
> > > or
> > > overwritten in /etc/hosts [...]
> > Well that's embarrassing. Yes, I had apparently left a line i
On Mon, 2016-03-07 at 13:26 +, Denny wrote:
> > Can it be that you have cached the DNS resolution in the system, or
> > overwritten in /etc/hosts [...]
>
> Well that's embarrassing. Yes, I had apparently left a line in
> /etc/hosts from when I was setting up the old server a few years ago.
Hi,
On 2016-03-07 09:30, Milan Crha wrote:
On Mon, 2016-03-07 at 01:32 +, Denny wrote:
When I fired Evolution back up after completing all the transfers, I
got
a message for each account asking me to accept new SSL certificates,
but
unexpectedly the Evolution messages give the old serve
On Mon, 2016-03-07 at 01:32 +, Denny wrote:
> When I fired Evolution back up after completing all the transfers, I got
> a message for each account asking me to accept new SSL certificates, but
> unexpectedly the Evolution messages give the old server name,
> vortex.shinyideas.co.uk. If I a
