Error "#4.4.2" when send mail.

[Nguyen Minh Son]

Hi.
I have trouble with my mail server. All day, when my client try to send
mail to 3 domain in Thailan, Singapore and Malaisia. They all receive
the error report :

Hi. This is the qmail-send program at mailsrv01.xxxx
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<x...@xxx.com.sg>:
User and password not set, continuing without authentication.
<x...@xxx.com.sg> Connected to xxx.xxx.xxx.xxx but connection died. (#4.4.2)
I'm not going to try again; this message has been in the queue too long.

I checked these domain and found mx was okie, port 25 in each server of
each domain was open.
I checked these log in my server and found that we can receive the email
from all these domain but can't send email to these domain. All email to
these domain were in the queue and can not be delivered. The log in the
smtp log said :

<x...@xxx.com.sg> Connected to xxx.xxx.xxx.xxx but connection died. (#4.4.2)

Can anyone give me an idea?
Thanks

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de

[U. George]

> <x...@xxx.com.sg> Connected to xxx.xxx.xxx.xxx but connection died. (#4.4.2)
>
>
> Can anyone give me an idea?
> Thanks
>

you are (probably) being blacklist by the ISP's IP firewall rules.

[Nguyen Minh Son]

U. George wrote:
>
>> <x...@xxx.com.sg> Connected to xxx.xxx.xxx.xxx but connection died.
>> (#4.4.2)
>>
>>
>> Can anyone give me an idea?
>> Thanks
>>

> you are (probably) being blacklist by the ISP's IP firewall rules.
>
>

But I can still send email to all other domain except these 3 domain
above include yahoo and gmail. :(

[Kyle Wheeler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday, March 3 at 05:53 PM, quoth Nguyen Minh Son:

> <x...@xxx.com.sg>:
> User and password not set, continuing without authentication.
> <x...@xxx.com.sg> Connected to xxx.xxx.xxx.xxx but connection died. (#4.4.2)
> I'm not going to try again; this message has been in the queue too long.

Connection died? Hmm. Have you changed your sending timeouts? Maybe
you should try making them longer. For example:

echo 2400 > /var/qmail/control/timeoutremote

It would be somewhat surprising if that was really the problem, but...
not out of the realm of possibility.

The real question you have to find an answer to is: why did the
connection die? The above solution MAY fix it if it's just that you've
got a slow network (if you've got a lousy network, you're dealing with
timeouts both on your side and on the receiver's side; they may decide
to close the connection because you haven't responded recently).

But maybe there's another reason; such as you have a lousy ISP or a
broken firewall appliance that is killing your SMTP connections.

Good luck figuring it out!

~Kyle
- --
Truth springs from argument amongst friends.
-- David Hume
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iEYEARECAAYFAkmtSywACgkQBkIOoMqOI17swgCg5cmCSg+9QTXXU6Dzwol1RL6l
C/8An3uNYzosU08fZsaT6lxb8fSGs3W7
=2loQ
-----END PGP SIGNATURE-----

[Erwin Hoffmann]

Hi,

actually, the most important information is:

--On Dienstag, März 03, 2009 09:22:20 -0600 Kyle Wheeler
<kyle-...@memoryhole.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tuesday, March 3 at 05:53 PM, quoth Nguyen Minh Son:

>> <x...@xxx.com.sg>:
>> User and password not set, continuing without authentication.
>> <x...@xxx.com.sg> Connected to xxx.xxx.xxx.xxx but connection died.

Which means, a patched qmail was used (for SMTP authentication; but not
mine).

> I'm not going to try again; this message has been in the queue
>> too long.
>

> Connection died? Hmm. Have you changed your sending timeouts? Maybe
> you should try making them longer. For example:

The remote server does not properly respond to none-authenticated SMTP
connections.

>
> echo 2400 > /var/qmail/control/timeoutremote
>
> It would be somewhat surprising if that was really the problem, but...
> not out of the realm of possibility.

This is not the problem; it is the AUTH protocol implementation which is
broken on any of both sides.

regards.
--eh.

---
Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de/

[Nguyen Minh Son]

Markus Stumpf wrote:
> On Tue, Mar 03, 2009 at 05:53:01PM +0700, Nguyen Minh Son wrote:
>
>> <x...@xxx.com.sg>:
>>
>
> xxx.com.sg is a domain parked at sedo (a company specialised in domain
> parking and selling).
> Probably they don't accept mail for that domain.
>
> If xxx.com.sg is NOT the domain, then stop obfuscating relevant
> information you want help for, by accusing someone not responsible for the
> domain you have problems with.
>
> You could have smtproutes set, fecked up your DNS, but by hiding this
> information all we have left is a false reference to an existing domain
> and a crystal ball.
>
> If you can't or don't want to disclose this information then hire
> someone who will sign a non-disclosure agreement. You can find a list
> of consultants at qmail.org.
>
> \Maex
>
>
I'm sorry if my question disclose some delicate info. But I just want to
make everything clearly.

[Nguyen Minh Son]

I discover that my user only can not send mail to 1 addr in this domain.
(other email in this domain are okie). And we can use Yahoo or Gmail to
send mail to this addr that I can not send by our company email.
Is there an error in my mail server or in my partner's mail server. In
my mail server there is no filter rule.

[Nguyen Minh Son]

Hi everybody.
My qmail server sometime drop email and send this error to client. After
a while (maybe a few hours or even a day) email to these domain was sent
okie.
I dont't know if this is my server or the remote server problem.
Can anyone help me?