Zitat von Viktor Dukhovni :
On Fri, Sep 13, 2013 at 11:45:54AM +0900, Jorgen Lundman wrote:
However, quite often the 3rd party involved uses software that can
use pipelining, and simply keeps sending mail, even though the
SMTPAuth account has been stopped.
What you are calling "pipelining"
Hi,
I'm using the latest version of postfix on Debian 6. I'm using an email
application to send mailings which automatically handles bounces through a
pipe php script. I have successfully setup a mail alias for postmaster to
the pipe script.
However in the bounce emails the "To" field in the mail
On 09/13/2013 08:47 AM, lst_ho...@kwsoft.de wrote:
> A workaround might be to force a mismatch with smtpd_sender_login_maps
> by removing the MAIL FROM --> Login-ID match in the table, no? But
> this only applies if reject_sender_login_mismatch could/should be used
> of course.
On top of that, plea
Viktor Dukhovni:
> > Can we add something similar to the "smtpd_client_restrictions" or
> > "smtpd_recipient_restrictions", and adding a new rule-entry which
> > would simply confirm that the "SMTPAuth LDAP 'user' used way back,
> > is still accountStatus=enabled" ?
Built-in message rate limit:
/
robby:
> Hi,
>
> I'm using the latest version of postfix on Debian 6. I'm using an email
> application to send mailings which automatically handles bounces through a
> pipe php script. I have successfully setup a mail alias for postmaster to
> the pipe script.
Please don't solve the wrong problem
If outgoing email bounced with 550,I would like, if not forever, for a
while, to bounce emails to that address locally. Is there a way to do
that?
Thanks in advance
Roman Gelfand:
> If outgoing email bounced with 550,I would like, if not forever, for a
> while, to bounce emails to that address locally. Is there a way to do
> that?
To bounce mail before it is delivered:
/etc/postfix/main.cf:
transport_maps = hash:/etc/transport
/etc/postfix/transport:
On Fri, Sep 13, 2013 at 04:29:28AM +, Viktor Dukhovni wrote:
> Sadly Postfix does not have an access table keyed by the SASL
> login name. Perhaps we should bite the bullet, and add one,
+1, a check_sasl_auth_access feature would be useful, despite the
fact that other approaches can accompli
This is a manual solution. Is there an automatic solution where based
on the log a transport file or database is maintained... something
that has smarts to automatically deal with 550's?
On Fri, Sep 13, 2013 at 11:05 AM, Wietse Venema wrote:
> Roman Gelfand:
>> If outgoing email bounced with 550
Roman Gelfand:
> If outgoing email bounced with 550,I would like, if not forever, for a
> while, to bounce emails to that address locally. Is there a way to do
> that?
Wietse:
> > To bounce mail before it is delivered:
> >
> > /etc/postfix/main.cf:
> > transport_maps = hash:/etc/transport
> >
>> I have nearly ten years experience with sending emails thru a newsletter.
>> BOTH of the undelivered email examples are due to INVALID EMAIL ADDRESSES.
>
> The next task will to find out why your server is sending to invalid
> addresses, too much of this just might find your server being blocke
Hello,
i've just setted up a postfix server, and i constantly have such error
in my logs :
Sep 13 21:31:34 effraie01 postfix/smtpd[12650]: SSL_accept error from
ng17.bullet.mail.bf1.yahoo.com
(ever from yahoo servers)
i can't figure out wher my mistake come from.
here is my postconf -n :
> Jim is absolutely correct about filtering your invalid emails, though I
> personally would
> never do it automatically, as there are too many variables to distinguish
> between
> ISP's that are subject to change. You could lose a lot of valid subscribers
> via
> automated filtering. The bounces t
On Fri, Sep 13, 2013 at 09:44:38PM +0200, Mathieu R. wrote:
> Sep 13 21:31:34 effraie01 postfix/smtpd[12650]: SSL_accept error
> from ng17.bullet.mail.bf1.yahoo.com
There is generally more information in the log than this when the
TLS handshake fails. DO NOT over-summarize the logs.
> (ever fro
Le 13/09/2013 22:29, Viktor Dukhovni a écrit :
On Fri, Sep 13, 2013 at 09:44:38PM +0200, Mathieu R. wrote:
Sep 13 21:31:34 effraie01 postfix/smtpd[12650]: SSL_accept error
from ng17.bullet.mail.bf1.yahoo.com
There is generally more information in the log than this when the
TLS handshake fails
On Fri, Sep 13, 2013 at 11:03:22PM +0200, Mathieu R. wrote:
> >There is generally more information in the log than this when the
> >TLS handshake fails. DO NOT over-summarize the logs.
>
> Sep 13 22:58:40 effraie01 postfix/smtpd[22230]: SSL_accept error
> from ng4.bullet.mail.bf1.yahoo.com[98.13
Le 13/09/2013 23:26, Viktor Dukhovni a écrit :
On Fri, Sep 13, 2013 at 11:03:22PM +0200, Mathieu R. wrote:
>There is generally more information in the log than this when the
>TLS handshake fails. DO NOT over-summarize the logs.
Sep 13 22:58:40 effraie01 postfix/smtpd[22230]: SSL_accept error
On Sep 13, 2013, at 23:51, Mathieu R. wrote:
> Le 13/09/2013 23:26, Viktor Dukhovni a écrit :
>> If your traffic volume is not too heavy, you can temporarily raise
>> the Postfix SMTP server TLS log level to "2":
>>
>> smtpd_tls_loglevel = 2
>>
>> this will show more details of the TLS han
On Fri, Sep 13, 2013 at 11:51:39PM +0200, Mathieu R. wrote:
> not very much more :
>
> Sep 13 23:33:09 effraie01 postfix/smtpd[25221]: connect from
> ng4.bullet.mail.bf1.yahoo.com[98.139.164.99]
> Sep 13 23:33:44 effraie01 postfix/smtpd[25221]: SSL_accept error
> from ng4.bullet.mail.bf1.yahoo.co
Le 14/09/2013 03:23, Viktor Dukhovni a écrit :
On Fri, Sep 13, 2013 at 11:51:39PM +0200, Mathieu R. wrote:
not very much more :
Sep 13 23:33:09 effraie01 postfix/smtpd[25221]: connect from
ng4.bullet.mail.bf1.yahoo.com[98.139.164.99]
Sep 13 23:33:44 effraie01 postfix/smtpd[25221]: SSL_accept e
20 matches
Mail list logo
