Displaying 20 results from an estimated 3000 matches similar to: "mount root fs as ext2 with ext3 enabled kernel"
2020 Apr 02
1
Disable Dovecot LDA
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
2020 Mar 12
0
lmtp and recipient_delimiter
> 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
2020 Mar 15
3
lmtp and recipient_delimiter
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
2003 Mar 13
6
Updated 2.4 htree patches available for 2.4.21-pre5
There's a new set of ext2/3 patches for 2.4.21-pre5 available at:
http://thunk.org/tytso/linux/extfs-2.4-update/extfs-update-2.4.21pre5-2
and in broken out form at:
http://thunk.org/tytso/linux/extfs-2.4-update/broken-out-2.4.21pre5-2
New to this patch set include:
* A kludge to help htree work well with Linux's NFS implementation
* Allow the orlov allocator to be disabled via a
2000 Nov 28
1
Oops when using ext3 with quota
Hi Stephen,
I posted a similar report on linux-kernel a month ago, but didn't hear
anything new from you. So I try it again in this list, this time with
some additional info:
Using a stock 2.2.17 kernel with NFS-patches and ext-0.0.3b I can
reliably lockup the kjournald when extracting two or three tar.gz files
(e.g. kernel tar-balls) onto a ext3 filesystem with activated quotas.
This
2001 Feb 09
0
Quotas?
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
2020 Mar 15
0
lmtp and recipient_delimiter
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
2020 Mar 15
0
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
> >
2019 Feb 09
0
offtopic: rant about thoughtless enabling DMARC checks [was: Re: Bounces?]
<!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>
2019 Feb 09
0
offtopic: rant about thoughtless enabling DMARC checks [was: Re: Bounces?]
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
2019 Feb 09
0
offtopic: rant about thoughtless enabling DMARC checks
* 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
2020 Mar 15
0
lmtp and recipient_delimiter
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
2020 Mar 15
1
lmtp and recipient_delimiter
<!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>
2000 Nov 05
1
rootflags argument doesn't work with initrd.
I tried to convert / to ext3, so I went ahead and entered
rootflags=noload,journal=355 on the LILO prompt. The kernel failed to
mount /:
EXT3-fs error (device ramdisk(1,0)): ext3_get_inode_loc: bad inode number: 355
The boot device is a scsi hard disk, so initrd is used to load the scsi
driver, before mounting /. So, it looks like the kernel rootflags= arg
gets applied to the ramdisk, not the
2004 Jan 13
3
RE: [OT] Re: Getting ext3 up and running
I referred to the entry
rootfs / rootfs rw 0 0
in the output of "cat /proc/mounts", that is not really very much explicative, due to the setting "auto" in /etc/fstab
and to the fact that file system had has_journal flag and no ext3 module was mounted.
But I was wrong: I think that if you have an ext3 fs and you mount it as ext2, you continue to see the has_journal flag with
2019 Feb 10
2
offtopic: rant about thoughtless enabling DMARC checks
On 10/02/2019 07:38, Ralph Seichter via dovecot wrote:
> * 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
2020 Mar 11
2
lmtp and recipient_delimiter
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 receive mail anymore, because lmtp truncates the localpart
after the '-' and of course can't find the first
2003 Feb 06
6
Why does old kernel boot when new kernel installed?
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
2019 Feb 09
8
offtopic: rant about thoughtless enabling DMARC checks [was: Re: Bounces?]
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
2002 Oct 26
3
How come fsck still kicks in and reports major errors with Ext3?
Greetings.
Total newbie with Ext3. I selected when I upgraded my system to
RH7.2. I upgraded my system again to RH8.0. Here is some info:
[root@world root]# cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext3 rw 0 0
/proc /proc proc rw 0 0
usbdevfs /proc/bus/usb usbdevfs rw 0 0
none /dev/shm tmpfs rw 0 0
none /dev/pts devpts rw 0 0
/dev/hdd1 /mnt/genericdata1 ext2 rw 0 0
Ok, so