> |Speaking of testing, the tests don't run at the moment. > > shit 8~/, sorry, that's because of the [mdn] topic, i've rebased > that back to [crawl] and fix it today.
I'm not sure if you meant you'll fix it later, or that it should be fixed now. Actually, [next] doesn't work at all (always loads MAILSPOOL on startup) so I switched to [crawl]. But tests still fail there. > So, it's not that we couldn't do it that way too, but still i > wonder what the benefit of it would be? I.e. and e.g. i now have > > set v15-compat netrc-load > set hostname=yandex.com smtp-hostname= smtp-auth=plain \ > smtp=smtps://smtp.yandex.ru:465 > ghost xi 'fi %:imaps://imap.yandex.ru' > > and two entries in ~/.netrc which are identical except for the > machine name, and in fact that is what is frustrating me, but > having globbing support as in `*.yandex.ru' is possibly not a good > idea by itself and is also non-standard, is it; i don't know > enough about misusage of .netrc to say wether that is acceptable > or not. But since i'm sick of having two entries for one account > after one day i think i'd go to single leading `*.' to mean "skip > one level of subdomains"; since the code i've seen performs exact > match only this shouldn't hurt! I don't think it's really relevant to what I said, but I agree a wildcard would be nice. The other option would be to do it automatically: if no "imap.yandex.ru" machine is found, automatically fallback to "yandex.ru". But this seems a bit more naughty than a simple `*.' wildcard. Anyway, all this isn't what I meant, but S-nail now works as I wanted it to so I guess you understood me. > I'm still thinking about your user case..? For instance if school.edu and work.com both use google apps, then both will use "imap.gmail.com" as the imap host. I'd guess many setups are like this. Or perhaps you might use both [email protected] and [email protected] as seperate accounts, each (for some reason???) with a different password. Dunno :P -- Cheers, Gavin ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ S-nail-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/s-nail-users
