Hi,
James Worix <[email protected]> (Fr 17 Apr 2015 20:15:37 CEST): … > issue with mobile devices that use third party email clients to send and > receive emails. The problem being that when they are in the field using > Verizon LTE or similar that their dynamic ips are automatically blacklisted > in most major DNS lists. I only really have 2 options. As Lena wrote, nobody should(!) care about thouse Received:-Header lines, as this is a quite common scenario. But … we had a similiar situation with our customers. The Received-Header we add does not contain the IP address the message was submitted from, if we got it via an authenticated connection. received_header_text = Received: \ ${if and{{!def:authenticated_id}{!def:tls_cipher}}\ {${if def:sender_rcvhost {from $sender_rcvhost\n\t}\ {${if def:sender_ident {from ${quote_local_part:$sender_ident} }}\ ${if def:sender_helo_name {(helo=$sender_helo_name)\n\t}}}}}}\ by $primary_hostname \ ${if def:received_protocol {with $received_protocol}} \ ${if def:tls_cipher {($tls_cipher)\n\t}}\ (Exim $version_number)\n\t\ ${if def:sender_address \ {(envelope-from <$sender_address>)\n\t}}\ id $message_exim_id\ ${if def:received_for {\n\tfor $received_for}} I believe, this solved the issue. If I remember well, it was SpamAssassin, that complained about dynamic address in the Received-Header (probably if there wasn't authentication mentioned in the same header, I do not know…) Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -
signature.asc
Description: Digital signature
-- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
