I had posted some of this before but since I wasn't a valid subscriber
I was "silently" ignored.. mybad.. :-)
---
I have an internal relay that I am replacing (sendmail with postfix)
I have followed :
http://www.postfix.org/STANDARD_CONFIGURATION_README.html#firewall
and have my transport working
I have several boxes that "check" my relay every 40 seconds to
check that the server is up.
After multiple attempts to get the number of checks reduced I would
like the know the preferred way to block specific IP addresses in Postfix.
I have no issue with checks.. but every 40 seconds is ridicul
Ansgar Wiechers wrote:
On 2010-04-15 groups wrote:
Syntax follow up question...
1.2.3.4 REJECT
or
1.2.3.4 REJECT
1.2.3.4 REJECT
Regards
Ansgar Wiechers
Ansgar..
Thank you..
a tab issue "bit me" sometime ago in BSD hence the
question..
Charles
ix/aliases
#root:m...@my-domain.tld
root:m...@localhost
Thx
CT
Noel Jones wrote:
On 4/18/2010 4:40 PM, groups wrote:
Noel Jones wrote, On 04/18/2010 04:20 PM:
On 4/18/2010 4:16 PM, groups wrote:
Postfix logs help you know what happened to a particular message.
Look
in your logs for bounces (sender=<>) arriving from your relayhost,
and
see what postfix
My relay sends as follows:
90% - relayhost
10% - other hosts in transport (these go "directly" out)
This works well.
my question:
When the primary relayhost is "unavailable" what would be
the best way to *send* the 90% out.. ?
(not about load balancing)
Thx
Charles
CT wrote:
Noel Jones wrote:
On 4/18/2010 4:40 PM, groups wrote:
Noel Jones wrote, On 04/18/2010 04:20 PM:
On 4/18/2010 4:16 PM, groups wrote:
Postfix logs help you know what happened to a particular message.
Look
in your logs for bounces (sender=<>) arriving from your
relayhost, an
I do believe this is a relatively simple issue to solve. but
haven't found it yet..
*my-relay* = internal relay
*master-relay* = internal and external relay
Setup
Sending host => *my-relay* => *master-relay*
relayhost = master-relay
Looping issue..
When the *master-relay* sends *my-relay* a bo
On 07/22/2010 08:20 PM, Sahil Tandon wrote:
On Thu, 2010-07-22 at 16:38:14 -0500, groups wrote:
I have an internal relay..
- relay is mx for my-sub-domain
- relay forwards of emails to many domains through trusted_networks
Hm? What is trusted_networks in the Postfix context?
- I want to dr
General postfix question regarding MX lookups..
Does Postfix do an MX lookup on "inbound mail" as part of
"spam" prevention or some other check.. ?
Thx
Charles
On 09/14/2010 08:02 AM, Simon Waters wrote:
On Tuesday 14 September 2010 13:51:12 CT wrote:
Does Postfix do an MX lookup on "inbound mail" as part of
"spam" prevention or some other check.. ?
Mind has "check_sender_mx_access" so and logs appropriate
Ralf..
> A MX lookup is performed to check if the sender domain exists; it can
> be activated using:
>
> reject_unknown_sender_domain
is what I was looking for..
Thank you ..
Charles
On 09/14/2010 08:18 AM, Ralf Hildebrandt wrote:
* CT:
It was a question that came up in a dis
the most efficient way to
"rewrite" the sender address with a valid smtp address
to a "specific" domain.
I only need to do this for 1 destination domain..
Thx
CT
valid sender domain (in reply to
RCPT TO command))
--
My question
What is the most efficient way to
"rewrite" the sender address with a valid smtp address
to a "specific" domain.
I only need to do this for 1 destination domain..
Thx
CT
I currently have an internal relay for "internal-1.example.com"
The "internal-1.example.com" relay :
-- is the MX for "internal-1.example.com"
-- primarily used for "system email"
-- relays "905%" of email to a "master relay".
-- drops any "return" email for the "internal-1.example.com"
Example:
On 05/05/2011 05:37 PM, Sahil Tandon wrote:
On Thu, 2011-05-05 at 13:16:31 -0500, CT wrote:
I would like a simple way to drop other "internal domains" email
that can't be delivered.
something like :
#@internal-2.example.com/dev/null
Google 'postfix + disca
On 05/06/2011 01:52 PM, Victor Duchovni wrote:
The routing of mail for a particular recipient address or all recipients
in a given domain is performed by resolving the recipient to a
(transport, nexthop, address) triple.
http://www.postfix.org/ADDRESS_REWRITING_README.html#resolve
http
Question on main.cf
mynetworks = hash:/etc/postfix/network_table
After much looking and I surmise the format should be
192.168.1.2 OK (a space between IP and "OK")
"should work"..
and that CIDR
192.168.1.0/24 OK (a space between IP and "OK")
does not work.
In my test the "single IP" did n
mynetworks = hash:/etc/postfix/network_table
After much looking and I surmise the format should be
192.168.1.2 OK (a space between IP and "OK")
"should work"..
For hash: or cidr: (see cidr_table(5)), yes.
and that CIDR
192.168.1.0/24 OK (a space between IP and "OK")
does not work.
For h
On 05/06/2011 05:59 PM, Sahil Tandon wrote:
Question on main.cf
mynetworks = hash:/etc/postfix/network_table
After much looking and I surmise the format should be
192.168.1.2 OK (a space between IP and "OK")
"should work"..
In this context, Postfix only cares if the lookup succeeds; the resu
I have done a lot of researching rate limit on outbound email.
There seems to be a 'plethora' of ways to do this..
- smtpd_client_connection_rate_limit
- smtpd_client_message_rate_limit
- smtpd_client_recipient_rate_limit
- transport_destination_concurrency_limit
- /etc/postfix/transport
dom
On 05/13/2011 12:52 PM, Wietse Venema wrote:
CT:
I have done a lot of researching rate limit on outbound email.
There seems to be a 'plethora' of ways to do this..
Note: you are search for *outbound* mail controls.
- smtpd_client_connection_rate_limit
- smtpd_client_message_
22 matches
Mail list logo
