Am 12.02.2011 22:53, schrieb Bob Proulx:
A friend's Mac running Postfix logged this rejected attack:
Feb 11 21:45:28 mailer postfix/smtpd[3708]: NOQUEUE: reject: RCPT from
unknown[216.104.47.74]: 504 5.5.2 bluedick: Helo command rejected: need
fully-qualified hostname; from=b...@dick.com
Ralf Hildebrandt:
This seems to be TLS related, since it happens whenever TLS is being
used.
Here is a patch. This part of the TLS library still needs to be
restructured. There is redundancy in the internal APIs: multiple
function arguments propagate the same information, and that same
* Wietse Venema wie...@porcupine.org:
Ralf Hildebrandt:
This seems to be TLS related, since it happens whenever TLS is being
used.
Here is a patch. This part of the TLS library still needs to be
restructured. There is redundancy in the internal APIs: multiple
function arguments
function arguments propagate the same information, and that same
information is maintained by different functions, so things got
out of step when code was updated yesterday.
Yep, it's working. Thanks.
Also uploaded as postfix-2.9-20110213 to ftp.porcupine.org.
Wietse
If you mean why doesn't he synchronize all mail storage between the servers -
do you really think that that will
DECREASE the traffic ?
doesn't a san decrease traffic between servers!?
--
Simone Caruso
IT Consultant
p.iva: 03045250838
On 02/13/2011 06:06 PM, Simone Caruso wrote:
If you mean why doesn't he synchronize all mail storage between the
servers - do you really think that that will
DECREASE the traffic ?
doesn't a san decrease traffic between servers!?
That would be the case if he specifically stated he
I'm testing a filter that's available as both a milter and as a
postfix-style policy daemon listening on a unix socket. Either way, the
functionality of the filter is identical. Which approach is better?
Milter or unix socket? In this case, better is actually two separate
criteria:
Hello,
I've the following in main.cf
header_checks = regexp:/etc/postfix/regexp_table
My postfix release is 2.3.8
I've the following in my header_checks regex table:
# MAL FORMATED EMAIL ADDRESS
/^From:.*\.@.*/ REJECT 1 - Your Email address is not compliant with
RFC, Go Away
Darren Pilgrim:
I'm testing a filter that's available as both a milter and as a
postfix-style policy daemon listening on a unix socket. Either way, the
functionality of the filter is identical. Which approach is better?
Milter or unix socket? In this case, better is actually two separate
For a while now, Postfix has logged that clients send commands
ahead of time (unauthorized pipelining) but I didn't have code to
log what those clients actually sent, because those commands haven't
been read yet - they still sit in the input buffer.
Meanwhile I have been puzzled by this message
I did the same test on a postfix release 2.6.5, and Ive the same behavior.
Any idea?
Franck
---
E: mailto:m...@civis.net m...@civis.net
De : Franck MAHE [mailto:m...@civis.net]
Envoyé : dimanche 13 février 2011 22:33
À :
On 02/13/2011 10:33 PM, Franck MAHE wrote:
Hello,
I've the following in main.cf
header_checks = regexp:/etc/postfix/regexp_table
My postfix release is 2.3.8
I've the following in my header_checks regex table:
# MAL FORMATED EMAIL ADDRESS
/^From:.*\.@.*/ REJECT 1 - Your Email
Hi,
OK, but the REJECT 3 works fine, so I think it is an issue with the if, but
I dont see why.
Franck
---
M: +33 6 6042 7249
E: m...@civis.net
De : owner-postfix-us...@postfix.org
[mailto:owner-postfix-us...@postfix.org] De la part de Jeroen
On 02/14/2011 12:13 AM, Franck MAHE wrote:
Hi,
OK, but the REJECT 3 works fine, so I think it is an issue with the
if, but I don't see why.
Define works fine.
What headers did you test, and what was the result ?
Franck
---
M: +33 6 6042 7249
E:
I did the test on the From header, so I dont understand why the if
!/^From:.*.*@.*/ dont catch header From: user...@domain.tld
I want to catch all character not compliant with the standard in the From
Header.
Franck
---
E: mailto:m...@civis.net
On 02/14/2011 12:37 AM, Franck MAHE wrote:
I did the test on the From header, so I don't understand why the if
!/^From:.*.*@.*/ don't catch
header From: user...@domain.tld
A. It does catch that, since it doesn't contain either or .
But
B. That is unlike anything you have shown before.
OK, so this configuration seems to work fine.
/^From:.*.*(\[|\]|\(|\)|\`|\;|\,|\^|\#|\:|\||\\|\@|||\/|\!|\
|\$|||\%|\|').*@.*/ REJECT 3 - Your Email address is not compliant with
RFC, Go Away
if !/^From:.*.*@.*/
/^From:.*([|]|\(|\)|`|;|,|^|#|:|\||\\|@|||\/|!|$||%||').*@/ REJECT 4 -
Your
On 02/14/2011 01:37 AM, Franck MAHE wrote:
OK, so this configuration seems to work fine.
/^From:.*.*(\[|\]|\(|\)|\`|\;|\,|\^|\#|\:|\||\\|\@|||\/|\!|\
|\$|||\%|\|').*@.*/ REJECT 3 - Your Email address is not
compliant with RFC, Go Away
if !/^From:.*.*@.*/
Gary Smith put forth on 2/11/2011 11:15 AM:
Problem isn't white/grey/black listings, its that they accepted the email
with a valid return code but it never made it to the destination box. It only
seems to be happened on a few recipients. Basically, in short, the
destination ISP (in this
Victor Duchovni put forth on 2/11/2011 4:50 PM:
On Fri, Feb 11, 2011 at 11:38:41PM +0100, Gergely Buday wrote:
Dear Postfix experts,
I'm new to mailing servers and need advice. Is it reasonable for my
small company to use my own mail server? How much configuration is
needed for a secure
On 2/13/2011 6:37 PM, Franck MAHE wrote:
OK, so this configuration seems to work fine.
/^From:.*.*(\[|\]|\(|\)|\`|\;|\,|\^|\#|\:|\||\\|\@|||\/|\!|\
|\$|||\%|\|').*@.*/
REJECT 3 - Your Email address is not compliant with RFC, Go Away
if !/^From:.*.*@.*/
On Mon, Feb 14, 2011 at 01:45:28AM +0100, Jeroen Geilman wrote:
Any idea for the REJECT 4 to reject the header From: us e...@domain.tld
mailto:e...@domain.tld, ie with a space in the first part.
The example I showed you, while being much more readable, already included
the space.
Dare I
On 02/14/2011 02:15 AM, Victor Duchovni wrote:
On Mon, Feb 14, 2011 at 01:45:28AM +0100, Jeroen Geilman wrote:
Any idea for the REJECT 4 to reject the header From: us e...@domain.tld
mailto:e...@domain.tld, ie with a space in the first part.
The example I showed you, while being
23 matches
Mail list logo
