logs archiveIRC Archive / Freenode / #exim / 2015 / September / 2 / 1
Rubin
T:uoneuro.uoregon.edu:128.223.140.127 -18 77 Remote host uoneuro.uoregon.edu [128.223.140.127] closed connection in response to sending data block
same thing i see in the log
i can cause the same bug with a gmail target too though
so its not just that server
hs12
So, exinext uoneuro.uoregon.edu tells you that that host has a problem?
Rubin
yes
it kinda bounces in and out, depending if this problem email is there. sometimes a few other messages will trickle in if tehy get lucky
hs12
You can modifiy the retry rules, at least. Asking for shorter intervals on you specific error or/and domain. And then start a queue runner more frequently.
Of course, independend on this, I try to understand why Exim considers this as a general host problem, not an message problem.
Rubin
yes. thats the real key i think
iv tried to google a bit about that, but i cant find anything :/
henk
Rubin: I agree, exim should reformat those headers &
Rubin
i did find a bug report about roundcube generating too-long references headers
henk
could you report a bug?
Rubin
yeah
         

hs12
Yahoo generates too long DKIM-Signature headers too.
Too long not for Exim but for an old mailscanner that is fed by Exim. (We solved it by deleting those headers...)
Rubin: retry_use_local_part could be your friend, but I'm not sure about all the implications.
Rubin
so i can maybe do: * lost_connection use_local_part ?
er retry_use_local_part
oh its in the router
hs12
Something like that, yes. Probably. I'm unsure about that retry magic.
OUTsider
how to disable ipv6 on outgoing mail
I did modify the remote_smtp transport and only have it use the v4, performed update-exim4.conf, restarted exim, and still it uses v6 outgoing
hs12
Rubin: It's not a bug, it's a feature, according to http://www.exim.org/exim-html-current/doc/html/spec_html/ch-smtp_processing.html#SECToutSMTPerr
Rubin
OUTsider, 'disable_ipv6' i think
OUTsider
I only want it disabled for outgoing, incoming is fine
Rubin
hs12, yes i was just reading that too.
OUTsider, it'll try both i think if v6 fails. so you can just leave it
hs12
OUTsider: I'm not sure about the debian config scheme, first of all check the resulting autogenerated.conf if you change was propagated there.
OUTsider
I have splitted setup with conf.d
hs12
OUTsider: try to use dns_ipv4_lookup
OUTsider
Rubin: yes, but it tries v6 first, connects successfully, and because my hoster has no facility to setup the PTR records, the mail bounces back
Rubin
ahh
OUTsider
thats why I only want it temp disabled for outgoing only :P
hs12
OUTsider: ... to avoid AAAA lookups
Rubin
do you NEED to receive via ipv6?
just disable it completely until you resolve that problem
hs12
OUTsider: or ignore_target_hosts = <; 0::0/0 in your router
OUTsider: So you put ignore_target_hosts ... into your remote_smtp_transport? And you see this option in the autogenerated.conf? And exim -bP transport remote_smtp shows you that option too?
OUTsider
whats the < for actually ?
hs12
OUTsider: Sorry, it's a router option, not a transport option. s/transport/router/ in my previous lines
OUTsider
there is no autogenerated.conf
         

hs12
check the output of exim -bV, the last line. Or exim -bP configure_file
OUTsider
/var/lib/exim4/config.autogenerated
hs12
Ok, that's what I meant... Sorry.
Check this file, or check the output from exim -bP routers ... depending on what you've changed. (You didn't tell us yet)
OUTsider
it did accept the ipv4 only in the remote_smtp
but it still tries to use the v6 then
well, I removed the ipv6 from the interface in the remote_smtp section
https://github.com/Exim/exim/wiki/How-to-force-IPv4-connections-for-specific-domains-if-IPv6-is-enabled
only applied the interface part, as that should be the end result, since the wiki gives hints on defining it per site
since I don't know which sites enforce the policy, I temporary want to disable v6 outgoing completly
and I think I can use the ignore_target_hosts in the dnslookup part :)
hs12
Ack. And exim -bP transports | grep interface shows you what?
OUTsider
exim -bP transports | grep interface
whoops
the v4, and one with empty content
hs12
Or you should avoid looking up AAAA at all, this saves time and ressources
What transports are you using? Check your log file, there should be a notice about the transport that was used to deliver the message, T=...
And then inspect that transport exim -bP transports remote_smtp ... or whatever
Rubin: I'd say, after reading the above mentioned document, it's really a host error. (Of course, in your situation it's bound to the message), but aren't they violating some standards, dropping the SMTP connection during the DATA phase?
OUTsider
ends with remote_smtp is not a known option
I guess you need coffee and actually want me to grep on remote_smtp ? :)
hs12
use singular ... exim -bP transport remote_smtp
OUTsider
well, transport shows me that remote_smtp
and it has only the v4 interface specified
hs12
Hm. Fine... then it should work as expected, accept you're not using that transport but another one. Check your logs for T=
OUTsider
I did, they fall under remote_smtp
hs12
Ok, than check the Info of your name ... the RTFM Enforcer ;)
I just checked the spec file, around the interface smtp transport option, it's written there: The first interface of the correct type (IPv4 or IPv6) is used for the outgoing
connection. If none of them are the correct type, the option is ignored. If
interface is not set, or is ignored, the system's IP functions choose which
interface to use if the host has more than one.
OUTsider
dude, I Spend the last 3 days fixing a messed up sendmail config where sasl2 didn't work
and yes, I did read that :)
and the interface IS set, and valid
hs12
If your DNS lookup returns AAAA the interface option doesn't have the proper type and is ignored.
Yes, for IPv4 it's set, but not for IPv6
OUTsider
ah yeah, hence the dns_ipv4_lookup
hs12
Bingo ;)
OUTsider
is that as driver ?
hs12
It's a main config option. Taking a domain list
And I'd say, the Wiki is clearly wrong. Never trust anything else than the spec.txt or the source. ;)
OUTsider
dns_ipv4_lookup ain't applicable
hs12
?
OUTsider
it is to disable eventual slow responses on ipv6 dns servers
This is a fudge to help with name servers that give big delays or otherwise do not work for the AAAA record type. In due course, when the worldÂ’s name servers have all been upgraded, there should be no need for this option.
hs12
Hm...
OUTsider
so I go for ignore target hosts :)
hs12
But dns_ipv4_lookups seems(!) to be right too.
Rubin
https://bugs.exim.org/show_bug.cgi?id=1684
hs12, im not sure if its a violation to violate the protocol after the other end violated first
i did some random testing with various mail sites i have accounts on, and every one of them hangs up in this way
i really think exim should not send long lines.
if its a problem to fix them after the fact, then it should reject them on receipt instead
hs12
Nope, Exim should hang up on long header lines, or better yet, Exim should not accept such messages and refuse them after the DATA phase.
This would delegate the problem to it's roots.
Rubin
yes agreed.
OUTsider
lol, it still uses ipv6 with ignore being set on the range :P
« prev 1 2 next »