Hi,
I need a clarification, can i know any way to take all outgoing
mail copy to backup mail id for a domain. We are already using "Taps"
method to take a copy of all mails. But this taking both outgoing and
incoming mails. But currently we are in need of taking outgoing mails
alone in separa
What's the current thinking on qmail-dk?
I've been debugging a case where some emails that I was expecting didn't
arrive, and I eventually traced it to:
@4000533200332362fb9c qmail-smtpd: qq hard reject (qmail-dk: Cannot
sign message due to invalid message syntax. (#5.3.0)):
MAILFR
I believe current thinking is to not use it. I turned it off long ago. I
am sure Eric or others that are better suited will reply soon.
From: Angus McIntyre [mailto:an...@pobox.com]
Sent: Wednesday, March 26, 2014 9:41 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: [qmailtoaster] qmail-d
It shouldn't really matter.
The man page says:
imapsync [options]
So you should be able to add
--sep1 .
or
--sep1 /
at the end of your command. Be sure to include the separation character.
Note that it's sep-ONE, not sep-EL.
There's also a --sep2 option.
On 03/25/2014 09:26 PM, Linux wrote:
E
1) install spamdyke if you haven't already.
# qtp-install-spamdyke
2) sanesecurity catches most of this kind of stuff (phishing attempts).
# qtp-install-sanesecurity
Sanesecurity is a set of rules that augments clamav.
On 03/26/2014 01:49 AM, Linux wrote:
Hi,
I am receiving such type of mails o
On 03/26/2014 05:55 AM, rajeshrudramani wrote:
Hi,
I need a clarification, can i know any way to take all outgoing
mail copy to backup mail id for a domain. We are already using "Taps"
method to take a copy of all mails. But this taking both outgoing and
incoming mails. But currently we ar
Yeah, the qmail-dk patch has occasional trouble figuring out whether to
sign or check a message, and in some cases tries to sign an incoming
message (or so it appears). That's definitely a bug. I've observed it
happening only on messages coming from another QMT host, oddly enough,
but it doesn'
Hi,
On Tue, Mar 25, 2014 at 2:27 AM, Eric Shubert wrote:
> It came to my attention recently that the ciphers used by the stock QMT
> aren't as secure as they might be. In fact, QMT was simply using all
> available ciphers in no particular priority.
>
> The general intention of QMT is to be as se
On 03/26/2014 12:46 PM, Peter Peltonen wrote:
One question: does qmail need to be restarted after issuing the openssl
command?
I don't expect restarting is enough. I would do a stop/start. The
restart command only effects qmail-smtpd on port 25, and doesn't restart
submissions or outbounds. W
