gmane.mail.imap.uw.c-client

Re: SELinux and dmail

Andrew Daviel — 2008-10-07T18:08:29

I think that the issue was indeed related to my mounting my old Reiserfs home disk. I copied the contents to a new ext3 partition, then did "touch /.autorelabel; reboot", and the flood of error messages has slowed to a trickle. (I was also missing entries in local-host-names, which probably accounted for a lot of daemon/postmaster mail rattling around). I still don't 100% understand the above error message, though, or the exact implications of having dmail deliver to a folder that is on a non-selinux-enabled partition or device. I think it is just the "getattr" that fails, not the disk write, so that the mail is still delivered. Maybe it's related to file locking.

RE: Re: [Alpine-info] Server name does not match certificate

Mark Crispin — 2008-10-07T15:39:09

Decades of unhappy experience proves that whatever time is saved, and convenience gained, by the use of non-FQDN names is vastly outweighed by the problems created.

Re: Re: [Alpine-info] Server name does not match certificate

Stefan Bertels — 2008-10-07T13:01:21

My IMAP server is a local machine (intranet) with a non-public IP address. The FQDN does not resolve by public DNS, too. Manipulation to DNS might result in a security issue, but I cannot see why FQDN would make this secure. It might get more difficult to infiltrate DNS. Nevertheless I have full control over DNS server, host resolves correctly and alpine is only run within intranet, so should be safe enough. I agree for internet systems (public IP, public FQDN) and for bigger intranets. This is a small local network and the domain name is just there because some software does not run (well) without. Anyway I will change to FQDN everywhere to remove the warning. _______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

Re: Re: [Alpine-info] Server name does not match certificate

Joel Reicher — 2008-10-07T12:11:33

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 Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

Re: Re: [Alpine-info] Server name does not match certificate

Stefan Bertels — 2008-10-07T11:17:08

Thanks for the hint. I changed the server name in Alpine config (remote pinerc) to use the FQDN. The warning is gone. It is quite annoying that I have to change all entries to FQDN in remote pinerc, now. Furthermore I have to change all machines where I configured remote pinerc. The SSL certificate (server) for IMAP didn't change, the client setup didn't change. So I'm a bit confused about the warning. The previous remote pinerc config had a non-FQDN (missing all parts behind the first dot) and it worked (no warning) until I upgraded some server software. I tried to change some settings in DNS resolution: client => default DNS suffix dns server (dnsmasq) => expand-hosts. But this didn't help. If I ask the DNS server for the short machine name (non-FQDN) or for the IP address I always get a FQDN. Any more hints how I can still use non-FQDN in alpine config? Stefan _______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailm

Re: Mix mailbox format file size vs. mailutil

Stefan Bertels — 2008-10-07T10:45:01

Thanks. I will test mixcvt. I have found some more tools here: http://andrew.triumf.ca/andrew/mbx/ (mbx2mix) I use Ubuntu and do not really want to build packages on my own. I'm glad that c-client.cf can be used to set up default mailbox format. I probably do not need to update MIXDATAROLL as 1Mbyte (or something similar) will work good enough. _______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

Re: Mix mailbox format file size vs. mailutil

Joel Reicher — 2008-10-07T08:46:29

http://mailman2.u.washington.edu/pipermail/imap-uw/2007-April/001278.html src/osdep/unix/mix.c; look for the MIXDATAROLL #define. mixcvt, mentioned in the thread linked to above, does not use c-client and so has its own hardcoded value which you may want to change too. Cheers, - Joel _______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

Re: Re: [Alpine-info] Server name does not match certificate

Joel Reicher — 2008-10-07T08:32:59

I think the mismatch is between the contents of the certificate and the server name configured in the client (Alpine). I'm pretty sure the server software plays no part in any of this. Cheers, - Joel _______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

Mix mailbox format file size vs. mailutil

Stefan Bertels — 2008-10-07T08:12:45

Hi, I'm just upgrading from mbx to mix and testing this. From what I know mix has a file size of about 1MByte where file size means that a new file is generated when the limit is reached. I'm trying to convert the mbx mailboxes using mailutil copy/move. But this seems to result in only one big mix file > 66MByte. I would prefer to have about 66 files instead, especially for improving (file based) backup performance. I have some more mbx files, most of them are much bigger. How can I convert to set of (around) 1Mbyte files in mix format? Additional question: Can the size value be adjusted (e.g. in c-client.cf)? Best regards Stefan _______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

Re: [Alpine-info] Server name does not match certificate

Stefan Bertels — 2008-10-07T07:31:29

(Continuing discussion in [alpine-info], this is a x-post) On Mon, 29 Sep 2008, Kevin Stevens wrote: Thanks for the hint. How does uw-imap get the server name? The imap server says "localhost" but /etc/hostname has the machine's network name. $HOSTNAME is set to this name, too. Best regards Stefan _______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

SELinux and dmail

Andrew Daviel — 2008-10-06T19:20:24

I just upgraded to Fedora 9 at home (disk went bad, FC4 didn't support new SATA disk on my motherboard, Firefox 3 wouldn't run ... time to change) Anyhow, newer Fedora (and RHEL 5 on my new desktop at work) come with SELinux turned on, and I thought I should get my head around it instead of turning it off (after all, it is a security feature and I'm supposed to know about that stuff..) So, a ton of SELinux errors (10,000 and counting) as soon as I start importing my stuff onto a virgin system. One relevant to this list is for dmail I don't really know what I'm doing here (yet). This is still the standard sendmail config calling procmail as local delivery; .procmailrc feeds "|dmail". I used chcon to set the attributes for dmail the same as procmail thinking that might help, but no. The mail is actually being delivered, though. .. I just thought .. this is my old home partition using Reiserfs 3 on sdb10. According to some other error message I'd seen, an ISO volume (CDROM loopback) also has nf

RE: mix format doesn't check sysinbox for status

Dan Lukes — 2008-09-23T10:32:54

I didn't do such attempt in any way. I cited the part of RFC you are helped to write only. The RFC say something, the sendmail did something other, which is no problem as it doesn't make any additional limits, the IMAP-UW also did something other, but it make additional limits to user's of those MTA which is written according the RFC, but not according mentioned unwritten consensus. I didn't sayd anything more, anything less. If you understatnded it as an offency, it's misunderstanding. Sincerelly (from Nepal, 3960m above sea, so no further discussion will be possible from my side) Dan _______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

Re: mix format doesn't check sysinbox for status

Joe Pruett — 2008-09-21T01:20:42

i just realized that the test account i was using has its home directory over nfs. so i'm sure that is the problem. i'll add a lock to the procmail delivery rule, but that won't fully fix things. _______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

Re: mix format doesn't check sysinbox for status

Erik Kangas — 2008-09-20T22:23:49

dmail should be fine for concurrent delivery (Mark has indicated so previously on the list). However, we always take the precaution of using procmail locking as well. -Erik Kangas _______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

RE: mix format doesn't check sysinbox for status

Joe Pruett — 2008-09-20T20:46:08

should dmail be fine for simultaneous delivery? one account i switched over to test dmail with is complaining about a corrupt .mix file now. do i need to serialize delivery via dmail? _______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

RE: mix format doesn't check sysinbox for status

Mark Crispin — 2008-09-20T16:49:18

I helped write that text. I know what it means. Please do not attempt to instruct me about the design of email. I have been one of the designers since the 1970s. I wrote one of the very first SMTP implementations. Sendmail is case-insensitive because the consensus of ALL the email developers -- with the exception of Multics -- was to be case-insensitive. _________________________________________________________________ Stay up to date on your PC, the Web, and your mobile phone with Windows Live. http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/_______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

RE: mix format doesn't check sysinbox for status

Dan Lukes — 2008-09-20T15:20:11

According the RFC822/RFC2822 then local part of email address is case-sensive, with exception of 'postmaster' which shall be compared insensitive. Yes, sendmail does case-independent matching, but it's proprietary extension. No program shall follow them, unless it's written specifically for sendmail. Dan _______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

RE: mix format doesn't check sysinbox for status

Mark Crispin — 2008-09-19T19:27:34

imapd does something different. It tries the name as the user supplied and squashes if and only iff that form doesn't exist. _________________________________________________________________ See how Windows connects the people, information, and fun that are part of your life. http://clk.atdmt.com/MRT/go/msnnkwxp1020093175mrt/direct/01/_______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

RE: mix format doesn't check sysinbox for status

David B Funk — 2008-09-19T19:22:31

Actually sendmail does configurable case squashing of user-ids, with the default of case squashing enabled. (In otherwords 'Joe' 'JOE' and 'joe' all get converted to 'joe' before any delivery processing is done, unless you add the 'u' mailer flag to preserve case). The net result, if you have the default config and a user with a login ID of "Joe", he can never receive any mail. (also if you try to use the "+" mailbox selector syntax, you cannot send mail to "joe+Drafts", it gets turned into "joe+drafts").

RE: mix format doesn't check sysinbox for status

Mark Crispin — 2008-09-19T18:25:25

Are you aware that sendmail also does case-independent matching of user ids? It is silly to assume that you want to have joey, Joey, JOEY, etc. as separate user ids. It's unfortunate that FTP makes that mistake. _________________________________________________________________ Want to do more with Windows Live? Learn “10 hidden secrets” from Jamie. http://windowslive.com/connect/post/jamiethomson.spaces.live.com-Blog-cns!550F681DAD532637!5295.entry?ocid=TXT_TAGLM_WL_domore_092008_______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

RE: mix format doesn't check sysinbox for status

Joe Pruett — 2008-09-19T18:32:47

yes, email addresses are case-insensitive. but as you know, in unix the login names aren't. yes, it would be stupid to have Joey, joey, and JOEY accounts, but it is "valid". i certainly understand the rationale for trying to cope with users using capitalization, it just has unintended consequences. i'll probably modify my squirrelmail plugin to do the case folding as well. _______________________________________________ Imap-uw mailing list Imap-uw< at >u.washington.edu http://mailman2.u.washington.edu/mailman/listinfo/imap-uw