However as far as I can determine from my forward test is that, the from
header is currently from the original message and not from the
forwarder.
-Original Message-
From: Scott Q. [mailto:qm...@top-consulting.net]
Sent: Sunday, October 25, 2020 5:01 PM
To: Marc Roos; dovecot
He of course meant the From: MIME sender. This can fail in a SPF check if
identity aligment is set to strict.
Rewriting the From: heasder is one way to solve it, another way which preserves
the original message in full, is to encapsulate the original message ina new
message/rfc822 container
I've got a basic dovecot master-master replication setup between two
servers (imap1 and imap2). Actions such as deleting messages or moving
them between folders are replicated correctly and quickly.
However, when new mail is delivered by postfix, replication does not
occur until something
Hello all,
I'm getting a very often panic on my local dovecot setup when accessing
some of the local folders.
Error message is always
Oct 25 14:34:50 imap(irusskikh): Panic: file mbox-sync.c: line 665
(mbox_sync_handle_header): assertion failed: (mail_ctx->mail.from_offset +
move_diff != 1 &&
Say someone has setup spf for his domain and sends an email to a user
that has in roundcube enabled the sieve forward. If the message is
forwarded without altering the message headers, this could result in a
message being blocked or not relayed, because sending hosts ip, is not
in the spf of
Am 25.10.20 um 16:48 schrieb Marc Roos:
Say someone has setup spf for his domain and sends an email to a user
that has in roundcube enabled the sieve forward. If the message is
forwarded without altering the message headers, this could result in a
message being blocked or not relayed, because
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
Citeren "Trever L. Adams" :
With a recent update, I started seeing this:
doveconf: Fatal: Error in configuration file
/etc/dovecot/conf.d/10-ssl.conf line 14: ssl_cert: Can't open file
/etc/letsencrypt/live/SERVER/fullchain.pem: Permission denied
1 4 * * * vmail /usr/bin/doveadm
There's no ambiguity here, if you send a message, you are the
sender. The envelope from should be yours.
On Sunday, 25/10/2020 at 11:48 Marc Roos wrote:
Say someone has setup spf for his domain and sends an email to a user
that has in roundcube enabled the sieve forward. If the message is
Marc Roos skrev den 2020-10-25 16:48:
Say someone has setup spf for his domain and sends an email to a user
that has in roundcube enabled the sieve forward.
roundcube does change envelope from on forwarding emails, if thats not
the case i like to see logs proving it does not
sorry if it
Yes, putting the From: into Reply-To: is a good idea to ensure the reply
button in receiver´s client doesn't break.
But remember to ONLY do it when Reply-To: is not present.
To avoid removing important information from the email, like the original
sender, it can be good to always add a header
>>"Never use a browser for email."
I don't agree.
In fact, using a browser for email or atleast initial setup, is actually more
secure. This because SMTP/IMAP clients normally don't support 2FA, so you would
have to "hack" a solution to enable 2FA for email.
This can be made in 2 ways:
>> why not just point them at a hosting service like google apps, and let
google keep things up to date?
Costs money, and also the problem is that gmail imposes heavy spam filters
and "reputation blocks" meaning smaller providers with low email volumes,
are put in the spam folder, even if they
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'
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
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
At 25 October, 2020 R. Diez wrote:
>
> I am too afraid, I would not expose any such port on the Internet. Who knows
> if the mail server stays months without an update. If I am to recommend or
> implement any such mail server solution to a small business, I would insist
> that the e-mail server
Hello R,
reply inline below:
Am 25.10.20 um 23:12 schrieb R. Diez:
That way your users can create their vacancies with the ISP portal,
> [...]
That's a good idea. But then internal e-mails need to go out to the ISP,
don't they? Because, if internal e-mails get delivered locally, the
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-2...@yahoo.de]
Sent: Sunday, October 25, 2020 6:57 PM
To: dovecot@dovecot.org
Subject: Looking for a
You look spammy if you don't have SPF or DKIM, and hopefully both. Your email
will either be bounced or sent to a spam folder. You need a reverse pointer as
well, but that shouldn't be an issue. The situation is actually worse than it
sounds. ATT/SBC needs to whitelist you by IP if you are
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
21 matches
Mail list logo
