Hello,
I was wondering where feature-wishes should be written to, so I assume
this maillinglist might be a good start. Might well be that other
people asked for similar features already, a fast look through the
archive didn't result in anything like that though.
There's warn_if_reject and defer_i
kshitij mali:
> Feb 20 00:54:17 D1OKH680RL postfix/smtp[4993]: 390077605C3: to=<
> xxx...@lcit.com >, relay=none,
> delay=13164, delays=13144/0/20/0, dsn=4.4.3, status=deferred (Host or
> domain name not found. Name service error for name=lcit.com type=MX: Host
> not found, try again)
Does this he
On Feb 15, 2012, at 8:09 PM, jeffrey j donovan wrote:
>
> On Feb 15, 2012, at 10:47 AM, Bill Cole wrote:
>
>> On 15 Feb 2012, at 7:57, jeffrey j donovan wrote:
>>
>>> On Feb 14, 2012, at 10:57 PM, Bill Cole wrote:
>>>
On 14 Feb 2012, at 17:35, Bradley Giesbrecht wrote:
> On Feb
Jack Knowlton:
> Hi guys.
> My mailserver uses a relayhost which basically only signs messages with
> DKIM and delivers them.
> I would like to add a custom header, something like "X-Abuse: if spam/uce
> email ab...@mydomain.com".
> How should I go about, without postfix adding the header twice (be
Hi guys.
My mailserver uses a relayhost which basically only signs messages with
DKIM and delivers them.
I would like to add a custom header, something like "X-Abuse: if spam/uce
email ab...@mydomain.com".
How should I go about, without postfix adding the header twice (before and
after dkimfilter-o
Le 20/02/2012 11:40, Nikolaos Milas a écrit :
> Hi,
>
> We would like to block ONLY user somebad...@example.net so that he can't
> send mail to myu...@example.com.
>
> Does the following look sane?
>
> smtpd_restriction_classes = controlled_senders, otherclass1, otherclass2
>
> controlled_sende
On 21-02-12 20:06, Ed W wrote:
> On 16/02/2012 23:07, Tom Hendrikx wrote:
>> On 16-02-12 23:52, Dipl.-Ing. Juergen Ladstaetter wrote:
>>> Thank you both very much. That input was very good and I might
>>> rethink the
>>> strategy we're aiming at. Probably active DNS checks and periodic
>>> re-check
On 2/21/2012 1:15 PM, Ed W wrote:
> On 21/02/2012 18:41, Wietse Venema wrote:
>> Martin Mielke:
>>> mynetworks = hash:/etc/postfix/network_table
>> ...
>>> # postmap -q 1.2.3 /etc/postfix/network_table
>>> OK
>> ...
>> Where does the POSTFIX documentation say that you can specify
>> less than 4 oct
Ed W:
> As the OP suggested, a desirable solution would be for the MTA to only
> check the various maps to decide a domain is local *after* having done a
> DNS check to see if the MX record points "to this machine". ie the end
> goal is if the MX record points to some other machine, then we del
On 21/02/2012 18:41, Wietse Venema wrote:
Martin Mielke:
mynetworks = hash:/etc/postfix/network_table
...
# postmap -q 1.2.3 /etc/postfix/network_table
OK
...
Where does the POSTFIX documentation say that you can specify
less than 4 octets in a mynetworks table?
Wietse
Perhaps it's
Wietse Venema:
> Wietse Venema:
> > Martin Mielke:
> > > mynetworks = hash:/etc/postfix/network_table
> > ...
> > > # postmap -q 1.2.3 /etc/postfix/network_table
> > > OK
> > ...
> > Where does the POSTFIX documentation say that you can specify
> > less than 4 octets in a mynetworks table?
>
> Ans
On 16/02/2012 23:07, Tom Hendrikx wrote:
On 16-02-12 23:52, Dipl.-Ing. Juergen Ladstaetter wrote:
Thank you both very much. That input was very good and I might rethink the
strategy we're aiming at. Probably active DNS checks and periodic re-checks
are better to ensure some security. Thanks guys
Wietse Venema:
> Martin Mielke:
> > mynetworks = hash:/etc/postfix/network_table
> ...
> > # postmap -q 1.2.3 /etc/postfix/network_table
> > OK
> ...
> Where does the POSTFIX documentation say that you can specify
> less than 4 octets in a mynetworks table?
Answer: it doesn't. Instead of using has
Martin Mielke:
> mynetworks = hash:/etc/postfix/network_table
...
> # postmap -q 1.2.3 /etc/postfix/network_table
> OK
...
Where does the POSTFIX documentation say that you can specify
less than 4 octets in a mynetworks table?
Wietse
Hi all,
I have been looking for a solution to this in the forums, lists, etc but
unfortunately I could not find an answer... I also know that the subject has
been discussed several times so please bear with me...
The environment:
--
# rpm -q postfix
postfix-2.3.3-2.3.el5_6
--
The symptoms:
--
On 2/21/2012 10:55 AM, Harakiri wrote:
>
>
> --- On Tue, 2/21/12, Noel Jones wrote:
>
>> From: Noel Jones
>> Subject: Re: check_sender_access only for "outbound" mails e.g. those that
>> are in mynetworks
>
>> something like:
>>
>> # /etc/postfix/mynetworks.cidr
>> 127.0.0.0/8 OK {or check_
--- On Tue, 2/21/12, Noel Jones wrote:
> From: Noel Jones
> Subject: Re: check_sender_access only for "outbound" mails e.g. those that
> are in mynetworks
> something like:
>
> # /etc/postfix/mynetworks.cidr
> 127.0.0.0/8 OK {or check_local_sender depending on
> what you want}
> 192.168.0.
Harakiri:
> smtpd_sender_restrictions =ldap2_config..., reject
>
> the problem with this is - that this check is also executed for
> inbound mails.
Wietse:
> smtpd_sender_restrictions = permit_mynetworks, ...
Harakiri:
>This is exactly the wrong away around - as i said i need to verify
>envelop
--- On Tue, 2/21/12, Wietse Venema wrote:
> From: Wietse Venema
> Subject: Re: check_sender_access only for "outbound" mails e.g. those that
> are in mynetworks
> To: "Postfix users"
> Date: Tuesday, February 21, 2012, 10:47 AM
> Harakiri:
> > smtpd_sender_restrictions =ldap2_config..., reje
On 2/21/2012 9:21 AM, Harakiri wrote:
> I have currently a whitelist which checks inbound recipients against an ldap
> using a combination of
>
> relay_recipient_maps = ldap_config...
> smtpd_recipient_restrictions = permit_mynetworks ...reject_unlisted_recipient
>
> Now i want to have a simila
Harakiri:
> smtpd_sender_restrictions =ldap2_config..., reject
>
> the problem with this is - that this check is also executed for
> inbound mails.
smtpd_sender_restrictions = permit_mynetworks, ...
Wietse
I have currently a whitelist which checks inbound recipients against an ldap
using a combination of
relay_recipient_maps = ldap_config...
smtpd_recipient_restrictions = permit_mynetworks ...reject_unlisted_recipient
Now i want to have a similar solution for outbound, only enveloped from
addres
On 2/21/2012 8:03 AM, polloxx wrote:
> Hi,
>
> I want to rewrite the From: address for inbound mail from that
> address. I use Address Rewriting: virtual_maps.
> It works for To: addresses but not for From: addresses. What's wrong here?
Sounds like what you want is canonical_maps.
http://www.pos
Hi,
I want to rewrite the From: address for inbound mail from that
address. I use Address Rewriting: virtual_maps.
It works for To: addresses but not for From: addresses. What's wrong here?
On 20/02/2012 21:36, Wietse Venema wrote:
to understand that only a minute portion of the entire return message
is "unstructured" text.
And might I add it would be worthwhile the OP reading the various MARF RFC's
if the objective is "readability". In almost every case I have come across,
these
Hello
I meant if it would be possible for Postfix to allow sending emails only
to certain destination domains and reject all
not-explicitly-defined-destination-domains.
Example :
Allow destination domain : *@surely-not-existent-domain.com
Deny destinations domains : *@*
Sincerely
On 02/20/12 1
26 matches
Mail list logo
