Hi Eric,

>This is why I have the following:
>
>smtpd_recipient_restrictions =
>        reject_unauth_pipelining,
>        reject_non_fqdn_recipient,
>        reject_non_fqdn_sender,
>
>That way the non-fqdn stuff is killed early, and the append_at_myorigin is
>a non-issue.

K, that mirrors the beginning of my smtpd_recipient_restrictions - but it is
my understanding that these deal with the SMTP envelope MAIL FROM: and RCPT
TO: addresses, not the From: and To: headers within the data portion of the
SMTP message.  The issue I'm seeing is with ig1/ig2.intouchmi.com showing up
in the data header - which isn't valid for any of the messages I've seen.

>
>> I don't see a useful reason for Postfix touching the message header -
>this
>> isn't the info thats used to route the messages anyway(?)
>
>It has to touch the header.  All mail servers do to enter the added lines.

:-) Bad wording on my part.  I do understand that each MTA has to 'touch'
the headers, to add "Received:" lines and such, but did not expect that the
MTA should by default ALTER existing data headers such as "From:" and
"To:" - from RFC 2821, 3.7 last paragraph:
   As discussed in section 2.4.1, a relay SMTP has no need to inspect or
   act upon the headers or body of the message data and MUST NOT do so
   except to add its own "Received:" header (section 4.4) and,
   optionally, to attempt to detect looping in the mail system (see
   section 6.2).

So maybe that's the defining difference - whether the MTA is being used for
a local mail system or simply a relay+anti-spam server (as is the case in my
application)

>There are plenty of other reasons, such as virtual mapping, canonical
>changes, so on and so forth.

none of that really going on in this application...

>One of the most typical reasons to do the append_at_myorigin is for local
>users sending mail.  That way they show up as @whatever rather than a
>non-fqdn.
>
>In a relay only anti-spam server, like the IMGate, many of the reasons for
>a MTA to fiddle with addresses are gone.  And that is why you wonder as to
>the purpose.  But never forget this is intended as an MTA for a POSIX OS
>that may have local users, and other issues.

These are truly just relay/anti-spam configs - no local users receiving
anything incoming, only cronjob reports/postmaster/MAILER-DAEMON stuff
coming out of it.

OK, so I think we're on the same page - append_at_myorigin=NO should cause
no problems in my config - as I'm not utilizing this as a local delivery
server - just relaying SMTP between my mailbox server (Imail) and the
Internet.

>I hope that helps.

Every little bit helps!  :-)
- Tony

>--Eric
>
>
>


Reply via email to