Mehmet Tolga Avcioglu:
> On Mon, Mar 14, 2011 at 5:56 PM, Victor Duchovni
> wrote:
> > On Mon, Mar 14, 2011 at 05:48:45PM -0400, Mehmet Tolga Avcioglu wrote:
> >
> >> Tried that and got the following:
> >>
> >> fatal: bad string length 0 < 1: inet_interfaces =
> >
> > Yes, you can set "inet_interf
Mehmet Tolga Avcioglu:
> warning: host 127.0.0.1[127.0.0.1]:25 greeted me with my own hostname
> warning: host 127.0.0.1[127.0.0.1]:25 replied to HELO/EHLO with my own
> hostname
You also need to configure a myhostname that is different than
the other MTA.
Wietse
On Mon, Mar 14, 2011 at 6:02 PM, Wietse Venema wrote:
> Mehmet Tolga Avcioglu:
>> On Mon, Mar 14, 2011 at 9:01 AM, Wietse Venema wrote:
>> > Mehmet Tolga Avcioglu:
>> >> I eventually fixed it by adding a transport rule "*
>> >> relay:127.0.0.1:10025" and having the other MTA listen on 10025, but
On Mon, Mar 14, 2011 at 5:56 PM, Victor Duchovni
wrote:
> On Mon, Mar 14, 2011 at 05:48:45PM -0400, Mehmet Tolga Avcioglu wrote:
>
>> Tried that and got the following:
>>
>> fatal: bad string length 0 < 1: inet_interfaces =
>
> Yes, you can set "inet_interfaces = loopback-only" or similar.
But I
Mehmet Tolga Avcioglu:
> On Mon, Mar 14, 2011 at 9:01 AM, Wietse Venema wrote:
> > Mehmet Tolga Avcioglu:
> >> I eventually fixed it by adding a transport rule "*
> >> relay:127.0.0.1:10025" and having the other MTA listen on 10025, but
> >> wondering if this is the best way. I would rather touch
On Mon, Mar 14, 2011 at 05:48:45PM -0400, Mehmet Tolga Avcioglu wrote:
> Tried that and got the following:
>
> fatal: bad string length 0 < 1: inet_interfaces =
Yes, you can set "inet_interfaces = loopback-only" or similar.
--
Viktor.
On Mon, Mar 14, 2011 at 9:01 AM, Wietse Venema wrote:
> Mehmet Tolga Avcioglu:
>> I eventually fixed it by adding a transport rule "*
>> relay:127.0.0.1:10025" and having the other MTA listen on 10025, but
>> wondering if this is the best way. I would rather touch the other MTA
>> as little as pos
Mehmet Tolga Avcioglu:
> I eventually fixed it by adding a transport rule "*
> relay:127.0.0.1:10025" and having the other MTA listen on 10025, but
> wondering if this is the best way. I would rather touch the other MTA
> as little as possible and current setup requires me to do some
> configuratio
I would like to run postfix on port 587, accept mail and than pass it
onto another MTA that is running on port 25.
Initially I thought I could achieve this by turning of smtp and
turning on submission on master.conf and than add a default_transport
to 127.0.0.1, but this resulted in "mail loops ba
