[exim-dev] [Bug 1685] interface_strict

[admin]

https://bugs.exim.org/show_bug.cgi?id=1685

Phil Pennock  changed:

   What|Removed |Added

 CC||p...@exim.org

--- Comment #1 from Phil Pennock  ---
For those wondering why there's a copy/paste of a chunk of the documentation,
the key is in the last two sentences, which redefine "ignored" (instead of
removing use of the term).

I think that this could be achieved with something like (UNTESTED):

interface = <; 192.168.123.123 ; 3ffe::836f::fe86:a061
condition = ${if or{\
   {match_ip{192.168.123.123}{@[]}}\
   {match_ip{3ffe::836f::fe86:a061}{@[]}}\
   }}

Easier to keep in sync using a macro (AGAIN UNTESTED):

# macro section
OUTBOUND_IPADDRESS=<; 192.168.123.123 ; 3ffe::836f::fe86:a061
# ... transport section, on the smtp transport:
interface = OUTBOUND_IPADDRESS
condition = ${if forany{OUTBOUND_IPADDRESS}{match_ip{$item}{@[]}}}

While a strict variant would be cleaner to configure, the use-case needs
clarification to explain why the situation is common enough that being able to
configure around it is not sufficient.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##

[exim-dev] [Bug 1684] Malformed headers which exceed length spec willingly passed to remote servers

[admin]

https://bugs.exim.org/show_bug.cgi?id=1684

--- Comment #4 from Heiko Schlittermann  ---
According to the spec, header_line_maxsize imposes a limit on the total length
of all joined lines of a specific header - so it's limit on the logical line
length.

And I'm sure you'll find legitimate logical header lines with >998 characters
in total, folded into individual physical lines.

Auto-folding may be an option (as Viktor writes) and maybe additionally a
configurable limit on the length if an individual physical line.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##

[exim-dev] [Bug 1684] Malformed headers which exceed length spec willingly passed to remote servers

[admin]

https://bugs.exim.org/show_bug.cgi?id=1684

--- Comment #3 from Rubin  ---
Note that adding: 

header_line_maxsize = 998

to the main config section, will stop exim from accepting messages that cause
this.

I propose the default value of that variable should be changed to that.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##

[exim-dev] [Bug 1685] New: interface_strict

[admin]

https://bugs.exim.org/show_bug.cgi?id=1685

Bug ID: 1685
   Summary: interface_strict
   Product: Exim
   Version: N/A
  Hardware: All
OS: All
Status: NEW
  Severity: wishlist
  Priority: medium
 Component: Transports
  Assignee: ni...@exim.org
  Reporter: outsi...@scarynet.org
CC: exim-dev@exim.org

interface_strict Use: smtp Type: string list Default: unset

This option specifies which interface to bind to when making an outgoing SMTP
call. The value is an IP address, not an interface name such as eth0. Do not
confuse this with the interface address that was used when a message was
received, which is in $received_ip_address, formerly known as
$interface_address. The name was changed to minimize confusion with the
outgoing interface address. There is no variable that contains an outgoing
interface address because, unless it is set by this option, its value is
unknown.

During the expansion of the interface option the variables $host and
$host_address refer to the host to which a connection is about to be made
during the expansion of the string. Forced expansion failure, or an empty
string result causes the option to be ignored. Otherwise, after expansion, the
string must be a list of IP addresses, colon-separated by default, but the
separator can be changed in the usual way. For example:

interface = <; 192.168.123.123 ; 3ffe::836f::fe86:a061

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 transport should fail and exim should
treat the connection as failed. This should force exim to only use the specific
ips and not pick any other random available in that type.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##

[exim-dev] [Bug 1685] interface_strict

[admin]

https://bugs.exim.org/show_bug.cgi?id=1685

Alexander Maassen  changed:

   What|Removed |Added

   Keywords||work:medium

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##