amavisd-new does not integrate with Postfix

Bug #41745 reported by René Brandenburger
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Server papercuts
Invalid
Undecided
Unassigned
amavisd-new (Ubuntu)
Confirmed
Wishlist
Unassigned
Declined for Karmic by Thierry Carrez
Declined for Lucid by Thierry Carrez
Nominated for Maverick by Dave Walker

Bug Description

When installing amavisd-new, it does not integrate with an existing postfix mta. To get it working, i have to tweak the configuration files of postfix myself. I would expect the installer / package manager to do this for me.

dapper with fixes up to 27.04.2006 applied.

Revision history for this message
Lionel Porcheron (lionel.porcheron) wrote :

What do you want to get easier ? To activate as the package amavisd-new is installed ?

Actually, you have to add one single line to your configuration file something like:
content_filter=smtp-amavis:[127.0.0.1]:10024

Changed in amavisd-new:
status: Unconfirmed → Needs Info
Revision history for this message
René Brandenburger (rene-brandenburger) wrote :

this is exactly what i expect the package manager to do for me (or at least present me an option to choose if it should be done or not).

I had to add the line you mentionto the main.cf. additionally i had to add the following to the master.cf

smtp-amavis unix - - y - 2 lmtp
 -o smtp_data_done_timeout=1200
 -o disable_dns_lookups=yes
127.0.0.1:10025 inet n - y - - smtpd
 -o content_filter=
 -o local_recipient_maps=
 -o smtpd_client_restrictions=
 -o smtpd_helo_restrictions=
 -o smtpd_sender_restrictions=
 -o smtpd_recipient_restrictions=permit_mynetworks,reject
 -o mynetworks=127.0.0.0/8

Revision history for this message
Ante Karamatić (ivoks) wrote :

Please, contribute to these specifictions:
https://launchpad.net/distros/ubuntu/+spec/server-config-wizard
https://launchpad.net/distros/ubuntu/+spec/postfix-candy

This isn't a bug, but a feauture request. Marking it as Whishlist.

Changed in amavisd-new:
status: Needs Info → Confirmed
Revision history for this message
Scott Kitterman (kitterman) wrote :

We have most of the piece parts into the Postfix package to support this in Intrepid, but it came very late in the process. We ought to be able to do something with this issue in Jaunty.

Changed in amavisd-new:
assignee: nobody → kitterman
milestone: none → jaunty-alpha-6
status: Confirmed → In Progress
Changed in amavisd-new:
assignee: kitterman → nobody
milestone: jaunty-alpha-6 → none
status: In Progress → Confirmed
Revision history for this message
Scott Kitterman (kitterman) wrote :

Not a papercut. Doing this in a policy compliant way is non-trivial (and subject of a spec).

Changed in server-papercuts:
status: New → Invalid
Revision history for this message
Ante Karamatić (ivoks) wrote :

Watch bug 41745.

Revision history for this message
Thierry Carrez (ttx) wrote :

Declining for Karmic until this is solved in the development release. Also not a post-FeatureFreeze Lucid target.

Revision history for this message
Dave Walker (davewalker) wrote :

Proposing for Maverick, as i believe there was already some work going on with this.

Also requesting some feedback with how that is going? :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.