Am Fr, den 23.04.2004 schrieb Tim Alberts um 00:47: > I think you are correct. The first message I posted seems to be an imap > message. Which leaves me with the following questions: > > Why is an IMAPmessage getting written with no IMAP service running? > Why after it gets written does email randomly dissappear? > Why does the SystemLogger keep telling me /var/spool/mail folder has to have > access 777? Ok, especially for you I did create a user for testing the issue and it appears this way: 1) created testuser and therefor /var/spool/mail/testuser was not there 2) date | sendmail -t realuser@xxxxxxxxxxxx testuser means I sent the new testuser a mail with the actual data as body mail received and was written into /var/spool/mail/testuser as the first mail, nothing else was in that file 3) telnet mailhost.tld 25 user testuser pass secret list --> shows 1 new mail retr 1 --> printed out the mail with full header and body dele 1 --> deleted the mail quit 4) checking /var/spool/mail/testuser showed then the new mail deleted BUT the dummy message in it: From MAILER-DAEMON Fri Apr 23 01:21:04 2004 Date: 23 Apr 2004 01:21:04 +0200 From: Mail System Internal Data <MAILER-DAEMON@xxxxxxxxxxxx> Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA Message-ID: <1082676064@xxxxxxxxxxxx> X-IMAP: 1082676046 0000000001 Status: RO This text is part of the internal format of your mail folder, and is not a real message. It is created automatically by the mail system software. If deleted, important folder data will be lost, and it will be re-created with the data reset to initial values. So though there is the X-IMAP header tag in it not IMAP daemon had participated. The ipop3 is writing it in. So your first question is answered, the one from the follow-up mail too. What do you mean with mail disappearing? As I understand what you might see is that the mailserver gets confused when you take him the inbox mail file away. Nothing I wonder about. Use a standard conform method to get new mails from one host to another. Either use fetchmail on the host which shall receive the mail. Or use an /etc/aliases entry if you wish the mail getting on one host to be sent to a different one. That is the function of aliases file. Ok, your last question, an important one. Be sure the permissions are really $ ls -ld /var/spool/mail /var/spool/mail/tuser drwxrwxr-x 3 root mail 4096 23. Apr 01:20 /var/spool/mail -rw-rw---- 1 tuser mail 542 23. Apr 01:21 /var/spool/mail/tuser Check whether they got changed running mailbox access. Maybe a different user uses a tool which modifies the permissions? I am running uw-imapd an have a user with KMail as her MUA and never faced such maillog messages. The message Mailbox Vulnerable - Directory /var/spool/mail must have 1777 protection only appears when the file /var/spool/mail/$user is set writable by accounts different than the user itself and systemuser mail. Or maybe even the permissions on the user's inbox are chmod 600 (like to be seen from the bugzilla article i pointed to before: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=120196). On my FC1 I have uw-imap RPM version imap-2002d-3 installed. Alexander -- Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13 Fedora GNU/Linux Core 1 (Yarrow) on Athlon CPU kernel 2.4.22-1.2179.nptl Sirendipity 01:21:18 up 4 days, 8:07, load average: 0.30, 0.10, 0.11 [ ÎÎÏÎÎ Ï'ÎÏÏÎÎ - gnothi seauton ] my life is a planetarium - and you are the stars
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil