On 19/09/2011 17:03, Reindl Harald wrote:
Am 19.09.2011 16:55, schrieb Tawanda Kavayi:
On 19/09/2011 16:44, Reindl Harald wrote:
so you should make your setup simpler or put your configuration in sql-tables
however, the MX has to reject unknown rcpt directly or you are a backscatter
and will be blocked soon somewhere
The server in question is actually not an MX and does not recieve mail directly
from the Internet. It only fetches mail from the actual MX server where every
user
has a mail box. Internet originating mail, sent to an unknown local mail box on
the
MX will be bounced immediately. So there is no chance of backscatter.
DO NOT POST OFFLIST
so what exactly is your problem?
if your MX is configured correct it would not deliver to the wrong destination
you say your MX knows valid addresses - so why does he not know the
final-destination?
BTW:
"on the MX will be bounced immediately. So there is no chance of backscatter"
if it is BOUNCED you ARE are backscatter
there is a hughe difference between bounce/reject
if a message is rejected to server who tried to deliver will generate the bounce
to his sender, if you bounce you will send error-message to forged senders which
is the definition of backscatters
I think I have failed to describe the scenario accurately.
The MX server is not the problem, and it is not where I want this setup.
If the MX server doesn't know a mailbox it will reject mail. There is a
second server. This second server does not receive or send Internet mail
directly. It uses fetchmail to collect mail from mailboxes on the MX
server and deliver it to local mailboxes. These local mailboxes are in
the same email domain as on the MX. Every user in the email domain has a
mailbox on the MX. A few users also have mail boxes on the second
server. Outbound mail is also sent from the second server, and relayed
via the MX to the Internet (the MX is the relayhost for the second server).
A local user on the second server wants to send mail to a user who is
not local to this box, but has a mailbox on the MX. Instead of the
second server rejecting the mail as being for a unknown local user, I
want it to deliver the mail instead to the MX.
I have had this working without a problem before, using the
fallback_transport parameter of Postfix. I was using unix accounts then.
This time, I want the same behaviour but I am using Postfixadmin and
non-unix accounts (Mysql). In main.cf, I had:
local_recipient_maps =
fallback_transport = smtp:another.server.com
Unknow local mail was not rejected, and instead forwarded to
another.server.com. My problem is that with postfixadmin, and non-unix
accounts, this doesn't work.
Tawanda
