Stefan Bertels writes:
> Any more hints how I can still use non-FQDN in alpine config?
Why do you want to? I have seen an a.b domain created so someone
could steal passwords of users wanting to log into a.b.c.d by typing
just "a.b". Not using FQDNs is always a little risky, and is the kind
of convenience that, IMHO, should be reserved for the command line, and
even then used with care.
I can't think of a reason for a "set once and forget about" (almost)
config to use anything other than a FQDN.
And as you have just found out, using the FQDN reduces the
dependence (coupling) between software modules. Isn't it a good thing to
have your email config not be vulnerable to changes in your resolver
config?
Cheers,
- Joel
_______________________________________________
Imap-uw mailing list
[email protected]
http://mailman2.u.washington.edu/mailman/listinfo/imap-uw
