> > while () {
> > ...
> > }
> >
> > So executed outside of Postfix it is a one-time script.
>
>
> Nope. The above loop handles an arbitrary number of greylist queries,
> until it sees EOF on the standard input stream.
I see so its simply matter of postifx holds open
STDIN of the script that expla
On 10 Jul 2015, at 00:24, Wietse Venema wrote:
> Don't use home_mailbox if you want maildirs outside the home directory.
Doh! How did I miss that?
Thanks Wietse
On Jul 9, 2015, at 3:00 PM, Jim Reid wrote:
> Is there some reason why home_mailbox gets hard-wired to a user's home
> directory for maildir-flavour delivery?
It *IS* in the name.
And I quote:
> home_mailbox (default: empty)
> Optional pathname of a mailbox file relative to a local(8) user's ho
Spectrum Computer Solutions:
> Is there a way for me to configure postfix to permit IP 1.2.3.4
> to relay only mail addressed from example1234.com, and IP 2.3.4.5
> to relay only mail addressed from example2345.com and so on and
> so forth? I appericate this wouldn't be full proof, but it would
> s
Jim Reid:
> Is there some reason why home_mailbox gets hard-wired to a user's home
> directory for maildir-flavour delivery?
Don't use home_mailbox if you want maildirs outside the home directory.
http://www.postfix.org/postconf.5.html#mail_spool_directory
Wietse
Jim Reid skrev den 2015-07-09 23:00:
Is there some reason why home_mailbox gets hard-wired to a user's home
directory for maildir-flavour delivery?
I would like to arrange for user inboxes to be held in the IMAP store
-- say in /var/imap//INBOX -- rather than in each user's
home directory. ie Al
Is there some reason why home_mailbox gets hard-wired to a user's home
directory for maildir-flavour delivery?
I would like to arrange for user inboxes to be held in the IMAP store -- say in
/var/imap//INBOX -- rather than in each user's home directory. ie All
email gets stored in one fixed pla
Hi all,
# uname -a
FreeBSD 9.3-RELEASE-p13 FreeBSD 9.3-RELEASE-p13 #0: Tue Apr 7 03:01:12 UTC 2015
# postconf mail_version
mail_version = 2.11.5
I have a couple of servers setup to relay mail from customers.
Relay access to control by IP address using mynetworks parameter and a MySQL
backup.
E.B.:
> > > I found two perl examples that are within my skill to understand
> > > and one is based from the example code in the Postfix
> > > examples/smtpd-policy/greylist.pl if you don't know I think this is
> > > http://heap.altlinux.org/usr/share/doc/postfix-2.2.11/examples/smtpd-policy/greyli
> Le 9 juil. 2015 à 22:04, Robert Wolfe a écrit :
>
> Retrieve a listing of what?
>
A list of all blocked senders, i.e, email adresses that were added by end users
using Junk -> Block Sender action
I quickly read that a PowerShell command exist
(Get-MailboxJunkEmailConfiguration) to list bloc
> > I found two perl examples that are within my skill to understand
> > and one is based from the example code in the Postfix
> > examples/smtpd-policy/greylist.pl if you don't know I think this is
> > http://heap.altlinux.org/usr/share/doc/postfix-2.2.11/examples/smtpd-policy/greylist.pl
> > so i
On Thu, 2015-07-09 at 21:33 +0200, Alexandre Ellert wrote:
> This error message appears when an Outlook end user right click on an email
> and choose Junk -> Block sender.
> I will ask the Exchange admin if it’s possible to retrieve a list and then
> upload it to a Postfix access table.
Retriev
Alexandre Ellert:
>
> > Le 9 juil. 2015 ? 20:09, Viktor Dukhovni a
> > ?crit :
> >
> > On Thu, Jul 09, 2015 at 07:43:17PM +0200, Alexandre Ellert wrote:
> >
> >> I have an inbound MX in front of an Exchange Server and I?d like to
> >> DISCARD email when Exchange answer "554 5.1.0 Sender Deni
> Le 9 juil. 2015 à 20:09, Viktor Dukhovni a écrit
> :
>
> On Thu, Jul 09, 2015 at 07:43:17PM +0200, Alexandre Ellert wrote:
>
>> I have an inbound MX in front of an Exchange Server and I?d like to DISCARD
>> email when Exchange answer "554 5.1.0 Sender Denied" (and avoid backscatter)
>> Is
On Thu, Jul 09, 2015 at 07:43:17PM +0200, Alexandre Ellert wrote:
> I have an inbound MX in front of an Exchange Server and I?d like to DISCARD
> email when Exchange answer "554 5.1.0 Sender Denied" (and avoid backscatter)
> Is it possible to do something like that with Postfix ?
No. Instead w
Hello,
I have an inbound MX in front of an Exchange Server and I’d like to DISCARD
email when Exchange answer "554 5.1.0 Sender Denied" (and avoid backscatter)
Is it possible to do something like that with Postfix ?
Thank you for help
Alexandre
dont you just have to edit one line in the /etc/postfix/main.cf where it
says -
relayhost = IP_of_XEAMS_server
On Thu, Jul 9, 2015, at 12:37 PM, Wietse Venema wrote:
> Peter:
> > Here comes the postfix part. I am still having a couple of emails that
> > have not been delivered because postfix remembers the old DNS resolution
> > and I end up with deffered emails like this one here:
>
> Postfix does not r
Peter:
> Here comes the postfix part. I am still having a couple of emails that
> have not been delivered because postfix remembers the old DNS resolution
> and I end up with deffered emails like this one here:
Postfix does not remember old DNS results. Your caching
resolver does.
Wietse
OK, seems to be the straightest way.
-Ursprüngliche Nachricht-
Von: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
Im Auftrag von A. Schulze
Gesendet: Mittwoch, 8. Juli 2015 16:54
An: postfix-users@postfix.org
Betreff: Re: different queue lifetime for specifi r
* on the Thu, Jul 09, 2015 at 10:48:50AM +0200, Peter wrote:
> I have just now stumbled upon a DNS item that I can not crack by myself
> and your help would be immensely appreciated.
> I have been forwarding my emails using postfix transport_maps to a
> couple MX weight-based receivers. Since the
Hi folks,
I have just now stumbled upon a DNS item that I can not crack by myself
and your help would be immensely appreciated.
I have been forwarding my emails using postfix transport_maps to a
couple MX weight-based receivers. Since the IPs of these servers have
changed I updated my DNS records
Rosenbaum, Larry M.:
If the client looks at the SIZE line of the EHLO response, it may
determine at that point that the message is too big and abort the
attempt. In that case the server doesn't have any envelope data to
log, and might not even know why the client gave up.
yes, that's the
23 matches
Mail list logo
