similar to: ..::MBOX ISSUE::..

On 24.02.2015 20:40, Reindl Harald wrote: > > > Am 24.02.2015 um 19:37 schrieb Adrian Minta: >> On 24.02.2015 20:29, Reindl Harald wrote: >>> >>> don't allow senders which you would not receive mail for - period >>> >> Seems interesting, at least until the bots adapt to this. >> Any idea how could this be implemented? > > with the

Am 24.02.2015 um 18:28 schrieb Luciano Mannucci: > for the virus doesn't necessarily use the e-mail of the > user as its from, just the user and password for the > authentication phase so you allow random envelope senders on your servers? why? smtpd_recipient_restrictions = permit_mynetworks reject_non_fqdn_recipient reject_non_fqdn_sender reject_unlisted_sender

Hi, I have a problem with my postfix/dovecot configuration, I can't receive mail from outside, i can send a mail from my mail to myself and others, but i can only receive one i send from myself, but when it comes from outside my domains, it dosn't work. Thaks for your help ! Here is my conf : ----------------------------------------------------------------- DOVECOT

I just discovered that, ever since I updated this computer to kernel-2.6.32-431.3.1, it hasn't been forwarding outbound email. I found this repeated in /var/log/maillog: "warning: relayhost configuration problem" This computer is set up to relay outbound email via postfix to another computer on my network by name, whose name and IP address is specified in the /etc/hosts file. A

Hi, Problem: Sockets /var/spool/postfix/private/auth and /var/spool/postfix/private/dovecot-lmtp are not created The only error message I get comes from postfix: no auth (SASL) founhd. Takes np wonder, the s ockets don't exist. Any help is welcome. Thanks. Bernd doveconf: # 2.1.17: /etc/dovecot/dovecot.conf # OS: Linux 3.11.10-11-default x86_64 openSUSE 13.1 (x86_64) ext4

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

I have a postfix mail server with sql authentication and I want to implement sieve on it. Sieve is working relative good, rules who contain 'fileinto' are executed perfectly. The problem is the redirect to other servers. I configured a rule in Sieve to redirect any email containing "redirect" in subject to a specified foreign destination. # So practically a email coming from

Hello! I've been trying to configure Dovecot to work as LDA for file-based virtual users with Postfix. Some part in the configuration seems to miss though, as mails are received by Postfix, but instead of giving it to Dovecot for delivery, it delivers the mails itself. Postfix drops the mail in /var/mail/<user>/mbox, if Dovecot would be called, it should deliver it to

Hi, I am struggling with Postfix/SASL/Dovecot-IMAP setup with ~/Maildir/ setup. Receiving the mail works fine, but viewing the mail(+listing) is failing. The setup I use is simple unix users from etc/passwd, (pam thru SASL) as I only host for a few people. The ~/Maildir folder has the ownership of the user, not mail or vmail, as I would have expected from the master.cf from Postfix, the

On 04/27/2016 12:41 AM, Alice Wonder wrote: > On 04/27/2016 12:30 AM, James Hogarth wrote: > *snip* >> >> Unless you have a very specific requirement for a very bleeding edge >> feature it's fundamentally a terrible idea to move away from the >> distribution packages in something as exposed as a webserver ... > > I use to believe that. > > However I no

hey friends, I am trying to make postfix run with tls in chroot mode, but I am not able to send the messages with tls on. I am using postfix 2.2.10 on centos 4.0 and I had compiled the postfix from sources with tls & cyrus-sasl support. I copied the certificates from /usr/share/ssl to /etc/postfix. Below are the errors I am getting: May 25 13:27:51 test1 postfix/smtpd[4095]: warning: TLS

All, Thank you for having this list, and I have a question regarding why postfix is not handing off delivery to Dovecot to virtual users. Here is all I can offer since I am not at my server: *Here is the debug information for my postfix setup:* [code] Mar 13 20:23:55 andromeda postfix/smtpd[15316]: name_mask: ipv4 Mar 13 20:23:55 andromeda postfix/smtpd[15316]: inet_addr_local: configured 2

On 04/27/2016 07:50 PM, Alice Wonder wrote: > On 04/27/2016 12:41 AM, Alice Wonder wrote: >> On 04/27/2016 12:30 AM, James Hogarth wrote: >> *snip* >>> >>> Unless you have a very specific requirement for a very bleeding edge >>> feature it's fundamentally a terrible idea to move away from the >>> distribution packages in something as exposed

new Dovecot 2.0.8 installation on Opensuse 11.3 I got the error "lmtp (xxx at mydomain.yy): Error: user xxx at mydomain.yy: Initialization failed: Namespace '': mbox: mbox requires client_limit=1 for service" while trying to transfer mails by lmtp from postfix to dovecot. I googled and looked on the dovecot wiki about this client_limit issue, but no success. What's the syntax

Migrating from UW IMAP/Qpopper mbox to Dovecot mbox. I have ~500 users, some with HUGE mbox (500MB-1GB), is there a script to create the Dovecot indexes at night to help speed up the migration process. Any idea. Thanks Bertrand Leboeuf leboeuf at emt.inrs.ca

Hi We have an mailserver running RedHat Linux 9.0 with UW-IMAP (imap-2001a- 18.progeny.1.src.rpm), we have user mailboxes in /var/spool/mail/username using the default mbox storage method. Some users have home directories and some dont. They only connect through the POP3 server, not IMAP. We are now migrating both hardware and software to an new server running RHEL 4, i have copied all

Hi, replying to my own issue: The dsync crash seems to be triggered when there are emails to copy in both directions, and it's fairly clear from comments in the code that it should be releasing a read lock before trying to grab a write lock. A work-around for the crash was doing a one-way sync manually. This allowed the process to complete and my setup is now replicating properly. I guess

http://dovecot.org/patches/mbox-snarf-plugin.c Also committed to CVS HEAD. Usage: mail_location = mbox:~/mail:INBOX=/var/mail/%u protocol imap { mail_plugins = mbox_snarf } protocol pop3 { mail_plugins = mbox_snarf } plugin { mbox_snarf = ~/mbox } If ~/mbox doesn't exist, nothing special is done. If ~/mbox exists, it's treated as INBOX and mails are moved from /var/mail/%u

On 24.02.2015 20:29, Reindl Harald wrote: > > > don't allow senders which you would not receive mail for - period > Seems interesting, at least until the bots adapt to this. Any idea how could this be implemented ? -- Best regards, Adrian Minta

I 'm using potfix-dovcote as an internal mail server(local.myco.com) and wan to run another potfix-dovcote as an external mail server (myco.com) on Internet.75% of my users should only work internally(no external mail) but the rest of users (25%)should be able to send mail to external network! These users have the same username on myco.com. I use smtp_generic_maps to map int username of these