Hi,
I would like to introduce mail gopher, a new all-in-one, MIT-licensed
mail filter.
Mopher is designed to be lightweight, modular and extensible, has
several unique features and uses a very flexible and customizable
configuration syntax that is very similar to the common firewall
rule-lists so
Check if you can do a early logrotate, this will help you with this problem
when running scripts.
You can every hour rotate the log file and then run this script into the old
log.
Newton Pasqualini Filho
newtonpasqual...@gmail.com
Em 13/06/2013, às 19:28, Newton Pasqualini Filho
escreveu:
You should use network tools to provide that solution.
I use SNAT to route our internal traffic to other postfix nodes into my
internal network.
The only think that you must do is setup SNAT with port too!
Checkout in Google "iptables SNAT" or "iptables -j SNAT --help"
Best regards
Newton Pasq
Wow,
So this error messages are not yours, this comes from the external side.
There is no way to catch this arg in same line as from.
You can do a script that can handle the log and store in memory to run in
realtime, or you can create a cronjob.
I can help you with the cronjob script to handl
As requested. I suppose I could grab the queue ID and back track to the sender
but when the logs get long (which they do, half a million or more lines) these
scans can take a while and I'm trying to capture this info in real time (more
or less):
Jun 13 15:10:47 neskowin postfix/qmgr[13765]: 6D
On Jun 13, 2013, at 6:04 PM, Newton Pasqualini Filho
wrote:
> You can do this with iptables rules using SNAT.
I'm sorry, I should have mentioned this need to happen on multiple instances of
the postfix on the same system.
One instance will send the traffic to :2501, another to :2502, etc.
It
On Thu, Jun 13, 2013 at 06:01:26PM -0400, Matthew Barr wrote:
> I'm looking for a way to change the default destination port for
> SMTP, similar to the effect of lmtp_tcp_port.
The default port for SMTP is not "25" it is the "smtp/tcp" entry
in /etc/services. But don't change that, since making
You can do this with iptables rules using SNAT.
Regards
Newton Pasqualini Filho
newtonpasqual...@gmail.com
Em 13/06/2013, às 19:01, Matthew Barr escreveu:
> I'm looking for a way to change the default destination port for SMTP,
> similar to the effect of lmtp_tcp_port.
>
> This is due to an
I'm looking for a way to change the default destination port for SMTP, similar
to the effect of lmtp_tcp_port.
This is due to an interesting outbound NAT setup, which will rewrite the actual
connection port for the destination hosts to be 25.
The smtp(5) command doesn't have an option to set d
Can you cut part of you log file and send to the list?
I am able to detect in a single line when I find "NOQUEUE" in log.
Regards,
Newton Pasqualini Filho
newtonpasqual...@gmail.com
Em 13/06/2013, às 18:34, Rob Tanner escreveu:
> Hi,
>
> I'm trying to come up with mechanisms to catch compro
Hi,
I'm trying to come up with mechanisms to catch compromised accounts sending
SPAM. Since spammers don't necessarily have all good addresses a large number
of their SPAM messages bounce with 550 errors (mailbox unavailable or doesn't
even exist). I would like to monitor men logs and catch t
Ravindra Gupta // Viva:
> Jun 12 20:29:27 ems31 postfix/smtp[1816]: CC78D22400E:
> to=, relay=imap.eemail.example.com[10.0.0.125]:25,
> delay=0.86, delays=0.01/0/0.42/0.42, dsn=5.0.0, status=bounced (host
> imap.eemail.example.com[10.0.0.125] said: 550 Action not taken (in
> reply to end of DATA co
On 06/13/2013 09:02 PM, Ravindra Gupta // Viva wrote:
Dear Wietse,
So how we will resolve the issue. Please let me know for your valuable
suggestion.
As your log clearly shows, the OTHER SIDE of the SMTP conversation tells
you this.
If this other side is a receiving SMTP *server*, then the
Dear Wietse,
So how we will resolve the issue. Please let me know for your valuable
suggestion.
On Fri, Jun 14, 2013 at 12:26 AM, Wietse Venema wrote:
> Ravindra Gupta // Viva:
> > Jun 12 20:29:27 ems31 postfix/smtp[1816]: CC78D22400E: to=<
> test.example.com>,
> > relay=imap.eemail.example.
Ravindra Gupta // Viva:
> Jun 12 20:29:27 ems31 postfix/smtp[1816]: CC78D22400E: to=,
> relay=imap.eemail.example.com[10.0.0.125]:25, delay=0.86,
> delays=0.01/0/0.42/0.42, dsn=5.0.0, status=bounced (host
> imap.eemail.example.com[10.0.0.125] said: 550 Action not taken (in reply to
> end of DATA co
Hello,
we have configured postfix in one of our Centos server.
[root@test ~]# postconf -d | grep mail_version
mail_version = 2.10.0
milter_macro_v = $mail_name $mail_version
When we have sent one message in our mail id we got below error code in
maillog.
Jun 12 20:29:23 ems31 postfix/smtpd[1
Ralf Hildebrandt:
> Currently, smtp_fallback_relay is being used after the first failed
> delivery.
>
> http://www.postfix.org/postconf.5.html#smtp_fallback_relay
> explicitly mentions: "With bulk email deliveries, it can be beneficial
> to run the fallback relay MTA on the same host, so that it
On Thu, Jun 13, 2013 at 03:40:33PM +0200, Ralf Hildebrandt wrote:
> Currently, smtp_fallback_relay is being used after the first failed
> delivery.
>
> http://www.postfix.org/postconf.5.html#smtp_fallback_relay
> explicitly mentions: "With bulk email deliveries, it can be beneficial
> to run the
Currently, smtp_fallback_relay is being used after the first failed
delivery.
http://www.postfix.org/postconf.5.html#smtp_fallback_relay
explicitly mentions: "With bulk email deliveries, it can be beneficial
to run the fallback relay MTA on the same host, so that it can reuse
the sender IP addres
Marcio Luciano Donada:
> Hi list
> Yesterday I updated to postfix version postfix-2.10.0, and am
> having trouble allowing the relay without authentication that was
> working perfectly before the update. The rules are as follows:
As described in the RELEASE_NOTES file. We aim to document so that
p
Hi list
Yesterday I updated to postfix version postfix-2.10.0, and am having trouble
allowing the relay without authentication that was working perfectly before the
update. The rules are as follows:
In main.cf
smtpd_recipient_restrictions= check_client_access
hash:/usr/local/etc/postfix/map
21 matches
Mail list logo
