Displaying 4 results from an estimated 4 matches for "n6mef".
2016 Aug 01
2
service-specific userdb affecting lmtp, quota-service
The service specific passwd-file userdb is causing quota-status and lmtp to
fail.
Using:
userdb {
args = ... /etc/dovecot/auth.d/%d/userdb.%s
}
I'm getting the following in /var/log/mail.err when I try to send/receive
mail:
Aug 1 15:46:57 n6mef-gw dovecot: auth: Error:
passwd-file(mefpop at email.n6mef.org):
stat(/etc/dovecot/auth.d/email.n6mef.org/userdb.quota-status) failed:
Address family not supported by protocol
Aug 1 15:47:08 n6mef-gw dovecot: auth: Error:
passwd-file(mefpop at email.n6mef.org):
stat(/etc/dovecot/auth.d/email.n6mef...
2016 Aug 03
2
service-specific userdb affecting lmtp, quota-service
...ta-status and lmtp
>> to
>> fail.
>>
>> Using:
>> userdb {
>> args = ... /etc/dovecot/auth.d/%d/userdb.%s
>> }
>>
>> I'm getting the following in /var/log/mail.err when I try to send/receive
>> mail:
>>
>> Aug 1 15:46:57 n6mef-gw dovecot: auth: Error:
>> passwd-file(mefpop at email.n6mef.org):
>> stat(/etc/dovecot/auth.d/email.n6mef.org/userdb.quota-status) failed:
>> Address family not supported by protocol
>> Aug 1 15:47:08 n6mef-gw dovecot: auth: Error:
>> passwd-file(mefpop at email.n6m...
2016 Jul 15
2
controlling STARTTLS by IP address
...challenge/response auth methods don't violate
the FCC rules. Of course, without TLS encryption, the auth process is not
totally secure. And, yes, the message itself would be in plain text. But
it's the best we can do given the rules. Think of it as packet radio on
steroids.
73,
Michael
N6MEF
2016 Jul 14
2
controlling STARTTLS by IP address
> Are you 100% sure your interpretation of the FCC rules is correct?
Yes
> Do you really want passwords going out over RF unencrypted?
No. I don't plan to use plaintext auth methods.
> As far as I know, only ham bands are not allowed to use encryption. Even
> baby monitors these days are DECT. (Mind you, not good encryption.)
Correct. It is ham radio.
Michael