I run some front end servers, transporting a bunch of domains, but I'd
like to restrict the access to users existing on the server itself
(u...@mailserver.domain.tld). E.g. only accessible from localhost.
There are no IMAP or POP servers present, just Postfix.
1) which consequences has such a rest
Hi mailing-list,
I'm running a webserver which provides web- as well as mailservices. To send
(relay) mails, remote users have to authenticate, but currently this is not
necessary for local users (PHP etc...). This would be fine, but sometimes jerks
inject php-files and start spamming. Virtuall
I would love to be able to use comments on the same line as conf and map
file entries. That has probably been requested before, but is it a
definite WILL NOT?
Best regards,
-Tom
I have a Postfix-relay with a bunch of domains.
Most oft them are relayed to an ms exchange-server behind.
Therefore I make a ldap-query against the ms ad-server (relay_recipient_maps =
ldap:/etc/postfix/ldap_relay_recipient_map.cf) which works perfect.
One domain is hosted on a Linux (Postfix to
Good afternoon list.
It hs been a while since i worked on a postfix problem , so I apologise if
this is a trivial post.
I have an outbound mail server where senders are mistyping the recipient
domains due to the "O" & "P" being next to each other.
The recipient domain is local.
Is there a way t
I would also suggest supporting standard pipes.
Like
smtp_check_tls_policy = pipe:/usr/sbin/some_script.pl
Preferable, for performance, the script will be long-running in a loop and
accept questions on and spit out responses on
-Ursprungligt meddelande-
Från: owner-postfix-us...@postfix
In order to protect the stability of the Postfix SMTP client, I
propose a new feature that builds on smtp_tls_policy_maps that
allows experimentation with STS and other features.
The design is similar to the way that Postfix SMTP server policies
build on access maps.
1) An optional smtp_check_tls
Sebastian Nielsen:
> I would also suggest supporting standard pipes.
> Like
> smtp_check_tls_policy = pipe:/usr/sbin/some_script.pl
>
> Preferable, for performance, the script will be long-running in a loop and
> accept questions on and spit out responses on
The long-running stdin/stdout model
Tom Browder:
> I would love to be able to use comments on the same line as conf and map
> file entries. That has probably been requested before, but is it a
> definite WILL NOT?
Definitely. That would require some kind of quoting mechanism to
indicate which "#" are part of the data which "#" are
On Tue, Mar 22, 2016 at 11:56 AM, Wietse Venema wrote:
> Tom Browder:
>> I would love to be able to use comments on the same line as conf and map
>> file entries. That has probably been requested before, but is it a
>> definite WILL NOT?
>
> Definitely. That would require some kind of quoting mec
Please also note that adding something like this onto the end of a
"Received:" header line will break the syntax. There isn't supposed to
be anything extra after the date/time stamp in a "Received:" line. If
you feel you need to do this anyway, please consider enclosing your new
"unique ID" info
Tom Browder:
> On Tue, Mar 22, 2016 at 11:56 AM, Wietse Venema wrote:
> > Tom Browder:
> >> I would love to be able to use comments on the same line as conf and map
> >> file entries. That has probably been requested before, but is it a
> >> definite WILL NOT?
> >
> > Definitely. That would requi
On Tue, Mar 22, 2016 at 2:38 PM, Wietse Venema wrote:
> Tom Browder:
>> On Tue, Mar 22, 2016 at 11:56 AM, Wietse Venema wrote:
...
>> But, couldn't there be a user option to build Postfix to allow such
>> (or maybe define some special comment character or characters such as
>> the common '//' or
On 3/22/2016 8:02 AM, Postfix Users wrote:
> I have a Postfix-relay with a bunch of domains.
>
> Most oft them are relayed to an ms exchange-server behind.
>
> Therefore I make a ldap-query against the ms ad-server
> (relay_recipient_maps =
> ldap:/etc/postfix/ldap_relay_recipient_map.cf) which w
Wietse:
[modeline support to turn on/off #comment support]
Tom Browder:
> I agree, but I was think of a non-default build config define for CCARGS, say,
> '-DALLOW_TRAILING_COMMENTS', so that all files read by postfix would
> always have trailing comments stripped before the rest of the line is
>
On Tue, Mar 22, 2016 at 3:23 PM, Wietse Venema wrote:
> Wietse:
> [modeline support to turn on/off #comment support]
>
> Tom Browder:
>> I agree, but I was think of a non-default build config define for CCARGS,
>> say,
>> '-DALLOW_TRAILING_COMMENTS', so that all files read by postfix would
>> alw
On 3/22/2016 8:07 AM, Thomas kinghorn wrote:
> Good afternoon list.
>
> It hs been a while since i worked on a postfix problem , so I
> apologise if this is a trivial post.
>
> I have an outbound mail server where senders are mistyping the
> recipient domains due to the "O" & "P" being next to ea
On 20 Mar 2016, at 14:11, @lbutlr wrote:
/etc/hosts.allow:
ALL : 185.103.253.246 : DENY
Has no effect.
For /etc/hosts.{allow,deny} files to have any effect on network access
to a program, the program must support the TCP Wrappers facility by
linking to libwrap OR be wrapped by the tcpd a
Hello,
I have configured my postfix to use virtual mailboxes (using berkeley dbs
for each setting), however postfix is not able to find the database files.
Here's the relevant configuration and setup:
/etc/postfix/main.cf:
canonical_maps = hash:/etc/postfix/canonical
virtual_alias_maps = hash:/et
OS X Postfix system rebuilt as a relay with no local mailboxes, but
we're not passing inbound mail to the final destination except for the
few people who have local accounts on the postfix server. Soft bounce
is onluckily (great safety net, Wietse). I have something that's
negating reject_un
On 3/22/2016 8:54 PM, Rick Zeman wrote:
> OS X Postfix system rebuilt as a relay with no local mailboxes, but
> we're not passing inbound mail to the final destination except for the
> few people who have local accounts on the postfix server. Soft bounce
> is onluckily (great safety net, Wiets
Hi,
is your trivial-rewrite daemon running chrooted?
On Debian (and possibly its childs, like Ubuntu) it matters how you
restarted postfix to get the new config active. /etc/init.d/postfix
copies some necessary files into chroot. In doubt, you should restart
postfix by "/etc/init.d/postfix restar
Oops, knew I forgot something, Noel. This is a (soft) bounce for a
recipient that does exist on the destination system, but not on the
postfix system, as the following telnet shows:
Mar 22 22:32:32 miniserv postfix/smtpd[70673]: NOQUEUE: reject: RCPT
from pmta1.delivery8.ore.mailhop.org[54.191.1
On 3/22/2016 10:03 PM, Rick Zeman wrote:
> Oops, knew I forgot something, Noel. This is a (soft) bounce for a
> recipient that does exist on the destination system, but not on the
> postfix system, as the following telnet shows:
>
> Mar 22 22:32:32 miniserv postfix/smtpd[70673]: NOQUEUE: reject:
24 matches
Mail list logo
