Hi, i have setup a postfix smtp inbound gateway on front of a qmail smtp
server with vpopmail; on the qmail server i have also dovecot with LMTP
service enabled for user and quota lookup served to my postfix smarthost
through lmtp communication.
Mails flow and virtual users lookup are ok but whe
On Wednesday, April 6, 2016 8:33 PM, Wietse Venema wrote:
>Next, have a look at the permissions of the saslauthd socket AND
>of its parent directories. Are the directories mode 755, is the
>socket mode 644? If it is group-restricted then that may not work.
I thought maildrop relied on it's own
On 2016-04-06 16:19, Benning, Markus wrote:
In sasl.h:
#define SASL_FAIL -1 /* generic failure */
Could this one be added to the AUTH_TEMP case?
I took a look at the cyrus-sasl code in lib/checkpw.c and most error
cases there
return SASL_FAIL.
Wrong credentails return SASL_BADAUTH,
Benning, Markus:
> vstring_strcpy(reply, xsasl_cyrus_strerror(sasl_status));
> switch (sasl_status) {
> + case SASL_FAIL:
> + case SASL_NOMEM:
> case SASL_TRYAGAIN:
> case SASL_UNAVAIL:
> return XSASL_AUTH_TEMP;
Fixed in Postfix 3.2.
Wiet
I am trying to work out what parameters to add to
/smtpd_relay_restrictions, /both in main.cf and master.cf.
1. We do not allow relaying by any means!
2. In-house users must be registered, use our domains and port 587
(submission) to send.
I use /check_sender_access/ with a table in the fo
follow-up:
If I put anything other than, at a minimum, permit_sasl_authenticated I
get the following error message -
/Apr 7 08:53:52 bilbo postfix/submission/smtpd[15279]: fatal: in
parameter smtpd_relay_restrictions or smtpd_recipient_restrictions,
specify at least one wor//king instance o
On Tue, Apr 5, 2016, at 07:09 PM, Scott Kitterman wrote:
> I'm pretty sure it's a local configuration error. I'll address it in the
> upstream bug.
just fyi, it took a few steps, but it's solved & working.
See https://bugs.launchpad.net/pypolicyd-spf/+bug/1566561/comments/13
In summary I
r
Le 06/04/2016 19:24, jaso...@mail-central.com a écrit :
>
> On Wed, Apr 6, 2016, at 10:20 AM, Noel Jones wrote:
>> A third-party policy daemon or milter is required for SPF. Postfix
>> ships with support for these external third-party programs.
>>
>> Postfix does not include nor officially recomme
Sorry if this has been asked a 1000 times (but I couldn't find a hint). I
need to relay the majority of users of one domain to another postfix host,
except two users. How would I accomplish this?
Like: us...@example.com and us...@example.com local, all other users relay
to another host.
Thanks!
J
Le 07/04/2016 20:19, Juerg Reimann a écrit :
> Sorry if this has been asked a 1000 times (but I couldn't find a hint). I
> need to relay the majority of users of one domain to another postfix host,
> except two users. How would I accomplish this?
>
> Like: us...@example.com and us...@example.com lo
On 4/7/2016 7:44 AM, John Allen wrote:
> I am trying to work out what parameters to add to
> /smtpd_relay_restrictions, /both in main.cf and master.cf.
>
> 1. We do not allow relaying by any means!
> 2. In-house users must be registered, use our domains and port 587
> (submission) to send.
>
On 07/04/16 20:19, Juerg Reimann wrote:
> Sorry if this has been asked a 1000 times (but I couldn't find a hint). I
> need to relay the majority of users of one domain to another postfix host,
> except two users. How would I accomplish this?
>
> Like: us...@example.com and us...@example.com local,
Jan Ceuleers:
[ Charset windows-1252 converted... ]
> On 07/04/16 20:19, Juerg Reimann wrote:
> > Sorry if this has been asked a 1000 times (but I couldn't find a hint). I
> > need to relay the majority of users of one domain to another postfix host,
> > except two users. How would I accomplish thi
Is there something I can add to this to help with getting an answer to what I
need to do to get this working?
Sent from my iPhone
> On 6 Apr 2016, at 22:29, Philip McGaw wrote:
>
> I am running Ubuntu Ubuntu 14.04.4 LTS “Trusty” and "postconf -d | grep
> mail_version” gives me “mail_version =
> On 7 Apr 2016, at 21:51, Julio Cesar Covolato wrote:
>
>
> Em 07/04/2016 17:19, Philip McGaw escreveu:
>> Is there something I can add to this to help with getting an answer to what
>> I need to do to get this working?
>>
>> Sent from my iPhone
>>
>>> On 6 Apr 2016, at 22:29, Philip McGaw
> On 7 Apr 2016, at 21:44, Julio Cesar Covolato wrote:
>
>
> Em 07/04/2016 17:19, Philip McGaw escreveu:
>> Is there something I can add to this to help with getting an answer to what
>> I need to do to get this working?
>>
>> Sent from my iPhone
>>
>>> On 6 Apr 2016, at 22:29, Philip McGaw
Thanks for the suggestion Julio,
I did the following: In my master.cf changing
> dovecot unix - n n - - pipeflags=DRhu
> user=vmail:mail argv=/usr/lib/dovecot/deliver -d ${recipient}
to
> dovecot unix- n n - - pipe flag
I'm no postfix expert, but I'm thinking out loud if this can be done by
specifying an alias for those emails ? the alias would redirect the mail to
another domain and get it delivered through the transport map for that domain.
On Thursday, April 7, 2016 7:23 PM, Juerg Reimann wrote:
So
Philip McGaw:
> >> Mar 11 17:48:08 njoror postfix/pipe[32605]: 1BAF055AB6:
> >> to=, relay=dovecot, delay=0.43,
> >> delays=0.34/0.01/0/0.09, dsn=4.1.1, status=SOFTBOUNCE (user unknown)
Hint: >>>DOVECOT<<< says "user unknown:".
Wietse
Wietse Venema:
> Philip McGaw:
> > >> Mar 11 17:48:08 njoror postfix/pipe[32605]: 1BAF055AB6:
> > >> to=, relay=dovecot, delay=0.43,
> > >> delays=0.34/0.01/0/0.09, dsn=4.1.1, status=SOFTBOUNCE (user unknown)
>
> Hint: >>>DOVECOT<<< says "user unknown:".
As Viktor pointed out (I am not familiar
Hello -- we're sending from a postfix instance as part of our
stress-testing infrastructure.
We need to limit the rate of outbound messages per second: sometimes to
a particular slow rate, sometimes to a medium speed, sometimes "as fast
as possible".
I found no easy way to do that; have I mi
See:
http://www.postfix.org/postconf.5.html#default_transport_rate_delay
http://www.postfix.org/postconf.5.html#default_destination_rate_delay
The names are similar but things work differently.
Wietse
Thank you -- will it accept decimal seconds?
We are sending on the order of 50-200+ messages per second in this
stress test, so the delay between messages could be smaller than .005
seconds.
On 04/07/2016 06:19 PM, Wietse Venema wrote:
See:
http://www.postfix.org/postconf.5.html#default_tran
> On Apr 7, 2016, at 11:32 PM, Casey Connor
> wrote:
>
> Thank you -- will it accept decimal seconds?
No.
> We are sending on the order of 50-200+ messages per second in this stress
> test, so the delay between messages could be smaller than .005 seconds.
Inject 50-200 messages per second i
We are sending on the order of 50-200+ messages per second in this stress test,
so the delay between messages could be smaller than .005 seconds.
Inject 50-200 messages per second into Postfix, and mail will not
be delivered faster than it comes in (unless a backlog develops
and clears when do
On 04/07/16 23:57, Casey Connor wrote:
>
>>> We are sending on the order of 50-200+ messages per second in this stress
>>> test, so the delay between messages could be smaller than .005 seconds.
>> Inject 50-200 messages per second into Postfix, and mail will not
>> be delivered faster than it co
> On Apr 7, 2016, at 11:57 PM, Casey Connor
> wrote:
>
> Please consider decimal-second rate limiting as a feature request. :-)
It is very unlikely to happen. To deliver much more than one message per
second, given typical message transaction latencies, delivery concurrency
is required, and s
27 matches
Mail list logo
