wietseporcupine.org (Wietse Venema) writes:

> change hash_queue_depth default
>
> The default depth of 2 subdirectory levels makes mailq
> unnecessarily slow for most sites. I am inclined to make the
> default 1, which sucks when your site has lots of mail queued.

My vote: Go for "1".

Rationale: Many file systems have been tuned or are under tuning,
particularly the DIRHASH stuff is going to make things fast. FreeBSD is
there, Linux is almost there (user-space, e2fsprogs, is there), and the
user can and should choose the OS best suited for his purpose.

> deprecate check_relay_domains
>
> This restriction should go away. As of version 1.2, any use of
> check_relay_domains should produce a warning and suggest using
> "reject_unauth_destination" instead, and this feature should
> be removed from the documentation.

My vote: Go for it. Less options, less confusion.

> keep HOLD/DISCARD actions
>
> I'm inclined to include these in the 1.2 release, even though
> their use in smtpd_xxx_restrictions is currently limited to
> access maps.

Do you consider them "mature" or "good enough"?

> keep qmgr_clog_warn_time
>
> I'm inclined to include this in the 1.2 release. When this
> parameter setting is non-zero, the Postfix queue manager warns
> when mail for some destination is piling up in the active queue,
> and suggests a variety of remedies to speed up delivery (increase
> per-destination concurrency limit, increase active queue size,
> use a separate delivery transport, increase per-transport
> process limit). The heuristics and recommendations are a bit
> questionable, but I haven't heard any complaints, which means
> either people don't read their logs or the suggestions actually
> help.

Or people don't even set that parameter ;-) Seriously, I've never seen
that warning -- OTOH, mail is usually delivered immediately, or destined
for the local transport with an NFS server down.

No vote here.

> snapshot only: sender-based routing
>
> I'm inclined to not include this in the 1.2 release. With
> sender_based_routing=yes, Postfix will choose the delivery
> transport and "nexthop" host by looking at the sender address
> instead of the recipient.

It's undocumented and last time I tried, you told me it worked different
from how I had described it, so I evidently hadn't understood it. Don't
include undocumented code: principle of least astonishment.

My vote: drop it from the stable branch.

> If you found other problematic default settings or features in
> recent snapshots, now is a good time to let me know.

I have one, make these defaults, to better match sendmail's behaviour
and "do the right thing":

local_recipient_maps = $alias_maps $relocated_maps
                       unix:passwd.byname nis:passwd.byname
recipient_delimiter = +

I'd also suggest adding

strict_rfc821_envelopes = yes

Yes, I know your opinion on strict_*, and while strict_7bit_headers has
caused grief particularly with broken Netscape Communicator versions (so
leaving that as no is fine), eBay mailings and various other stuff, I
haven't seen a single RFC-821 reject except for spam.

I also have line for sample-local.cf, add below the procmail line:

#mailbox_command = /some/where/maildrop -d "$USER" -f "$SENDER" "$EXTENSION"

(Note the -d is mandatory to prevent maildrop from mistaking the
"$EXTENSION" as a configuration file to use instead of
$HOME/.mailfilter.)

I have a question as to the local(8) mbox vs. maildir behaviour and
From_ lines; my local(8) man page currently states that

- in maildir delivery, Delivered-To and Return-Path were added, and

- for UNIX-style mailbox delivery, the From_ line, X-Original-To,
  Delivered-To and Return-Path were added.

I feel that X-Original-To should be present in any case regardless of
the spool format, and if it is, the local man page might need fixing.

The differences I see between mbox and maildir are only related to
From_, escaping these and adding an empty line if the last line of the
mail is incomplete in mbox.

I'd also appreciate an explicit note in local(8) if mail to external
commands escapes existing From_ lines or no.

For your post-1.2 TODO: Instead of turning From_ lines to >From_, an
option for quoted-printable mail is: change "From " to "=46rom ". I
believe this is mentioned as option in one of the MIME RFCs
(2045ff). This "From " -> "=46rom " should also be considered for
outgoing mail that is re-encoded from 8bit to quoted-printable as per
RFC-1652 (8BITMIME).

-- 
Matthias Andree

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]