On 07 Jun 2013, at 21:17 , Nikolas Kallis n...@nikolaskallis.com wrote:
Its not true that there is no benefit using a SSL certificate from a CA. Some
MTA's will reject connecting to a remote host if it cannot validate its
security credentials from a CA.
Are you sure about that? I've *never*
Nikolas, please do not reply off-list. Always reply to the list unless
there is a good reason not to (such as a shouting argument with another
user, a thread drifts wildly off topic, you are asked to, etc).
On 6/7/2013 11:20 PM, Nikolas Kallis wrote:
On 08/06/13 14:09, Stan Hoeppner wrote:
On
On 2013-06-08 05:24, Nikolas Kallis wrote:
On 08/06/13 03:48, Per olof Ljungmark wrote:
Hi all,
Hopefully I can explain this good enough for someone to understand and
perhaps even suggest a solution.
Our email system is built from a LDAP directory that contains all the
necessary
On 08/06/13 17:49, Stan Hoeppner wrote:
Nikolas, please do not reply off-list. Always reply to the list unless
there is a good reason not to (such as a shouting argument with another
user, a thread drifts wildly off topic, you are asked to, etc).
On 6/7/2013 11:20 PM, Nikolas Kallis wrote:
On
Please tell me how to find out that some other component has locked the
pid files. I have done the following things to find out :-
[root@drmail1 ~]# /etc/init.d/postfix status
master dead but pid file exists
[root@drmail1 ~]# ps -ef | grep postfix
root 1412 1 0 Jun07 ?00:00:00
Hi.
When an user inputs an incorrect password, I have the following message
in the logs:
mx1 postfix/smtpd[1069]: warning: unknown[89.xx.xx.xx]: SASL LOGIN
authentication failed: UGFzc3dvcmQ6
Which is perfectly normal.
But how can I also show the username that was tried in the logs? I want
to
jayanta.gh...@cesc.co.in:
Please tell me how to find out that some other component has locked the
pid files. I have done the following things to find out :-
[root@drmail1 ~]# /etc/init.d/postfix status
master dead but pid file exists
Please file a bug report with REDHAT. They have broken
Hello everyone,
Need some assistance...
Had a power problem that resulted in a hard reset of our mail server.
Everything seems to be back up and running, postfix is delivering all of
our mail, and successfully sending outbound mail (all using virtual
transport), with one exception - mailman
Bogdan Enache:
Hi.
When an user inputs an incorrect password, I have the following message
in the logs:
mx1 postfix/smtpd[1069]: warning: unknown[89.xx.xx.xx]: SASL LOGIN
authentication failed: UGFzc3dvcmQ6
Which is perfectly normal.
'UGFzc3dvcmQ6' decodes into 'Password:'. That's part of
Charles Marcus:
2013-06-08T06:49:34-04:00 myhost postfix/cleanup[30010]: 2C8D7B7D633:
message-id=51b30786.7020...@media-brokers.com
2013-06-08T06:49:34-04:00 myhost postfix/qmgr[29915]: 2C8D7B7D633:
from=listname-boun...@media-brokers.com, size=4185, nrcpt=6 (queue active)
Per olof Ljungmark:
Hi all,
Hopefully I can explain this good enough for someone to understand and
perhaps even suggest a solution.
Our email system is built from a LDAP directory that contains all the
necessary information about our users. A box receives mail from the MX's
and routes it
On 6/7/2013 4:26 PM, DTNX Postmaster wrote:
On Jun 8, 2013, at 00:47, Noel Jones njo...@megan.vbhcs.org wrote:
On 6/7/2013 3:28 PM, Asai wrote:
Greetings,
We're starting to incorporate iPhone users into our email system.
Sometimes we seem to be having trouble with mail being delayed for a
On Jun 8, 2013, at 17:16, Asai a...@globalchangemusic.org wrote:
On 6/7/2013 4:26 PM, DTNX Postmaster wrote:
The Mail.app applications on iOS (iPhones or iPads) or OS X will
attempt to autodetect the port to connect to; 25, 465, and 587. It
works just fine over the submission port (587)
On 06/04/2013 02:20 PM, Erwan David wrote:
On Tue, Jun 04, 2013 at 01:44:46PM CEST, Tom Hendrikx t...@whyscream.net said:
On 06/04/2013 01:22 PM, Antonio Gutiérrez Mayoral wrote:
Hi Wietse,
Yes, its a solution, but these emails should be delivered in
bussines-time :-(
(it doesnt matter if it
Jeroen Geilman:
On 06/04/2013 02:20 PM, Erwan David wrote:
On Tue, Jun 04, 2013 at 01:44:46PM CEST, Tom Hendrikx t...@whyscream.net
said:
On 06/04/2013 01:22 PM, Antonio Guti?rrez Mayoral wrote:
Hi Wietse,
Yes, its a solution, but these emails should be delivered in
bussines-time
On 2013-06-08 8:26 AM, Wietse Venema wrote:
[the same error on the virtual socket disappeared after a while]
The Postfix warranty does not cover file system corruption, so
I can only provide generic system repair suggestions.
If Solaris or *BSD, boot single-user mode and fsck the file system.
Charles Marcus:
On 2013-06-08 8:26 AM, Wietse Venema wrote:
[the same error on the virtual socket disappeared after a while]
The Postfix warranty does not cover file system corruption, so
I can only provide generic system repair suggestions.
If Solaris or *BSD, boot single-user mode
Wietse Venema wrote:
Charles Marcus:
On 2013-06-08 8:26 AM, Wietse Venema wrote:
[the same error on the virtual socket disappeared after a while]
The Postfix warranty does not cover file system corruption, so
I can only provide generic system repair suggestions.
If Solaris or *BSD, boot
On 2013-06-08 5:01 PM, wie...@porcupine.org (Wietse Venema)
wie...@porcupine.org (Wietse Venema) wrote:
Charles Marcus:
On 2013-06-08 8:26 AM, Wietse Venema wrote:
[the same error on the virtual socket disappeared after a while]
The Postfix warranty does not cover file system corruption, so
I
On Sat, Jun 08, 2013 at 05:52:55PM -0400, Charles Marcus wrote:
I'm working on the mailman list to see if they can help.
Make sure all databases (built via postalias, ...) are in
good working order. Rebuild them all from the plaintext
source files.
Use netstat/lsof to find processes listening
On 08 Jun 2013, at 04:09 , Bogdan Enache enachebog...@gmx.com wrote:
But how can I also show the username that was tried in the logs? I want
to see:
1. Which user keeps entering the wrong password.
2. What user is someone else trying to hijack.
Are you using courier authlib?
It has a
Bogdan Enache skrev den 2013-06-08 12:09:
mx1 postfix/smtpd[1069]: warning: unknown[89.xx.xx.xx]: SASL LOGIN
authentication failed: UGFzc3dvcmQ6
Which is perfectly normal.
normal in what way ?
i have seen this here aswell with that user
But how can I also show the username that was tried in
22 matches
Mail list logo
