On Mon, May 29, 2017 at 05:02:36PM +1200, Peter wrote:
> On 29/05/17 16:57, Peter wrote:
> > find "$(postconf -h queue_directory)/deferred/)" -type f -exec postcat
> > -e {} + | your_program | postsuper -d -
>
> Oops, typo there, should be:
>
> find "$(postconf -h queue_directory)/deferred/" -typ
On 30/05/17 19:40, Geert Stappers wrote:
> On Mon, May 29, 2017 at 05:02:36PM +1200, Peter wrote:
>> On 29/05/17 16:57, Peter wrote:
>>> find "$(postconf -h queue_directory)/deferred/)" -type f -exec postcat
>>> -e {} + | your_program | postsuper -d -
>>
>> Oops, typo there, should be:
>>
>> find "
On Tue, May 30, 2017 at 07:42:24PM +1200, Peter wrote:
> On 30/05/17 19:40, Geert Stappers wrote:
> > On Mon, May 29, 2017 at 05:02:36PM +1200, Peter wrote:
> >> On 29/05/17 16:57, Peter wrote:
> >>> find "$(postconf -h queue_directory)/deferred/)" -type f -exec postcat
> >>> -e {} + | your_program
Hello,
I did all the steps from this page :
http://www.postfix.org/SASL_README.html
postconf -a gives cyrus and dovecot
postconf -A gives me only cyrus.
So it followed the cyrus steps on Centos 7.
but as soon as I do :
testsaslau
> On May 30, 2017, at 8:40 AM, Roelof Wobben wrote:
>
> testsaslauthd -u username -p password
>
> I see this as output : connect() : no file or directory.
>
> How can I figure out which file or directory is missing ?
Likely the saslauthd "mux" socket. Probably saslauthd is not running,
b
> On 30 May 2017, at 3:47 pm, rolelael wrote:
>
> Hello
>
> I'm trying to accomplish the following :
>
> If the return-path is <> ( empty ) then do the following ;
>
> if domain is robbya.be or robbyb.be route via mailrobby.test.com ; if domain
> is robbyc.be then route via mailrobby2.test.co
Yes I tested that. The problems seems to lie in the header Return-Path not
being found in the headers of the mail. I tried with the header From: and
look for the string from=<> but I cannot accomplish this.
Really stuck
--
View this message in context:
http://postfix.1071664.n5.nabble.com/
> On May 30, 2017, at 9:23 AM, Peter West wrote:
>
>> If the return-path is <> ( empty ) then do the following ;
>>
>> if domain is robbya.be or robbyb.be route via mailrobby.test.com ; if domain
>> is robbyc.be then route via mailrobby2.test.com
>>
>> if /^Return-Path...
This is misconceived
Victor ; what should I accomplish with check_sender_access ? Seems this one
is used to block senders ? We do not want to block emails, but reroute all
the mails on postfix towards relayhosts ( specified by the sending domain ).
In this case thinking in terms of out of office mails comming from O365
Hi, I see you have gotten plenty of good responses, but here is how I deal with
it.
Once I know what I am looking for from the command line I do this, and it
is pretty fast for 1 to 2 thousand emails at a time.
These are some recent examples I used to clean things up, that were sitting
ther
On 5/30/2017 9:29 AM, Viktor Dukhovni wrote:
On May 30, 2017, at 9:23 AM, Peter West wrote:
If the return-path is <> ( empty ) then do the following ;
if domain is robbya.be or robbyb.be route via mailrobby.test.com ; if domain
is robbyc.be then route via mailrobby2.test.com
if /^Return-Pat
Op 30-5-2017 om 14:56 schreef Viktor Dukhovni:
On May 30, 2017, at 8:40 AM, Roelof Wobben wrote:
testsaslauthd -u username -p password
I see this as output : connect() : no file or directory.
How can I figure out which file or directory is missing ?
Likely the saslauthd "mux" socket. Proba
12 matches
Mail list logo
