on 5/2/2012 9:36 AM Prabhpal S. Mavi spake the following:
>
>> ntpdate should be run just once and then just have ntpd on.. the nptdate
>> should bring the server to the proper time and cause dovecot to
>> fail..you should only need to run it once (assuming the server is left
>> on and not off for
> ntpdate should be run just once and then just have ntpd on.. the nptdate
> should bring the server to the proper time and cause dovecot to
> fail..you should only need to run it once (assuming the server is left
> on and not off for long periods).
> I run ntpd as a daemon, but not ntpdate...
> y
On 5/2/2012 12:16 PM, Prabhpal S. Mavi wrote:
>>> But when i restarted the server, dovecot failed to start on boot (it is
>>> virtual machine). with this error.
>>>
>>> dovecot: dovecot: Fatal: Time just moved backwards by 537 seconds. This
>>> might cause a lot of problems, so I'll just kill mysel
>> But when i restarted the server, dovecot failed to start on boot (it is
>> virtual machine). with this error.
>>
>> dovecot: dovecot: Fatal: Time just moved backwards by 537 seconds. This
>> might cause a lot of problems, so I'll just kill myself now.
>>
>> immediately then, i tried to send one
On 5/2/2012 7:51 AM, Prabhpal S. Mavi wrote:
> Hello Mike,
>
> that actually worked!! i configured ntpd& ntpdate& restarted the server.
> But when i restarted the server, dovecot failed to start on boot (it is
> virtual machine). with this error.
>
> dovecot: dovecot: Fatal: Time just moved backw
> Hello, Prabh.
>
> Your answer lies in the info you provided:
>
> domainkeys=neutral (no sig); from=digital-infotech.net; dkim=permerror
> (future timestamp)
>
> Yahoo appears to think that your timestamp is off by some amount of time
> in the future.
>
> --
> Mike Burger
Hello Mike,
that actua
> Hello, Prabh.
>
> Your answer lies in the info you provided:
>
> domainkeys=neutral (no sig); from=digital-infotech.net; dkim=permerror
> (future timestamp)
>
> Yahoo appears to think that your timestamp is off by some amount of time
> in the future.
>
> --
> Mike Burger
> http://www.bubbanfrien
> Hello, Prabh.
>
> Your answer lies in the info you provided:
>
> domainkeys=neutral (no sig); from=digital-infotech.net; dkim=permerror
> (future timestamp)
>
> Yahoo appears to think that your timestamp is off by some amount of time
> in the future.
>
> --
> Mike Burger
> http://www.bubbanfrien
> Hi Dear Community Friends,
>
> it is few days now, i am trying to figure out why DKIM is working / not
> working. Any assistance would be very much appreciable.
>
> Server IP is not blacklisted ever, MX, PTR SPF, DKIM records are available
> in DNS. why it is working at Gmail, why failing at Yah
Hi Dear Community Friends,
it is few days now, i am trying to figure out why DKIM is working / not
working. Any assistance would be very much appreciable.
Server IP is not blacklisted ever, MX, PTR SPF, DKIM records are available
in DNS. why it is working at Gmail, why failing at Yahoo?
Gmail
dk
10 matches
Mail list logo