Mailing List Archive

Rejaine Monteiro <rejaine@bhz.jamef.com.br> wrote:
>
> I'm using qmail with jms1-7.10 combined patch and having problems
> with multiple MX records.
>
> When trying tosend mailfora especific domain,messages
> arerejectedwiththe this code:
>
> deferral: Connected_to_III.III.III.III_but_connection_died._(#4.4.2)/
>
> According tothe patch,this problemshould notbe occurring,because
> whenfirstMXis responding, butrefusetheconnection, then
> qmailshouldshould trythesecondaryMX,whatis not occurring.

The above deferral message indicates that the server did *not* refuse the
connection. qmail successfully connected to it, and the connection later
died.

I do not know if the patch you're using handles that particular case, but it's
not the case you think it is.

Charles
--
--------------------------------------------------------------------------
Charles Cazabon
GPL'ed software available at: http://pyropus.ca/software/
Read http://pyropus.ca/personal/writings/12-steps-to-qmail-list-bliss.html
--------------------------------------------------------------------------

On 11/6/2013 12:00 PM, Rejaine Monteiro wrote:
>
> Hi,
>
> I'm using qmail with jms1-7.10 combined patch and having problems with
> multiple MX records.
>
> When trying tosend mailfora especific domain,messages arerejectedwiththe
> this code:
>
> deferral: Connected_to_III.III.III.III_but_connection_died._(#4.4.2)/
>
> According tothe patch,this problemshould notbe occurring,because
> whenfirstMXis responding, butrefusetheconnection, then qmailshouldshould
> trythesecondaryMX,whatis not occurring.
>
> Any ideia how can I fix this?

If you are sure that there is another MX record for this domain that is
not being tried, as a workaround, you can create an smtproutes entry for
this domain with the other MX record domain name as its value.

-
John J.

Em 07-11-2013 13:24, John Johnstone escreveu:
>
> If you are sure that there is another MX record for this domain that
> is not being tried, as a workaround, you can create an smtproutes
> entry for this domain with the other MX record domain name as its value.
great tip, I forgot the smptroutes.
the problem is that the primary MX server is responding to smtp
connection, however is in trouble, and closes by timeout. I've tried to
contact the service provider, but I got no reply.

> Em 07-11-2013 13:24, John Johnstone escreveu:
> the problem is that the primary MX server is responding to smtp
> connection, however is in trouble, and closes by timeout. I've tried to
> contact the service provider, but I got no reply.

One alternative is to set up a firewall rule the blocks access to the SMTP
server on that IP. Then qmail can't connect and you'll see the behavior
you were expecting to see...

Josh

Joshua Megerman
SJGames MIB #5273 - OGRE AI Testing Division
You can't win; You can't break even; You can't even quit the game.
- Layman's translation of the Laws of Thermodynamics
josh@honorablemenschen.com

Yes, it would be another alternative (including tried this first). But I
was looking for some patch on qmail to resolve this issue (which is not
a problem of qmail, actually) so that you don't have to manually create
alternatives.
(sorry for bad english)

Em 08-11-2013 12:33, Joshua Megerman escreveu:
>> Em 07-11-2013 13:24, John Johnstone escreveu:
>> the problem is that the primary MX server is responding to smtp
>> connection, however is in trouble, and closes by timeout. I've tried to
>> contact the service provider, but I got no reply.
> One alternative is to set up a firewall rule the blocks access to the SMTP
> server on that IP. Then qmail can't connect and you'll see the behavior
> you were expecting to see...
>
> Josh
>
> Joshua Megerman
> SJGames MIB #5273 - OGRE AI Testing Division
> You can't win; You can't break even; You can't even quit the game.
> - Layman's translation of the Laws of Thermodynamics
> josh@honorablemenschen.com
>


--
Rejaine da Silveira Monteiro
Suporte-TI
Jamef Encomendas Urgentes
Matriz - Contagem/MG
Tel: (31) 2102-8854
www.jamef.com.br

Hi,

there is actually little hope, if the MTA does not provide an error code at
all, but rather times out.

In case some useful response is provided, you can give the attached patch
for qmail-remote a try.


--On 8. November 2013 11:50:42 -0200 Rejaine Monteiro
<rejaine@bhz.jamef.com.br> wrote:

> Em 07-11-2013 13:24, John Johnstone escreveu:
>>
>> If you are sure that there is another MX record for this domain that
>> is not being tried, as a workaround, you can create an smtproutes
>> entry for this domain with the other MX record domain name as its value.
> great tip, I forgot the smptroutes.
> the problem is that the primary MX server is responding to smtp
> connection, however is in trouble, and closes by timeout. I've tried to
> contact the service provider, but I got no reply.

You can patch qmail-remote.c to cope with this situation:

--- ../qmail-1.03/qmail-remote.c 1998-06-15 12:53:16.000000000 +0200
+++ qmail-remote.c 2013-11-08 15:25:23.673079112 +0100
@@ -236,7 +236,9 @@
substdio_flush(&smtpto);
code = smtpcode();
if (code >= 500) quit("DConnected to "," but sender was rejected");
- if (code >= 400) quit("ZConnected to "," but sender was rejected");
+ if (code == 421) quit("ZConnected to "," but greylisted");
+ if (code != 220) quit("ZConnected to "," but greeting failed");
+ if (code >= 400) return; /* try next MX */

flagbother = 0;
for (i = 0;i < reciplist.len;++i) {


Simply try it.

regards.
--eh.

--
Dr. Erwin Hoffmann | FEHCom | http://www.fehcom.de/ | PGP-Key-Id: 7E4034BE