Bug#317598: procmail accepts messages even though partition full
severity 317598 normal thanks I reiterate that I can't take this report seriously unless you tell me a way to reproduce it. In particular, you didn't tell me about your procmail.log file at all. I'm downgrading the severity to normal, as I don't want to see a non-reproducible bug in the periodical "list of bugs that must be fixed urgently". -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#317598: procmail accepts messages even though partition full
Processing commands for [EMAIL PROTECTED]: > severity 317598 normal Bug#317598: procmail accepts messages even though partition full Severity set to `normal'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#317598: procmail accepts messages even though partition full
On Sun, 10 Jul 2005, CaT wrote: > Package: procmail > Version: 3.22-11 > Severity: critical > Justification: causes serious data loss Please don't just show me your logs. I need a way to *reproduce* the data loss, including a minimal .procmailrc showing such behaviour, and an exact description of a procedure which may lead to such data loss. (You have not even tell me what your procmail.log file contains, maybe it can tell you where your mail went). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#317598: procmail accepts messages even though partition full
On Sun, Jul 10, 2005 at 10:55:03AM +1000, CaT wrote: > Package: procmail > Version: 3.22-11 > Severity: critical > Justification: causes serious data loss > > > Tonight my /var/mail partition ran out of disk space (again) and > procmail continued to allow delivery (again) despite of this. It > occasionally rejected messages via return code 75: I don't know anything about procmail, but I have one thought. Are you sure the messages are lost? I was thinking that maybe some particularly large messages were rejected first, filling up some more disk space, and then, eventually, every message was rejected (when there was not a single spare unit on the disk). Is this possible? Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#317598: procmail accepts messages even though partition full
Package: procmail Version: 3.22-11 Severity: critical Justification: causes serious data loss Tonight my /var/mail partition ran out of disk space (again) and procmail continued to allow delivery (again) despite of this. It occasionally rejected messages via return code 75: Jul 10 10:35:09 theirongiant fetchmail[1063]: reading message [EMAIL PROTECTED]:4 of 4 (2982 octets) Jul 10 10:35:11 theirongiant fetchmail[1063]: MDA returned nonzero status 75 Jul 10 10:35:11 theirongiant fetchmail[1063]: not flushed And all is well, but in the same hit it also decides that accepting is a great idea: Jul 10 10:35:07 theirongiant fetchmail[1063]: 4 messages for cat at zipworld.com.au (13738 octets). Jul 10 10:35:07 theirongiant fetchmail[1063]: reading message [EMAIL PROTECTED]:1 of 4 (2949 octets) Jul 10 10:35:08 theirongiant fetchmail[1063]: flushed Jul 10 10:35:08 theirongiant fetchmail[1063]: reading message [EMAIL PROTECTED]:2 of 4 (4429 octets) Jul 10 10:35:09 theirongiant fetchmail[1063]: flushed Jul 10 10:35:09 theirongiant fetchmail[1063]: reading message [EMAIL PROTECTED]:3 of 4 (3378 octets) Jul 10 10:35:09 theirongiant fetchmail[1063]: flushed And those messages are lost. The next time around it accepted the message it rejected above and so it was lost. It doesn't do it for just one message out of the pickup: Jul 10 10:40:58 theirongiant fetchmail[1063]: 4 messages for cat at zipworld.com .au (14719 octets). Jul 10 10:40:58 theirongiant fetchmail[1063]: reading message [EMAIL PROTECTED] u:1 of 4 (2615 octets) Jul 10 10:40:58 theirongiant fetchmail[1063]: flushed Jul 10 10:40:58 theirongiant fetchmail[1063]: reading message [EMAIL PROTECTED] u:2 of 4 (8077 octets) Jul 10 10:41:00 theirongiant fetchmail[1063]: MDA returned nonzero status 75 Jul 10 10:41:00 theirongiant fetchmail[1063]: not flushed Jul 10 10:41:00 theirongiant fetchmail[1063]: reading message [EMAIL PROTECTED] u:3 of 4 (2010 octets) Jul 10 10:41:00 theirongiant fetchmail[1063]: MDA returned nonzero status 75 Jul 10 10:41:00 theirongiant fetchmail[1063]: not flushed Jul 10 10:41:00 theirongiant fetchmail[1063]: reading message [EMAIL PROTECTED] u:4 of 4 (2017 octets) Jul 10 10:41:01 theirongiant fetchmail[1063]: flushed 2 messages gone and 2 messages saved. Procmail is called via the following in fetchmail: mda "/usr/sbin/sensible-mda %F %T '' localhost" Which is the way sendmail calls it. Help? This is rather annoying. I just lost a whole nights worth of email. :/ -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.11-mm3 Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Versions of packages procmail depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
