On 28/11/2011 20:16, Vincenzo Romano wrote:
2011/11/28 Viktor Dukhovni postfix-us...@dukhovni.org:
On Mon, Nov 28, 2011 at 06:17:30PM +0100, Vincenzo Romano wrote:
2011/11/28 Wietse Venema wie...@porcupine.org:
Vincenzo Romano:
The point is that postfix/smtp is not logging the Message-ID
Am 30.11.2011 11:39, schrieb Simone Caruso:
Correct, Viktor.
Once I'm said the queue ID is useful, then useless, then useful again.
Now I know.
Te lo spiego in italiano, Viktor dice di assegnare un ID a livello APPLICATIVO
che sia univoco e che t renda tracciabile un messaggio.
Se vuoi
what about speaking english in a public mailing-list instead switch
the language inside a running thread?
Sorry I forgot to remove the list from 'Cc'; anyway i translated only Wietse and
Viktor emails without adding anything.
--
Simone Caruso
IT Consultant
+39 349 65 90 805
Hallo,
I would to like to enable SMTP authentication, as an option feature for our
users, but I have some questions before doing so.
1st: Is it possible to enable it, without Cyrus of Dovecot? I do not want to
install Cyrus of Dovecot on my gateway.
2nd: As far as I understand, there is an
On 11/30/2011 12:55 PM, Peter Tselios wrote:
Hallo,
I would to like to enable SMTP authentication, as an option feature for our
users, but I have some questions before doing so.
1st: Is it possible to enable it, without Cyrus of Dovecot? I do not want to
install Cyrus of Dovecot on my
Thank you Brian,
Sorry, to bug you, but, do you have any link to read how to enable the SMTP
Auth? My plan is to enable it (first for selected users and later for all users
(in the openLDAP). All how-tos I have found so far are with Cyrus or Dovecot.
P.
- Αρχικό μήνυμα -
Απο: Brian
On 11/30/2011 1:13 PM, Peter Tselios wrote:
Thank you Brian,
Sorry, to bug you, but, do you have any link to read how to enable the SMTP
Auth? My plan is to enable it (first for selected users and later for all
users (in the openLDAP). All how-tos I have found so far are with Cyrus or
Hi All;
I am new to postfix.
I am using Fedora and I installed it using yum, also I was able to send email
by using the telnet method. I added one user in the linux using adduser command.
But when I tried to use outlook to send email, it failed !
First of all, I feel it is most probably
Am 30.11.2011 23:39, schrieb bilal ghayyad:
I am new to postfix.
I am using Fedora and I installed it using yum, also I was able to send email
by using the telnet method. I added one user in the linux using adduser
command.
But when I tried to use outlook to send email, it failed !
Hi *,
My google-foo is failing me at this point, so I turn to you all. I
am using a standard Postfix setup and am sending messages via
Thunderbird. I am choosing under the Options menu "Delivery Status
Notification". The results:
DSN's for email sent
Nevermind, I have finally found an article that explains DSN from
behind the scenes. It is quite different than just a standard "250
OK" status message of course. Article was written in 1997
apparently, but still helpful
Russell Jones:
html
head
meta content=text/html; charset=ISO-8859-1
http-equiv=Content-Type
/head
body bgcolor=#FF text=#00
Nevermind, I have finally found an article that explains DSN from
behind the scenes. It is quite different than just a standard 250
Hi Wietse,
Thanks! That's different from what I read in that article then...
according to that article the remote mail server needs to support DSN as
well for the reports to be generated.
If what you are saying is correct, how can I go about diagnosing why I
am not receiving DSN success
Russell Jones:
Hi Wietse,
Thanks! That's different from what I read in that article then...
according to that article the remote mail server needs to support DSN as
well for the reports to be generated.
Per RFC 3461..3464, Postfix sends DSN relayed (not success) if
the remote server does
Ah that makes sense!
This problematic mail server does announce DSN when you telnet to it,
while Google, Yahoo etc do not announce DSN support.
Thanks for your help. Final question (hopefully), is there a way to
ignore DSN announcements from remote servers and just treat them as if
they
Russell Jones:
Ah that makes sense!
This problematic mail server does announce DSN when you telnet to it,
while Google, Yahoo etc do not announce DSN support.
Thanks for your help. Final question (hopefully), is there a way to
ignore DSN announcements from remote servers and just treat
Thanks! Just got it working as intended =)
Nov 30 18:33:04 bigbertha postfix/smtp[22632]: discarding EHLO keywords: DSN
On 11/30/2011 6:33 PM, Wietse Venema wrote:
Russell Jones:
Ah that makes sense!
This problematic mail server does announce DSN when you telnet to it,
while Google, Yahoo
Hello,
I am running a mail relay that forwards all mail from some management
network to a corporate MTA. For security reasons, my gateway is configured to
relay mail only to internal destination addresses (us...@mydomain.com). There
are a few
exceptions and all external addresses must be
On Wed, Nov 30, 2011 at 08:38:13PM -0500, Vladimir Parkhaev wrote:
Augment this:
smtpd_recipient_restrictions =
check_recipient_access hash:/usr/local/etc/postfix/access,
reject_unauth_destination,
permit
As follows (and avoid using access, name each table after its
Hello Group,
I am trying some extra configuration for postfix where it would mark some
destinations as undeliverable. I have found that there are some
destinations, start deferring the mails (may be greylisting) for a
particular period of time (times ranging from 1min to 4hrs), and after the
time
20 matches
Mail list logo
