Re: Maillog error - warn: Unescaped left brace in regex is deprecated here (and will be fata))
--On December 15, 2018 at 9:36:56 PM -0500 Bill Cole wrote: On 15 Dec 2018, at 14:00, Paul Schmehl wrote: --On December 14, 2018 at 4:09:08 PM -0500 Bill Cole wrote: On 14 Dec 2018, at 15:32, Bill Cole wrote: On 14 Dec 2018, at 0:46, Paul Schmehl wrote: I'm seeing this error in the logs: warn: Unescaped left brace in regex is deprecated here (and will be fata)) NOTE: that message should specify the source of the error. If it does not, something in your logging plumbing is mangling error messages. I tried increasing the debug level and even added -v to the pipe line in master.cf, but the message was the same. This is the entire line. Dec 15 18:50:32 mail postfix/pipe[33227]: A3CE22F157E: to=, relay=filter, delay=13, delays=3.7/0/0/9.7, dsn=2.0.0, status=sent (delivered via filter service (Dec 15 18:50:25.479 [33256] warn: Unescaped left brace in regex is deprecated here (and will be fata)) That's broken... Something between Perl and your log is mangling and truncating the error message. Maybe the Postfix 'pipe' plumbing? That's a secondary issue though, as it is easy to run SA by itself to. find the problem. Try this: spamassassin -D all --lint That should give you a large amount of debug output including the original error message with a file & line reference. These are the lines in master.cf that points to the pipe for filter: [...] That solved the problem. It was a single ruleset, and I removed it. I thought I only had default rulesets, but I guess I added a few extra ones over the years. Thanks for your help. Errors bug me to no end, as you've probably figured out by now. Paul Schmehl Independent Researcher
Re: Maillog error - warn: Unescaped left brace in regex is deprecated here (and will be fata))
--On December 15, 2018 at 9:36:56 PM -0500 Bill Cole wrote: Remove any rules file with 'sare' in its name. It would also be wise to make sure that you are running 'sa-update' regularly (weekly at least, ideally daily) to be sure that you have the current default ruleset. Thanks, Bill. I'll do that right away. Paul Schmehl Independent Researcher
Re: Maillog error - warn: Unescaped left brace in regex is deprecated here (and will be fata))
On 15 Dec 2018, at 15:50, Paul Schmehl wrote:
--On December 14, 2018 at 4:09:08 PM -0500 Bill Cole
wrote:
On 14 Dec 2018, at 15:32, Bill Cole wrote:
On 14 Dec 2018, at 0:46, Paul Schmehl wrote:
I'm seeing this error in the logs:
warn: Unescaped left brace in regex is deprecated here (and will be
fata))
NOTE: that message should specify the source of the error. If it does
not, something in your logging plumbing is mangling error messages.
Also note: there is at least one 3rd-party ruleset (http://sa.zmi.at)
which appears to have had a typo ('.' where a ',' should have been)
which
also resulted in this error message in a recent version. See
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7669 for a report
of
this issue (which is not a bug in SA per se, as the rules with the
typo
are an independent distribution.)
I did the following searches trying to locate this issue:
# grep -ro "\[,.\]" /usr/local/lib/perl5/site_perl/*
The warning message only applies to '{' NOT '[' and NOT '('
[...]
# grep -ro "{,.}" /usr/local/lib/perl5/site_perl/*
Try "{,.*}" instead. Also, don't use the 'o' option to grep. It
eliminates useful context, specifically whether the pattern is inside a
regex.
[...]
The same searches run on SA rules found one possible issue:
# grep -ro "\[,.\]" /usr/local/etc/mail/spamassassin/*
/usr/local/etc/mail/spamassassin/70_sare_specific.cf:[,s
As I said in my prior message: remove that file and any others with
'sare' in their name. They are dangerously obsolete.
Also check /var/db/spamassassin, which is where anything maintained by
sa-update will be.
I say possible because in my researching this issue I've seen both
curly braces only and also both curly braces and square braces, so I'm
not completely certain which (or if both) are a problem.
It's always helpful to look at actual documentation, rather than trust
research of secondary sources...
Try 'perldoc perldeprecation' for the definitive truth of deprecation
warnings.
At any rate, I don't see any dependency on Text::Unicode, although I
wouldn't be surprised if it's used by SA.
It absolutely is not, because Text::Unicode does not exist. :)
SA also does not use Text::Unidecode, which is a last-resort tool for
special cases where Unicode characters absolutely must be translated to
a reasonable US-ASCII representation.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Available For Hire: https://linkedin.com/in/billcole
Re: Maillog error - warn: Unescaped left brace in regex is deprecated here (and will be fata))
On 15 Dec 2018, at 14:00, Paul Schmehl wrote:
--On December 14, 2018 at 4:09:08 PM -0500 Bill Cole
wrote:
On 14 Dec 2018, at 15:32, Bill Cole wrote:
On 14 Dec 2018, at 0:46, Paul Schmehl wrote:
I'm seeing this error in the logs:
warn: Unescaped left brace in regex is deprecated here (and will be
fata))
NOTE: that message should specify the source of the error. If it does
not, something in your logging plumbing is mangling error messages.
I tried increasing the debug level and even added -v to the pipe line
in master.cf, but the message was the same. This is the entire line.
Dec 15 18:50:32 mail postfix/pipe[33227]: A3CE22F157E:
to=, relay=filter, delay=13, delays=3.7/0/0/9.7,
dsn=2.0.0, status=sent (delivered via filter service (Dec 15
18:50:25.479 [33256] warn: Unescaped left brace in regex is deprecated
here (and will be fata))
That's broken... Something between Perl and your log is mangling and
truncating the error message. Maybe the Postfix 'pipe' plumbing? That's
a secondary issue though, as it is easy to run SA by itself to. find the
problem.
Try this:
spamassassin -D all --lint
That should give you a large amount of debug output including the
original error message with a file & line reference.
These are the lines in master.cf that points to the pipe for filter:
[...]
This isn't a Postfix problem except for the incomplete log message. The
cause of the warning is what matters.
Also note: there is at least one 3rd-party ruleset (http://sa.zmi.at)
which appears to have had a typo ('.' where a ',' should have been)
which
also resulted in this error message in a recent version. See
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7669 for a report
of
this issue (which is not a bug in SA per se, as the rules with the
typo
are an independent distribution.)
I checked for this problem in the SA rules, but didn't find any
problems. I'm using the default set, and my research says these have
all been fixed. So, the problem must be in an affiliated perl module,
but I have no idea how to find it.
And yet, in your later message you say:
The same searches run on SA rules found one possible issue:
# grep -ro "\[,.\]" /usr/local/etc/mail/spamassassin/*
/usr/local/etc/mail/spamassassin/70_sare_specific.cf:[,s
That is NOT part of the default ruleset. For a few years there was a
3rd-party collection of rules files known as SARE which was distributed
independently of the SpamAssassin project. It was last updated well over
a decade ago. No one should be using those rules with a modern SA to
catch modern spam. They are neither safe nor effective. Remove any rules
file with 'sare' in its name. It would also be wise to make sure that
you are running 'sa-update' regularly (weekly at least, ideally daily)
to be sure that you have the current default ruleset.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Available For Hire: https://linkedin.com/in/billcole
Re: Maillog error - warn: Unescaped left brace in regex is deprecated here (and will be fata))
--On December 14, 2018 at 4:09:08 PM -0500 Bill Cole
wrote:
On 14 Dec 2018, at 15:32, Bill Cole wrote:
On 14 Dec 2018, at 0:46, Paul Schmehl wrote:
I'm seeing this error in the logs:
warn: Unescaped left brace in regex is deprecated here (and will be
fata))
NOTE: that message should specify the source of the error. If it does
not, something in your logging plumbing is mangling error messages.
Also note: there is at least one 3rd-party ruleset (http://sa.zmi.at)
which appears to have had a typo ('.' where a ',' should have been) which
also resulted in this error message in a recent version. See
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7669 for a report of
this issue (which is not a bug in SA per se, as the rules with the typo
are an independent distribution.)
I did the following searches trying to locate this issue:
# grep -ro "\[,.\]" /usr/local/lib/perl5/site_perl/*
/usr/local/lib/perl5/site_perl/LWP/Authen/Digest.pm:[,;]
/usr/local/lib/perl5/site_perl/LWP/Authen/Digest.pm:[,;]
/usr/local/lib/perl5/site_perl/Mail/Header.pm:[,;]
/usr/local/lib/perl5/site_perl/Mail/SpamAssassin/ArchiveIterator.pm:[,.]
# grep -ro "{,.}" /usr/local/lib/perl5/site_perl/*
/usr/local/lib/perl5/site_perl/Text/Unidecode/x0f.pm:{, }
/usr/local/lib/perl5/site_perl/Text/Unidecode/x18.pm:{, }
{, }
/usr/local/lib/perl5/site_perl/Text/Unidecode/x20.pm:{,,}
/usr/local/lib/perl5/site_perl/Text/Unidecode/x30.pm:{, }
/usr/local/lib/perl5/site_perl/Text/Unidecode/x30.pm:{,,}
/usr/local/lib/perl5/site_perl/Text/Unidecode/x00.pm:{,,}
/usr/local/lib/perl5/site_perl/mach/5.26/opie.ph:{,;}
The same searches run on SA rules found one possible issue:
# grep -ro "\[,.\]" /usr/local/etc/mail/spamassassin/*
/usr/local/etc/mail/spamassassin/70_sare_specific.cf:[,s
I say possible because in my researching this issue I've seen both curly
braces only and also both curly braces and square braces, so I'm not
completely certain which (or if both) are a problem.
At any rate, I don't see any dependency on Text::Unicode, although I
wouldn't be surprised if it's used by SA.
If square braces are included as well, then Mail::Header and
ArchiveIterator.pm would likely be potential culprits for the error message.
If parenthetical braces are also implicated, then there is an additional
potential problem:
# grep -ro "(,.)" /usr/local/lib/perl5/site_perl/*
/usr/local/lib/perl5/site_perl/mach/5.26/sys/lock.ph:(, )
/usr/local/lib/perl5/site_perl/mach/5.26/sys/lock.ph:(, )
At this point, I need an experienced programmer to decipher all this and
let me know where the issue(s) might be.
Paul Schmehl
Independent Researcher
Re: Maillog error - warn: Unescaped left brace in regex is deprecated here (and will be fata))
--On December 14, 2018 at 4:09:08 PM -0500 Bill Cole
wrote:
On 14 Dec 2018, at 15:32, Bill Cole wrote:
On 14 Dec 2018, at 0:46, Paul Schmehl wrote:
I'm seeing this error in the logs:
warn: Unescaped left brace in regex is deprecated here (and will be
fata))
NOTE: that message should specify the source of the error. If it does
not, something in your logging plumbing is mangling error messages.
I tried increasing the debug level and even added -v to the pipe line in
master.cf, but the message was the same. This is the entire line.
Dec 15 18:50:32 mail postfix/pipe[33227]: A3CE22F157E:
to=, relay=filter, delay=13, delays=3.7/0/0/9.7,
dsn=2.0.0, status=sent (delivered via filter service (Dec 15 18:50:25.479
[33256] warn: Unescaped left brace in regex is deprecated here (and will be
fata))
These are the lines in master.cf that points to the pipe for filter:
# grep filter /usr/local/etc/postfix/master.cf
smtp inet n - n - - smtpd -o
content_filter=filter:dummyr
# -o content_filter=spamassassin
filterunix - n n - 10 pipe
flags=Rq user=filter argv=/usr/local/bin/filter.sh -f ${sender} --
${recipient}
smtpd pass - - n - - smtpd -o
content_filter=filter:dummy
Also note: there is at least one 3rd-party ruleset (http://sa.zmi.at)
which appears to have had a typo ('.' where a ',' should have been) which
also resulted in this error message in a recent version. See
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7669 for a report of
this issue (which is not a bug in SA per se, as the rules with the typo
are an independent distribution.)
I checked for this problem in the SA rules, but didn't find any problems.
I'm using the default set, and my research says these have all been fixed.
So, the problem must be in an affiliated perl module, but I have no idea
how to find it.
Everything on this server is up to date. I just upgraded to 11.2-RELEASE
last week and rebuilt all the ports. I've run portmaster -ad twice since
and updated several other ports.
If there's a way to do it, I'd like to run this problem down and notify the
developer, but I have no clue how to go about that. I don't know how to
setup a trace on the filter process.
Paul Schmehl
Independent Researcher
Re: Maillog error - warn: Unescaped left brace in regex is deprecated here (and will be fata))
On 14 Dec 2018, at 17:35, Paul Schmehl wrote:
--On December 14, 2018 at 3:32:11 PM -0500 Bill Cole
wrote:
On 14 Dec 2018, at 0:46, Paul Schmehl wrote:
I'm seeing this error in the logs:
warn: Unescaped left brace in regex is deprecated here (and will be
fata))
It would be a wise choice to update ALL of your Perl modules to the
latest releases, as this issue can arise in non-obvious places...
So, I would assume it would be one of these modules?
BUILD_DEPENDS= p5-Encode-Detect>=0:converters/p5-Encode-Detect \
p5-HTML-Parser>=3.46:www/p5-HTML-Parser \
p5-HTTP-Date>=0:www/p5-HTTP-Date \
p5-Net-DNS>=0.63:dns/p5-Net-DNS \
p5-NetAddr-IP>=4.010:net-mgmt/p5-NetAddr-IP
RUN_DEPENDS:= ${BUILD_DEPENDS} \
p5-Net-IDN-Encode>=0:textproc/p5-Net-IDN-Encode \
p5-Net-LibIDN>=0:dns/p5-Net-LibIDN \
p5-URI>=0:net/p5-URI \
re2c>=.12.0:devel/re2c
Those or any of the modules upon which they depend, recursively.
There are also Perl modules that will NOT appear as hard dependencies of
SA anywhere because they are optional or only required for particular
features. When running the build of SA, these will be looked for and
noted by Makefile.PL.
It is also possible (even likely) that this particular error is the
result of problematic syntax in a SpamAssassin rules file, because many
rules include regexes.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Available For Hire: https://linkedin.com/in/billcole
Re: Maillog error - warn: Unescaped left brace in regex is deprecated here (and will be fata))
--On December 14, 2018 at 3:32:11 PM -0500 Bill Cole
wrote:
On 14 Dec 2018, at 0:46, Paul Schmehl wrote:
I'm seeing this error in the logs:
warn: Unescaped left brace in regex is deprecated here (and will be
fata))
It would be a wise choice to update ALL of your Perl modules to the
latest releases, as this issue can arise in non-obvious places...
So, I would assume it would be one of these modules?
BUILD_DEPENDS= p5-Encode-Detect>=0:converters/p5-Encode-Detect \
p5-HTML-Parser>=3.46:www/p5-HTML-Parser \
p5-HTTP-Date>=0:www/p5-HTTP-Date \
p5-Net-DNS>=0.63:dns/p5-Net-DNS \
p5-NetAddr-IP>=4.010:net-mgmt/p5-NetAddr-IP
RUN_DEPENDS:= ${BUILD_DEPENDS} \
p5-Net-IDN-Encode>=0:textproc/p5-Net-IDN-Encode \
p5-Net-LibIDN>=0:dns/p5-Net-LibIDN \
p5-URI>=0:net/p5-URI \
re2c>=.12.0:devel/re2c
Paul Schmehl
Independent Researcher
Re: Maillog error - warn: Unescaped left brace in regex is deprecated here (and will be fata))
On 14 Dec 2018, at 15:32, Bill Cole wrote:
On 14 Dec 2018, at 0:46, Paul Schmehl wrote:
I'm seeing this error in the logs:
warn: Unescaped left brace in regex is deprecated here (and will be
fata))
NOTE: that message should specify the source of the error. If it does
not, something in your logging plumbing is mangling error messages.
Also note: there is at least one 3rd-party ruleset (http://sa.zmi.at)
which appears to have had a typo ('.' where a ',' should have been)
which also resulted in this error message in a recent version. See
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7669 for a report of
this issue (which is not a bug in SA per se, as the rules with the typo
are an independent distribution.)
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Available For Hire: https://linkedin.com/in/billcole
Re: Maillog error - warn: Unescaped left brace in regex is deprecated here (and will be fata))
--On December 14, 2018 at 3:32:11 PM -0500 Bill Cole
wrote:
On 14 Dec 2018, at 0:46, Paul Schmehl wrote:
I'm seeing this error in the logs:
warn: Unescaped left brace in regex is deprecated here (and will be
fata))
This is a new warning in Perl 5.26. The use of curly-brace regex
enumeration ranges with an implied zero first term ( e.g. {,5} instead of
{0,5} ) will be a fatal error in a later version (maybe 5.28, I have not
checked...)
It would be a wise choice to update ALL of your Perl modules to the
latest releases, as this issue can arise in non-obvious places...
It comes right after this:
status=sent (delivered via filter service
The filter service uses filter.sh (stolen from the docs) and
spamassassin. Is it safe to assume this is a code problem in spam
assassin (which I assume they will fix at some point)?
Not if you're using the current release (3.4.2) of SpamAssassin. As one
of the developers who worked on that specific issue, I am sure that we
believed all cases of that problem that were internal to the SpamAssassin
framework were fixed in 3.4.2. There are a lot of modules which SA
depends on, some of which can also cause that warning.
# spamassassin -V
SpamAssassin version 3.4.2
running on Perl version 5.26.3
Thanks, Bill. Guess I'll start rummaging through the modules.
Paul Schmehl
Independent Researcher
Re: Maillog error - warn: Unescaped left brace in regex is deprecated here (and will be fata))
On 14 Dec 2018, at 0:46, Paul Schmehl wrote:
I'm seeing this error in the logs:
warn: Unescaped left brace in regex is deprecated here (and will be
fata))
This is a new warning in Perl 5.26. The use of curly-brace regex
enumeration ranges with an implied zero first term ( e.g. {,5} instead
of {0,5} ) will be a fatal error in a later version (maybe 5.28, I have
not checked...)
It would be a wise choice to update ALL of your Perl modules to the
latest releases, as this issue can arise in non-obvious places...
It comes right after this:
status=sent (delivered via filter service
The filter service uses filter.sh (stolen from the docs) and
spamassassin. Is it safe to assume this is a code problem in spam
assassin (which I assume they will fix at some point)?
Not if you're using the current release (3.4.2) of SpamAssassin. As one
of the developers who worked on that specific issue, I am sure that we
believed all cases of that problem that were internal to the
SpamAssassin framework were fixed in 3.4.2. There are a lot of modules
which SA depends on, some of which can also cause that warning.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Available For Hire: https://linkedin.com/in/billcole
Re: maillog says "Service unavailable", bounce msg claims bad addr
On 3/6/2014 11:08 AM, Jay G. Scott wrote: > > The maillog says this, and I believe it: > > Mar 5 08:22:02 ns5.arlut.utexas.edu sendmail[5427]: s25EM0Zg005419: > to=, delay=00:00:01, xdelay=00:00:00, mailer=relay, > pri=1081946, relay=ns2.arlut.utexas.edu. [146.6.211.1], dsn=5.1.3, > stat=Service unavailable > The above is from sendmail(TM) not postfix. Uninstall/disable sendmail. > > But the user's bounce msg said: > > ns2.arlut.utexas.edu # recipient address syntax> It's not unusual for a mail client to "transform" error text, for example, to display a message in the local language. The 5.1.3 status code is preserved. > > However, that address is okay -- sendmail -bv says it's deliverable. If that's postfix, it may be using a different delivery path. Or maybe the problem got fixed. > > So is this disconnect between service availability and what the > user sees normal? or fixable? Current behavior is no indication of historical behavior, unless you have repeatable and consistent results. "A" always answers "foo" "B" always answers "bar" is something to investigate. Otherwise, chalk it up to a temporary external error. -- Noel Jones
Re: maillog - identifying port smtp, submission
Benny Pedersen: > santosh malavade skrev den 2012-12-28 05:59: > > > smtp 25 > > submission 587 > > in master.cf set -o syslog_name=foo for the 2 services > > then in syslog its possible to split them to 2 seperate files if wanted With vanilla syslog daemons, splitting the files might be easier by setting "-o syslog_facility=local1" or something similar in master.cf, and having a rule "local1.* /path/to/file" in syslog.conf. You MAY have to create the new logfile by hand, and you WILL have to update the logfile rotation procedure. Wietse
RE: maillog - identifying port smtp, submission
> Date: Fri, 28 Dec 2012 06:05:06 +0100 > From: m...@junc.eu > To: postfix-users@postfix.org > Subject: Re: maillog - identifying port smtp, submission > > santosh malavade skrev den 2012-12-28 05:59: > > > smtp 25 > > submission 587 > > in master.cf set -o syslog_name=foo for the 2 services > I have been able to override the syslog_name parameter for the submission port. > then in syslog its possible to split them to 2 seperate files if wanted > if possible, pls. provide example of this. Thanks. Rgds, Santosh Malavade
Re: maillog - identifying port smtp, submission
santosh malavade skrev den 2012-12-28 05:59: smtp 25 submission 587 in master.cf set -o syslog_name=foo for the 2 services then in syslog its possible to split them to 2 seperate files if wanted
Re: maillog
you MUST NOT stop bounces you have to look why they are happening and solve the root-cause which is maybe you do not reject messages to non-existent rcpt directly if you accept a message and it can not be finally delivered the server sends a NDR, if you reject the message the sending machine is responsible for the NDR - so maybe you are a backscatter Am 31.10.2011 14:31, schrieb Amira Othman: > T have tested server for open relay and it is not open already > How can I stop this kind of mail ? > > On the contrary, this is almost always a sign of trouble. Why was a > bounce sent? > > Common causes: backscatter, spammer exploit, open relay ... signature.asc Description: OpenPGP digital signature
Re: maillog
* Amira Othman : > T have tested server for open relay and it is not open already We did not mention an open relay as a sole cause. Why was the bounce sent. Grep for ED0466E68594 to find out -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
RE: maillog
T have tested server for open relay and it is not open already How can I stop this kind of mail ? > > from=<>, size=4794, nrcpt=1 (queue active) > > > > Oct 31 12:22:36 mailserver postfix/smtp[24079]: connect to > > smtp.icom.com[64.224.110.142]: Connection timed out (port 25) > > > > Oct 31 12:22:36 mailserver postfix/smtp[24079]: ED0466E68594: > > to=, relay=none, delay=47406, > > delays=47385/0.02/21/0, dsn=4.4.1, status=deferred (connect to > > smtp.icom.com[64.224.110.142]: Connection timed out) > > > > > > > > Is this normal to appear in my log file or it must be denied as > > it is from <> (what does this mean??) > > <> is the mailer daemon address no need to worry > guess it wants to send some bounce etc On the contrary, this is almost always a sign of trouble. Why was a bounce sent? Common causes: backscatter, spammer exploit, open relay ... --
Re: maillog
On Monday 31 October 2011 05:38:16 Robert Schetterer wrote: > Am 31.10.2011 11:35, schrieb Amira Othman: > > I was checking postfix maillog and I found something strange in > > it > > > > from=<>, size=4794, nrcpt=1 (queue active) > > > > Oct 31 12:22:36 mailserver postfix/smtp[24079]: connect to > > smtp.icom.com[64.224.110.142]: Connection timed out (port 25) > > > > Oct 31 12:22:36 mailserver postfix/smtp[24079]: ED0466E68594: > > to=, relay=none, delay=47406, > > delays=47385/0.02/21/0, dsn=4.4.1, status=deferred (connect to > > smtp.icom.com[64.224.110.142]: Connection timed out) > > > > > > > > Is this normal to appear in my log file or it must be denied as > > it is from <> (what does this mean??) > > <> is the mailer daemon address no need to worry > guess it wants to send some bounce etc On the contrary, this is almost always a sign of trouble. Why was a bounce sent? Common causes: backscatter, spammer exploit, open relay ... -- Offlist mail to this address is discarded unless "/dev/rob0" or "not-spam" is in Subject: header
Re: maillog
* Amira Othman : > Hi all > > I was checking postfix maillog and I found something strange in it > > from=<>, size=4794, nrcpt=1 (queue active) It's a bounce > Oct 31 12:22:36 mailserver postfix/smtp[24079]: connect to > smtp.icom.com[64.224.110.142]: Connection timed out (port 25) > > Oct 31 12:22:36 mailserver postfix/smtp[24079]: ED0466E68594: > to=, relay=none, delay=47406, delays=47385/0.02/21/0, > dsn=4.4.1, status=deferred (connect to smtp.icom.com[64.224.110.142]: > Connection timed out) > > > > Is this normal to appear in my log file Yes > or it must be denied as it is from <> (what does this mean??) It's a bounce (a non delivery report) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: maillog
Am 31.10.2011 11:35, schrieb Amira Othman: > Hi all > > I was checking postfix maillog and I found something strange in it > > from=<>, size=4794, nrcpt=1 (queue active) > > Oct 31 12:22:36 mailserver postfix/smtp[24079]: connect to > smtp.icom.com[64.224.110.142]: Connection timed out (port 25) > > Oct 31 12:22:36 mailserver postfix/smtp[24079]: ED0466E68594: > to=, relay=none, delay=47406, delays=47385/0.02/21/0, > dsn=4.4.1, status=deferred (connect to smtp.icom.com[64.224.110.142]: > Connection timed out) > > > > Is this normal to appear in my log file or it must be denied as it is > from <> (what does this mean??) > > > > Regards > <> is the mailer daemon address no need to worry guess it wants to send some bounce etc -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
