search for: nowheres

hi, when i give samba a workgroup name with more than 15 characters [the limit for netbios names], nmbd is unable to participate in browse master elections. it appears that parts of internal samba code honor 16 characters and parts only honor 15. details: i used a workgroup name of nodomain.nowhere, 16 characters, on samba 2.2.1a. the samba box was the only member of this workgroup on the

Hello, I am running samba 4.11.8 as Active Directory DC and a member server. I wanted to authenticate cyrus-imapd by GSSAPI, and found this mailhttps://lists.samba.org/archive/samba-technical/2013-April/091429.html I tried to run the cyrus-imap server on a member server, which has successfuly 'net ads join'ed and authenticate user with winbindd without problems. I followed the method

People might find this entertaining and/or useful: http://www.gnu.org/manual/autoconf-2.52/html_chapter/autoconf_10.html With the help of Jos Backus I just discovered the answer to http://lists.samba.org/pipermail/rsync-cvs/2002-January/001271.html is that Sun's test(1) is breathtakingly broken when passed a dangling symlink: $ ln -s /nowhere bad $ ls -l bad lrwxrwxrwx 1 josb

Hello, Sometimes, when delivering mails, this warning appears in my syslog: > lda(...): Warning: Failed to parse return-path header: Invalid character in localpart dovecot-lda still exits with 0 and the mail is inserted into my inbox. Looking at the mails in question, I determined that the error is caused by a multiline Return-Path header. Here's a testcase: --- snip ---

Hello, On 31.01.2018 22:35, Stephan Bosch wrote: > Op 1/31/2018 om 6:17 PM schreef Christian Authmann: >> Hello, >> >> Sometimes, when delivering mails, this warning appears in my syslog: >> >>> lda(...): Warning: Failed to parse return-path header: Invalid >> character in localpart >> >> dovecot-lda still exits with 0 and the mail is inserted

Oh Nooooooo! It looks as if there is a limit of 9 (not 10) maximum #include statments that you can have in extensions.conf. For example, the following extensions.conf causes the error to appear.. [user_3250071] #include "inc/wildwildwest/features.conf" #include "inc/wildwildwest/features.conf" #include "inc/wildwildwest/features.conf" #include

nowhere does it say that centos is approved for use in DoD. it is not on the APL, only RedHat and SuSE

Do somebody know where to find a real good documentation for the observe_form? I have some problems with it and find nowhere a documentation. -- Posted via http://www.ruby-forum.com/.

Can someone tell me why the following from extensions.conf generates this error on asterisk load? Jan 13 09:27:24 WARNING[31701]: config.c:938 ast_config_internal_load: Maximum Include level (10) exceeded As far as I can tell I don't have a DEPTH of 10 includes. I certainly have more than 10 include statements, but I don't have them drilled down to a depth of 10. I'm thinking the

Hi, I'm still trying to open a Samba share from Windows XP, via an ssh tunnel. From Linux, and RiscOS no problem, but Windows no. Surely someone here has needed to do this at some time or other. Please help. Cheers, Paul.

Hi all, I have, what I think is a relatively simple samba/kerberos problem that I am not seeing the obvious side to. I'll explain the scenario. I have an OpenLDAP KDC or Directory Master. For the purposes of this conversation, it is the authentication server, and the bit that grants/ hands out all the ticket information. I have a Solaris 10 system running the default Sun shipped Samba

On 6/16/2015 10:44 AM, Steve Matzura wrote: > The next phase of my testing procedure involves the simple act of > delivering mail to my test box. When I send a message to either a > valid or relayed user at my remote machine's address, it never gets > there. I know this virtually for sure because I'm tailing > /var/log/maillog and nothing new has been added for the past

On Tue, 16 Jun 2015 11:27:58 -0500, you wrote: >No attempt to deliver almost always means either: >- a DNS problem; the sender can't find the destination, or finds the >"wrong" destination. That would be interesting, since I tried both the actual IP address and the DNS name for the test node. Neither message got through. >- a connectivity problem; the sender can't

> Date: Tuesday, June 16, 2015 01:13:47 PM -0400 > From: Steve Matzura <number6 at noisynotes.com> > > On Tue, 16 Jun 2015 11:27:58 -0500, you wrote: > >> No attempt to deliver almost always means either: >> - a DNS problem; the sender can't find the destination, or finds >> the "wrong" destination. > > That would be interesting, since I

Am Dienstag, den 16.06.2015, 11:44 -0400 schrieb Steve Matzura: > The next phase of my testing procedure involves the simple act of > delivering mail to my test box. When I send a message to either a > valid or relayed user at my remote machine's address, it never gets > there. I know this virtually for sure because I'm tailing > /var/log/maillog and nothing new has been

can you: $ telnet yourhost.com 25 (obviously replacing yourhost.com with whatever your domain/ip actually is) from the machine you are sending the mail from? If not make sure the service is running and make sure there isn't a firewall rule preventing this. On 06/16/15 10:44, Steve Matzura wrote: > The next phase of my testing procedure involves the simple act of > delivering mail

> Date: Tuesday, June 16, 2015 07:05:43 PM -0400 > From: Steve Matzura <number6 at noisynotes.com> > > On Tue, 16 Jun 2015 17:31:07 +0000, you wrote: > >> By default, most MTAs only listen to localhost, so don't accept >> externally derived mail. Try telnetting to port 25 on the machine >> from some place off your machine's network. If you get a

> Date: Tuesday, June 16, 2015 07:21:06 PM -0400 > From: Steve Matzura <number6 at noisynotes.com> > > On Tue, 16 Jun 2015 22:02:29 +0200, you wrote: > >> Am Dienstag, den 16.06.2015, 11:44 -0400 schrieb Steve Matzura: >>> The next phase of my testing procedure involves the simple act of >>> delivering mail to my test box. When I send a message to

On Wed, 17 Jun 2015 09:10:26 -0400, you wrote: >Please send the output of postconf -n to the mailing list. Paul: I purposefully obfuscated my FQDN and domain, but they both have real and good data in them. alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory =

Hello Using Asterisk 1.4.20 and Zaptel 1.4.3-1, I notice that Asterisk sends FXO calls to a context named "numberplan-local" that is not mentionned in my configuration file, which prevents incoming calls to be successfull: ======= /etc/asterisk/zapata.conf ================== [trunkgroups] [channels] ;Send incoming calls to this context in extensions.conf context=from_fxo