search for: xforward

Package: logcheck-database Version: 1.3.13 Severity: wishlist Hi, after upgrading Postfix from 2.7.1-1 to 2.8.1-1 (using testing) parts of the log format from postfix/smtpd have changed. This problem only seems to trigger when accepting connections in smtpd using XFORWARD (http://www.postfix.org/XFORWARD_README.html), for example when Amavisd-new reinjects mail to postfix. The new log lines look like this: Mar 9 15:15:53 hostname postfix/smtpd[5100]: 056DA13C1C0: client=localhost[127.0.0.1], orig_client=host.domain.tld[1.2.3.4] In version 2.7.1-1, the whole ori...

OS: Tru64 5.1 OpenSSH version: 3.2.2p1 and higher. Problem: after upgrading sshd my servers no longer forward X11 connections. I ran the server as 'sshd -d' and saw that the server was successfully creating and binding the IPV6 socket but failing to bind the IPV4 socket. The error message is: Bind to port 22 on 0.0.0.0 failed: Address already in use. Also, when channels.c tries to open

Package: logcheck-database Version: 1.3.13 Severity: normal Tags: patch Hi, after examining the code for postfix/smtpd, the following parameters for that specific log line can be present: client, sasl_method, sasl_username, sasl_sender, orig_queue_id, orig_client "client" is always present, the others are added where applicable, but always in the order explained above. There have been

...ne piece giving me some problem-- a component which gives status info via a GUI. In the past, on previous installations, I could ssh to the bacula server with the -X option, and run the application (called 'bat'), and it would display back.? I'd have to make sure the sshd_config permits Xforwarding, but that was all. On my new CentOS 6.4 minimal, I always get: bat: cannot connect to X server I tried the usual tricks of exporting the display to my system where I want to see the GUI, which shouldn't be necessary anyway due to the 'ssh -X', but I thought I'd give it a shot...

http://wine.1045685.n5.nabble.com/file/n3244941/mons.rar mons.rar I need help with this application.. It's a small monitor (for Win32) wich connects to the SCADA server. In Windows it's uses Exceed (X Windows for Win32), but I want to run it in Ubuntu 10.10... Wine run this mons.exe, but it's didn't connect.. ('could not establish connection'), firewall down. What

...oxes. The problem is: When I run it from CentOS 3 it's OK form CentOS 4 I cannot find a bad word in logs ... My local machine stoping firewall [root at klima-pc ~]# service iptables stop [root at klima-pc ~]# iptables-save [root at klima-pc ~]# SELinux is OFF I am connecting by ssh with Xforwarding enabled to - Centos 3 box [09:32 root at tux:root]# gvim --sync The program 'gvim' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAtom (invalid Atom parameter)'. (Details: serial 287 error_code 5 request_code 20 minor_code 0)...

...ich I have noticed that something gets written to /root/.cache/mesa every so often (once every several days). It is my understanding that mesa is related to GUI (X11), but on these machines (on neither of my machines, actually) root never logs in to GUI X11. I may have remote root logins with Xforwarding though. Hence my puzzle: what is that that writes to /root/.cache/mesa? Some, but not all of occasions seem to happen upon machine [re]boots. Thanks. Valeri PS This gives me dejavu. A while ago when people started demanding to have google chrome browser installed on their workstations I had...

...xauth cookies Whilst this reasoning does make sense, it presumes one thing - that the users home directory exists on the machine. On a workstation this will generally be the case, but it's not unusual for users/admins not to have home directories on servers, which means that since this patch xforwarding has been broken in such cases. The attached patch (also available at http://www.docbert.org/outgoing/xauthority-in-tmp.patch ) re-introduces this feature via a configuration option "XauthorityInTmp". The default value of this variable is "no" (ie, the default behaviour is...

...61]: 1FCA540467: > to=<andr?@homebox.space>, relay=127.0.0.1[127.0.0.1]:34001, delay=1.4, > delays=0.73/0.02/0.07/0.59, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued > as 6AC3240807) > Apr 05 19:20:46 portal postfix/smtpd[30763]: disconnect from > localhost[127.0.0.1] ehlo=1 xforward=2 mail=1 rcpt=1 data=1 quit=1 > commands=7 > Apr 05 19:20:46 portal postfix/qmgr[21470]: 1FCA540467: removed > Apr 05 19:20:46 portal dovecot[12813]: lmtp(30766): Connect from local > Apr 05 19:20:46 portal dovecot[12813]: lmtp(andre): > WGTdAo6qp1wueAAAeNB+QA: sieve: > msgid=&...

Andr?, are you quite sure you have it working? In this thread someone from Open-Xchange stated that no, Dovecot doesn?t have SMTPUTF8 support implemented, and the same response was given by another Dovecot developer last September (it ?is being considered? was the answer then, see https://dovecot.org/pipermail/dovecot/2018-September/112887.html). I am using LMTP to deliver mail to Dovecot from