Autor: Phil Pennock Datum: To: Davide D'Amico CC: exim-users Betreff: Re: [exim] Strange behaviour using non default port in remote smtp
On 2012-10-02 at 13:59 +0200, Davide D'Amico wrote: > Il 02/10/12 13:44, Phil Pennock ha scritto:
> > On 2012-10-02 at 08:10 +0200, Davide D'Amico wrote:
> >> So changing route_data to route_list isn't a good idea to solve this
> >> problem?
> >
> > No; route_list is simply a more powerful wrapper around route_list,
> > taking matching patterns and options. It doesn't affect this case.
>
> do you mean "route_data is simply a wrapper around "route_list", right?
The route_data option expands to one place to send a message to. It's
the data part of a routing rule.
The route_list option provides a list of routing rules.
route_data is simpler; route_list is more powerful in some situations.
Think of route_list as a set of domain constraints, a route_data rule
for each constraint, and perhaps some options on each item too.
> So I don't see any failed attempt (just now I enabled retry_defer) but
> for every 'missed' mail, I see very long delivery times:
>
> 2012-10-01 12:35:45 1TIdLP-000KQL-JO [...]
> 2012-10-01 12:38:30 1TIdLP-000KQL-JO => xxx.yyy.zzz@???
> F=<> R=internal T=remote_smtp S=1226 H=internal_host_ip
> [internal_host_ip]* C="250 ok 1349087906 qp 49471"
If you "exigrep 1TIdLP-000KQL-JO /path/to/mainlog" you should get all
the entries for that msgid.
There should be some items using "==" instead of "=>"; the "==" lines
are for deferrals.
> Anyway, what's the '*' after the backend ip address in mainlog:
> 2012-10-01 12:38:30 1TIdLP-000KQL-JO => xxx.yyy.zzz@???
> F=<> R=internal T=remote_smtp S=1226 H=internal_host_ip
> [internal_host_ip]* C="250 ok 1349087906 qp 49471"
>
> "[internal_host_ip]*"
The Exim Specification, "51.7 Logging deliveries":
----------------------------8< cut here >8------------------------------
When more than one address is included in a single delivery (for example, two
SMTP RCPT commands in one transaction) the second and subsequent addresses are
flagged with "->" instead of "=>". When two or more messages are delivered down
a single SMTP connection, an asterisk follows the IP address in the log lines
for the second and subsequent messages.
----------------------------8< cut here >8------------------------------
which is evidence in favour of the theory that the retry db is the
source of the problem you're encountering.
I'm encountering problems with bugzilla right now, or I'd include a
shiny new bug number to give you for tracking.
The multiple-hostname workaround should work for now.
