Re: [qmailtoaster] How to debug 'qq soft reject'?

ve changed the ran on the run shall see. This only happens after I convert from Eric original Clamv to the new rpm. Remo On Jul 23, 2020, at 12:40 AM, Andrew Swartz wrote: I had this problem about 8 months ago. It it was extremely difficult to troubleshoot, but I eventually figu

Re: [qmailtoaster] How to debug 'qq soft reject'?

I had this problem about 8 months ago. It it was extremely difficult to troubleshoot, but I eventually figured it out. It is a problem which has been around for a decade or more. The clamav deamon signature file, which is updated frequently, continuously grows as the amount of malware it

Re: [qmailtoaster] letsencrypt certificate issue

I meant "spamdyke" rather than "spamassassin". -Andy On 4/29/2020 7:10 AM, Andrew Swartz wrote: Letsencrypt certificates are fine for email servers, I've been using them for several years. I initially had this same problem. Spamassassin/qmail starts a new instanc

Re: [qmailtoaster] letsencrypt certificate issue

Letsencrypt certificates are fine for email servers, I've been using them for several years. I initially had this same problem. Spamassassin/qmail starts a new instance with each new SMTP connection, so when a new cert is saved it starts getting used on the next SMTP connection. However,

Re: [qmailtoaster] ssl problem

Also remember that SSLv3 refers to two different things: 1. The SSLv3 protocol 2. The SSLv3 ciphers (known as the ciphersuite). In the s_client output below, it uses the SSLv3 protocol to negotiate NO cipher (i.e. the "Cipher is (NONE)" part). It establishes a plaintext session using the

Re: [qmailtoaster] SMTPS Port - Who is Failing ?

If the problem is arising during the TLS negotiation, then there will never be an SMTP session started and therefore there will never be an attempt to even submit a password. I do not think that a TLS negotiation problem will show up in any mail-related log file. I've yet to find it in any

Re: [qmailtoaster] SMTPS Port - Who is Failing ?

rt_handshake_failure;_connected_to_103.27.32.20./ What would it look like in my logs if they where to have the reverse issue David Bray 0418 745334 2 ∞ & < On Tue, 21 Apr 2020 at 02:54, Andrew Swartz <mailto:awswa...@acsalaska.net>> wrote: Port 465 should be SMTP o

Re: [qmailtoaster] SMTPS Port - Who is Failing ?

;_connected_to_103.27.32.20./ What would it look like in my logs if they where to have the reverse issue David Bray 0418 745334 2 ∞ & < On Tue, 21 Apr 2020 at 02:54, Andrew Swartz <mailto:awswa...@acsalaska.net>> wrote: Port 465 should be SMTP over SSL/TLS.  Therefore the sequen

Re: [qmailtoaster] SMTPS Port - Who is Failing ?

Port 465 should be SMTP over SSL/TLS. Therefore the sequence of events is: 1. Establish TCP connection 2. Negotiate SSL/TLS session 3. Begin SMTP session Of these, the SSL/TLS negotiation is by far the most CPU-intensive. Consider trying to see what is happening with the SSL/TLS

Re: [qmailtoaster] Slow connection and transaction times

Are you using Spamdyke?  If so, depending upon configuration, it does several DNS queries prior to passing the connection to qmail-smtpd. On mine, it does reverse DNS lookup, checks several DNS blacklists, etc.  That could easily account for the delayed smtp response. You could test this by

Re: [qmailtoaster] spam folder into gmail

Your email does not contain a DKIM signature. The ARC* headers are signatures added by gmail after receipt. If you had a DKIM signature, it would be below this part of the header chain: Received: frommail.pan-asia.in ([49.128.33.86]) bymx.google.com

Re: [qmailtoaster] SSL Problem Dovecot

ussion. Overall, I'm glad people are interested in this. -Andy On 9/3/2019 9:46 PM, Andrew Swartz wrote: Some background: During the TLS negotiation, the client gives the server a list of ciphers which it supports, then from that list the server chooses which one to use. The server's ciphe

Re: [qmailtoaster] SSL Problem Dovecot

eed to watch logs to see if I have problems. I'm guessing problems would show up in both the dovecot.log and the /var/log/qmail/smtp or /var/log/qmail/send logs. Thanks, Gary On 9/4/2019 1:46 AM, Andrew Swartz wrote: Some background: During the TLS negotiation, the client gives the server a

Re: [qmailtoaster] SSL Problem Dovecot

I just fact-checked my statement about enclosing the list in single-quotes.  The man page for openssl ciphers specifies only a colon-separated list.  The enclosing in single quotes may just be community habit rather than an actual requirement. -Andy On 9/4/2019 5:04 AM, Andrew Swartz wrote

Re: [qmailtoaster] SSL Problem Dovecot

ed to watch logs to see if I have problems. I'm guessing problems would show up in both the dovecot.log and the /var/log/qmail/smtp or /var/log/qmail/send logs. Yes. Thanks, Gary -Andy On 9/4/2019 1:46 AM, Andrew Swartz wrote: Some background: During the TLS negotiation, the client

Re: [qmailtoaster] SSL Problem Dovecot

Some background: During the TLS negotiation, the client gives the server a list of ciphers which it supports, then from that list the server chooses which one to use. The server's cipher list is a list, in order of preference, of the ciphers it will use (from the client's list). If there

Re: [qmailtoaster] Emails to Spam folder

in_creation": 5524, "suspicious_tld": false, "spam": false, "free_provider": false, "disposable": false, "deliverable": true, "accept_all": false, "valid_mx"

Re: [qmailtoaster] Emails to Spam folder

le": true, "accept_all": false, "valid_mx": true, "spoofable": true, "spf_strict": true, "dmarc_enforced": false, "profiles": [] } } Appreciate of

Re: [qmailtoaster] Emails to Spam folder

This seems an issue mostly with server "suspiciousness", of which reputation is a component. Of the factors effecting suspiciousness, only two are local to the smtp server: 1. DKIM signatures 2. TLS certificates To address these, confirm that both are working properly: 1. DKIM: send an

Re: [qmailtoaster] Authentication issues with Squirrelmail and RoundCube

Angus, That is an intriguing error. SNI adoption has been very slow for email. Dovecot supports it for POP3/IMAP clients. Opensmtpd may be the only SMTP server which supports it. The workaround SMTP behavior has been to look up the MX record of the "To:" domain, and then connect to THAT

Re: [qmailtoaster] vpopmail in the latest toaster

I built a Centos 7 toaster last year (upgrading from Centos 5). vpopmail is unchanged and still uses a file system structure for mail storage. Therefore the vpopmail management commands are unchanged. As I recall, the major headache was migrating the login credentials. And once migrated, a

Re: [qmailtoaster] Development version

encryption is inside an encrypted tunnel. IMHO opinion it's really quite useless. On 1/27/2019 8:16 PM, Andrew Swartz wrote: Ahhh... that's right. But then the next question is should one use cram-md5?  I believe it is currently considered insecure. I just found this link which explains the qmail

Re: [qmailtoaster] Development version

; Enforcing SMTP Auth of type "LOGIN", "PLAIN", or "CRAM-MD5" "-" Disabling SMTP Auth (for a particular connection) The complete patch info is listed here : https://www.fehcom.de/qmail/smtpauth.html Regards -P On 1/26/19 8:06 PM, Andrew Swartz w

Re: [qmailtoaster] Development version

I would add the caveat that STARTTLS is only "probably safe". Unfortunately, it suffers from a critical error in the very concept of going from an plaintext session to a TLS session, resulting in an unfixable (as far as I know) vulnerability. A man-in-the-middle can inject text into the

Re: [qmailtoaster] my qmailtoaster queue full, send a lot of spam

Sounds suspicious for malware. Check the logs (var/log/qmail/smtp/cur and the similar one for the submission port) to see if email is coming from outside the system. If it is not from outside the system, then I would go looking for some sort of rogue running process (likely malware) which is

Re: [qmailtoaster] Fwd: Re: vpopmail

sql logging = OFF --disable-sql-logging (default) >>> mysql limits = OFF --disable-mysql-limits (default) >>> MySQL valias = ON --enable-valias >>> auth inc = -I/usr/include/mysql >>> auth lib = -L/usr/lib64/mys

Re: [qmailtoaster] Fwd: Re: vpopmail

Eric, What configuration options do you use when compiling vpopmail? -Andy On 10/4/2018 9:17 AM, Andrew Swartz wrote: > Yet I believe we have solved this problem: > > Remote IMAP/POP3 authentication should be done via STARTTLS or TLS. > Therefore CRAM-MD5 is not necessary and PL

Re: [qmailtoaster] Fwd: Re: vpopmail

that someone can configure if they desire an especially insecure configuration. -Andy On 10/4/2018 8:00 AM, Remo Mattei wrote: > +1 > > When I read it.. > >> On Oct 4, 2018, at 08:10, Andrew Swartz wrote: >> >> I have ABSOLUTELY NO IDEA what that is supposed to mean

Re: [qmailtoaster] Fwd: Re: vpopmail

I have ABSOLUTELY NO IDEA what that is supposed to mean. -Andy On 10/4/2018 3:56 AM, Eric Broch wrote: > Here's the answer I got from the Dovecot mailing list concerning the > question of clear text password authentication...not sure how to > implement...ideas? : > > On 03.10.2018 23:30, Eric

Re: Fwd: [qmailtoaster] dovecot

ail setup, hope you get it working > > -Eric > > > On 10/3/2018 9:18 PM, Andrew Swartz wrote: >> And I'll add that at the end, with pw_clear_passwd set to null, login >> succeeds via IMAP but fails via Squirrelmail. >> >> -Andy >> >> >> >>

Re: Fwd: [qmailtoaster] dovecot

cot'; > $imap_auth_mech = 'login'; > > worked for my squirrelmail setup, hope you get it working > > -Eric > > > On 10/3/2018 9:18 PM, Andrew Swartz wrote: >> And I'll add that at the end, with pw_clear_passwd set to null, login >> succeeds via IMAP but fa

Re: [qmailtoaster] dovecot

.tld --auth-password $userpassword > > > On 10/3/2018 7:45 PM, Andrew Swartz wrote: >> Eric, >> >> On Centos7 QMT: >> >> I just created a new user account and set the password to '0123456789'. >> Then I used your SQL command to set pw_clear_passwd to null.

Fwd: [qmailtoaster] dovecot

And I'll add that at the end, with pw_clear_passwd set to null, login succeeds via IMAP but fails via Squirrelmail. -Andy Forwarded Message Subject: Re: [qmailtoaster] dovecot Date: Wed, 3 Oct 2018 19:12:11 -0800 From: Andrew Swartz To: qmailtoaster-list@qmailtoaster.com

Re: [qmailtoaster] dovecot

Eric, On Centos7 QMT: I just created a new user account and set the password to '0123456789'. Then I used your SQL command to set pw_clear_passwd to null. Then I viewed the table to confirm it was empty (it was). Then I tried to log in to Squirrelmail using password '0123456789': Login failed.

Re: [qmailtoaster] Passwords after backup/restore

Eric, I am missing something: what is the utility of keeping the plaintext passwords for any of the accounts if QMT is 100% functional without them? I cringe when I use WebMin to click to view the vpopmail database and literally scroll through cleartext passwords. -Andy On 10/3/2018 2:36

Re: [qmailtoaster] Passwords after backup/restore

Dan, Good explanations of how the crypted password contains the hash specification and the salt. Thank you. I looked through the dovecot documentation, and they describe the $1$ through $6$ just as you did. Therefore this seems a generally accepted password storage format. However, I just

Re: [qmailtoaster] Passwords after backup/restore

t; > > On 10/3/2018 12:10 AM, Andrew Swartz wrote: >> Eric, >> >> Excellent test with very useful results! >> >> Modern security practice would indicate elimination of the cleartext >> passwords.  How difficult would it be compile vpopmail without cleartext

Re: [qmailtoaster] Passwords after backup/restore

he clear text password to null: >> mysql> update mydomain_tld set pw_clear_passwd='' where pw_name ='user'; >> >> Then Dovecot authenticated fine against the 17 character >> password...now encrypted to 40 chars. >> >> >> On 10/2/2018 11:09 PM, Andrew

Re: [qmailtoaster] Passwords after backup/restore

> Dovecot mailing list. >> >> >> On 10/2/2018 10:22 PM, Eric Broch wrote: >>> Okay, >>> >>> 17 character password works with Submission port. Not with IMAP which >>> is authenticated through Dovecot. >>> >>> Eric >&g

Re: [qmailtoaster] Passwords after backup/restore

10/2/2018 10:22 PM, Eric Broch wrote: >>> Okay, >>> >>> 17 character password works with Submission port. Not with IMAP which >>> is authenticated through Dovecot. >>> >>> Eric >>> >>> >>> On 10/2/2018 9:21 PM, Andrew Swartz

Re: [qmailtoaster] Passwords after backup/restore

is the problem. I hope that Dovecot is not directly accessing the database (i.e. bypassing vpopmail) and authenticating with the cleartext (truncation of) the password. I'm open to other theories which can explain this behavior. -Andy On 10/2/2018 7:21 PM, Andrew Swartz wrote: > Eric, > >

Re: [qmailtoaster] Passwords after backup/restore

xxx > > I could not log in with 17x password but I could with 16x password. > > Not sure what this means, I'm open to enlightenment. Could it be the hash? > > > > On 10/2/2018 8:41 PM, Eric Broch wrote: >> Will do. >> >> >> On 10/2/2018 8:4

Re: [qmailtoaster] Passwords after backup/restore

: > Andrew, > > > On 10/2/2018 7:34 PM, Andrew Swartz wrote: >> 1.  vpopmail (or something else) is NOW authenticating against the >> cleartext password instead of the hash. > I don't think so, or I hope not. I've done nothing except compile > vpopmail on CentOS 7 back

Re: [qmailtoaster] Passwords after backup/restore

Or if any authentication is done by some means other than through vpopmail? -Andy On 10/2/2018 4:02 PM, Eric Broch wrote: > This might be worthy of a note to the MariaDB folks. > > > On 10/2/2018 5:59 PM, Andrew Swartz wrote: >> I felt a new subject appropriate. >> >&

[qmailtoaster] Passwords after backup/restore

behavior is not due to the backup/restore scripts, but rather to some sort of different functionality of the Centos7 setup. It may take a lot of digging and expert knowledge to sort this out. Curious to hear if others can replicate this behavior. -Andy On 10/2/2018 3:19 PM, Andrew Swartz

Re: Fwd: Re: [qmailtoaster] centos 6

r >>> qmailq users) or even vpopmail (vpopmail user) will NOT be able to >>> run that command. >>> >>> I also CHANGE the default passwords for the MySQL database... so if >>> you CAN break in, you CANNOT just query the database (because the >>> vpop

Re: Fwd: Re: [qmailtoaster] centos 6

Eric Broch > Sent: Friday, September 28, 2018 1:35 AM > To: qmailtoaster-list@qmailtoaster.com > Subject: Re: Fwd: Re: [qmailtoaster] centos 6 > > Thanks, Andy. Plain text password have been a part of qt for as long as I've > been using it. I understand you're concern. I'm no

Re: Fwd: Re: [qmailtoaster] centos 6

I recently did the backup/restore and I have one hiccup to report. A few of the account passwords did not work after backup from centos5 and restore to centos7. Took some time to troubleshoot, but I poked around in the vpopmail database and figured it out. It was due to the vpopmail database

Re: [qmailtoaster] Allowing percent sign in email addresses

Consider the possibility that this could be a spamdyke option/issue. I mention this because with my centos5 toaster I had to manually install spamdyke but it installed automatically with my recent centos7 toaster. Also, the spamdyke version has upgraded from 4.x to 5.x which was a fairly

Re: [qmailtoaster] clamav-toaster 0.100

I notice that these clamav rpm's are still in the "testing" directory of the repo. Can anyone report success or problems with the centos-7 verions? -Andy On 6/11/2018 9:45 AM, Eric Broch wrote: > Hi Jason, > > CentOS 6 & 7 clamav-0.100.0 source RPMS > >

Re: [qmailtoaster] /ect/crontab

>&1 > /dev/null > 03 2 * * * root /etc/rc.d/daily-backup > 01 8 * * * root /etc/rc.d/mysql-sync.sh > > > > >> On Aug 20, 2018, at 18:34, Andrew Swartz wrote: >> >> I accidentally overwrote /etc/crontab on my centos-7 toaster. >> >> Can someone please post theirs so I can recreate it. >> >> Thanks, >> -Andy >> > smime.p7s Description: S/MIME Cryptographic Signature

[qmailtoaster] /ect/crontab

I accidentally overwrote /etc/crontab on my centos-7 toaster. Can someone please post theirs so I can recreate it. Thanks, -Andy smime.p7s Description: S/MIME Cryptographic Signature

Re: [qmailtoaster] How to turn of DKIM check?

It worked for me. -Andy On 8/18/2018 10:52 AM, Jaime Lerner wrote: > So I received a bounce notice from the list (ezmlm) with the following > error, and since domain keys aren't really being used anymore, I'd like > to turn off the DK check of incoming mail so my server won't bounce them > if

[qmailtoaster] Removing domain keys

Eric, After a little research, I've come up with this plan to remove domainkeys: 1. Removed from each tcprules file: DKQUEUE="/var/qmail/bin/qmail-queue.orig" DKVERIFY="DEGIJKfh", DKSIGN="/var/qmail/control/domainkeys/%/private" 2. Reinstate the original qmail-queue: rm

Re: [qmailtoaster] status of qmail-1.03-3 CentOS 7 ?

main keys, be aware that if you > upgrade to qmail-1.03-3.1 domainkeys have been removed. > > Eric > > > On 8/16/2018 5:25 PM, Andrew Swartz wrote: >> Eric, >> >> Your request prompted me to look more closely at these files. >> >> I believe that insta

Re: [qmailtoaster] status of qmail-1.03-3 CentOS 7 ?

PD $VCHKPW /bin/true 2>&1 A line had to be added to /etc/rc.d/init.d/qmail (a near copy of line 83, placed right after it) so that /etc/tcprules.d/tcp.smtps gets compiled to /etc/tcprules.d/tcp.smtps.cdb when running 'qmailctl cdb'. -Andy On 8/16/2018 1:33 PM, Eric Broch wrote: > A

Re: [qmailtoaster] status of qmail-1.03-3 CentOS 7 ?

2018 9:35 AM, Eric Broch wrote: > Thanks, Andy. > > It installed SMTPS, correct? > > If you felt bold, I needed some folks to test 1.03-3.1. ;-) > > Eric > > > On 8/16/2018 11:28 AM, Andrew Swartz wrote: >> Eric, >> >> Thanks for the help.  I

Re: [qmailtoaster] Asking the password frequently

Dan, I too noticed your mention of selinux. Do you have qmail running with selinux? If so, I'd love to know how. I have stumbled across some selinux contexts for qmail components, but I've never seen any clear explanation or script for configuration. -Andy On 8/16/2018 7:42 AM, Remo Mattei

Re: [qmailtoaster] status of qmail-1.03-3 CentOS 7 ?

gt; On 8/15/2018 9:22 AM, Andrew Swartz wrote: >> I just realized that the qt-install script did not install qmail-1.03-3 >> on my new centos-7 toaster. >> >> Does anyone have experience with the qmail-1.03-3 update? >> >> -Andy >> > smime.p7s Description: S/MIME Cryptographic Signature

[qmailtoaster] status of qmail-1.03-3 CentOS 7 ?

I just realized that the qt-install script did not install qmail-1.03-3 on my new centos-7 toaster. Does anyone have experience with the qmail-1.03-3 update? -Andy smime.p7s Description: S/MIME Cryptographic Signature

Re: [qmailtoaster] status of qt-backup and qt-restore?

the new machine. Let >> me take a look at my replicate script and I'll get it to you. >> >> >> On 8/14/2018 7:17 PM, Andrew Swartz wrote: >>> Do I just rsync the /home/vpopmail directories?  Or is there >>> data/settings elsewhere also? >>> >>

Re: [qmailtoaster] status of qt-backup and qt-restore?

sassin vs > /etc/spamassassin. > > If I had the servers side by side I wouldn't use backup and restore, I'd > use rsync. > > > On 8/14/2018 11:09 AM, Andrew Swartz wrote: >> Does anyone know if these will do a backup of a centos-5 toaster and >> restore to a centos

[qmailtoaster] status of qt-backup and qt-restore?

Does anyone know if these will do a backup of a centos-5 toaster and restore to a centos-7 toaster? vpopmail seems unchanged, but mysql has changed to mariadb and courier has changed to dovecot. I have very little database knowledge. I'm fearful of the restore causing disaster on the new

Re: [qmailtoaster] Requested DIGEST-MD5 scheme, but we have only SHA1

EST-MD5: what is that auth mechanism for and > why did my toaster conf use it? Anything bad that can happen by > removing it? And what is the difference between PLAIN and LOGIN auth > mechanisms? Are there client configs For Outlook / Thunderbird / Apple > Mail that could be broken b

Re: [qmailtoaster] Requested DIGEST-MD5 scheme, but we have only SHA1

Peter, If you are using ports 110/143, which are clear-text, then you should switch to 993/995 (if possible, of course). Ports 993/995 are never intentionally clear-text; they are either TLS or STARTTLS. Many servers/clients can be configured for either, but they cannot be configured for both

Re: [qmailtoaster] setting up port 465 listening

/dh1024.new /var/qmail/control/dh1024.pem 2>&1 > /dev/null I've changed to "2048" (from 1024) toward the end of the first line.  -Andy On 8/13/2018 10:39 PM, Remo Mattei wrote: > How did y-I gen the dh1024? > > Thanks  > > Sent from my iPad > > On Aug 13, 2

Re: [qmailtoaster] setting up port 465 listening

ILQUEUE="/var/qmail/bin/simscan",DKQUEUE="/var/qmail/bin/qmail-queue.orig",DKVERIFY="DEGIJKfh",DKSIGN="/var/qmail/control/domainkeys/%/private” > > >> On Aug 13, 2018, at 22:43, Andrew Swartz > <mailto:awswa...@acsalaska.net>> wrote: >>

Re: [qmailtoaster] setting up port 465 listening

I meant "servercert.pem" and NOT "tlsserverciphers". -Andy On 8/13/2018 9:43 PM, Andrew Swartz wrote: > > Remo, > > I don't think the order matters in tlsserverciphers.  I cat'd the > cert, the key, and the chain into my file, in that order, and

Re: [qmailtoaster] setting up port 465 listening

rt. looks like.. trying to > figure that out now.. not sure which order they go. > > Andrew Swartz wrote on 8/13/18 22:24: >> Remo, >> >> I just did this: >> >> openssl s_client -starttls smtp -crlf -connect qmail.rm.ht:587 >> >> and got the

Re: [qmailtoaster] setting up port 465 listening

see it’s from COMODO. But not sure > about the first few lines > > Remo  > >> On Aug 13, 2018, at 21:42, Andrew Swartz > <mailto:awswa...@acsalaska.net>> wrote: >> >> I just realized that the plain text line-wrapped the script, so here >>

Re: [qmailtoaster] setting up port 465 listening

COMODO CA Limited/CN=COMODO > RSA Domain Validation Secure Server CA > --- > > > I do have a valid cert as you can see it’s from COMODO. But not sure > about the first few lines > > Remo  > >> On Aug 13, 2018, at 21:42, Andrew Swartz > <mailto:awswa...@acsalas

Re: [qmailtoaster] setting up port 465 listening

y. I do not offer 465 any longer :)  > >  *dal mio iPhone X* > > Il giorno 13 ago 2018, alle ore 20:25, Andrew Swartz > mailto:awswa...@acsalaska.net>> ha scritto: > >> I eventually figured this out, and accomplished the same result though I >> wen

Re: [qmailtoaster] setting up port 465 listening

\ qmailctl start; \ netstat -lnp | grep 465 -Andy On 8/13/2018 7:32 PM, Remo Mattei wrote: > Cool! I remember I did it like Eric described but the bottom line is > it works either way. I do not offer 465 any longer :)  > >  *dal mio iPhone X* > > Il giorno 13 ago 2

Re: [qmailtoaster] setting up port 465 listening

UNT=`cat /var/qmail/control/logcount` > exec /usr/bin/setuidgid qmaill /usr/bin/multilog \ >     t s$LOGSIZE n$LOGCOUNT /var/log/qmail/smtps 2>&1 > > > > Start qmail (# qmailctl start) > > > On 8/11/2018 6:36 PM, Andrew Swartz wrote: >> I just installed qma

[qmailtoaster] setting up port 465 listening

I just installed qmailtoaster onto CentOS-7. The qt_install script opened port 465 on the firewall. However, s_client cannot connect to port 465 and netstat shows that nothing is listening on port 465. Can anyone point me at appropriate instructions for setting up listening on port 465 which

Re: [qmailtoaster] Dkim headache

FYI... your messages which I am receiving from this list have a bad DKIM signature, while messages from other gmail.com posters have good DKIM signatures. I'm attaching a snapshot of what "DKIM verifier" displays in Thunderbird. Some listserves do modify the messages in such a way that all mail

Re: [qmailtoaster] oh oh I got blacklisted

Some other thoughts: 1. Consider how secure your router/firewall is. There are lots of DefCon talks on Youtube where they hack into routers running linux firmware and install malware. Therefore don't overlook the possibility that your router is the culprit. 2. Tighten up your firewall rules

Re: [qmailtoaster] Qmaintoaster-plus error

is the listing of /etc/yum.repos.d? Eric On 6/24/2015 10:53 AM, Andrew Swartz wrote: I installed CentOS-6 from: CentOS-6.6-x86_64-minimal.iso I followed the below instructions. qt-install ends with numerous dependency errors

Re: [qmailtoaster] Qmaintoaster-plus error

I installed CentOS-6 from: CentOS-6.6-x86_64-minimal.iso I followed the below instructions. qt-install ends with numerous dependency errors: - -- Finished Dependency Resolution Error: Package: 1:dovecot-2.2.7-8.qt.el6.x86_64

Re: [qmailtoaster] Qmaintoaster-plus error

On 6/24/2015 10:53 AM, Andrew Swartz wrote: I installed CentOS-6 from: CentOS-6.6-x86_64-minimal.iso I followed the below instructions. qt-install ends with numerous dependency errors: - -- Finished Dependency Resolution Error

[qmailtoaster] SMTP and SSLv3

Has anyone come up with a way to disable SSLv3 PROTOCOL in qmail-smtp and qmail-remote? I have done a fair amount of searching on this topic, both here and elsewhere, and I've found no solution. I will share what I have found. Disabling SSLv2 and SSLv3 was easy for IMAP/POP3 by setting