On 22 Apr 2015, at 10:28, Robert Chalmers wrote:
I’ll install another mail client that can be a bit more verbose I
think.
As you appear to be running on MacOS, a good choice for that would be
MailMate, which can give you a verbatim transcript of all connections.
Wietse Venema:
> Jesse Osby:
> > But it only works when I send to a local address that gets forwarded to an
> > external one via /etc/aliases. Here's what I've found:
> >
>
> sender_canonical_maps can rewrite the sender in:
>
> - mail submitted with the Postfix sendmail command
>
> - mail re
Jesse Osby:
> But it only works when I send to a local address that gets forwarded to an
> external one via /etc/aliases. Here's what I've found:
>
sender_canonical_maps can rewrite the sender in:
- mail submitted with the Postfix sendmail command
- mail received via the SMTP server
- mail
Hi,
I'm having a problem with Postfix 2.6.6 on CentOS 6.6. I want to rewrite the
sender for all mail sent by box to be "w...@mydomain.com". I added to my
main.cf a line "sender_canonical_maps = regexp:/etc/postfix/sender_canonical",
and the contents of that file are:
/.+/
On Wed, Apr 22, 2015 at 06:07:19PM +0800, Daniel Mare wrote:
> We have an old Mac OS X mail server that we plan to replace with a new
> Zimbra server, but we can't move all mailboxes over in one go, instead,
> we plan to route all internet mail to our new Zimbra server, which has
> the authoritati
Edgaras Luko?evi?ius:
> mail-backend-1 postfix/cleanup[24838]: warning: unix_trigger_event: read
> timeout for service public/qmgr
> mail-backend-2 postfix/cleanup[14219]: warning: unix_trigger_event: read
> timeout for service public/qmgr
Wietse:
> Your active queue is full. The system is fall
Thanks Noel, that gets me closer.
So it actually IS something to do with the SASL parts. The brevity of the
message in the syslog isn’t helping…
So I can continue the hunt now, first SASL - which I’m working on, then IMAP
for a possibly mis-configured Mail client
I’ll install another mail clie
On 4/22/2015 7:35 AM, Robert Chalmers wrote:
> I could really use some help with this one, not just a flick off. I
> love the software, and am trying my best to come to grips with it.
> The following just simply elude me.
>
> Is this something in postfix, or dovecot perhaps causing this
> message
Default limit is:
qmgr_message_active_limit = 2
I don’t have that many messages in active queue at any time.
And the only way to avoid this warning is to either throttle new messages of
try to deliver them faster?
On 22 Apr 2015, at 14:13, Wietse Venema wrote:
> Edgaras Luko?evi?ius:
> [
I could really use some help with this one, not just a flick off. I love the
software, and am trying my best to come to grips with it.
The following just simply elude me.
Is this something in postfix, or dovecot perhaps causing this message in syslog
I’ve searched everywhere I can think of for so
Hi Daniel,
Here we use another technique. For each user that we transfer from the old
server to the new one, I just add a line in transport.cf saying the
complete mailbox name for that user and the IP or DNS name of the new
server. For example:
ferna...@test.com : newserver.test.com
Also, it mak
Edgaras Luko?evi?ius:
[ Charset windows-1252 converted... ]
> Hello,
>
> I?m getting a lot of these messages. Anyone have an idea what is wrong?
> Should I tune some settings or what?
>
> mail-backend-1 postfix/cleanup[24838]: warning: unix_trigger_event: read
> timeout for service public/qmgr
On 2015-04-22 12:47, Edgaras Lukoševičius wrote:
Also, I see that postfix is piping messages to only a small number of
pipes while my cpu and disk is almost idling..
There’s only 5-7 dovecot/deliver pipes. How can I increase this?
Hi Edgaras,
You could for example use LMTP delivery to dovecot,
Also, I see that postfix is piping messages to only a small number of pipes
while my cpu and disk is almost idling..
There’s only 5-7 dovecot/deliver pipes. How can I increase this?
virtual_transport = dovecot
default_destination_concurrency_limit = 100
initial_destination_concurrency = 25
local
All servers are running on CentOS 7.1
And I’m getting these errors while stress testing my environment.
Mail queue can get up to 1000 for each server at the time of testing.
I’’m not getting this warning on incoming server, just on backend, that
actually flush messages to disks. Maybe this is re
We have an old Mac OS X mail server that we plan to replace with a new Zimbra
server, but we can't move all mailboxes over in one go, instead, we plan to
route all internet mail to our new Zimbra server, which has the authoritative
list of all users on the domain and can thus reject non-existent
Hello,
I’m getting a lot of these messages. Anyone have an idea what is wrong? Should
I tune some settings or what?
mail-backend-1 postfix/cleanup[24838]: warning: unix_trigger_event: read
timeout for service public/qmgr
mail-backend-2 postfix/cleanup[14219]: warning: unix_trigger_event: read
On Tue, 2015-04-21 at 19:57 +, Viktor Dukhovni wrote:
> On Tue, Apr 21, 2015 at 09:50:05PM +0200, josef radinger wrote:
>
> > a domain xy.org which has users on two servers: one exchange server (B)
> > and one postfix(A). in front of that two systems is another portal-host,
> > which cannot di
18 matches
Mail list logo
