Sponsored Content
Full Discussion: PostFix configuration
Top Forums UNIX for Advanced & Expert Users PostFix configuration Post 302500044 by giorgiocol78 on Saturday 26th of February 2011 01:47:42 PM
Old 02-26-2011
PostFix configuration

Hello

I'm new in this forum so I don't know if this is the correct page for my question.
We have a server ,running RedHat 3, with installed Postfix 2.2.11 with Amavis , SpamAssassin and ClamAv.
This server is used by several years without problem.

Now we have some some problems with spam/bounced messages and we have the necessity, if possible , to send forwarding errors ( in case of errors during forward of messages to some mailling list we have configured ) only to a local mail system administrator on our system , so that this person can verify/fix the problem.

I have seen that in the master.cf file there is a line in which we can decide what to do with bounce messages ( default operation is "bounce" ).
We have set it to "discard" but i don't think this is the correct solution - in this case simply postfix deletes the bounce message.

Also, when relaying authenticated mail, we need to add the authenticated user as a
header in the relayed mail.

Please, can you help me with this problems / configurations?

Thank you
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Postfix

I can send email. I just can't receive email I am getting and error Permanent Failure: 554_Transaction_failed. All the services are running. I can telnet to 110 25 143. I am also running Imap. I can send and receive email internally I can send email outside of my network I can't receive emails... (3 Replies)
Discussion started by: rbizzell
3 Replies

2. UNIX for Advanced & Expert Users

Postfix 2.3.

When I use the postalias command I am getting an error that says no mapping in /etc/mail/mailer.conf. I am running FreeBsd 6.1 and in my main.cf I have my alias database is alias_maps= hash:/etc/mail/aliases I tried the command two different ways /usr/local/sbin/postalias /etc/mail/aliases... (2 Replies)
Discussion started by: rbizzell
2 Replies

3. Linux

postfix configuration issues...specifically masquerading (lack of )

postfix configuration issues...specifically masquerading (lack of ) Mail sent to our intranet arrives correctly (me@domain.com). Mail sent to our intranet arrives correctly (me@domain.com). Anything going outside does not, so my tests get rejected (me@hostname.com) :( any assistance... (5 Replies)
Discussion started by: mr_manny
5 Replies

4. Linux

postfix

hi when I telnet to my machine on port 25 and send an email to myself, the machine sends the email to the old corporate mail server instead of the new corporate mail server. how to change that so that any email sent from my linux box goes directly to the new mail server? thx (2 Replies)
Discussion started by: melanie_pfefer
2 Replies

5. IP Networking

postfix - reinject mail to postfix from hold queue directory

hi all. Am using smtpd_recipient_restrictions & check_recipient_access in postfix. The hash file looks like this: emailaddress1 HOLD emailaddress2 HOLD The aim is to place email from these recipients in the hold directory,check them then reinject them back in postfix on some... (0 Replies)
Discussion started by: coolatt
0 Replies

6. UNIX for Dummies Questions & Answers

Please help with Postfix config issue - How to allow remote Exchange server to relay to my postfix

Hi guys One of our clients have a problem with sending email to a certain domain. No matter what we try, the mails just dont get delivered. What I did then, is created a new connector on their Exchange server, pointing all mail sent to their client at "domain1" to relay to our Postfix mail... (0 Replies)
Discussion started by: wbdevilliers
0 Replies

7. Solaris

Errors in postfix configuration on solaris 10

Hi Geeks, I am trying to configure 'postfix' for sending mail only instead of 'sendmail'. I am getting following error when I try to send mail using mailx command. #echo "test" | mailx -s "test mail" <username> -- command executed from server --/var/log/syslog output : Jul 8 12:55:44... (0 Replies)
Discussion started by: abhkadam
0 Replies

8. UNIX for Dummies Questions & Answers

Postfix Configuration:Hostname/Domain Name Doubts

I have a RHEL server where I want to create a mail server so I can send myself alerts whenever X process have problems. Disclaimer: Im a programmer thats been forced to do IT. So I'm trying my best here. The problem: While configuring Postfix it asks for $myhostname which apparently must be... (2 Replies)
Discussion started by: RedSpyder
2 Replies

9. UNIX and Linux Applications

Postfix: Active Directory and postfix alias

I have a mailserver with postfix i want to alias all mail for administrator@domain.fqdn to root@domain.fqdn I have the aliases configured,and i did newliases but doesn't work. How to did this?Postfix is configured for virtual domain on ad server. (2 Replies)
Discussion started by: Linusolaradm1
2 Replies

10. UNIX for Advanced & Expert Users

Postfix Configuration

Hi, i have to configure postfix in this mode: - if i receive a mail from a@a.a relay to - if i receive a mail NOT from a@a.a relay the mail to user "test" that is on localhost For the first rule i do this in main.cf: sender_dependent_default_transport_maps = hash:/etc/postfix/sender_check... (0 Replies)
Discussion started by: certo85
0 Replies
BOUNCE(5)							File Formats Manual							 BOUNCE(5)

NAME
bounce - Postfix bounce message template format SYNOPSIS
bounce_template_file = /etc/postfix/bounce.cf postconf -b [template_file] DESCRIPTION
The Postfix bounce(8) server produces delivery status notification (DSN) messages for undeliverable mail, delayed mail, successful delivery or address verification requests. By default, these notifications are generated from built-in templates with message headers and message text. Sites can override the built- in information by specifying a bounce template file with the bounce_template_file configuration parameter. This document describes the general procedure to create a bounce template file, followed by the specific details of bounce template for- mats. GENERAL PROCEDURE
To create a customized bounce template file, create a temporary copy of the file /etc/postfix/bounce.cf.default and edit the temporary file. To preview the results of $name expansions in the template text, use the command postconf -b temporary_file Errors in the template will be reported to the standard error stream and to the syslog daemon. While previewing the text, be sure to pay particular attention to the expansion of time value parameters that appear in the delayed mail notification text. Once the result is satisfactory, copy the template to the Postfix configuration directory and specify in main.cf something like: /etc/postfix/main.cf: bounce_template_file = /etc/postfix/bounce.cf TEMPLATE FILE FORMAT
The template file can specify templates for failed mail, delayed mail, successful delivery or for address verification. These templates are named failure_template, delay_template, success_template and verify_template, respectively. You can but do not have to specify all four templates in a bounce template file. Each template starts with "template_name = <<EOF" and ends with a line that contains the word "EOF" only. You can change the word EOF, but you can't enclose it in quotes as with the shell or with Perl (template_name = <<'EOF'). Here is an example: # The failure template is used for undeliverable mail. failure_template = <<EOF Charset: us-ascii From: MAILER-DAEMON (Mail Delivery System) Subject: Undelivered Mail Returned to Sender Postmaster-Subject: Postmaster Copy: Undelivered Mail This is the mail system at host $myhostname. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system EOF The usage and specification of bounce templates is subject to the following restrictions: o No special meaning is given to the backslash character or to leading whitespace; these are always taken literally. o Inside the << context, the "$" character is special. To produce a "$" character as output, specify "$$". o Outside the << context, lines beginning with "#" are ignored, as are empty lines, and lines consisting of whitespace only. Examples of all templates can be found in the file bounce.cf.default in the Postfix configuration directory. TEMPLATE HEADER FORMAT
The first portion of a bounce template consists of optional template headers. Some become message headers in the delivery status notifica- tion; some control the formatting of that notification. Headers not specified in a template will be left at their default value. The following headers are supported: Charset: The MIME character set of the template message text. See the "TEMPLATE MESSAGE TEXT FORMAT" description below. From: The sender address in the message header of the delivery status notification. Subject: The subject in the message header of the delivery status notification that is returned to the sender. Postmaster-Subject: The subject that will be used in Postmaster copies of undeliverable or delayed mail notifications. These copies are sent under con- trol of the notify_classes configuration parameter. The usage and specification of template message headers is subject to the following restrictions: o Template message header names can be specified in upper case, lower case or mixed case. Postfix always produces bounce message header labels of the form "From:" and "Subject:". o Template message headers must not span multiple lines. o Template message headers do not support $parameter expansions. o Template message headers must contain ASCII characters only, and must not contain ASCII null characters. TEMPLATE MESSAGE TEXT FORMAT
The second portion of a bounce template consists of message text. As the above example shows, template message text may contain main.cf $parameters. Besides the parameters that are defined in main.cf, the following parameters are treated specially depending on the suffix that is appended to their name. delay_warning_time_suffix Expands into the value of the delay_warning_time parameter, expressed in the time unit specified by suffix, which is one of seconds, minutes, hours, days, or weeks. maximal_queue_lifetime_suffix Expands into the value of the maximal_queue_lifetime parameter, expressed in the time unit specified by suffix. See above under delay_warning_time for possible suffix values. The usage and specification of template message text is subject to the following restrictions: o The template message text is not sent in Postmaster copies of delivery status notifications. o If the template message text contains non-ASCII characters, Postfix requires that the Charset: template header is updated. Specify an appropriate superset of US-ASCII. A superset is needed because Postfix appends ASCII text after the message template when it sends a delivery status notification. SEE ALSO
bounce(8), Postfix delivery status notifications postconf(5), configuration parameters LICENSE
The Secure Mailer license must be distributed with this software. HISTORY
The Postfix bounce template format was originally developed by Nicolas Riendeau. AUTHOR(S) Wietse Venema IBM T.J. Watson Research P.O. Box 704 Yorktown Heights, NY 10598, USA BOUNCE(5)
All times are GMT -4. The time now is 12:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy