Problem with Bounce Mails for non-existent users
Benjamin Bär
I=B4am having some problems with postfix regarding bounce mails for non
existing users.
Following scenario':
Postfix Version 2.0.9 running on a gentoo linux box version 1.4, postfix =
is
running with smtp auth enabled and some virtual_domains attached to it.
Imap or the like is not enabled. Most mail clients are outlook 2000, and
thats where the problem occurs.
If someone using outlook sends a mail to some user within the local domai=
n
but the misspelled the account name, postfix gives back an 550 error
reporting the user does not exist, which is ok, but outlook is too dumb t=
o
recognize that so the mail resides in the outbox of outlook, and on the n=
ext
run outlook will try to send that mail again.
Now my question is, is there a way to tell postfix that it should "FIRST"
collect the mail from the client, then disconnect from the client, check
what to to with that specific mail, and when it detects send back an boun=
ce
that the user does not exist, and no directly during the smtp connection,
because if someone within the company does that on friday evening and
forgets to shutdown his computer, i woould get something bout 500 bounce
mails to the postmaster account on monday.
I remember that there was some feature in the version prior to 2.x that t=
ook
care of that, but apperently some default setting was changed, and it see=
ms
I=B4am not smart enough to find it.
many thanks in advance.
yours Benjamin
attached, postconf -n
----- snip -------
2bounce_notice_recipient =3D sysa...@vcc.de
alias_database =3D hash:/etc/mail/aliases
alias_maps =3D hash:/etc/mail/aliases
bounce_notice_recipient =3D sysa...@vcc.de
broken_sasl_auth_clients =3D yes
command_directory =3D /usr/sbin
config_directory =3D /etc/postfix
content_filter =3D smtp-amavis:[127.0.0.1]:10024
daemon_directory =3D /usr/lib/postfix
debug_peer_level =3D 2
default_destination_concurrency_limit =3D 10
disable_verp_bounces =3D yes
disable_vrfy_command =3D yes
local_destination_concurrency_limit =3D 2
local_recipient_maps =3D $alias_maps unix:passwd.byname
mail_owner =3D postfix
mail_spool_directory =3D /var/spool/mail
mailbox_size_limit =3D 512000000
message_size_limit =3D 50214400
mydestination =3D $myhostname, localhost.$mydomain $mydomain
mydomain =3D vcc.de
myhostname =3D mail.vcc.de
mynetworks =3D 127.0.0.0/8, 217.111.2.0/24
myorigin =3D vcc.de
notify_classes =3D resource, software, bounce, protocol
queue_directory =3D /var/spool/postfix
queue_file_attribute_count_limit =3D 1000
recipient_delimiter =3D +
relay_transport =3D smtp
show_user_unknown_table_name =3D no
smtpd_recipient_restrictions =3D permit_sasl_authenticated, permit_mynetw=
orks,
reject_unauth_destination
smtpd_sasl_auth_enable =3D yes
smtpd_sasl_local_domain =3D
smtpd_sasl_security_options =3D noanonymous
soft_bounce =3D no
----- snap ------
Kyle Dent
You can disable local_recipient_maps. But be aware that you'll
also have to bounce all the junk mail that comes in for
non-existent users -- bad idea.
Kyle
Wietse Venema
> On Fri, 23 Jan 2004, [iso-8859-1] Benjamin B?r wrote:
> > Now my question is, is there a way to tell postfix that it should "FIRST"
> > collect the mail from the client, then disconnect from the client, check
> > that the user does not exist, and no directly during the smtp connection,
> You can disable local_recipient_maps. But be aware that you'll
> also have to bounce all the junk mail that comes in for
> non-existent users -- bad idea.
What I can do for Postfix 2.1 is to make the automatic local
recipient check optional so that you can make exceptions.
Then it would look like this:
smtpd_reject_unlisted_recipient = no
smtpd_recipient_restrictions =
permit_mynetworks
permit_sasl_authenticated
reject_unauth_destination
reject_unlisted_recipient
...other restrictions...
Ditto with unlisted sender addresses; the Postfix 2.1 server will
reject those by default as well.
(reject_unlisted_recipient is an alias for check_recipient_maps;
the name change is because Postfix 2.1 also has the same test
for senders, and it's called reject_unlisted_sender for obvious
reasons).
Wietse
Kyle Dent
Yep, I suppose that will help alot of people. More complications
(and documentation) to work around braindead software. Oh, well.
Kyle
Benjamin Bar
additional 500 mails a week.
And i think adding that option to the code would be better, because if i get
this right, when i disable the local_recipient_maps, the existing local
users would not get their mails aswell ? or am I wrong at this.
Anyway, that sounds like a solution so i wait for version 2.1
Wietse do you allready have some release date on focus ?
yours Benjamin
-----Ursprungliche Nachricht-----
Von: owner-pos...@postfix.org
[mailto:owner-pos...@postfix.org]Im Auftrag von Kyle Dent
Gesendet: Freitag, 23. Januar 2004 17:48
An: Postfix users
Betreff: Re: Problem with Bounce Mails for non-existent users