Jesse,
It's probably fine, I'd guess - that's what your postfix config
is setup to use, also. Try "file /usr/sbin/sendmail.postfix" and
see if it is a readable script though, just for fun. What linux
distribution are you using, btw?
I use RedHat v8.0 in my linux box. I made the file comand and this is
just a link to /usr/sbin/sendmail.
From looking at your aliases table, neither one of these are in
there. So all the messages having problems are trying to be delivered
to addresses that aren't found ... what version of dbmail are you
running? All addresses you're going to send to need to be in the
aliases table; I just tried a bad address here, and dbmail created
a bounce saying the user was unknown.
In your dbmail.conf you have:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
But you don't have a [EMAIL PROTECTED] alias in dbmail's
aliases table. There are a lot of other postmaster aliases (all of
which have "postmaster" as the deliver_to, which itsself doesn't have
an entry in aliases table either).
This email adress are not in alias table becouse they are in another
machine. I have two mail servers one is only for cnett.com.br domain and
the other (this one that is getting crazy) is for my domain like
marilon.com.br, radioeducadora1120.com.br and many others.
I have an alias like this:
All messages for domain @lojatrento.com.br must be redirected to email
address [EMAIL PROTECTED] (in other server), will it work?
It looks like there may be some confusion on postfix vs. dbmail
aliases (which isn't terribly uncommon - a good item to be covered
in the upcomming documentation). Postfix has it's own aliases,
in /etc/postfix/aliases for your case; these are completely seperate
from dbmail's aliases table. Postfix uses them for forwarding/
duplicating/whatever mail before it ever hits dbmail. When a
message is going for final delivery (from postfix's perspective)
and it is to a domain handled by the dbmail: transport, postfix
hands it off, telling dbmail what it's current recipient is (via
${recipient} param in master.cf). Dbmail then takes the message
and will try to lookup an entry in the aliases table for whatever
recipient it was given. If that fails, it'll try to send a bounce,
using sendmail (which re-injects into postfix's arena). If the
aliases table lookup does return something, it'll try to recursively
lookup that result back into the aliases table, until it finally
gets something that's not in the "alias" side of that table, and
it tries to deliver it. If the result is numeric, it's treated as
a user_idnr from a user in the users table, and looks for an INBOX.
It could also be a command or an email address for off-site delivery.
Never will dbmail look at your postfix aliases table to expand
"postmaster" into anything else, so any of those should be failing.
So if I need to make all postmaster messagens from all domains
registered in dbmail tranport be sent to another postmaster account in
another linux box, how can I do the alias for this?
You might see if you can find the package for this program,
as it's very useful in tracking what a process is doing (about
as good as you can do without actually tracing it in a debugger).
I will find this and install in my box.
I've never run across this exact problem before, and don't know
why the processes are hanging around so long. Try cleaning up
all the aliases though, and see if that fixes things. Typically you
just get a huge amount of mail in a loop trying to deliver/bounce
to bad addresses when things are messed up like this. Is any mail
getting through at all, just certain ones failing?
Yes... The most emails are getting in correctly but some hangs. Some of
them hangs in SMTP (when some user from one of the domains try to send
an email) and others hangs in POP (when a client try to catch his messages).
I will wait for you answer about my aliases and them I will delete every
alias and create all by hand.
Thanks a lot for you help.
Nataniel Klug
