Postings by Andreas Thienemann

Trying to understand smtpd_recipient_restrictions order


I was under the impression, that smtpd_recipient_restrictions and other
restriction configuration items were being processed top to bottom.

I am running postfix 3.2.2 and as far as I can see my postfix is showing a
different behavior.

I have the following items in my config:

smtpd_recipient_restrictions = check_recipient_access proxy:mysql:/etc/postfix/
check_recipient_access proxy:mysql:/etc/postfix/

Virtual Mailbox Delivery with mixed address classes.


I am trying to wrap my head around the different address classes and how
to combine that with the virtual mailbox delivery system.

I currently have a mailserver that serves as final destination for a
domain, say which is configured as mydestination.

I have users on that domain (<a href="mailto: ... at example dot com"> ... at example dot com</a>) which are getting mail
delivered via lmtp configured under mailbox_transport to a dovecot server.

There are some virtual users that have mailroutes such as <a href="mailto: ... at example dot net"> ... at example dot net</a>
-> user.

Re: Postfix and smfi_setmlreply() milter command resulting in SMTP protocol breakage.

Hi John,

True. But considering that Net::Milter also does the right thing, it seems like
a good conclusion that Postfix was doing line folding.

But you are right, it is good to verify.

Postfix and smfi_setmlreply() milter command resulting in SMTP protocol breakage.


I have a locally developed milter using the python-milter bindings which
seems to trigger a Postfix bug.

The milter in question uses the smfi_setmlreply() command to set a
multiline response as defined in rfc5321.

Multiline replies should result in the smtpd replying with something like
the following to e.g.

check_recipient_access after rewrite happens


During migration of an inherited mail system I have the situation that I
would like to reject certain recipient address _after_ they have been
rewritten through the virtual_alias_maps.

The old system had a spam sink where users could redirect certain local
parts. e.g. a user has a catchall account on his domain but
has burned <a href="mailto: ... at example dot com"> ... at example dot com</a> and it is full of spam.

Mixing of address classes per domain


I have inherited an older postfix and sendmail system with a cyrus imapd.
My plan now is to migrate that to a postfix 3.x MTA with a dovecot imap
Pretty standard so far.

When trying to migrate the existing mail routing logic I did come accross
certain rules which are working correctly on the old system but where I am
having problems fitting them into the current address classes logic.

Local addresses are handled currently through a mailbox_transport =
lmtp:private/dovecot-lmtp entry.

Interest in a 32bit tree of the upcoming CentOS7?


I'm in the process of building myself a 32bit tree of the RHEL7 beta as
I do have a few x86 machines I am not ready to retire yet.

Now that CentOS is all open and community etc.

RPM Soft dependencies (Was: Re: Agenda for the 2009-05-26 Packaging Committee meeting)

Your example explains why the current SuSE way of doing soft dependencies
is not the best way of doing it.

But I think everyone is in agreement that we need soft dependencies in
order to sort out our current dependency mess. It increasingly happens
that half the desktop is being pulled in for system services. Soft
dependencies, together with dlopen() might be a good way of solving this.

Therefore I'm wondering: Are there any better ways of solving this and
when can we expect them? :)