This is the Postfix program <postmaster>

[edge]

... 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>

I think the <postmaster> should show an email address? (the email address of the server owner)?

Is there a place where I can set this, and if so.. where :-)?

Thank you..

[falko]

Take a look here: http://www.postfix.org/bounce.5.html

[edge]

Originally Posted by falko

Take a look here: http://www.postfix.org/bounce.5.html

Hmmm

1)

GENERAL PROCEDURE
To create customized bounce template file, create a tempo-
rary copy of the file /etc/postfix/bounce.cf.default and
edit the temporary file.

I do not have the "bounce.cf.default", so I created one named temporary_file with this in it (as test):

# 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_name program 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_name program
           EOF

2)

To preview the results of $name expansions in the template
text, use the command

postconf -b temporary_file

This is a no go.... I get this error:

[root@host postfix]# postconf -b temp_bounce
postconf: invalid option -- b
postconf: fatal: usage: postconf [-c config_dir] [-d (defaults)] [-e (edit)] [-he...]

There is NO -b option !

Falko..... HELP PLS! :-)

[falko]

Please run

updatedb
locate bounce.cf

and post the output.

Maybe something's different on your Postfix version. Instead of reading http://www.postfix.org/bounce.5.html, you can do

man 5 bounce

[edge]

Originally Posted by falko

Please run

updatedb
locate bounce.cf

and post the output.

Maybe something's different on your Postfix version. Instead of reading http://www.postfix.org/bounce.5.html, you can do

man 5 bounce

Hmm I've setup the server with your 'perfect_setup_fedora_core_4'

this is what I get after updating the db (updatedb)

[root@host ~]# updatedb
[root@host ~]# locate bounce.cf
[root@host ~]#

Looks like I do not have a bounce.cf!

Still.. It does send the

This is the Postfix program at host removed_for_now.

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 Postfix program

re: man 5 bounce

[root@host postfix]# man 5 bounce
No entry for bounce in section 5 of the manual

Running 'man 8 bounce' does show me the readme :/


I guess I need to read: http://www.postfix.org/bounce.8.html :-)

Noel

[edge]

Hmmm I'm lost, or I'm missing something here.. There nothing that even looks close with the text

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

in it..

[falko]

Maybe you must install something like postfix-devel on your system? What's the output of

yum search postfix

?

[edge]

Originally Posted by falko

Maybe you must install something like postfix-devel on your system? What's the output of

yum search postfix

?

Lot's of info..

[root@host ~]# yum search postfix
Searching Packages:
Setting up repositories
livna 100% |=========================| 951 B 00:00
updates-released 100% |=========================| 951 B 00:00
base 100% |=========================| 1.1 kB 00:00
extras 100% |=========================| 1.1 kB 00:00
Reading repository metadata in from local files
primary.xml.gz 100% |=========================| 253 kB 00:00
livna : ################################################## 870/870
Added 34 new packages, deleted 0 old in 1.62 seconds
primary.xml.gz 100% |=========================| 380 kB 02:59
updates-re: ################################################## 1078/1078
Added 52 new packages, deleted 144 old in 2.82 seconds
primary.xml.gz 100% |=========================| 1.1 MB 00:02
extras : ################################################## 3343/3343
Added 374 new packages, deleted 177 old in 5.87 seconds


spamassassin.i386 3.0.3-4.fc4 base
Matched from:
SpamAssassin provides you with a way to reduce if not completely eliminate
Unsolicited Commercial Email (SPAM) from your incoming email. It can
be invoked by a MDA such as sendmail or postfix, or can be called from
a procmail script, .forward file, etc. It uses a genetic-algorithm
evolved scoring system to identify messages which look spammy, then
adds headers to the message so they can be filtered by the user's mail
reading software. This distribution includes the spamd/spamc components
which create a server that considerably speeds processing of mail.

To enable spamassassin, if you are receiving mail locally, simply add
this line to your ~/.procmailrc:
INCLUDERC=/etc/mail/spamassassin/spamassassin-default.rc

To filter spam for all users, add that line to /etc/procmailrc
(creating if necessary).


postfix.i386 2:2.2.2-2 base
Matched from:
postfix
Postfix Mail Transport Agent
Postfix is a Mail Transport Agent (MTA), supporting LDAP, SMTP AUTH (SASL),
TLS
http://www.postfix.org


postfix-pflogsumm.i386 2:2.2.2-2 base
Matched from:
postfix-pflogsumm
A Log Summarizer/Analyzer for the Postfix MTA
Pflogsumm is a log analyzer/summarizer for the Postfix MTA. It is
designed to provide an over-view of Postfix activity. Pflogsumm
generates summaries and, in some cases, detailed reports of mail
server traffic volumes, rejected and bounced email, and server
warnings, errors and panics.
http://www.postfix.org


spamassassin.i386 3.0.4-2.fc4 updates-released
Matched from:
SpamAssassin provides you with a way to reduce if not completely eliminate
Unsolicited Commercial Email (SPAM) from your incoming email. It can
be invoked by a MDA such as sendmail or postfix, or can be called from
a procmail script, .forward file, etc. It uses a genetic-algorithm
evolved scoring system to identify messages which look spammy, then
adds headers to the message so they can be filtered by the user's mail
reading software. This distribution includes the spamd/spamc components
which create a server that considerably speeds processing of mail.

To enable spamassassin, if you are receiving mail locally, simply add
this line to your ~/.procmailrc:
INCLUDERC=/etc/mail/spamassassin/spamassassin-default.rc

To filter spam for all users, add that line to /etc/procmailrc
(creating if necessary).


pop-before-smtp.noarch 1.36-2 extras
Matched from:
Spam prevention requires preventing open relaying through email
servers. However, legit users want to be able to relay. If legit
users always stayed in one spot, they'd be easy to describe to the
daemon. However, what with roving laptops, logins from home, etc.,
legit users refuse to stay in one spot.

pop-before-smtp watches the mail log, looking for successful
pop/imap logins, and posts the originating IP address into a
database which can be checked by Postfix, to allow relaying for
people who have recently downloaded their email.


postfix.i386 2:2.2.2-2 installed
Matched from:
postfix
Postfix Mail Transport Agent
Postfix is a Mail Transport Agent (MTA), supporting LDAP, SMTP AUTH (SASL),
TLS and running in a chroot environment.
http://www.postfix.org


spamassassin.i386 3.0.3-4.fc4 installed
Matched from:
SpamAssassin provides you with a way to reduce if not completely eliminate
Unsolicited Commercial Email (SPAM) from your incoming email. It can
be invoked by a MDA such as sendmail or postfix, or can be called from
a procmail script, .forward file, etc. It uses a genetic-algorithm
evolved scoring system to identify messages which look spammy, then
adds headers to the message so they can be filtered by the user's mail
reading software. This distribution includes the spamd/spamc components
which create a server that considerably speeds processing of mail.

To enable spamassassin, if you are receiving mail locally, simply add
this line to your ~/.procmailrc:
INCLUDERC=/etc/mail/spamassassin/spamassassin-default.rc

To filter spam for all users, add that line to /etc/procmailrc
(creating if necessary).


spamassassin.i386 3.0.4-2.fc4 installed
Matched from:
SpamAssassin provides you with a way to reduce if not completely eliminate
Unsolicited Commercial Email (SPAM) from your incoming email. It can
be invoked by a MDA such as sendmail or postfix, or can be called from
a procmail script, .forward file, etc. It uses a genetic-algorithm
evolved scoring system to identify messages which look spammy, then
adds headers to the message so they can be filtered by the user's mail
reading software. This distribution includes the spamd/spamc components
which create a server that considerably speeds processing of mail.

To enable spamassassin, if you are receiving mail locally, simply add
this line to your ~/.procmailrc:
INCLUDERC=/etc/mail/spamassassin/spamassassin-default.rc

To filter spam for all users, add that line to /etc/procmailrc
(creating if necessary).
[root@host ~]#

Whats next :-)

Noel

[falko]

Ok, there's no such package.
You should download the Postfix source code from www.postfix.org and check if there's a bounce.cf.default in there.

[edge]

Originally Posted by falko

Ok, there's no such package.
You should download the Postfix source code from www.postfix.org and check if there's a bounce.cf.default in there.

Okay falko, I'll do so, but the message that is send to users

... 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>

must be somewhere on my my server, as it does send it!
Is there no way of 'hard' coding the <postmaster> to an emailaddress in some file?