Change or suppress technical errors

Hello users, I've been wondering if there is any way to alter or suppress technical errors from reject messages. In a virtual mailbox setup, a spammer frequently attempts to send mail to non-existent mailboxes and receives the response: "Recipient address rejected: User unknown in virtual

Re: Change or suppress technical errors

On 1/20/2016 9:11 PM, Steven Kiehl wrote: > Hello users, > > I've been wondering if there is any way to alter or suppress > technical errors from reject messages. In a virtual mailbox setup, > a spammer frequently attempts to send mail to non-existent mailboxes > and receives the response: > >

Re: Cannot get destination_concurrency_limit working properly

On 1/20/2016 8:28 PM, Russell Jones wrote: > Still interested in trying to figure this out if I can. I am not > sure what else to look for on this. Any assistance will be > gratefully accepted! > For further help, please show "postconf -n" output, any modifications you've made to master.cf, and

Re: Cannot get destination_concurrency_limit working properly

Still interested in trying to figure this out if I can. I am not sure what else to look for on this. Any assistance will be gratefully accepted! On 1/18/2016 6:49 PM, Russell Jones wrote: Sorry that was a typo, I meant I checked for "destination_recipient_limit" and did not have anything set

Re: lmtp: transport unavailable

wilfried.es...@essignetz.de: [ Charset windows-1252 converted... ] > Am 20.01.2016 um 14:59 schrieb Wietse Venema: > > Wietse Venema: > >> Arian Sanusi: > >>> /var/log/mail.log: > Jan 20 11:31:40 chichak postfix/error[31253]: 6716E6A79: > to=,

Re: sender_canonical_maps for incoming e-mails

El 2016-01-19 18:37, wie...@porcupine.org escribió: Nicol?s: Hi, We have a filter located outside our organization for outgoing mail which rewrites the Return-Path to their domain, in the form: username=abc@theirdomain.com. Once the filter processes the message, it's forwarded to the

Re: sender based mail routing

On Mon, Jan 18, 2016 at 12:25:12PM -0500, Wietse Venema wrote: > The Postfix SMTP client uses the name from sender_dependent_relayhost_maps > for MX lookups (A lookups if the name is inside []). > > The Postfix SMTP client will not consider other names unless your > DNS provider lies, or you

Re: lmtp: transport unavailable

> You need to look earlier in the logfile. Look for fatal or warning > records. Just did - the only thing that's there is not helpful to me, either: Jan 20 11:31:40 chichak postfix/qmgr[31189]: warning: connect to transport private/local: Connec tion refused signature.asc Description:

lmtp: transport unavailable

Hi all, I'm trying to configure postfix for lmtp local delivery - delivery fails with "transport unavailable" however. lmtpd ist dovecot-lmtp, which works, I can send mail using smtp-source. Google did only find me questions about "pipe to dovecot"-style delivery, due to lmtp being in config

Re: lmtp: transport unavailable

Arian Sanusi: > /var/log/mail.log: > > Jan 20 11:31:40 chichak postfix/error[31253]: 6716E6A79: > > to=, orig_to=, relay=none, > > delay=0.42, delays=0.37/0/0/0.04, dsn=4.3.0, status=deferred (mail > > transport unavailable) > You need to look earlier

Re: sender based mail routing

Christian Recktenwald: > is there a way to use multiple target adresses? Actually, your question is about *prioritized* addresses. For equal-preference addresses you can use /etc/hosts with multiple records per name, or Postfix 3.0 builtin idiom based on pipemap:, inline: and randmap:

Re: sender_canonical_maps for incoming e-mails

nico...@devels.es: > > You may need to specify: > > > > local_header_rewrite_clients = static:all > > > > Or some other suitable filter. > > > > Wietse > > Thanks, that did the trick. > > I'm confused about the following, however. As documented, default value > for

Enforcing strict TLS servers validations possible?

Hi there! I've spent several hours trying to get it right, but seems I'm not getting much to anywhere, so I finally wanted to check whether I was doing something wrong or what. Given the circumstances, I wanted to validate a remote TLS-enabled smtpd certificate before sending any email at all. I

Re: lmtp: transport unavailable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 20.01.2016 um 12:18 schrieb Arian Sanusi: > >> You need to look earlier in the logfile. Look for fatal or >> warning records. > > Just did - the only thing that's there is not helpful to me, > either: Jan 20 11:31:40 chichak postfix/qmgr[31189]:

Re: lmtp: transport unavailable

Am 20.01.2016 um 14:59 schrieb Wietse Venema: > Wietse Venema: >> Arian Sanusi: >>> /var/log/mail.log: Jan 20 11:31:40 chichak postfix/error[31253]: 6716E6A79: to=, orig_to=, relay=none, delay=0.42, delays=0.37/0/0/0.04, dsn=4.3.0,

Re: lmtp: transport unavailable

>> Just did - the only thing that's there is not helpful to me, >> either: Jan 20 11:31:40 chichak postfix/qmgr[31189]: warning: >> connect to transport private/local: Connec tion refused > Looks like lack of rights or wrong path. lack of rights: postfix should be able to use the socket, if it

RE: lmtp: transport unavailable

Ok, debian, my thing.. ;-) Try : Edit /etc/dovecot/dovecot.conf To Change : protocols = imap lmtp And add: service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } protocol lmtp {

Re: Enforcing strict TLS servers validations possible?

dererk: > Hi there! > > I've spent several hours trying to get it right, but seems I'm not > getting much to anywhere, so I finally wanted to check whether I was > doing something wrong or what. There is no evidence in your email that the client is required to send a certificate. TO REPORT A

Re: lmtp: transport unavailable

Wietse Venema: > Arian Sanusi: > > /var/log/mail.log: > > > Jan 20 11:31:40 chichak postfix/error[31253]: 6716E6A79: > > > to=, orig_to=, relay=none, > > > delay=0.42, delays=0.37/0/0/0.04, dsn=4.3.0, status=deferred (mail > > > transport unavailable)