search for: malamute

I use Dovecot for SASL authentication from Postfix. In Postfix main.cf I have: smtpd_sasl_type = dovecot It works good, but now I need to allow users to connect by IMAP only from given IP adresses. I've added extra field allow_nets to passdb in Dovecot, and IMAP authentication works fine. But now I can't connect to my SMTP server because when smtpd ask dovecot about user

this is semi-off topic but still related to ror. i had a problem with testing my depot program (which i follow the tutorial in agile web development book). it took me many hours to solved the problem. all the while i thought i was using spaces inside the test/fixtures/products.yml programmer_book: id: 1 title: Pragmatic Programmer description: Best book

Today I've found a very irritating bug: I use mail_location = maildir:/var/mail/%u/ in my dovecot.conf. And if user type Username, username, USERname etc at login dovecot create a different Maildir's for one real user. But LDA works corretly and save all messages to lowercase username mailbox. No problem, add L: mail_location = maildir:/var/mail/%Lu/ Then all works good. But I has

...g other server tasks. I prefer to run CentOS 7 but given RHEL's refusal to support Samba AD functionality I have been using the Sernet packages. I thought if I used the RPI3s for the AD I could use the Samba source directly. I only use the AD for my home network and and a non-profit Alaskan malamute rescue website I support so running Samba is somewhat a hobby. Since I presently have only 1 AD using the two RPI3s would allow me to run two ADs so given that I presently only have one AD that might mitigate some of the potential issues should one of the RPI3s fail. A better idea, which I had...

Im having trouble with Testing models. im following the tutorials in the book Agile Web Development with Rails. if i execute the code product_test.rb, i get this error: ============================================================ 1) Failure: test_update2(ProductTest) [test/unit/product_test.rb:30]: <29.95> expected but was <99.95>. 3 tests, 11 assertions, 1 failures, 0 errors

...CentOS 7 but given RHEL's PRGvs> refusal to support Samba AD functionality I have been using the Sernet PRGvs> packages. I thought if I used the RPI3s for the AD I could use the Samba PRGvs> source directly. I only use the AD for my home network and and a PRGvs> non-profit Alaskan malamute rescue website I support so running Samba is PRGvs> somewhat a hobby. Since I presently have only 1 AD using the two RPI3s PRGvs> would allow me to run two ADs so given that I presently only have one AD PRGvs> that might mitigate some of the potential issues should one of the RPI3s PRGvs&g...

...s > PRGvs> refusal to support Samba AD functionality I have been using the > Sernet > PRGvs> packages. I thought if I used the RPI3s for the AD I could use the > Samba > PRGvs> source directly. I only use the AD for my home network and and a > PRGvs> non-profit Alaskan malamute rescue website I support so running > Samba is > PRGvs> somewhat a hobby. Since I presently have only 1 AD using the two > RPI3s > PRGvs> would allow me to run two ADs so given that I presently only have > one AD > PRGvs> that might mitigate some of the potential issues s...

A few months ago, I built a samba 4 DC on a RPi 2B v1.1 with Louis' packages. It's just like a normal Intel cpu based installation with a couple of minor exceptions. I built mine on Raspbian Lite. You'll have to add an additional user and give it sudo privileges.The network setup was like the older Debian 9 by simply adjusting /etc/network/interfaces. To add Louis' repo

On 2/12/19 10:55 PM, Alice Wonder wrote: > DNSSEC keys do not expire. Signatures do expire. How long a signature > is good for depends upon the software generating the signature, some > lets you specify. ldns I believe defaults to 60 days but I am not sure. > > The keys are in DNSSKEY records that are signed by your Key Signing > Key and must be resigning before the signature

Hello! Why Debian repo is so strange? Path to a repo should not contain version and subversion numbers. Now you can't receive and even check updates automatically. It's very-very simple to create correct repo. You can even add to it all versions of packages, if it is important. And where is i386 builds? Could anybody create a correct Debian repo for gluster from existing one?