similar to: dovecot transport with postfix and recipient restrictions.

On 4/28/2015 1:40 PM, Tobias Franz?n <lists.zxinn at otaking.se> wrote: > On 2014-01-08 14:32, Charles Marcus wrote: >> On 2012-04-09 8:53 AM, Timo Sirainen <tss at iki.fi> wrote: >>> On 9.4.2012, at 15.50, Charles Marcus wrote: >>>>> LMTP adds a new Delivered-To:<rcpt-to at address> header when there is >>>>> a single RCPT TO. You

I'm resurrecting this again because I'm getting pretty close to possibly being ready to install a brand new dovecot server (finally), but I still need for dovecots LMTP to add the x-original-to header. So... was this completed quietly, or is support for it still not there? Thanks, Charles On Tue Apr 28 2015 15:27:07 GMT-0400 (Eastern Standard Time), Charles Marcus <CMarcus at

On 2014-01-08 14:32, Charles Marcus wrote: > On 2012-04-09 8:53 AM, Timo Sirainen <tss at iki.fi> wrote: >> On 9.4.2012, at 15.50, Charles Marcus wrote: >>>> LMTP adds a new Delivered-To:<rcpt-to at address> header when there is >>>> a single RCPT TO. You can force a single RCPT TO from Postfix side by >>>> setting

hi to all, im using my box as mail server (CENTOS 4.4) with postfix 2.3.4 when i try to send message i got this message in my mail log any idea with my problem, thank you very much in advanced,hope you can help me. Dec 11 18:35:33 support postfix/lmtp[3341]: CCB9B40698: to=<personal at xxx.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.95, delays=0.13/0.03/0.01/0.78, dsn=2.6.0,

Hello, I have a freshly setup postfix/dovecot mail server (after a server upgrade I decided to change my sendmail/popper conf to something more modern :) It mostly works, there is no problem in sending/receiving mails in local network, both using text clients like mutt or pine dealing with the incoming/outcoming mail directly. Also dovecot works fine with SSL authentication from the outside

Hi, according to the both discussions in the last few days I've tried to find a solution for Postfix with a PostgreSQL back-end. Its working nice for regular recipient addresses like user at example.com and addresses with an extension like user+foo at example.com. Alias addresses are currently ignored. * An alias may expand into multiple destinations. If one of this destinations is

On 2019-05-22 08:18, Tuomo Soini via dovecot wrote: > On Tue, 21 May 2019 18:24:46 +0000 > MRob via dovecot <dovecot at dovecot.org> wrote: > >> Many people prefer to use LMTP for delivery from postfix for better >> efficiency but X-Original-to header support still missing after many >> years. One affect of this is need to set >>

Hi, I'm hoping that someone might be able to help, as I've been going in circles with trying to get the right configuration done here. I'm also not sure whether this is more of a Dovecot or DSpam question, so I'm posting the same to both mailing lists. My goal is to have a mail setup that is as follows: [Incoming email] --> [Postfix] --> [Amavis] --> [DSpam] -->

I search from google on how to restrict user from sending mail and I did trial and errors for three days already but to no success. What I want to do is to restrict some user in sending mail while some unrestricted user will send mail to internet and intranet. I am able to restrict outside address (i.e. gmail, yahoo) to not send mail on restricted users but the vice versa I can not do. Is there

Hidy-ho, I'm having a difficult time getting catch-all working when using Dovecot LMTP. I would like *@example.com (everything) to go to virtual at example.com, where virtual is a valid virtual user. It seems that things are getting as far as LMTP, but then the mail gets bounced. To wit: Aug 21 08:02:50 hostname postfix/lmtp[4914]: 8DF8E9AFE6: to=<test at example.com>,

Hi list, I have noted over the last week or so my DNS servers are dumping lots of messages for bogus domain lookups. Examining the postfix queue with postqueue -p: I see many (Host or domain name not found. Name service error for name=bdgiedjhea.po6e4ina.com type=MX: Host not found, try again) Jake at bdgiedjhea.po6e4ina.com My question - why does this

Hi list, I have been getting the following types of log messages Jan 30 08:22:33 ndgonline postfix/smtpd[30538]: NOQUEUE: reject: RCPT from unknown[71.46.229.50]: 450 4.7.1 Client host rejected: cannot find your hostname, [71.46.229.50]; from=<DWoodman at orangebankfl.com> to=<rkampen at ndgonline.net> proto=ESMTP helo=<mail.floridianbank.com> a rdns check shows all is well

On Tue, 21 May 2019 18:24:46 +0000 MRob via dovecot <dovecot at dovecot.org> wrote: > Many people prefer to use LMTP for delivery from postfix for better > efficiency but X-Original-to header support still missing after many > years. One affect of this is need to set > sieve_vacation_dont_check_recipient = yes which violate Sieve > standard and cause auto-replyies sent to

Hi, I'm currently fine-tuning my mail server (Postfix and Dovecot on CentOS 7). SPF, DKIM and DMARC work fine, now I'd like to limit the spam tsunami. Besides the official Postfix documentation, I've read a few articles about Postfix spam restrictions, namely these : https://www.linuxbabe.com/mail-server/block-email-spam-postfix https://wiki.centos.org/HowTos/postfix_restrictions

Hallo Waffenmeister! Ralf Hildebrandt <Ralf.Hildebrandt at charite.de> wrote: > > Apr 7 14:07:52 delta postfix/qmgr[19078]: 1D8921B31260: from=<anmeyer at anup.de>, size=1492149, nrcpt=1 (queue active) > > Apr 7 14:07:53 delta postfix/pipe[19091]: 1D8921B31260: to=<miles at anup.de>, relay=dovecot, delay=2542, delays=2542/0.01/0/0.29, dsn=4.3.0, status=deferred

Hi, I run a mail server on debian squeeze system , i installed the following software postfix dovecot spamassassin postgrey I configured a virtual domain and virtual mailbox but postfix don't pipe mail in dovecot. In log, it's appear that the relay mode is local and the delivery message is delivered to mailbox) Jun 7 15:23:01 ns230370 postfix/smtpd[27501]: 66BBA4D40F0:

Hi all, I?ve got postfix setup to use dovecot-lmtp for (virtual) user delivery, and things to users or aliases that Dovecot knows about now get delivered correctly. However, I?ve done something wrong with postfix and/or the LMTP configuration because upon RCPT TO, instead of forwarding the mail off to the configured smartest, somehow dovecot-lmtp is ending up in the mix. (Perhaps this is more a

Hi, I'm running our local school's mail server on CentOS 7, Postfix and Dovecot. We get quite a lot of spam, so I have the following sender restrictions in my /etc/postfix/main.cf: --8<------------------------------------------------------ # Restrictions SMTP smtpd_helo_restrictions = reject_unknown_helo_hostname smtpd_sender_restrictions = reject_unknown_sender_domain,

Hi all. Intro: Timo has already done great job providing patch which allows postfix to authenticate directly against dovecot (included in latest postfix sorce code/release). Now I'm looking around for one more thing. I want to use dovecot's user db as source for postfix lookup tables. In particular: virtual_mailbox_maps Main reason is - postfix access rules and fighting against spam.

Hello, I'm using Postfix with virtual domains (MySQL), Dovecot 1.0beta7 and CVS LDA. I've set up postfix to use the LDA for maildir delivery and defined a global sieve script. -- master.cf -- ... dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -d ${recipient} ... -- main.cf -- smtpd_banner =