On Monday 02 November 2009 20:30:00 /dev/rob0 wrote:
>
> Please note that the question itself is a matter of GIGO. The munged
> IP address cannot be in mynetworks according to the postconf shown,
> because it was rejected, not accepted then bounced.
I get this behaviour with permit_mynetworks and
Hello,
I have a Postfix e-mail receiving server setup.
I have applied the following setting in my Postfix main.cf file:
smtpd_recipient_restrictions =
reject_unauth_destination,
reject_rbl_client sbl-xbl.spamhaus.org,
reject_rbl_client bl.spamcop.net
permit
for checking the mails with D
On Tue, Nov 03, 2009 at 09:26:33AM +, Simon Waters wrote:
> On Monday 02 November 2009 20:30:00 /dev/rob0 wrote:
> >
> > Please note that the question itself is a matter of GIGO. The munged
> > IP address cannot be in mynetworks according to the postconf shown,
> > because it was rejected, not
Hi,
let's assume the following setup:
main.cf:
myhostname = main.example.com
mydestination = $myhostname
master.cf
## 1st smtpd instance on 1.1.1.1
1.1.1.1:smtp inet n - n - - smtpd
## 2nd smtpd instance on 2.2.2.2
2.2.2.2:smtp inet n - n - - sm
* Sharma, Ashish :
> Hello,
> I have a Postfix e-mail receiving server setup.
> I have applied the following setting in my Postfix main.cf file:
> smtpd_recipient_restrictions =
> reject_unauth_destination,
> reject_rbl_client sbl-xbl.spamhaus.org,
You may want to use zen.spamhaus.org
>
Anyone have a filter they'd like to share that rejects mail at smtp
based on known malicious attachment file types? I've been out of the
game for a while in this regard. Received a spam today (that squeaked
past all my current filters) with a .docx file attached, and I don't
even know what that e
On 11/3/2009 9:13 AM, Stan Hoeppner wrote:
> Anyone have a filter they'd like to share that rejects mail at smtp
> based on known malicious attachment file types? I've been out of the
> game for a while in this regard. Received a spam today (that squeaked
> past all my current filters) with a .do
* Stan Hoeppner :
> Anyone have a filter they'd like to share that rejects mail at smtp
> based on known malicious attachment file types?
Of course .)
mime_header_checks:
/name=\"(.*)\.(386|bat|chm|cpl|cmd|com|do|exe|hta|jse|lnk|msi|ole)\"$/
REJECT Unwanted attachment/Unerwuenschter Anhang $
Sharma, Ashish put forth on 11/3/2009 3:58 AM:
> Hello,
>
> I have a Postfix e-mail receiving server setup.
>
> I have applied the following setting in my Postfix main.cf file:
>
> smtpd_recipient_restrictions =
> reject_unauth_destination,
> reject_rbl_client sbl-xbl.spamhaus.org,
> r
On 3-Nov-2009, at 07:13, Stan Hoeppner wrote:
Anyone have a filter they'd like to share that rejects mail at smtp
based on known malicious attachment file types?
main.cf:
mime_header_checks = pcre:$config_directory/mime_headers.pcre
$ cat mime_headers.pcre
/^\s*Content-(Disposition|Type).*n
Ralf Hildebrandt put forth on 11/3/2009 8:32 AM:
> * Stan Hoeppner :
>
>> Anyone have a filter they'd like to share that rejects mail at smtp
>> based on known malicious attachment file types?
>
> Of course .)
>
> mime_header_checks:
>
> /name=\"(.*)\.(386|bat|chm|cpl|cmd|com|do|exe|hta|jse|lnk
* Stan Hoeppner :
> Thanks Ralf. Is smtpd_recipient_restrictions the appropriate place to
> put mime_header_checks, like this?
No.
> smtpd_recipient_restrictions =
It's just:
mime_header_checks = pcre:/etc/postfix/mime_header_checks
> BTW, I can't tell--are these regexp or pcre format?
I u
On Tue, Nov 03, 2009 at 11:04:21AM +0100, Wolfram Schlich wrote:
> Hi,
>
> let's assume the following setup:
>
> main.cf:
>
> myhostname = main.example.com
> mydestination = $myhostname
>
> master.cf
>
> ## 1st smtpd instance on 1.1.1.1
> 1.1.1.1:smtp inet n - n - - sm
Hello all,
On Oct 30, 2009, ICANN announced that the Fast Track Process will begin
on Nov 16, 2009, which will allow non-Latin characters in domain names.
And as early as mid 2010 we may see these domains.
Does postfix support this? If yes, what versions are safe. If no, when
can support
On 3-Nov-2009, at 13:29, Brett Kislin wrote:
Hello all,
On Oct 30, 2009, ICANN announced that the Fast Track Process will
begin on Nov 16, 2009, which will allow non-Latin characters in
domain names.
Non-latin characters have been allowed in domain names for a long time.
For example: ht
On Tue, Nov 03, 2009 at 12:47:53PM -0800, William Jordan wrote:
> Folks,
>
> I assume we aren't the only ones whose users prefer Outlook as their mail
> client but use PostFix as their company e-mail server? I am doing research
> into Exchange (very costly) and other options for shared calendar
Peter Macko wrote:
> I have tried it, but it is still the same.
> Thank you very much for your help.
> I am almost sure, that there is a bug in AVG and
> I think I have found a workaround.
>
Please tell us what you did.
hi all
i understand i can transport an email id in the transport map; so i can put:
a...@example.com smtp:[192.168.0.1]
example.com smtp:[192.168.0.12]
my doubt :
with the above all mails to example.com will go to 192.168.0.12; will it
include a...@example.com? or that particular mail w
18 matches
Mail list logo
