Displaying 20 results from an estimated 50000 matches similar to: "POP3 logging in wrong timezone"
2020 Apr 24
4
Timezone conversion on Ubuntu 20.04
Hi all,
I am testing R 4.0 and ran into an issue with timezones on Ubuntu
Focal: converting a timestamp to another timezone results in NA:
as.POSIXct(as.POSIXlt(Sys.time(), tz = "CET"), tz = "EST")
This only happens on Ubuntu Focal, it seems to work fine on Ubuntu
Bionic. I am the standard ubuntu docker image icw/ r-base from Dirk's
ppa:edd/r-4.0 on both systems.
Am I
2008 Nov 24
1
timezone attribute lost
Hi,
As I didn't get any response on the general help list and I don't know
if there is a bug in action I am trying my luck here.
I was highly surprised to find out that during simple operations (see
code below) the timezone attribute for POSIXct data is lost and then,
upon the next interpretation, the system settings are used (which are
plain wrong in my case).
I have used R 2.8.0
2017 Oct 20
1
Another issue with Sys.timezone
>>>>> Stephen Berman <stephen.berman at gmx.net>
>>>>> on Thu, 19 Oct 2017 17:12:50 +0200 writes:
> On Wed, 18 Oct 2017 18:09:41 +0200 Martin Maechler <maechler at stat.math.ethz.ch> wrote:
>>>>>>> Martin Maechler <maechler at stat.math.ethz.ch>
>>>>>>> on Mon, 16 Oct 2017 19:13:31 +0200
2020 Oct 02
2
timezone tests and R-devel
Yes, the potential issue I see is that
make check
fails when I explicitly set TZ. However, I set it to be the same as what
the system reports when I login.
Details: The system (RHEL) I am working on has
$ strings /etc/localtime | tail -n 1
EST5EDT,M3.2.0,M11.1.0
$ date +%Z
EDT
$ echo $TZ
US/Eastern
On Fri, Oct 2, 2020 at 9:48 AM Sebastian Meyer <seb.meyer at fau.de> wrote:
> Thank
2008 Sep 22
8
TimeZone daylight savings time problems
Here is the following from my console:
>> Time.now
=> Mon Sep 22 11:33:34 +0200 2008
>> Time.now.utc_offset
=> 7200
>> TimeZone[Time.now.utc_offset]
=> #<TimeZone:0x11aea90 @tzinfo=nil, @utc_offset=7200, @name="Athens">
>> Time.now.in_time_zone(TimeZone[Time.now.utc_offset])
=> Mon, 22 Sep 2008 12:34:22 EEST +03:00
(I am in Spain - CET - and
2008 Jan 11
2
Syslog timezone issue
We recently upgraded (as in, backup, reinstall, selective restore) a
couple of servers from CentOS-3.9 to CentOS-5.1. This generally went
smoothly but we've encountered one confusing problem with syslog.
Under CentOS-3, syslog entries were always dated in the host local
timezone. With CentOS-5.1, they're dated in UTC *most* of the time,
but occasionally in the local timezone. This has
2017 May 18
2
[R] R-3.4.0 fails test
This has to do with your own timezone. If I run that code on my computer,
both formats are correct. If I do this after
Sys.setenv(TZ = "UTC")
Then:
> cbind(format(dlt), format(dct))
[,1] [,2]
[1,] "2016-12-06 21:45:41" "2016-12-06 20:45:41"
[2,] "2016-12-06 21:45:42" "2016-12-06 20:45:42"
The reason for that, is that
2005 Apr 05
2
Dovecot 1.0 POP3 login but no mail
Dovecot is installed on the hosted FC1 server I have, it was working fine
until yesterday when they had to bounce the server. I can login fine from
Outlook or connect telnet <hostname> 110. But even though I can see sendmail
has received mail into my %h/.maildir (via webmail's user mail facility)
when I log into dovecot via Outlook it does not retrieve any of it.
I tried from W2K
2017 May 18
2
[R] R-3.4.0 fails test
> On 18 May 2017, at 13:47 , Joris Meys <jorismeys at gmail.com> wrote:
>
> Correction: Also dlt uses the default timezone, but POSIXlt is not recalculated whereas POSIXct is. Reason for that is the different way values are stored (hours, minutes, seconds as opposed to minutes from origin, as explained in my previous mail)
>
I would suspect that there is something more subtle
2016 Mar 12
2
Regression in strptime
On 3/12/16 12:33 AM, peter dalgaard wrote:
>> On 12 Mar 2016, at 00:05 , Mick Jordan <mick.jordan at oracle.com> wrote:
>>
>> This is definitely obscure but we had a unit test that called .Internal(strptime, "1942/01/01", %Y/%m/%d") with timezone (TZ) set to CET.
> Umm, that doesn't even parse. And fixing the typo, it doesn't run:
>
>>
2024 Oct 10
2
Time zones in POSIClt objects
Thanks.
On 10/10/24 16:13, Jeff Newmiller wrote:
> POSIXt vectors do not support different time zones element-to-element.
> I complained about this on this list a couple of decades ago, and was
chastised for it. Evidently handling timezones per element was
considered to be too impractically slow to be a standard feature.
This is where it is unclear to me what the purpose is of the
2024 Oct 10
2
Time zones in POSIClt objects
POSIXt vectors do not support different time zones element-to-element.
If you want to keep track of timezones per element, you have to create a vector of timestamps (I would recommend POSIXct using UTC) and a parallel vector of timezone strings. How you manipulate these depends on your use cases, but from R's perspective you will have to manipulate them element-by-element.
I complained about
2016 Nov 21
4
nologin + reason -> logging reason
Hi.
I'm using nologin with own reason [1]. That works fine. For example pop3
client gets nice message like "-ERR [AUTH] Account is locked. Please contact
support."
Unfortunately maillog lacks information details about why user was not allowed
to log in.
pop3-login: Disconnected (auth failed, 1 attempts in 2 secs): user=<testuser>,
method=LOGIN, rip=1.1.1.1, lip=2.2.2.2,
2020 Oct 01
3
timezone tests and R-devel
The return value of Sys.time() today with a timezone of US/Eastern is
unchanged between 4.0.3-patched and devel, but on devel the following test
fails
all.equal(x, as.POSIXlt(x))
with
x = Sys.time()
This means that devel does not complete make tests (failure on
tests/reg-tests-2.R)
It is entirely possible that it is an error on my end, I use
export TZ="US/Eastern"
but I have been
2013 Jan 11
1
Date time conversion bug (as.POSIXct)?
There is something wrong, I think, with the date-time conversion from a
numeric value if you use Central European Time (CET) as timezone.
Examples from R:
If I use the GMT time zone it is OK, I get the same time back from
as.POSIXct as I entered
> as.POSIXct(as.numeric(strptime("30/01/2012 13:00:00", format="%d/%m/%Y
>
2017 Oct 18
2
Another issue with Sys.timezone
>>>>> Martin Maechler <maechler at stat.math.ethz.ch>
>>>>> on Mon, 16 Oct 2017 19:13:31 +0200 writes:
>>>>> Stephen Berman <stephen.berman at gmx.net>
>>>>> on Sun, 15 Oct 2017 01:53:12 +0200 writes:
> > (I reported the test failure mentioned below to R-help but was advised
> > that this list is
2024 Oct 10
1
Time zones in POSIClt objects
Sys.setenv(TZ = "GMT") will set the local time zone to GMT so there
would only be one time
zone regardless of whether local or GMT were used.
On Thu, Oct 10, 2024 at 11:17?AM Jan van der Laan <rhelp at eoos.dds.nl> wrote:
>
> Thanks.
>
> On 10/10/24 16:13, Jeff Newmiller wrote:
> > POSIXt vectors do not support different time zones element-to-element.
>
>
2008 Dec 09
8
pop3 attack
I was looking at my maillog and it looks like someone is trying to get
into my pop3 server.
Dec 9 15:28:54 mailserver dovecot: pop3-login: Aborted login: user=<alexis>, method=PLAIN, rip=::ffff:66.167.184.203, lip=::ffff:192.168.1.2
Dec 9 15:29:08 mailserver dovecot: pop3-login: Aborted login: user=<alfonso>, method=PLAIN, rip=::ffff:66.167.184.203, lip=::ffff:192.168.1.2
Dec 9
2016 Mar 15
4
Regression in strptime
>>>>> peter dalgaard <pdalgd at gmail.com>
>>>>> on Sat, 12 Mar 2016 19:11:40 +0100 writes:
> OK, .Internal is not necessary to reproduce oddity in this area. I also see things like (notice 1980)
>> strptime(paste0(sample(1900:1999,80,replace=TRUE),"/01/01"), "%Y/%m/%d", tz="CET")
...............
>
2016 Mar 11
2
Regression in strptime
This is definitely obscure but we had a unit test that called
.Internal(strptime, "1942/01/01", %Y/%m/%d") with timezone (TZ) set to
CET. In R-3.1.3 that returned "1942-01-01 CEST" which, paradoxically, is
correct as they evidently did strange things in Germany during the war
period. Java also returns the same. However, R-3.2.4 returns "1942-01-01
CET".