similar to: Looking for a guide to collect all e-mail from the ISP mail server

> Have a look at Mailcow too, it comes with almost everything. > I?ve been running it for a year now, after many years of usin > a self-assembled stack, and it?s a bliss. Thanks for the hint. I initially discarded Mailcow because of this: "mailcow: dockerized comes with multiple containers" The installation instructions mention that Docker Compose is required. Not long ago I

Why don't you configure all stuff internally and ask your provider to relay the e-mails from and to you via "smart relay"?? You will communicate only via smtp and only with your provider, and you can use a nice open-source bundle ( dovecot is mandatory because you wrote on that list :) ) in your LAN. > > > > > > > > > > ? Original Message >

Hi all: I am evaluating mail server solutions for a small business. The trouble is, I am only a part-time admin and a newbie to mail servers. Most guides I have seen are rather unrealistic: they encourage you to expose your e-mail server to the Internet, and hope that you have the resources to keep it patched up. I would rather have an internal mail server that collects e-mails from a standard

> 2. install and configure OfflineIMAP to synchronize the IMAP folders between your ISP IMAP server and your Dovecot server; see for example > http://www.offlineimap.org/doc/quick_start.html OfflineIMAP is not the way to go. Many ISPs have very low size limits for the mailbox sizes. The one I am looking at right now does have this problem (unless you pay extra). From what I have

26. 10. 2020 v 12:15, R. Diez <rdiezmail-2006 at yahoo.de>: > > I would be happy to take a pre-packaged mail server solution like iRedMail which includes RoundCube or whatever. Have a look at Mailcow too, it comes with almost everything. I?ve been running it for a year now, after many years of using a self-assembled stack, and it?s a bliss. I have it coupled with Amazon SES for some

The reason there's no pretty complete how-to is because what you're doing seems completely insane to the vast majority of people who'd look at your problem and select your way of approaching solving it. Yeah, you can also host your own website off of a DSL line, using a rasp-pi connected via a ham data relay which is faxing pages back and forth over a couple of soup-cans and string -

> Your goal does not sound weird. OK, thanks for the confirmation. > The most painless way might be to fetch incoming messages from > the ISP's IMAP and deliver them to your local dovecot. > A shortened fetchmailrc would read: > > poll remote.server ? > ? user ?, password ? > ? folder 'INBOX' > ? fetchall > ? idle > ? ssl > mda

Maybe get something like Zimbra, such solutions also have support that you can buy when you need it or don't have time (I guess). -----Original Message----- From: R. Diez [mailto:rdiezmail-2006 at yahoo.de] Sent: Sunday, October 25, 2020 6:57 PM To: dovecot at dovecot.org Subject: Looking for a guide to collect all e-mail from the ISP mail server Hi all: I am evaluating mail server

You need SPF and DKIM for your outgoing email to be accepted. My idea of a secure email server is to use submission port 587. Expose port 25 to the world and aggressively filter all remaining email ports with a firewall. And I mean aggressive. Geographically filter so only countries where youe users reside can send and retrieve email. Block major hosting IP space. How many users will be on the

Am 25.10.20 um 21:01 schrieb Marc Roos: > > Maybe get something like Zimbra, such solutions also have support that > you can buy when you need it or don't have time (I guess). > > > > -----Original Message----- > From: R. Diez [mailto:rdiezmail-2006 at yahoo.de] > Sent: Sunday, October 25, 2020 6:57 PM > To: dovecot at dovecot.org > Subject: Looking for a

> You need SPF and DKIM for your outgoing email to be accepted. > [...] I don't understand why that is the case (but keep in mind that I am a newbie). Is it not possible to set up some internal SMTP server that only relies the e-mails to the external ISP SMTP server? The internal SMTP server would then act like a normal user's Thunderbird. At first I tought that the internal

> There are plenty of guides available. I don't know your mother tongue, > but seeing your last name, I assume you may be speaking German. Take a > look at these German language guides: I do speak German, thanks for the links. > https://www.it-management-kirchberger.at/manuals-tutorials/server-centos-7/postfix-mailserver-vimbadmin/postfix-amavisd-new-clamav-spamassassin.html I

>> I would not advice any company that is continuously being fined for breaking the law. > This is not only an overstatement, it is completely irrelevant.? Given the OP problem > statement (small business, part-time admin, newbie to mail > servers), I do not think there is a better solution > A small server already costs 20 USD / month, running a mail server consumes a

> Why don't you configure all stuff internally and ask your provider to relay > the e-mails from and to you via "smart relay"?? You will communicate only > via smtp and only with your provider, > [...] When you are a small business or a volunteer-run club or charity, you don't ask your provider. You have no leverage. You may not even be able to change provider so

>> Besides, the way you suggest means opening a SMTP port to the outside > world. A security risk and more work at the firewall etc. > > You can just allow some ip addresses of your provider to connect, not? > Nothing outside world. Yes, you all want me to open ports. I'm sorry guys, but I won't budge: 1) Opening a port means reconfiguring the firewall. You may find

Hello R, Your goal does not sound weird. The most painless way might be to fetch incoming messages from the ISP's IMAP and deliver them to your local dovecot. A shortened fetchmailrc would read: poll remote.server ? user ?, password ? folder 'INBOX' fetchall idle ssl mda "HOME=%T /usr/bin/sudo -u %T /usr/lib/dovecot/deliver" That way your users can create

> Start of a HOWTO: > > 1) Install dovecot, create virtual accounts for all of your users > 2) Install fetchmail, make it pull the ISPs IMAP and deliver locally > 3) Install postfix as a smart relay and deliver locally to locals > > Feel free to fill in the details ;) And I thought you guys had nothing else to do, sitting here on the mailing list and pretending to have some

[...] > I could not find anything there related to multidrop or "catch all" mailboxes. [...] > Nothing like that there either. [...] > This is a huge document with little introduction. It seems to be > mostly about fighting spam. I did not find anything like the setup I described. looks like the collective wisdom of this group can't provide precisely what you are looking

>>> That way your users can create their vacancies with the ISP portal, >> But then internal e-mails need to go out to the ISP, >> don't they? Because, if internal e-mails get delivered locally, the >> vacation autoresponses on the ISP will not trigger, will they? > Hello R, I only wrote about the incoming side - of course, you also want to > send mail to