Wietse wrote:
I repeat my suggestion that you collect real data to show that
those SMTP packets from gmail actually reach you. Because when
you finally discover that they don't then you can go and fix the
real problem.
You wrote:
i have no idea HOW to get that real data.. I do not have access to the
servers that are connecting and none of my logs shwo info on the
failed attempts
...
Apart from not actually reading what he said. I think you have some weird
crap running on your machine. If you are running postfix, I would expect to
see a postfix banner:
Connected to 209.160.65.133.
Escape character is '^]'.
220 tuna.theoceanwindow-bv.com
Er, no.
tuna.theoceanwindow-bv.com. 360 IN A 209.160.68.112
Okay, lets forget that mess, it will just cause people to look foolish. Fix that
on
the sly would you.
So, go read the top paragraph again. Then have a LONG GOOD LOOK at your
system and work out what the hell is going on. After that, fire up a packet
sniffer
such as tcpdump, snoop, etherreal (or whatever the fsck it's called now) and
watch
for packets on port 25. Sit there and watch it, send yourself some google spam
from
somewhere and WAIT for the connection.
You are, of course, free to install sendmail, it is well known that the best way
to
fix problems with the jellyware is to go do something completely unrelated. If,
by
some magic, installing sendmail fixes your problem. Well and good. Do not
consider
a career as a unix admin, art needs you.
P
