1 (edited by silky 2011-12-14 03:57:56)

Topic: Sending from another IP

==== Provide basic information to help troubleshoot and get quick answer ====
- iRedMail version:
- Linux/BSD distribution name and version:
- Any related log? Log is helpful for troubleshooting.
====

Latest version of iredmail on debain 6.0

ok trying to send mail from mail.coverage-plus.info with ip 208.93.108.171

for some reason it still uses the original ip .170 and will fail spf and dkim

how to i get it to tell it to use the .171 as the originating server and not .170

Delivered-To: silkys@gmail.com
Received: by 10.220.191.68 with SMTP id dl4cs71907vcb;
        Tue, 13 Dec 2011 11:54:55 -0800 (PST)
Received: by 10.229.78.165 with SMTP id l37mr1520563qck.126.1323806094330;
        Tue, 13 Dec 2011 11:54:54 -0800 (PST)
Return-Path: <noreply@mail.coverage-plus.info>
Received: from n1.globalnewsletter.com (mail1.globalnewsletter.com. [208.93.108.170])
        by mx.google.com with SMTP id fe2si65757qab.76.2011.12.13.11.54.54;
        Tue, 13 Dec 2011 11:54:54 -0800 (PST)
Received-SPF: fail (google.com: domain of noreply@mail.coverage-plus.info does not designate 208.93.108.170 as permitted sender) client-ip=208.93.108.170;
Authentication-Results: mx.google.com; spf=hardfail (google.com: domain of noreply@mail.coverage-plus.info does not designate 208.93.108.170 as permitted sender) smtp.mail=noreply@mail.coverage-plus.info; dkim=hardfail header.i=@mail.coverage-plus.info
Received: from localhost (localhost [127.0.0.1])
    by n1.globalnewsletter.com (Postfix) with ESMTP id 6DF3544067
    for <silkys@gmail.com>; Tue, 13 Dec 2011 14:55:02 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=
    mail.coverage-plus.info; h=content-transfer-encoding
    :content-type:content-type:mime-version:reply-to:from:from:date
    :date:message-id:subject:subject:to; s=dkim; t=1323806102; x=
    1326398102; bh=bo+H1VYPIHMja2u7i1lnzr4k/j4Pe8iSf79bVw94XpI=; b=s
    VgijxxxJk55G0TgjJfdDufPrrd2/08SVYDDLbRXL9Z+yK7UdBxKo6K0Skup+peGe
    T2Ne+XlIXO9PWtjjDDPz0DW7KjDRtGAGZlLu9iC5ojM1H1rTpxu4cS6hP6dXixXG
    8EFUrJ5HrvK/Y+kIy6KrXoVTRl3IcXlx/m+VPRCjco=
Received: from n1.globalnewsletter.com ([127.0.0.1])
    by localhost (n1.globalnewsletter.com [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id W358ufkuzFjk for <silkys@gmail.com>;
    Tue, 13 Dec 2011 14:55:02 -0500 (EST)
Received: from mail.coverage-plus.info (mail.coverage-plus.info [208.93.108.171])
    by mail.coverage-plus.info (Postfix) with ESMTPA id 4BAD544065
    for <silkys@gmail.com>; Tue, 13 Dec 2011 14:55:02 -0500 (EST)
To: silkys@gmail.com

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Sending from another IP

Did you try Postfix setting "smtp_bind_address"?
Reference: http://www.postfix.org/postconf.5.html# … nd_address

3

Re: Sending from another IP

ZhangHuangbin wrote:

Did you try Postfix setting "smtp_bind_address"?
Reference: http://www.postfix.org/postconf.5.html# … nd_address

==== Provide basic information to help troubleshoot and get quick answer ====
- iRedMail version:
- Linux/BSD distribution name and version:
- Any related log? Log is helpful for troubleshooting.
====

i currently have my master.cf set as follows

#smtp      inet  n       -       -       -       -       smtpd
localhost:smtp      inet  n       -       -       -       -       smtpd
208.93.108.170:smtp      inet  n       -       -       -       -       smtpd
208.93.108.171:smtp      inet  n       -       -       -       -       smtpd -o myhostname=mail.coverage-plus.info
#submission inet n       -       -       -       -       smtpd

i can connect to the server per ip and have it connect with the correct hello but always looks like it loops back through the original ip . should i add the bind to master.cf or main.cf and do i have to add inet_interfaces? i dont know much about postfix as i mostly use exim on debian

thanks

S.

4

Re: Sending from another IP

Setting either myhostname and/or smtp_bind_address won't alleviate the problem of having two outgoing domains who should have separate domainkeys, spf etc. Imagine the server having mailer.foobar.com, mailer.squiggly.com and mailer.jazz.com all on different IP addresses, with different dkim and spf data in their respective DNS zone files. They in turn bind .10, .11 and .12 (for example). When connecting and sending mail through .10 (mailer.foobar.com), the mailer should exclusively use this interface with its transport and signing and everything, likewise when using .11 (mailer.squiggly.com), etc.

What happens now, if you use .11 (fictional), it relays through .10 while generating a new mailid (see above pasted output, going from coverage-plus to globalnewsletter), entirely breaking verification (as well as being horribly strange behavior).

E.

5

Re: Sending from another IP

Edge wrote:

Setting either myhostname and/or smtp_bind_address won't alleviate the problem of having two outgoing domains who should have separate domainkeys, spf etc. Imagine the server having mailer.foobar.com, mailer.squiggly.com and mailer.jazz.com all on different IP addresses, with different dkim and spf data in their respective DNS zone files. They in turn bind .10, .11 and .12 (for example). When connecting and sending mail through .10 (mailer.foobar.com), the mailer should exclusively use this interface with its transport and signing and everything, likewise when using .11 (mailer.squiggly.com), etc.

What happens now, if you use .11 (fictional), it relays through .10 while generating a new mailid (see above pasted output, going from coverage-plus to globalnewsletter), entirely breaking verification (as well as being horribly strange behavior).

E.

==== Provide basic information to help troubleshoot and get quick answer ====
- iRedMail version:
- Linux/BSD distribution name and version:
- Any related log? Log is helpful for troubleshooting.
====

It seems it gets confused once it leaves amavisd via the localhost. How do i get it to scan via the domain instead of localhost ?

S.