search for: commands

...ized. >>>> aXB0Pg0KPC9IRUFEPg0KPC9IVE1MPg== **** Command 'axb0pg0kpc9irufepg0kpc9ive1mpg==' not recognized. >>>> >>>> ----------geinwhjqlzkmqlsdwpel-- **** Command '----------geinwhjqlzkmqlsdwpel--' not recognized. >>>> **** No valid commands found. **** Commands must be in message BODY, not in HEADER. **** Help for majordomo@xiph.org: <p>This help message is being sent to you from the Majordomo mailing list management system at majordomo@xiph.org. This is version 1.94.4 of Majordomo. If you're familiar with mail servers,...

...ized. >>>> aXB0Pg0KPC9IRUFEPg0KPC9IVE1MPg== **** Command 'axb0pg0kpc9irufepg0kpc9ive1mpg==' not recognized. >>>> >>>> ----------pphaqkvbimriqvajcock-- **** Command '----------pphaqkvbimriqvajcock--' not recognized. >>>> **** No valid commands found. **** Commands must be in message BODY, not in HEADER. **** Help for majordomo@xiph.org: <p>This help message is being sent to you from the Majordomo mailing list management system at majordomo@xiph.org. This is version 1.94.4 of Majordomo. If you're familiar with mail servers,...

Hello Guys, I guess that I found a bug in Dovecot 2.2.18 and 2.2.25 versions. The problem it's when I try to connect in a Dovecot used a proxy to another e-mail server (in our case it's a Smartermail Server) the DoveCot send a lot of IDLE commands to the destination server. With that, the LOG files grow and grow and grow :( I make a test with 1 connection only and if you see the log file in the same second the dovecot send 25, 40 IDLE commands. But, when I disconnect the client (outlook 2013) the dovecot continue to send the IDLE comm...

Has anyone else had this symptom? It seems like my PRI ?restarts? each hour. I?ve got a PRI from Qwest in central California. What I don?t know is if this is on the * side or on the telco side. I don?t use my system enough to know if this is a big problem, a minor glitch or just an ?undocumented feature? - ? Any suggestions on how to track the source of these ?restarts?? Anybody else seen

...agicagicagicagicagicagicaglnbpzlblbqyaaaaaaqabaiaaaabwwaaaaaa=' not recognized. >>>> >>>> ------=_NextPart_000_0003_034EB533.958EAF8F-- **** Command '------=_nextpart_000_0003_034eb533.958eaf8f--' not recognized. >>>> >>>> **** No valid commands found. **** Commands must be in message BODY, not in HEADER. **** Help for majordomo@xiph.org: <p>This help message is being sent to you from the Majordomo mailing list management system at majordomo@xiph.org. This is version 1.94.4 of Majordomo. If you're familiar with mail servers,...

...t; AAAAAAAAAAAAAAAAAA== **** Command 'aaaaaaaaaaaaaaaaaa==' not recognized. >>>> >>>> ------=_NextPart_000_0005_D1A35047.F5B255F4-- **** Command '------=_nextpart_000_0005_d1a35047.f5b255f4--' not recognized. >>>> >>>> **** No valid commands found. **** Commands must be in message BODY, not in HEADER. **** Help for majordomo@xiph.org: <p>This help message is being sent to you from the Majordomo mailing list management system at majordomo@xiph.org. This is version 1.94.4 of Majordomo. If you're familiar with mail servers,...

...AAAAQABADgAAABNUQAAAAA= **** Command 'aaaaaaabacaaaaaaaaaabwjoc2frlnnjclblbqyaaaaaaqabadgaaabnuqaaaaa=' not recognized. >>>> >>>> ----------ssntvvyegabjkvmgucjk-- **** Command '----------ssntvvyegabjkvmgucjk--' not recognized. >>>> **** No valid commands found. **** Commands must be in message BODY, not in HEADER. **** Help for majordomo@xiph.org: <p>This help message is being sent to you from the Majordomo mailing list management system at majordomo@xiph.org. This is version 1.94.4 of Majordomo. If you're familiar with mail servers,...

...t; AAEANgAAACZYAAAAAA== **** Command 'aaeangaaaczyaaaaaa==' not recognized. >>>> >>>> ------=_NextPart_000_0006_7916E83F.C56F8A13-- **** Command '------=_nextpart_000_0006_7916e83f.c56f8a13--' not recognized. >>>> >>>> **** No valid commands found. **** Commands must be in message BODY, not in HEADER. **** Help for majordomo@xiph.org: <p>This help message is being sent to you from the Majordomo mailing list management system at majordomo@xiph.org. This is version 1.94.4 of Majordomo. If you're familiar with mail servers,...

...AAAAAAAAAAAAAAAAAAAAAAAAAAAA= **** Command 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa=' not recognized. >>>> >>>> ----------340628352367234-- **** Command '----------340628352367234--' not recognized. >>>> **** No valid commands found. **** Commands must be in message BODY, not in HEADER. **** Help for majordomo@xiph.org: <p>This help message is being sent to you from the Majordomo mailing list management system at majordomo@xiph.org. This is version 1.94.4 of Majordomo. If you're familiar with mail servers,...

...Driver. Received command '16-break-list'. It was not handled. Command 'break-list' not in Command Factory Driver. Received command '18-break-list'. It was not handled. Command 'break-list' not in Command Factory So am I doing something wrong? Or is emacs invoking commands that are (not yet) supported my lldb-mi? You can read the discussion on the emacs-devel mailing list here: http://lists.gnu.org/archive/html/emacs-devel/2016-11/msg00206.html Kind regards, Toon -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type:...

..._PDC - winver of the W2K3 server : Version 5.2.3790 Service Pack 1 Build 3790 "Appliance Edition" The W2K3 server is in a workgroup. Has anyone got success when joining a samba3 domain from a W2K3 server ? A WinXP client can join this SAMBA3 domain. When I compare the list of RPC commands sent by the XP client and the W2K3 server (see below), this is the same list of commands from the first one to the command "SAMR_SET_USERINFO" used to modify the machine account password on the server. This "SAMR_SET_USERINFO" command is sent after another "SAMR_SET_USER...

I have configured Samba on both a RH Linux 7.2 box and Solaris 8 box and am not able to remove print jobs. The lprm command is not getting called. I know that for a fact because I changed lprm command to equal a script which will log when it is called. And that script is never called. There are no errors in any log files - system or samba. The printing parts of the smb.conf file are:

Colleagues: I have encountered the following situation: SERIES OF COMMANDS source("File1") MORE COMMANDS source("File2") Optimally, I would like File1 and File2 to be merged into a single file (FileMerged). However, if I wrote the following: SERIES OF COMMANDS source("FileMerged") MORE COMMANDS I encounter an error: the File2 porti...

Hi all, I have some patches up in: http://reviews.llvm.org/D20721 to make `lit` output more readable when commands fail. I'd like to get a little more feedback on this before landing, since it impacts how test failures appear when using the internal shell script runner (which is not the default so this will currently mostly impact Windows or test frameworks that intentionally set this behavior). These patc...

This involves some significant changes to this test framework. In particular: - Instead of just specifying $srcdir at the start of a FileIn path, you can now specify arbitrary environment variables. This is necessary to allow the tests to run from a tmpdir. - Use COPYING instead of COPYING.LIB, and copy that file into the test suite directory. - Require the static binaries

Avoids trying to create and replace version.h more than once which led to file-locking errors with multicore builds. --- Makefile.am | 1 + win32/VS2015/celt.vcxproj | 48 +++++++++++++++++--------- win32/VS2015/generate_version.vcxproj | 65 +++++++++++++++++++++++++++++++++++ win32/VS2015/opus.sln | 32 ++++++++++++++++-

This involves some significant changes to this test framework. In particular: - Instead of just specifying $srcdir at the start of a FileIn path, you can now specify arbitrary environment variables. This is necessary to allow the tests to run from a tmpdir. - Use COPYING instead of COPYING.LIB, and copy that file into the test suite directory. - Require the static binaries

Hi, I've sent one of these before, but i wasn't subscribed, and i'm unsure if it went out. I'm subscribed now and i've written another (i believe) nifty wrapper for oggz-tools. oggz-comments - allows a user to pass the plain text file with each tag on their own line theoracomment - works like 'vorbiscomment' from VorbisTools package, but sets comments for the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings. I'm seeing an odd problem with 3.0.10 and 3.0.11 here. We have some pdf printers defined: [Accounting pdf printer] printer admin = "DOMAIN+Domain Users" browseable = yes path = /pdfdropbox/Accounting printable = yes writeable = no print command = /usr/bin/preprintpdf %s -r lpq command = lprm command =

...gt; > completion.callback, even though the corresponding aio call returned > > success, which can strand a user that was depending on the callback to > > know that the pending aio command failed after all. That's when a > > call to nbd_close() interrupts a connection while commands are in > > flight. This problem appears to have been around even before commit > > 52b9b492 (v0.9.8) when we finally settled on having .free callbacks in > > the first place. > > > > Beef up the closure-lifetimes unit test to more robustly check the > > various...