similar to: Oops when using ext3 with quota

Hi Stephen, it's me again with a problem report about quotas and ext3... I'm not quite sure whether you tried to resolve the quota problems yet, but since I read in the changelog of 0.0.5e that you included some quota specific fixes I decided to give a try (again). And once again: Bad news. Still lockups, reliable reproducible. But this time I have a little backtrace for you of two

The list has gotten pretty quiet over the last week. As I understand it, we are down to the following big ticket items: 1. Quotas on meta journaling 2. ext3 + LFS 3. Various minor bugs. Is this accurate? -- Keith Barrett Red Hat HA Team

I've just set up a brand new system with software raid1 (in degraded mode) with one IDE 20GB drive, using kernel 2.2.19pre16 with ext3 0.0.6b. It's split like this.. 32MB /dev/hda1 /boot 2GB /dev/hda2 / ~18GB /dev/hda3 /home all partitions are marked as 0xfd (autostart raid) with the patches from http://people.redhat.com/mingo/raid-patches for 2.2.17. And I've made all the ext3

So there is no way to skip Postfix for incoming messages and go directly to LMTP/LDA but I need two instances of Postfix in that case? Regarding your second question - it is required to be complaint with Direct Trust. Thanks, Adam ?On 4/2/20, 3:07 PM, "dovecot on behalf of Juri Haberland" <dovecot-bounces at dovecot.org on behalf of juri at koschikode.com> wrote: On

Hello! I'm using i868 (Pentium III) machine running Windows 2000 and running Linux, installed on dedicated partition, in parallel via VMWare. Linux config is RedHat 7.0 (kernel ) As I'm pretty new to Linux, I'd like to know exact procedure how to install ext3 filesystem support (also which packages do I need). My kernel config is as follows: kernel-headers-2.2.14-5.0

On 12/03/2020 08:04, Jean-Daniel wrote: > > >> Le 11 mars 2020 ? 19:32, Juri Haberland <juri at koschikode.com> a ?crit : >> >> Hi list, >> >> I have a small problem with recipient_delimiters contained in usernames. >> Recently I have extended recipient_delimiter from "+" to "+-" in both >> Postfix and Dovecot (using

On 09/02/2019 10:44, Aki Tuomi via dovecot wrote: > For some reason mailman failed to "munge from" for senders with dmarc policy ;( > > It's now configured to always munge to avoid this again. I'd say, let Mailman throw all people off the list that have enabled DMARC checking without using exceptions for the lists they are on. It's a known fact that DMARC does not

On 15/03/2020 21:26, GMX Account wrote: > have a look at this: > > http://www.postfix.org/postconf.5.html#recipient_delimiter > > [...]When the recipient_delimiter [1] set contains multiple characters > (Postfix 2.11 and later), a user name or .forward file name is > separated from its extension by the first character that matches the > recipient_delimiter [1] set.[...]

Hi list, I was looking for a kernel option to mount the root fs (/) as ext2 with an ext3 enabled kernel. I searched the list archive and I'm not sure whether rootflags=noload is the right option... Can someone give me a hint? I'm using 2.4.6-pre5 with ext3-0.0.8. TIA Juri -- Juri Haberland <juri@koschikode.com>

> Le 11 mars 2020 ? 19:32, Juri Haberland <juri at koschikode.com> a ?crit : > > Hi list, > > I have a small problem with recipient_delimiters contained in usernames. > Recently I have extended recipient_delimiter from "+" to "+-" in both > Postfix and Dovecot (using lmtp) and now any user that have a '-' in it's > username can't

Hi, have a look at this: http://www.postfix.org/postconf.5.html#recipient_delimiter [...]When the recipient_delimiter [1] set contains multiple characters (Postfix 2.11 and later), a user name or .forward file name is separated from its extension by the first character that matches the recipient_delimiter [1] set.[...] --- Original Nachricht --- Betreff:?Re: lmtp and recipient_delimiter

On Sonntag, 15. M?rz 2020 21:43:08 CET Juri Haberland wrote: > On 15/03/2020 21:26, GMX Account wrote: > > have a look at this: > > > > http://www.postfix.org/postconf.5.html#recipient_delimiter > > > > [...]When the recipient_delimiter [1] set contains multiple characters > > (Postfix 2.11 and later), a user name or .forward file name is > >

On 15/03/2020 20:26, Peter wrote: > Poorly documented, imo, but you want lmtp_save_to_detail_mailbox = yes: Thanks, tried it, but no, that's not what I want and it doesn't help in my case. To recap: If I set recipient_delimiter to "+-" (or "-" alone), having a user named "foo-bar" won't work anymore, because Dovecot always tries to deliver to user

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 09 February 2019 at 20:48 Juri Haberland via dovecot < <a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote: </div>

On 2/9/19 10:48 AM, Juri Haberland via dovecot wrote: > On 09/02/2019 10:44, Aki Tuomi via dovecot wrote: >> For some reason mailman failed to "munge from" for senders with dmarc policy ;( >> >> It's now configured to always munge to avoid this again. > > I'd say, let Mailman throw all people off the list that have enabled DMARC > checking without

* Juri Haberland via dovecot: > Blindly enabling DMARC checks without thinking about the consequences > for themselves should not be the problem of other well behaving > participants. Can you judge if DMARC is enabled "blindly"? No, I thought not. Also, the issue was not on the receiving end, but the reject policy for the originating domain. Personally, I choose to treat

On 16/03/20 7:10 am, Juri Haberland wrote: > My question would be: > Is this due to a misconfiguration somewhere? > Is this the intended behavior? > Or is this a bug? Poorly documented, imo, but you want lmtp_save_to_detail_mailbox = yes: https://github.com/dovecot/core/blob/master/doc/example-config/conf.d/20-lmtp.conf#L8 Peter

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 15/03/2020 21:26 Peter < <a href="mailto:peter@pajamian.dhs.org">peter@pajamian.dhs.org</a>> wrote: </div> <div>

Hi, I am not totally sure what caused this but I just wanted to know if anything of this sort has been seen in the ext3 world. I did a fresh install of redhat 7.2 linux with kernel-2.4.9(we have some patches applied to this). I have root and boot filesystems as ext3 type. After running some tests the system gets into a strange state. I cannot move one file to another if that destination file

I thought I'd summarise this with a proper subject line: 1. We used up2date to upgrade the kernel of a 7.2 machine that is doing far too much journalling (kjournald at 50% CPU+ often). 2. It installed fine, but when we reboot - GRUB only shows the old 2.4.7-10 although there are 3 kernels listed in grub.conf My Question is "How can we select booting to 2.4.18-24.7 when GRUB lonly lists