> Hello.
>
> I would also recommend having unique hostnames as well, so that postfix
> can keep track. It's perfectly fine to have the same IP.
>
> IE: mail.mydomain.com, mail2.mydomain.com etc
This working great, two different hostnames solves the problem
solution of one instance seems to be m
OK thanks for sharing your experience
I'll be changing configurations
> Hello.
>
> I would also recommend having unique hostnames as well, so that postfix
> can keep track. It's perfectly fine to have the same IP.
>
> IE: mail.mydomain.com, mail2.mydomain.com etc
>
> Also, it might not be n
On Sun, Aug 02, 2015 at 01:53:14PM +0200, michalr0 wrote:
> NOQUEUE: reject_warning: RCPT from 1-2-3-4.dynamic.xx[1.2.3.4]: 450 4.1.7
> : Sender address rejected: unverified address: mail for
> mydomain.dd loops back to myself; from=
> to= proto=ESMTP helo=<[192.168.1.140]>
Don't forward mail
Hello.
I would also recommend having unique hostnames as well, so that postfix
can keep track. It's perfectly fine to have the same IP.
IE: mail.mydomain.com, mail2.mydomain.com etc
Also, it might not be necessary to have two instances, you can probably
do it with one, as SMTPD is for incomi
Hello,
mail.mydomain.dd[6.7.8.9] is the machine running your two instances?
Looks like your outgoing postfix himself thinks, he is the one for
domain mydomain.dd. Maybe you could give him a transport-table entry like :
mydomain.dd smtp:[1.2.3.4]:25
(Remember to run postmap)
If that doesn
Hello i have two instance of postfix
one for incoming (p:25) and one for outgoing (p:587)
I use this configuration because in this way i may check DNS and MX records. I
have some virtual domains. When I send email to client which changing mail
server (from me to other ISP) I sending emails to me
