Displaying 5 results from an estimated 5 matches for "valona".
2013 Mar 04
2
lda: duplicate prefix?
..._date_add
envelope_to_add
return_path_add
#group = mail
#mode = 0660
temp_errors = 64 : 69 : 70: 71 : 72 : 73 : 74 : 75 : 78
What am I doing wrong?
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c) E-Mail: larryrtx at gmail.com
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dovecot.n.conf
Type: application/octet-stream
Size: 1329 bytes
Desc: not available
URL: <http://dovecot.org/pipermail/dovecot/attachments/20130304/e2cb5e5c/attachment.obj>
2008 Aug 10
1
IPMI Console: No luck once OS is booted
...interact with the BIOS, etc, but no joy once we get past the loader.
Anyone have ideas?
Attached is the kernel config, and the /var/run/dmesg.boot file.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 512-248-2683 E-Mail: ler@lerctr.org
US Mail: 430 Valona Loop, Round Rock, TX 78681-3893
-------------- next part --------------
#
#
# For more information on this file, please read the handbook section on
# Kernel Configuration Files:
#
# http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html
#
# The handbook is also avail...
2013 May 31
2
LDA/LMTP - saving to INBOX fallback on tempfail?
Currently if saving to mailbox fails for any reason, the mail is saved to INBOX instead. Same if a Sieve redirect fails, the mail is saved to INBOX. I'm wondering if anyone actually prefers this behavior when the error is temporary? For example if some index file corruption was detected, the save will most likely succeed the next time it's attempted. Or if the redirect fails because the
2012 Jul 21
2
lsof needs update
hi, lsof on freebsd 9.1:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
ntpd 1707 root cwd unknown file
system type: newnfs
ntpd 1707 root rtd unknown file
system type: newnfs
ntpd 1707 root txt unknown file
system type: newnfs
ntpd 1707
2013 May 12
2
Reinstalling boot blocks on a ZFS-only system
So, I've long known and it makes sense that when you're booted from a ZFS volume, you can't mess with the boot-loader. And, I know a few months ago I had a set of commands I would use when booted from a CD that would initialize the network and copy the "release/boot" from somewhere else so that I could install bootblocks and boot-loaders from more recent code. Sadly, I