Prev: Restrict sending to specific domains only.
Next: Problem with email to subdomains
From: donovan jeffrey j on 28 Jul 2010 22:56
version 2.5.5,

greetings
im upgrading a couple of xserves to 10.6 from 10.4. the main.cf used to be pretty straight forward. The default main.cf on 10.6 snow leopard server has overwhelmed my old eyeballs. may new lines most i understand but they pretty much list every option known to man. anyhoo.

I want to use this system to pickup with postfix, send it to amavis and have either prostfix or amavis realy to another server.

from what i can remember in main.cf

content_filter = smtp-amavis:[127.0.0.1]:10024
this should send to amavis right ?



then in amavisd.conf
$forward_method = 'smtp:smtp.beth.k12.pa.us:2525';

after scanning relay to another system on port 2525

I just want to make sure i have that config down, I don't want the mail to stop and stay on this server. Do I have to add a transport or edit the master to make sure mail hits the content filter?
-j
From: Wietse Venema on 29 Jul 2010 07:16
donovan jeffrey j:
> version 2.5.5,
>
> greetings
> im upgrading a couple of xserves to 10.6 from 10.4. the main.cf
> used to be pretty straight forward. The default main.cf on 10.6
> snow leopard server has overwhelmed my old eyeballs. may new lines
> most i understand but they pretty much list every option known to
> man. anyhoo.

The simplest way to upgrade an existing configuration is:

- Back up the new main.cf, master.cf, postfix-files, postfix-script
and post-install files.

- Install the old main.cf and old master.cf and any files that
you have added to the old Postfix setup.

- DO NOT INSTALL THE OLD POSTFIX-FILES, POSTFIX-SCRIPT AND POST-INSTALL
FILES. You must use the new versions of those files.

- Execute (as root): "postfix upgrade-configuration". This will
update the old main.cf and old master.cf files and add missing
entries that Postfix needs.

This procedure assumes that your vendor did not break "postfix
upgrade-configuration" or any of the files that it depends on.

Wietse

> I want to use this system to pickup with postfix, send it to amavis
> and have either prostfix or amavis realy to another server.
>
> from what i can remember in main.cf
>
> content_filter = smtp-amavis:[127.0.0.1]:10024
> this should send to amavis right ?
>
>
>
> then in amavisd.conf
> $forward_method = 'smtp:smtp.beth.k12.pa.us:2525';
>
> after scanning relay to another system on port 2525
>
> I just want to make sure i have that config down, I don't want
> the mail to stop and stay on this server. Do I have to add a
> transport or edit the master to make sure mail hits the content
> filter?
> -j
>

From: donovan jeffrey j on 29 Jul 2010 08:54

On Jul 29, 2010, at 7:16 AM, Wietse Venema wrote:

> The simplest way to upgrade an existing configuration is:
>
> - Back up the new main.cf, master.cf, postfix-files, postfix-script
> and post-install files.
>
> - Install the old main.cf and old master.cf and any files that
> you have added to the old Postfix setup.
>
> - DO NOT INSTALL THE OLD POSTFIX-FILES, POSTFIX-SCRIPT AND POST-INSTALL
> FILES. You must use the new versions of those files.
>
> - Execute (as root): "postfix upgrade-configuration". This will
> update the old main.cf and old master.cf files and add missing
> entries that Postfix needs.
>
> This procedure assumes that your vendor did not break "postfix
> upgrade-configuration" or any of the files that it depends on.
>
> Wietse

thanks Wietse

these two systems have different mailbox_transports
mailbox_transport = dovecot
mailbox_transport = cyrus

is it as simple as switching these two ? or are there any other considerations.
i have also needed to change the user and group info

mail_owner = postfix to mail_owner = _postfix
setgid_group = postdrop to setgid_group = _postdrop

-j

From: Wietse Venema on 29 Jul 2010 09:33
donovan jeffrey j:
>
> On Jul 29, 2010, at 7:16 AM, Wietse Venema wrote:
>
> > The simplest way to upgrade an existing configuration is:
> >
> > - Back up the new main.cf, master.cf, postfix-files, postfix-script
> > and post-install files.
> >
> > - Install the old main.cf and old master.cf and any files that
> > you have added to the old Postfix setup.
> >
> > - DO NOT INSTALL THE OLD POSTFIX-FILES, POSTFIX-SCRIPT AND POST-INSTALL
> > FILES. You must use the new versions of those files.
> >
> > - Execute (as root): "postfix upgrade-configuration". This will
> > update the old main.cf and old master.cf files and add missing
> > entries that Postfix needs.
> >
> > This procedure assumes that your vendor did not break "postfix
> > upgrade-configuration" or any of the files that it depends on.
> >
> > Wietse
>
> thanks Wietse
>
> these two systems have different mailbox_transports
> mailbox_transport = dovecot
> mailbox_transport = cyrus
>
> is it as simple as switching these two ? or are there any other considerations.

You'll also need to configure the receiving end (dovecot or cyrus).

> i have also needed to change the user and group info
>
> mail_owner = postfix to mail_owner = _postfix
> setgid_group = postdrop to setgid_group = _postdrop

My procedure above is for upgrading an existing setup when there
are no other changes.

If the new system has different usernames or pathnames etc. then
you'll need to put that into the new Postfix configuration.

Wietse

From: donovan jeffrey j on 29 Jul 2010 11:07

On Jul 29, 2010, at 9:33 AM, Wietse Venema wrote:

> donovan jeffrey j:
>>
>> On Jul 29, 2010, at 7:16 AM, Wietse Venema wrote:
>>
>>> The simplest way to upgrade an existing configuration is:
>>>
>>> - Back up the new main.cf, master.cf, postfix-files, postfix-script
>>> and post-install files.
>>>
>>> - Install the old main.cf and old master.cf and any files that
>>> you have added to the old Postfix setup.
>>>
>>> - DO NOT INSTALL THE OLD POSTFIX-FILES, POSTFIX-SCRIPT AND POST-INSTALL
>>> FILES. You must use the new versions of those files.
>>>
>>> - Execute (as root): "postfix upgrade-configuration". This will
>>> update the old main.cf and old master.cf files and add missing
>>> entries that Postfix needs.
>>>
>>> This procedure assumes that your vendor did not break "postfix
>>> upgrade-configuration" or any of the files that it depends on.
>>>
>>> Wietse
>>
>> thanks Wietse
>>
>> these two systems have different mailbox_transports
>> mailbox_transport = dovecot
>> mailbox_transport = cyrus
>>
>> is it as simple as switching these two ? or are there any other considerations.
>
> You'll also need to configure the receiving end (dovecot or cyrus).

for right now, there are no users on this server. there willl only be a junkmail/nojunkmail folder.
all mailboxes are on other servers i have an external relay at server.mydomain:2525 pickingup and delivering this system i want dedicated to filtering content.

>
>> i have also needed to change the user and group info
>>
>> mail_owner = postfix to mail_owner = _postfix
>> setgid_group = postdrop to setgid_group = _postdrop
>
> My procedure above is for upgrading an existing setup when there
> are no other changes.
>
> If the new system has different usernames or pathnames etc. then
> you'll need to put that into the new Postfix configuration.
>
> Wietse


thanks for the reply, i did the update and have no errors on postfix check.

i have setup a test on my mx server to transport mail for lukeskywalker(a)beth.k12.pa.us to mx2.beth.k12.pa.us ( my new 10.6 filter )

so far my mail2 primary mx can send to the filter (mx2). Mx2 ;postfix picks up and sends to amavis. then I get some 554 error,.. im not sure who is complaining.

Jul 29 10:20:08 mx2 postfix/smtpd[63722]: connect from mail2.beth.k12.pa.us[192.227.0.10]
Jul 29 10:20:08 mx2 postfix/smtpd[63722]: 15B7551C06DA: client=mail2.beth.k12.pa.us[192.227.0.10]
Jul 29 10:20:08 mx2 postfix/cleanup[63726]: 15B7551C06DA: message-id=<0D766F25-EC81-452B-9F77-F4C2A0CE2DE1(a)gmail.com>
Jul 29 10:20:08 mx2 postfix/qmgr[63217]: 15B7551C06DA: from=<doctorfoo1(a)gmail.com>, size=2231, nrcpt=1 (queue active)
Jul 29 10:20:11 mx2 postfix/smtp[63727]: 15B7551C06DA: to=<lukeskywalker(a)beth.k12.pa.us>, relay=127.0.0.1[127.0.0.1]:10024, delay=3.4, delays=0.01/0.01/0.01/3.3, dsn=5.1.0, status=bounced (host 127.0.0.1[127.0.0.1] said: 554 5.1.0 Failed, id=63219-01, from MTA([smtp.beth.k12.pa.us]:2525): 554 <mx2.beth.k12.pa.us[10.135.1.23]>: Client host rejected: Access denied (in reply to end of DATA command))

so amavis picks it up then someone says access denied. my next relay is sitting at " smtp.beth.k12.pa.us:2525 " so it looks like that MTA is complaining about MX2 sending to it. maybe because it's says it's hostname is localhost ???

this below is another issue where the bounce can't leave the building.

Jul 29 10:20:11 mx2 postfix/cleanup[63726]: 6C64951C06E7: message-id=<20100729142011.6C64951C06E7(a)mx1.beth.k12.pa.us>
Jul 29 10:20:11 mx2 postfix/bounce[63731]: 15B7551C06DA: sender non-delivery notification: 6C64951C06E7
Jul 29 10:20:11 mx2 postfix/qmgr[63217]: 6C64951C06E7: from=<>, size=4388, nrcpt=1 (queue active)
Jul 29 10:20:11 mx2 postfix/qmgr[63217]: 15B7551C06DA: removed
Jul 29 10:20:11 mx2 postfix/smtp[63732]: connect to gmail-smtp-in.l.google.com[74.125.91.27]:25: Connection refused
Jul 29 10:20:11 mx2 postfix/smtp[63732]: connect to alt1.gmail-smtp-in.l.google.com[74.125.77.27]:25: Connection refused
Jul 29 10:20:11 mx2 postfix/smtp[63732]: connect to alt2.gmail-smtp-in.l.google.com[74.125.43.27]:25: Connection refused
Jul 29 10:20:11 mx2 postfix/smtp[63732]: connect to alt3.gmail-smtp-in.l.google.com[74.125.155.27]:25: Connection refused
Jul 29 10:20:11 mx2 postfix/smtp[63732]: connect to alt4.gmail-smtp-in.l.google.com[74.125.157.27]:25: Connection refused
Jul 29 10:20:11 mx2 postfix/smtp[63732]: 6C64951C06E7: to=<foo1(a)gmail.com>, relay=none, delay=0.03, delays=0/0.01/0.01/0, dsn=4.4.1, status=deferred (connect to alt4.gmail-smtp-in.l.google.com[74.125.157.27]:25: Connection refused)



postconf from MX2
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debug_peer_level = 2
disable_vrfy_command = yes
enable_server_options = yes
html_directory = no
inet_interfaces = localhost
local_recipient_maps =
mail_owner = _postfix
mailbox_size_limit = 0
mailbox_transport = dovecot
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
mydestination = $myhostname,localhost.$mydomain,localhost,beth.k12.pa.us,bethsd.org
mydomain = beth.k12.pa.us
mydomain_fallback = localhost
myhostname = mx1.beth.k12.pa.us
mynetworks = 127.0.0.1/32,10.135.0.0/16,192.227.0.10
mynetworks_style = host
myorigin = $myhostname
newaliases_path = /usr/bin/newaliases
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpd_client_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_rbl_client zen.spamhaus.org, permit
smtpd_data_restrictions = permit_mynetworks, reject_unauth_pipelining
smtpd_helo_required = yes
smtpd_helo_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_non_fqdn_hostname, reject_invalid_hostname, permit
smtpd_recipient_restrictions = permit_mynetworks, reject_unauth_destination, reject_rbl_client zen.spamhaus.org, permit
smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_non_fqdn_sender, permit
smtpd_tls_key_file =
unknown_local_recipient_reject_code = 550



postconf -v has tons of info beyond what i have set.

 |  Next  |  Last
Pages: 1 2
Prev: Restrict sending to specific domains only.
Next: Problem with email to subdomains