search for: f33

...rector1.rz.hs-example.de 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING MAIL FROM:<hs at schlittermann.de> 250 2.1.0 OK RCPT TO:<heiko at hs-example.de> 250 2.1.5 OK And here is, what TCPDUMP sees (cut for clarity): 00:22:23.029251 IP6 2001:638:914:f33::5:1.59466 > 2001:638:914:f33::5:ff.2525: Flags [S], 00:22:23.029376 IP6 2001:638:914:f33::5:ff.2525 > 2001:638:914:f33::5:1.59466: Flags [S.], 00:22:23.029660 IP6 2001:638:914:f33::5:1.59466 > 2001:638:914:f33::5:ff.2525: Flags [.], 00:22:23.051436 IP6 2001:638:914:f33::5:ff...

...2.2.9 with a director/backend setup. The user base is about 4711 users currently. If I start at one of the directors doveadm search -A all savedbefore 5000d it terminates with doveadm(1rrissma): Error: doveadm server disconnected before handshake: EOF doveadm(1rrissma): Error: 2001:638:913:f33::5:ff:24245: Command search failed for 1phaaman: EOF doveadm(1rrissma): Error: doveadm server failure doveadm: Error: Failed to iterate through some users The backend logs about that ... Feb 12 23:09:41 backend1 dovecot: doveadm(2001:638:913:f33::5:1,1mstrei2): Error: doveadm search: Client sent...

.... `host directors.<domain>` returns one A and AAA for each of the two directors: directors.<domain> has address 149.x.y.96 (director1) directors.<domain> has address 149.x.y.97 (director2) directors.<domain> has IPv6 address 2001:x:y:f33::5:1 (director1) directors.<domain> has IPv6 address 2001:x:y:f33::5:2 (director2) But connecting the the neighbor director gives: Oct 13 21:23:29 director1 dovecot: director: Warning: Director 2001:x:y:f33::5:2:9090/left disconnected us with reason: Invalid input: ME 149.x.y.96 909...

On 14 Oct 2015, at 00:34, Heiko Schlittermann <hs at schlittermann.de> wrote: > > Hi Timo, > > Heiko Schlittermann <hs at schlittermann.de> (Di 13 Okt 2015 22:33:23 CEST): >>> Does the attached patch work? Compiles, but untested. >> I'm about to test it. > > It seems to update the struct mail_host, but it looks as if the data > in mail_host

...I can check this further tomorrow. > > I've put an i_warning("*** %s: ...", __FUNCTION__, ...) into several places. > > Oct 14 00:02:33 director1 dovecot: director: Warning: *** login_host_callback: OK#0112#011user=foo#011proxy#011ssl=yes#011nopassword=y#011lip=2001:x.y:f33::5:1#011lport=993#011pass=x#011proxy_refresh=450#011host=2001:x.y:f33::5:fe > > Here it seems that the director doesn't send it's knowledge about the > hostname. > > Here some other output, to show that the host list contains names and addresses: > > Oct 14 00:02:32...

...;domain>` returns one A and AAA for each > of the two directors: > > directors.<domain> has address 149.x.y.96 (director1) > directors.<domain> has address 149.x.y.97 (director2) > directors.<domain> has IPv6 address 2001:x:y:f33::5:1 (director1) > directors.<domain> has IPv6 address 2001:x:y:f33::5:2 (director2) > > But connecting the the neighbor director gives: > > Oct 13 21:23:29 director1 dovecot: director: Warning: Director 2001:x:y:f33::5:2:9090/left disconnected us with reason: Invalid...

...orrectly. > > I can check this further tomorrow. I've put an i_warning("*** %s: ...", __FUNCTION__, ...) into several places. Oct 14 00:02:33 director1 dovecot: director: Warning: *** login_host_callback: OK#0112#011user=foo#011proxy#011ssl=yes#011nopassword=y#011lip=2001:x.y:f33::5:1#011lport=993#011pass=x#011proxy_refresh=450#011host=2001:x.y:f33::5:fe Here it seems that the director doesn't send it's knowledge about the hostname. Here some other output, to show that the host list contains names and addresses: Oct 14 00:02:32 director1 dovecot: director: Warnin...

...The other one is using an unpatched version of dovecot. If I shutdown the other director instance, it seems to work. Tomorrow I'll do more testing. Good work, thank you. BTW: I've put there an IPv6 address into the director_servers list (not an DNS name). director_servers = 2001:x:y:f33::5:1 ? inet_listener { address = :: port = 9090 } it doesn't recognize itself: Oct 14 01:06:13 director1 dovecot: director: Fatal: director_servers doesn't list ourself director_servers = 2001:x:y:f33::5:1:9090 ? inet_listener { address = :...

Over the last several days, I've been working hard to get all of the Fedora R packages rebuilt against R 4.0 in rawhide (in the F33-R-4 side tag). With the exception of R-biomaRt, R-BSgenome, R-GenomicAlignments, and R-rtracklayer, I believe everything is built and updated to the latest versions. And of those packages, they're all ready to go when Fedora infrastructure is working reliably again (the great datacenter migrati...

...it seems (not checked in the source yet), that for SSL certificate verification the director doesn't know the original host name anymore. The certificate's CN gets compared to the IP address the director connects to. Oct 12 23:56:51 director2 dovecot: director: Error: director(2001:683:921:f33::5:1:9090/out): connect() failed: Connection reset by peer Oct 12 23:57:53 director2 dovecot: imap-login: Error: proxy: hostname doesn't match SSL certificate at 2001:683:921:f33::5:fe:993: user=<foo>, method=PLAIN, rip=2001:638:912:f33::1:1, lip=2001:638:912:f33::5:2, TLS, session=<fL...

...lly, it runs a command like this for a SMB backup of a PC: /usr/bin/smbclient \\\\new-pelican\\C\$ -U backup -E -d 2 -c tarmode\ full -Tc - Output is piped to BackupPC utilities that unpack and index the backup, and do other housekeeping My backups have consistently failed since my upgrade to F33 (were working without problems for years before, and most recently on F32). Looking closely, it appears 'smbclient' is crashing after passing exactly 47 files. (BackupPC then quits after data stops coming in.) I've run this command at the command-line; it runs for a few seconds the...

...>> /usr/bin/smbclient \\\\new-pelican\\C\$ -U backup -E -d 2 -c tarmode\ >> full -Tc - >> >> Output is piped to BackupPC utilities that unpack and index the >> backup, and do other housekeeping >> >> My backups have consistently failed since my upgrade to F33 (were >> working without problems for years before, and most recently on F32). >> >> Looking closely, it appears 'smbclient' is crashing after passing >> exactly 47 files. (BackupPC then quits after data stops coming in.) >> >> I've run this command...

...-05 week3 2.735904e-05 -1.151881e-05 7.413345e-07 -1.532306e-05 week4 4.880167e-04 -7.139705e-05 1.360150e-05 -2.548684e-04 Residual Deviance: 143.6754 AIC: 257.6754 -------------- next part -------------- > nose126s2.mu <- multinom(Spoilage ~ F25 + F26 + F27 + F28 + F29 + F30 + F31+ F32 + F33 + F34 + F35+ F36 + F37 + F38 + F39+ F40 + F41 + F42 +F43 + F44 + F45 + F46 + F47 + F48 + F49 + F50 + F51 + F52 + F53 + F54 + F55 + F56 + F57 + F58 + F59 + F60 + F61 + F62 + F63 + F64 + F65 + F66 + F67 + F68 + F69 + F70 + F71 + F72 + F73 + F74 + F75 + F76 + F77 + F78 + F79 + F80 + F81 + F82 + F83 +...

...s for a SMB backup of a PC: > >/usr/bin/smbclient \\\\new-pelican\\C\$ -U backup -E -d 2 -c tarmode\ >full -Tc - > >Output is piped to BackupPC utilities that unpack and index the >backup, and do other housekeeping > >My backups have consistently failed since my upgrade to F33 (were >working without problems for years before, and most recently on F32). > >Looking closely, it appears 'smbclient' is crashing after passing >exactly 47 files. (BackupPC then quits after data stops coming in.) > >I've run this command at the command-line; it run...

On Tue, 9 Jun 2020 at 04:42, Tom Callaway <tcallawa at redhat.com> wrote: > > Over the last several days, I've been working hard to get all of the Fedora > R packages rebuilt against R 4.0 in rawhide (in the F33-R-4 side tag). With > the exception of R-biomaRt, R-BSgenome, R-GenomicAlignments, and > R-rtracklayer, I believe everything is built and updated to the latest > versions. And of those packages, they're all ready to go when Fedora > infrastructure is working reliably again (the grea...

On Tuesday, 9 June 2020 03.40.52 WEST Tom Callaway wrote: > Over the last several days, I've been working hard to get all of the Fedora > R packages rebuilt against R 4.0 in rawhide (in the F33-R-4 side tag). With > the exception of R-biomaRt, R-BSgenome, R-GenomicAlignments, and > R-rtracklayer, I believe everything is built and updated to the latest > versions. And of those packages, they're all ready to go when Fedora > infrastructure is working reliably again (the grea...

..., Jul 6, 2020 at 10:40 AM Jos? Ab?lio Matos <jamatos at fc.up.pt> wrote: > On Tuesday, 9 June 2020 03.40.52 WEST Tom Callaway wrote: > > Over the last several days, I've been working hard to get all of the > Fedora > > R packages rebuilt against R 4.0 in rawhide (in the F33-R-4 side tag). > With > > the exception of R-biomaRt, R-BSgenome, R-GenomicAlignments, and > > R-rtracklayer, I believe everything is built and updated to the latest > > versions. And of those packages, they're all ready to go when Fedora > > infrastructure is working...

often when I "try to" visit the scriptaculous, it crashes IE - does anybody else experience this as well? _________________________________________________________________ FREE pop-up blocking with the new MSN Toolbar – get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/

Hi folks, years ago I had no problem installing CentOS7 on my iMac workstation (iMac Late 2015). The installation worked out of the box. Today I wanted to upgrade to CentOS8 and while configuring the partitions I get an error that the installation can not start because: "HFS+ ESP needed and mounted on /boot/efi". In fact they are the same partition as for CentOS7. Is this a regression

Please excuse my ignorance as I''m a linux newbie. Basically I have a setup of an adsl ethernet modem (nated and then everything forwarded to the external ip of my Mandrake mnf firewall) connected to the mnf firewall which then connects to the lan. internet <--> adsl modem <--> mnf firewall <--> lan There''s only 2 nics in the mnf firewall so it''s a