The Stovebolt Geek:
> In the case of the OP, the MX should be configured to only accept mail from
> the firewall when the final recipient is internal.
>
> Is there an alternative way to get the MX to accept mail from the firewall?
The proper way is one of the following:
- If the MX host is fina
--On October 12, 2012 6:49:06 AM -0400 Wietse Venema
wrote:
The Stovebolt Geek:
--On October 11, 2012 4:38:12 PM -0500 Noel Jones
wrote:
> On 10/11/2012 4:05 PM, Paul Schmehl wrote:
>> mynetworks = 127.0.0.0/8,IP.Of.Fortimail.Firewall
>
> While that may mask the problem, it is almost certa
Am 12.10.2012 13:05, schrieb Reindl Harald:
>
>
> Am 12.10.2012 12:56, schrieb Noel Jones:
>> On 10/11/2012 11:34 PM, The Stovebolt Geek wrote:
>>> --On October 11, 2012 4:38:12 PM -0500 Noel Jones
>>> wrote:
>>>
On 10/11/2012 4:05 PM, Paul Schmehl wrote:
> mynetworks = 127.0.0.0/8,IP.O
Am 12.10.2012 13:55, schrieb /dev/rob0:
> I don't think open relay is likely to be the result, but again,
> there's no reason why a relayhost should EVER be in $mynetworks
surely it is
* barracuda as MX
* postfix as mail-server
* check_recipient_access proxy:mysql:/etc/postfix/mysql-spamfilter
On Thu, Oct 11, 2012 at 04:05:14PM -0500, Paul Schmehl wrote:
> mynetworks = 127.0.0.0/8,IP.Of.Fortimail.Firewall
(BTW the /32 is implied, you do not need to specify it.)
This in reply to:
> --On October 11, 2012 1:44:04 PM -0700 BeauSanders
> wrote:
>
> >I am attempting to configure a Postfix
Am 12.10.2012 12:56, schrieb Noel Jones:
> On 10/11/2012 11:34 PM, The Stovebolt Geek wrote:
>> --On October 11, 2012 4:38:12 PM -0500 Noel Jones
>> wrote:
>>
>>> On 10/11/2012 4:05 PM, Paul Schmehl wrote:
mynetworks = 127.0.0.0/8,IP.Of.Fortimail.Firewall
>>>
>>> While that may mask the pro
On 10/11/2012 11:34 PM, The Stovebolt Geek wrote:
> --On October 11, 2012 4:38:12 PM -0500 Noel Jones
> wrote:
>
>> On 10/11/2012 4:05 PM, Paul Schmehl wrote:
>>> mynetworks = 127.0.0.0/8,IP.Of.Fortimail.Firewall
>>
>> While that may mask the problem, it is almost certainly the wrong
>> solution.
The Stovebolt Geek:
> --On October 11, 2012 4:38:12 PM -0500 Noel Jones
> wrote:
>
> > On 10/11/2012 4:05 PM, Paul Schmehl wrote:
> >> mynetworks = 127.0.0.0/8,IP.Of.Fortimail.Firewall
> >
> > While that may mask the problem, it is almost certainly the wrong
> > solution.
> >
>
> Please explain
--On October 11, 2012 4:38:12 PM -0500 Noel Jones
wrote:
On 10/11/2012 4:05 PM, Paul Schmehl wrote:
mynetworks = 127.0.0.0/8,IP.Of.Fortimail.Firewall
While that may mask the problem, it is almost certainly the wrong
solution.
Please explain why.
I'll grant you I left off the CIDR mask.
gt;> Please advise me on what I am missing. I have not been able to
>> locate any
>> posts from users with similar problems. I will be happy to answer
>> questions if somewhere will help me correct this issue.
>>
>> Thank you in advance for your help.
>>
>> -Beau
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://postfix.1071664.n5.nabble.com/Postfix-and-Portimail-Issues-tp51465
>>
>> .html Sent from the Postfix Users mailing list archive at Nabble.com.
>
>
>
http://postfix.1071664.n5.nabble.com/Postfix-and-Portimail-Issues-tp51465
.html Sent from the Postfix Users mailing list archive at Nabble.com.
--
Paul Schmehl (g...@stovebolt.com)
The Stovebolt Geek
The Net's Oldest and Most Complete
Resource for Antique Chevy and GM Trucks
http://www.stovebolt.com
On 10/11/2012 3:44 PM, BeauSanders wrote:
> I am attempting to configure a Postfix MTA in CentOS 6.3 for our school. The
> Postfix server has to send and receive email through a Fortimail firewall.
> Outgoing email is working fine. Email sent locally using the mail command to
> a local user on the
with similar problems. I will be happy to answer questions
if somewhere will help me correct this issue.
Thank you in advance for your help.
-Beau
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfix-and-Portimail-Issues-tp51465.html
Sent from the Postfix Users mailing
13 matches
Mail list logo
