OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Vivek Khera (khera_at_kcilink.com)
Date: Mon Feb 03 2003 - 08:43:13 CST

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

    >>>>> "p" == postfix-users <postfix-userslists.netways.de> writes:

    p> Postfix is receiving the mails as usual -> then it does a forward of all mails via transport to -> smtp:localhost:10024 -> to the amavisd ?!

    Not via transport, via content_filter.

    p> Then amavisd is doing itīs work -> then it should forward all mail again to (my internal server or whatever, via the parameter:
    p> $forward_method = 'smtp:xx.xx.xx.xx:25';

    No, to smtp:localhost:10025

    p> smtp-amavis unix - - n - 2 smtp
    p> -o smtp_data_done_timeout=1200
    p> -o disable_dns_lookups=yes

    This adjusts how postfix speaks to amavis.

    p> 127.0.0.1:10025 inet n - n - - smtpd
    p> -o content_filter=
    p> -o local_recipient_maps=
    p> -o smtpd_helo_restrictions=
    p> -o smtpd_client_restrictions=
    p> -o smtpd_sender_restrictions=
    p> -o smtpd_recipient_restrictions=permit_mynetworks,reject
    p> -o mynetworks=127.0.0.0/8

    This is so that when amavisd-new hands the filtered content back to
    postfix, it doesn't go into a loop.

    p> In main.cf :
    p> content_filter=smtp-amavis:[localhost]:10024 (the port amavis is listening on)

    This is what tells postfix to give it to amavis.

    Just follow the directions in the amavisd-new install file and you'll
    be all set.

    -- 
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Vivek Khera, Ph.D.                Khera Communications, Inc.
    Internet: kherakciLink.com       Rockville, MD       +1-240-453-8497
    AIM: vivekkhera Y!: vivek_khera   http://www.khera.org/~vivek/