Ioannis, disable all the firewalls but for basic SPI NAT/PAT (if you're
using
NAT) on the dedicated Shorewall guest. Route TCP 25 inbound via a PAT rule
to
the Postfix guest. See if that eliminates the timeout and related TCP
errors.
--
Stan
Dear Stan, I was just about to get enthusiastic
From: Stan Hoeppner (stanhardwarefreak.com)
Date: Fri May 28 2010 - 18:09:48 CDT
IIRC from his initial post, Ioannis has 3 virtual machines atop ESXi: one a
dedicated Ubuntu Shorewall instance, one running Ubuntu Shorewall (again)
and
Postfix, one running Microsoft SBS plus Exchange.
A basic
Ioannis Tsouvalas put forth on 5/30/2010 9:47 AM:
Stan thanks for the reply, and please excuse me for the time interval in
between your post and my reply. Geek and neato! wasn't exactly what I
was aiming for, but still I appreciate that you identified the geeky
complexity of the idea that I
I have disabled shorewall on Postfix machine using #shorewall clear , but
I'm still working on clearing shorewall on the dedicated machine, but I
haven't managed to make it happen since all the NAT has been implemented on
the shorewall configuration. I'm still trying to figure out a safe way to
Stan, thanks again for your input, I am getting the idea and I'm working
towards that direction, still from 3 months testing this implementation has
moved to production, and I am working remotely, so being careful is one
way to describe my actions.
Ps. The net diagram looked much better when I
Ioannis Tsouvalas put forth on 5/30/2010 2:46 PM:
I have disabled shorewall on Postfix machine using #shorewall clear , but
I'm still working on clearing shorewall on the dedicated machine, but I
haven't managed to make it happen since all the NAT has been implemented on
the shorewall
In the original scenario, Exchange was in the same network with Postfix
(both in dmz). For a reason, when applied on the customer premises, dhcp
wouldn't go through for the local workstations, so exchange was moved to the
local zone. To be honest, the testing didn't include large attachments (if
Dear everyone,
It's my first posting on mailing list so please accept my apologies for any
gaps that may appear until I get the hang of the way things should be
said
Case Scenario
Esxi implementation hosting the following
ZoneOS ( url of implementation if any)
Ioannis Tsouvalas put forth on 5/28/2010 4:09 AM:
My guess so far is to go and lower the link speed between the Shorewall,
Postfix, and maybe even SBS2008, and that's because similar problems having
been encountered where the MTU is bigger than 1500. Now, the only reason I
haven't done it so
reply
Stan Hoeppner put forth on 5/28/201 5:42 AM:
The vmxnet 'NIC' is a virtual device, strictly a software driver. The
vmxnet driver communicates with the ESX kernel at the speed of system
memory, which on modern servers is over 10x faster than the 10 Gbe
signaling rate. There is no such
On Fri, 28 May 2010 14:41:46 +0300
Ioannis Tsouvalas tsouval...@atic.gr wrote:
reply
Stan Hoeppner put forth on 5/28/201 5:42 AM:
The vmxnet 'NIC' is a virtual device, strictly a software driver.
The vmxnet driver communicates with the ESX kernel at the speed of
system memory, which on
Are there any firewalls between the Postfix and Exchange Server ?
Mihira
Yes there is, shorewall as implemented on the link provided
http://flurdy.com/docs/postfix/
--
Ioannis
As well as the shorewall in the three interface firewall
http://www.shorewall.net/three-interface.htm
__
Ioannis Tsouvalas put forth on 5/28/2010 6:41 AM:
Stan thanks for the reply, as well as the insight regarding the difference
between soft and hard nic devices. The only reason I'm pointing out the link
pulse as well as the MTU, is that my search so far points me towards that
direction. Now if
Ioannis Tsouvalas:
451 Requested action aborted: local error in processing
This is not a Postfix error mesage. It is an error in a non-Postfix MTA.
Please do not shoot the messenger.
451 Temporary local problem - please try later
This is not a Postfix error message. It is an error in a
Stan Hoeppner put forth on 5/28/2010 06:41 AM
Per the list welcome messages, you should post the complete output of
postconf -n. This will aid members in solving your issue, if the cause
of
your problem is indeed related to your Postfix configuration.
--
Stan
Postconf -n output:
Ioannis Tsouvalas:
451 Requested action aborted: local error in processing
This is not a Postfix error mesage. It is an error in a non-Postfix MTA.
Please do not shoot the messenger.
451 Temporary local problem - please try later
This is not a Postfix error message. It is an error in a
Ioannis Tsouvalas:
Ioannis Tsouvalas:
451 Requested action aborted: local error in processing
451 Temporary local problem - please try later
These you can do nothing about, except perhaps retry when the remote
system is under less stress.
421 4.4.1 Connection timed out (in reply to
Ioannis Tsouvalas:
Ioannis Tsouvalas:
451 Requested action aborted: local error in processing
451 Temporary local problem - please try later
These you can do nothing about, except perhaps retry when the remote
system is under less stress.
421 4.4.1 Connection timed out (in reply to
Postconf -n output:
alias_database = hash:/etc/postfix/aliases
alias_maps = hash:/etc/postfix/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
delay_warning_time = 4h
disable_vrfy_command = yes
inet_interfaces = all
local_recipient_maps =
mailbox_size_limit = 0
Wietse Venema put forth on 5/28/2010 9:37 AM:
Ioannis Tsouvalas:
Ioannis Tsouvalas:
451 Requested action aborted: local error in processing
451 Temporary local problem - please try later
These you can do nothing about, except perhaps retry when the remote
system is under less stress.
20 matches
Mail list logo
