Re: [qmailtoaster] Qmail Admin File error 6 - IP Address Change

Jeff Koch wrote on 4/2/24 9:27 AM: Hi - we have a user getting File error 6  errors ( IP != IP) when he uses qmail admin on his cell phone and tablet and sometimes from his office. This is due to his provider changing his IP address during his session. I understand qmail admin may view the IP

Re: [qmailtoaster] OT - Question about Rocky Linux

Remo Mattei wrote on 2/18/24 5:40 PM: Nevertheless, I would not change Rocky Linux to others at this point. It rocks. If you have been a Red Hat customer and CentOS then you are perfect to become a Rocky guy. Is Rocky the approved/most-recommended OS for qmailtoaster these days? (I believe

Re: [qmailtoaster] Issues with wiki.qmailtoaster.com

Tony White wrote on 7/11/23 9:10 AM: >   Can anyone tell me why this is happening please? At a guess, the site's database is down or unreachable. > Is anyone else seeing it? Yes. We'll probably need to wait for Eric to give the DB a kick. Eric, would it be worth putting the wiki behind

Re: [qmailtoaster] do we support php 8 ?

According to the RoundCube website, the latest version of RoundCube -- v1.6.0 -- should work with PHP 8.1. Squirrelmail says that the "nightly snapshots" of recent versions are compatible with "the newest versions of PHP8". That announcement dates from mid-2021, which is a little ominous. I

Re: [qmailtoaster] Mail not delivering ... CHKUSER not accepting recipients

Eric Broch wrote on 1/16/23 10:03 PM: > What version of qmail are you using? > > In the later versions, <=1.03-3.3.4, you can use SMTP_DEBUG to monitor > the SMTP transaction logged to a different file. > > > On 1/16/2023 6:22 PM, Angus McIntyre wrote: >> I h

Re: [qmailtoaster] Mail not delivering ... CHKUSER not accepting recipients

not as if it's overwhelmed. It also doesn't seem to affect all TLS encrypted messages equally; some are processed in a couple of seconds at most, others take several minutes. If anyone has any thoughts on this, I'd be interested to hear them. Angus Angus McIntyre wrote on 1/16/23 8:22 PM: > I h

[qmailtoaster] Mail not delivering ... CHKUSER not accepting recipients

I have a qmailtoaster that's been running without problems for a while. I haven't made any configuration changes, and the server is healthy, with enough disk space available etc. Today, I noticed that certain expected messages are not getting delivered. Lots of mail is still coming in without

Re: [qmailtoaster] forwarding to gmail address fails because of hard spf check

Peter Peltonen wrote on 1/2/23 11:57 AM: > Some of my toaster users have their email forwarded to Gmail ... Some > googling around tells me that SRS could be the solution for this > problem. > > There is info on this at Qmailtoaster Wiki, but the site seems to be > somehow broken. Which

Re: [qmailtoaster] About hide my email

Eric Broch wrote on 3/27/22 7:32 PM: > Can you explain what features you'd like to see...maybe why. I don't > have my mind around the "why" of it. The "why" of services like Apple's Hide my Email or disposable email address systems like Sneakemail or the homebrew systems that I described in my

Re: [qmailtoaster] About hide my email

Remo wrote on 3/27/22 11:51 AM: > I kind of like the new option about iCloud hide my email how could we do it > with qmail I don't know how you'd produce the precise features of "hide my email", but it's pretty easy to set up a disposable email address system (like the old Sneakemail) with

Re: [qmailtoaster] Issue with clamav

I seem to remember a past thread that said that ClamAV is very memory-hungry, and getting more so over time as more definitions get added. It's the main reason why I use a 4GB VM for my toaster; the consensus seemed to be that clamav won't run successfully on anything smaller. I don't know what

Re: [qmailtoaster] Best Config for new server

My impression is that Rocky is more widely supported than Springdale by VM providers like Digital Ocean and Linode. But I think they also allow you to provide your own images for initializing VMs, so maybe that's not an obstacle so much as an extra step. Angus Remo wrote on 1/20/22 10:46 AM: >

Re: [qmailtoaster] 550 5.7.511 Access denied, banned sender - Office 365

My Linode-hosted qmailtoaster install was blocked by MSN (Hotmail/Outlook/Live) recently. However, it seems that they had singled out just my IP. I don't know why; logs showed that users on my servers had sent a total of around 600 messages to about 25 distinct Hotmail etc. users in the previous

Re: [qmailtoaster] Problem with forwarding service

st...@keptprivate.com wrote on 10/26/21 8:29 PM: > Setting the spfbehavior file to 1, did resolve the problem! Hooray! > I can see the SPF fail in the headers of messages that used to be rejected. > I had tried to whitelist the IPs of the forwarding servers and expected > that would have

Re: [qmailtoaster] Problem with forwarding service

st...@keptprivate.com wrote on 10/21/21 9:52 PM: > Thanks for looking at the problem and suggesting this. I'm starting > to question my ability to read, because I swear I read that spfbehavior of > 3 was soft-fail (kicks self)! I'm testing now to see if setting it to 1 > fixes it. I was going

Re: [qmailtoaster] Block/Reject email to specific qmail dash alias/extension?

Jonas Simpson wrote on 5/25/21 12:44 PM: > I have a user who has given out various "user-extens...@domain.com" > address to different senders and is now receiving spam to one specific > address, let's call it "user-extension...@domain.com". > > The user no longer needs to receive any email at

[qmailtoaster] Apparent dovecot corruption leading to spurious 'user over quota' messages

I'm seeing intermittent bounces from an address on one of the domains hosted on my CentOS 8/QMT server. The address in question is 'info@', which is handled by the file '.qmail-info' for that domain. The contents of that file look like:

Re: [qmailtoaster] dh key too small

Problem solved. My crypto policies were set to DEFAULT. Changing them to LEGACY and rebooting fixed the issue. Thank you xaf and Eric. Angus xaf wrote on 12/17/20 4:07 AM: Angus McIntyre a écrit le 16/12/2020 à 21:10 : 2048 bits ought to be enough, I would think. Most of the references

Re: [qmailtoaster] dh key too small

on a CentOS/qmailtoaster server? Thanks, Angus Eric Broch wrote on 12/16/20 2:48 PM: hmmm Ours is 2048 bits. What's the remote server? On 12/16/2020 11:27 AM, Angus McIntyre wrote: CentOS 8 and Qmail Toaster Ver. 1.03-3.3.1.qt.el8. Angus Eric Broch wrote on 12/14/20 11:50 PM: What

Re: [qmailtoaster] dh key too small

CentOS 8 and Qmail Toaster Ver. 1.03-3.3.1.qt.el8. Angus Eric Broch wrote on 12/14/20 11:50 PM: What QMT/CentOS versions? On 12/14/2020 6:53 PM, Angus McIntyre wrote: My new toaster delivers mail just fine to almost all hosts. However, with one destination host I get the error:   TLS

[qmailtoaster] dh key too small

My new toaster delivers mail just fine to almost all hosts. However, with one destination host I get the error: TLS connect failed: error:141A318A:SSL routines:tls_process_ske_dhe: dh key too small; connected to x.x.x.x I'm not going to try again ... The question is, which host has the

Re: [qmailtoaster] Future of qmailtoaster on CentOS?

20 6:49 am, Unai Rodriguez wrote: Debian! -- unai On Wed, Dec 9, 2020, at 8:20 PM, Boheme wrote: I’ve been meaning to learn to compile all the source for Ubuntu for a while. This may be the kick in the pants I needed. -Sent from my Pip-Boy 3000 On 10/12/2020, at 12:50 AM, Angus McIntyre wrot

Re: [qmailtoaster] Future of qmailtoaster on CentOS?

g/p/centos-governing-board-do-not-destroy-centos-by-using-it-as-a-rhel-upstream On 12/9/2020 4:50 AM, Angus McIntyre wrote: Does anyone have any thoughts on the likely future of qmailtoaster given the new plans for CentOS? (See https://centos.org/distro-faq/ for more details) I'd never actually heard

[qmailtoaster] Future of qmailtoaster on CentOS?

Does anyone have any thoughts on the likely future of qmailtoaster given the new plans for CentOS? (See https://centos.org/distro-faq/ for more details) I'd never actually heard of CentOS Stream before today, but having just painfully built a working toaster on top of CentOS 8, I'm a little

Re: [qmailtoaster] Close to quota message or scam

"Valued Customer" is such an obvious giveaway that I wouldn't bother looking any further. It's a very common phrase in scams of all kinds. Your message is a scam and it almost certainly came from outside your system. Incidentally, on the subject of quota messages, I did see an interesting

[qmailtoaster] SOLVED (was: Re: [qmailtoaster] maildrop and qmail)

eplacement for procmail for final delivery filtering on your qmailtoaster. Angus Angus McIntyre wrote on 11/29/20 10:01 PM: Yeah, for some reason that doesn't work for me. I'm not sure if I need to be running maildrop in a different mode or something, but when I tell it: to

Re: [qmailtoaster] TLSv1.0

It identifies itself as Qmail Toaster Ver. 1.03-3.3.1.qt.el8. Latest version from qmailtoaster.com. Angus Eric Broch wrote on 12/1/20 7:00 PM: What version of qmail? On 12/1/2020 4:27 PM, Angus McIntyre wrote: I have to support a user who's using OS X El Capitan, which apparently tops out

[qmailtoaster] TLSv1.0

I have to support a user who's using OS X El Capitan, which apparently tops out at TLSv1.0. Her laptop is able to connect with POP but not with SMTP, so she can fetch mail but can't send it. From the logs, it looks as if the POP connection is using TLSv1.0: Dec 1 10:51:33 Mail[607] :

Re: [qmailtoaster] maildrop and qmail

il-address On 11/29/2020 6:59 PM, Angus McIntyre wrote: Does anyone have any experience of using maildrop with qmail? I'm able to get maildrop to filter and deliver locally without problems, but attempts to forward to remote (or local) addresses just cause maildrop to report an unhelpful "Err

[qmailtoaster] maildrop and qmail

Does anyone have any experience of using maildrop with qmail? I'm able to get maildrop to filter and deliver locally without problems, but attempts to forward to remote (or local) addresses just cause maildrop to report an unhelpful "Err!". If anyone has made this work successfully, I'd

Re: [qmailtoaster] Missing subjects in SquirrelMail

to have taken care of the issue. Thanks, Angus Eric Broch wrote on 11/29/20 1:09 AM: Would it help to role the most recent squirrelmail? On 11/28/2020 9:14 PM, Angus McIntyre wrote: I'm finalizing a new CentOS 8 install, built using an ansible role based on Eric's install instructions. The role

[qmailtoaster] Missing subjects in SquirrelMail

I'm finalizing a new CentOS 8 install, built using an ansible role based on Eric's install instructions. The role sources the qmailtoaster packages from Eric's collection including squirrelmail. The squirrelmail version installed is 1.4.22.-3.qt.el8. It's running on PHP 7.4.3. In the Inbox

Re: [qmailtoaster] Filtering: procmail, maildrop, other?

was thinking about implementing. Of course it could be implemented like Dspam as well, but it's always better that garbage not make it into the queue. Eric On 9/3/2020 8:37 AM, Angus McIntyre wrote: Yeah, it's definitely out of EPEL 8, as far as I can tell. Looking around for other filtering

Re: [qmailtoaster] Time stamp

Biju Jose | WHITES Systems wrote on 9/21/20 5:34 AM: How do I convert the time stamp to human readable format? /var/log/qmail/submission/@40005f6532c63981467c.s:7141:@40005f64d1c20b27b874 CHKUSER relaying rcpt: from . There's a program called 'tai64nlocal'

Re: [qmailtoaster] Mailserver temporarily rejected message

Also, use 'toaststat' or equivalent to make sure all the components of your toaster are up and running. If you don't have enough memory on your box, then ClamAV will sometimes crash, making mail undeliverable and generating the "temporarily rejected" message you've seen. Rebooting will cure

Re: [qmailtoaster] Filtering: procmail, maildrop, other?

/20 9:49 AM: It doesn't look like dspam is in the EPEL repo for CentOS 8--may be wrong, I might have to do some contorting. It's really the only thing that's kept the inbox clean. Will do some investigation and get back to you. Eric On 9/3/2020 7:37 AM, Angus McIntyre wrote: Thanks, Eric. I

Re: [qmailtoaster] Filtering: procmail, maildrop, other?

.com/qmtoaster/dspam On 9/1/2020 7:54 PM, Angus McIntyre wrote: Thanks, Eric The user-level dspam support sounds intriguing. Is that something already documented online somewhere, or that you could describe (and wouldn't mind sharing)? Angus Eric Broch wrote on 9/1/20 1:43 PM: I like maild

Re: [qmailtoaster] Filtering: procmail, maildrop, other?

, Angus McIntyre wrote: Thank you, Eric. That's extremely helpful. Out of interest, does anyone have any thoughts about the relative merits of maildrop and sieve: any reason to prefer one over the other? Angus Eric Broch wrote on 9/1/20 6:36 AM: I have a Sieve setup guide on the website

[qmailtoaster] Spamassassin: failed to create readable default_prefs

In the process of testing my new toaster, I noticed the following lines in '/var/log/maillog'. Sep 1 21:43:16 s6 spamd[19967]: spamd: setuid to clamscan succeeded Sep 1 21:43:16 s6 spamd[19967]: spamd: creating default_prefs: //.spamassassin/user_prefs Sep 1 21:43:16 s6 spamd[19967]:

Re: [qmailtoaster] Filtering: procmail, maildrop, other?

://www.qmailtoaster.org/dovecot-lda-sieve.html On 9/1/2020 2:25 AM, Angus McIntyre wrote:  I was afraid someone would say that. ;-) Any pointers? For procmail and maildrop it's fairly straightforward -- just set up your .qmail files to pipe incoming mail through them. It looks as if Sieve support is via dovecot

Re: [qmailtoaster] Filtering: procmail, maildrop, other?

implemented Sieve have any pointers or recommendations to share? Thanks, Angus Eric Broch wrote on 8/31/20 6:41 PM: I'd support both Sieve and Maildrop. On 8/31/2020 4:27 PM, Angus McIntyre wrote: For a long time, I've used procmail for filtering incoming mail in qmailtoaster setups. I understand

[qmailtoaster] Filtering: procmail, maildrop, other?

For a long time, I've used procmail for filtering incoming mail in qmailtoaster setups. I understand that procmail is now unmaintained, and that maildrop might be a more future-proof choice. So I'm adding maildrop support to my ansible role. Are there other tools that I should consider? I'm

[qmailtoaster] dspam -- yay or nay?

I'm (still!) working on my Ansible role for installing qmailtoaster, but I've switched to CentOS 8, based on Eric's new script, and it seems much more straightforward and robust. One question I have is whether I should try to support dspam or not. It looks as if the project was abandoned in

Re: [qmailtoaster] Distressing strange behavior

Check for a '.forward' file in '/root'? That could account for the status report going somewhere other than where it's supposed to, but might not explain the other issues you're seeing. Angus Chas Hockenbarger wrote on 8/16/20 6:09 PM: I just got another piece of information.  I got a

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

, the signature file will always continue to grow as more malware accrues, so in another couple years I'll surely need to increase the RAM again. Hope this helps. -Andy On 7/20/2020 10:01 AM, Angus McIntyre wrote: My qmailtoaster running on CentOS 7 was behaving fine, but now seems to soft reject

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

Eric Broch wrote on 7/20/20 8:47 PM: Interesting that when you put 'clam=no' in simcontrol that that didn't, at the very least, stop the soft rejects. Yeah. I'm not going to think too hard about that one. I'll put it down to 'operator error' on my part. This may be a bad move: the first

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

SCAN_DEBUG="5" Eric On 7/20/2020 1:36 PM, Angus McIntyre wrote: Thank you Finn and Remo I tried doubling the softlimit, and using Remo's configuration, but the problem remains. I'm not seeing any additional output in /var/qmail/log/smtp/current. Is that the logfile where the

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

/domainkeys/%/private” you probably want to have that out of the 127. Remo On Jul 20, 2020, at 11:52 AM, qm...@mailonly.dk wrote: Hi Angus. Have You tried to increase the softlimit in the run file ? (to get rid of the issue ;-)) Cheers, Finn Den 20-07-2020 kl. 20:01 skrev Angus McIntyre:

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

re is the steps: :allow,SIMSCAN_DEBUG="2”,CHKUSER_EXTRA_ then run qmailctl cdb That should do it On Jul 20, 2020, at 11:03 AM, Remo Mattei  wrote: Angus, I notice this as well and I rerun the Eric’s script and all comes back to normal, I have had not time to debug this yet. Re

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

My qmailtoaster running on CentOS 7 was behaving fine, but now seems to soft reject everything, and I'm having a hard time working out why. It doesn't seem to be a ClamAV issue: I set 'clam=no' in '/var/qmail/control/simcontrol' and restarted qmail, but I still get the rejections. I added

Re: [qmailtoaster] DKIM on CentOS 8

haven't gotten around to it yet. On 7/20/2020 7:10 AM, Angus McIntyre wrote: What's the status of qmailtoaster on CentOS 8? Is it stable enough that you'd recommend new installs to be built on CentOS 8, or should we stay with the tried and tested CentOS 7? Thanks, Angus Eric Broch wrote

Re: [qmailtoaster] DKIM on CentOS 8

What's the status of qmailtoaster on CentOS 8? Is it stable enough that you'd recommend new installs to be built on CentOS 8, or should we stay with the tried and tested CentOS 7? Thanks, Angus Eric Broch wrote on 7/19/20 11:02 PM: https://lxadm.com/Generating_DKIM_key_with_openssl On

Re: [qmailtoaster] Re: Email delivery repeats

On 2020-07-10 04:15, Chris wrote: I've disabled spamdyke, the source of the 421 timeout error; but I'm still getting re-delivery of emails. Not as frequently, but I've received the same two emails a dozen times today. Has anyone else experienced this before? On my very ancient qmailtoaster

[qmailtoaster] CentOS 8?

I see that CentOS 8 is upon us. What's the recommendation for anyone contemplating a new QMT install: make it the target platform of choice, or stay the hell away from it because QMT support is still bleeding edge? Recommendations gratefully received, Angus

Re: [qmailtoaster] Slow connection and transaction times

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 temporarily deactivating Spamdyke and seeing if that speeds it up. -Andy On 12/31/2019 4:41 AM, Angus McIntyre wrote

Re: [qmailtoaster] Slow connection and transaction times

is as an anti-spam tactic, and whether it has any impact on real mail? Angus On 2019-12-31 04:57, Eric Broch wrote: If you have spamdyke installed it may have a timer (greeting-delay-secs=) to inhibit spammers. On 12/31/2019 2:54 AM, Angus McIntyre wrote: I'm testing a newly-built mail server

[qmailtoaster] Slow connection and transaction times

I'm testing a newly-built mail server, and the tool at: https://mxtoolbox.com/SuperTool.aspx reports very slow connection and transaction times (approx. 6 seconds and 8 seconds respectively). The server is on a reasonably powerful and very lightly-loaded VM. Are these times typical?

Re: [qmailtoaster] Roundcube and Squirrelmail: relaying refused

hich works for squirrelmail) : 127.:allow,RELAYCLIENT="",RBLSMTPD="",NOP0FCHECK="1" On 12/30/2019 3:03 PM, Angus McIntyre wrote: I'm still trying to set up an Ansible role for creating a qmailtoaster install, and I've run into some issues with Roundcube and

[qmailtoaster] Roundcube and Squirrelmail: relaying refused

I'm still trying to set up an Ansible role for creating a qmailtoaster install, and I've run into some issues with Roundcube and Squirrelmail (Rainloop works fine). Following Eric's advice, I'm using local SMTP for submission, so the Roundcube '/etc/roundcubemail/config.inc.php' file

Re: [qmailtoaster] SquirrelMail

Some quick Googling suggests that this is a dovecot error, not a Squirrelmail error. One person responding to a question about this error suggests checking '/etc/dovecot/dovecot.conf' to make sure that the 'quotadict' variable is not commented out. I don't know if that's relevant to your

Re: [qmailtoaster] dovecot CVE-2019-11500

I think Eric is saying that the version in the testing repository -- which, as you said, is 2.3.7.2 -- fixes the vulnerability. The relevant part of the CVE-2019-11500 report -- which Eric quoted in his message, with the key words emphasized -- says that this vulnerability exists in versions

[qmailtoaster] Rainloop and folders (was: Re: [qmailtoaster] Authentication issues with Squirrelmail and RoundCube)

Eric Broch wrote on 7/23/19 8:58 AM:> Also, as a side note Rainloop refuses to display one of my folders which roundcube and squirrelmail do display. Has anyone else seen this? I found that with Rainloop, you need to specifically switch on the folders that you want to see in the sidebar.

Re: [qmailtoaster] Authentication issues with Squirrelmail and RoundCube

Jul 22, 2019 at 5:46 PM -0600, "Angus McIntyre" mailto:an...@pobox.com>> wrote: r...@mattei.org wrote on 7/22/19 10:22 AM: > You need to install the cert on your machine. Does the /etc/hosts > have the name of your machine can you try to ping that

Re: [qmailtoaster] Authentication issues with Squirrelmail and RoundCube

with past configurations. Eric Get Outlook for Android [1] On Mon, Jul 22, 2019 at 5:46 PM -0600, "Angus McIntyre" wrote: r...@mattei.org wrote on 7/22/19 10:22 AM: You need to install the cert on your machine. Does the /etc/hosts have the name of your machine can you try to ping

Re: [qmailtoaster] Authentication issues with Squirrelmail and RoundCube

come your recommendations. Thanks, Angus Il giorno 21 lug 2019, alle ore 20:03, Angus McIntyre ha scritto: Thanks to a great deal of help from Remi and Eric, I have now managed to get my Ansible role to the point where it can successfully build out a QMailToaster server runnin

[qmailtoaster] Authentication issues with Squirrelmail and RoundCube

Thanks to a great deal of help from Remi and Eric, I have now managed to get my Ansible role to the point where it can successfully build out a QMailToaster server running PHP 7.1 and RoundCube 1.4rc1. However, because nothing is ever that easy, RoundCube and SquirrelMail have now stopped

Re: [qmailtoaster] Roundcube login fails on PHP 7.x

/19 7:55 PM: Did you follow these instructions: https://www.qmailtoaster.org/roundcube.html On 7/14/2019 4:56 PM, Angus McIntyre wrote: Remo, Eric, thank you. Installing 1.4 seems to take me into dependency hell. This is what I have so far in ansible: - name: add REMI test repo   become: yes

Re: [qmailtoaster] Roundcube login fails on PHP 7.x

://www.mail-archive.com/qmailtoaster-list@qmailtoaster.com/msg41927.html On 7/14/2019 11:29 AM, Angus McIntyre wrote: Has anyone been able to successfully run Roundcube with PHP7 on a QMT install? I'm following -- more or less -- the install guidelines given on the qmailtoaster site. When I have PHP

[qmailtoaster] Roundcube login fails on PHP 7.x

Has anyone been able to successfully run Roundcube with PHP7 on a QMT install? I'm following -- more or less -- the install guidelines given on the qmailtoaster site. When I have PHP 5.4 installed, I am able to log in and use Roundcube without problems. When I have PHP7.2 or 7.3

Re: [qmailtoaster] Testing and development repos

it in a production environment. Eric On 7/11/2019 6:23 PM, Angus McIntyre wrote: This is probably a question for Eric B. On the 'qmailtoaster.com' homepage, under CentOS 7 QMT Host, section 3, it offers three apparent alternatives -- a straight yum update, followed by yum update with 'qmt-testing

[qmailtoaster] Testing and development repos

This is probably a question for Eric B. On the 'qmailtoaster.com' homepage, under CentOS 7 QMT Host, section 3, it offers three apparent alternatives -- a straight yum update, followed by yum update with 'qmt-testing' enabled, and yum update with 'qmt-devel' enabled. There are then four qmail

[qmailtoaster] vpopmail in the latest toaster

I'm currently building out a new server, and I'm trying to automate the qmailtoaster install process using Ansible. The last time I did a full qmailtoaster install was several years ago, on CentOS 5, and I understand that things have changed a bit since then. In particular, I believe that

Re: [qmailtoaster] sslv3 alert handshake failure

under a different name and qmail is linked to it. Every other package will  continue as usual using older version. Eric On 6/17/2019 8:10 PM, Angus McIntyre wrote: Thank you, Eric. Unfortunately, I've hit a "can't get there from here" situation. Upgrading the SSL library requires a new

Re: [qmailtoaster] sslv3 alert handshake failure

mail wrote: https://www.qmailtoaster.org/newopensslclamavcnt50.html [1] Get Outlook for Android [2] On Mon, Jun 17, 2019 at 5:40 AM -0600, "Angus McIntyre" wrote: I've recently started getting bounces when trying to send email to one particular domain. The errors read: TLS connect fa

[qmailtoaster] sslv3 alert handshake failure

I've recently started getting bounces when trying to send email to one particular domain. The errors read: TLS connect failed: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO: sslv3 alert handshake failure I'm running a probably fairly elderly version of QMT on CentOS 5 (yes, I know,

[qmailtoaster] fail2ban and 'null password given'

If you're smart, you're probably running 'fail2ban' (or something similar) on your qmailtoaster to block password-guessing attempts. You may also have used the rules given at:     http://wiki.qmailtoaster.com/index.php/Fail2Ban to configure it. This morning I happened to check my logs and

Re: [qmailtoaster] Getting multiple copies of emails

I've seen duplicate emails when the server is very heavily loaded. If you had any runaway processes that were causing loads to spike, you could get duplicates. Angus On 2019-05-31 09:34, Peter Peltonen wrote: In the past I remember this kind thing happening with the old Courier IMAP.

Re: [qmailtoaster] Mailing list -- frontend web

I need something that has like unsubscribe using a web page, and something I am also looking on how to use the ezmlm-cron if anyone has set that up please let me know for tips etc. Remo On Feb 1, 2019, at 12:56, Angus McIntyre wrote: I have used mailman on a qmailtoaster host. I never loved it. Everyth

Re: [qmailtoaster] Mailing list -- frontend web

I have used mailman on a qmailtoaster host. I never loved it. Everything about it, from the UI to the general technical approach, seemed to be stuck in about 1996. However, once I'd got it set up and working, it did the job and needed very little attention. I'd like to think that there's

Re: [qmailtoaster] Simultaneous pop3 connections from two devices

I doubt a single user would ever need 256 simultaneous connections, but -- judging by the name -- the setting might specify the number of connections allowed from a single IP, which would be different. If you had a large number of users on a NAT'ted network, so that they looked to the server

Re: [qmailtoaster] CNAME lookup failed temporarily -- workarounds?

Eric Broch wrote: Angus, qmail-toaster ( and pop3d) x86_64 RPMS (CNAME lookup removed) in this folder: ftp://ftp.qmailtoaster.org/pub/repo/qmt/CentOS/5/development/x86_64/ On 2/15/2018 7:16 AM, Angus McIntyre wrote: I'm running a fairly ancient qmail (netqmail-1.0.5, according to the manual

[qmailtoaster] CNAME lookup failed temporarily -- workarounds?

I'm running a fairly ancient qmail (netqmail-1.0.5, according to the manual) on CentOS 5, and I'm starting to get bitten with increasing frequency by the 'CNAME lookup failed temporarily' bug. I urgently need to build a new host with an up-to-date OS and the latest version of qmail and move

[qmailtoaster] QMT install and Ansible

I’m in the process of setting up a new qmailtoaster box for the first time in many years, and I’m checking over the install scripts. It looks like Eric has done an amazing job of packaging the process. My tool of choice for system administration now is Ansible (https://www.ansible.com/), which

Re: [qmailtoaster] Roundcube with QMT

> On Feb 13, 2017, at 2:57 PM, CarlC Internet Services Service Desk > wrote: > Cool, I was always interested in Roundcube. > > Any gotcha's on installation? Or do I just "yum install roundcube" [Doubt > it's that easy or I would be that lucky] :) ? I don’t know if it’s as

Re: [qmailtoaster] catch all account and the spam

> On Jul 11, 2016, at 2:16 PM, CarlC Internet Services Service Desk > wrote: > I know a few years ago, I did have a few customers this happened to. We had > to disable the catch-all and instead, set it to bounce-no-mailbox. When we > did that, the spammers stopped trying to

Re: [qmailtoaster] catch all account and the spam

> On Jul 7, 2016, at 1:10 PM, Jim Shupert wrote: > I am wondering what a "wise" method of doing the catch all account regarding > spam might be > > To limit the amount of spam that a standard user who is catch all (me for > example ) > > I have created a usr named

Re: [qmailtoaster] Qmail queue is stuck

> On Apr 1, 2016, at 10:59 PM, Aneesh Hariyappan wrote: > I killed the qmail send pid s and started qmail again .. now the current log > shows the following... and the email queue is piling up. > > I am using qmail for intranet only.. some of the users enabled

[qmailtoaster] QMT -- state of the union?

I’ve been running a QMT server on a CentOS 5 VPS for a while, and I’m now looking to migrate it to a newer host. What’s the currently-preferred platform? CentOS 6, or CentOS 7? Are there any other special requirements? Also, I know that in the absence of Eric Shubart, Eric Broch has been doing

Re: [qmailtoaster] QMT -- state of the union?

t-7-1.noarch.rpm> 2> > > Eric Shubert is still the lead for QMT. I will continue to do packaging in > his absence. Eventually, I'd like to move all the work that I've done to > GitHub. There are many people using and updating CentOS 7 and have been since > near the begi

Re: [qmailtoaster] Request for ideas: limiting outbound traffic

> On Oct 20, 2015, at 10:29 AM, Dan McAllister wrote: > I have an issue I'd like to throw out there -- I have a small number of users > (on a server with about 20,000 users) that are abusing the service in that > they're purposefully sending out huge amounts of mail. > >

Re: [qmailtoaster] Shubes

> On Sep 17, 2015, at 6:09 PM, Fabian Santiago > wrote: > That's wild. I also ventured over to another mailing list for an organization > he's been involved in, main plug. They claim he should be just fine and well > and someone claimed to have just recently spoken

Re: [qmailtoaster] protection against word / excel macro viruses

On Jun 12, 2015, at 1:32 PM, Rajesh M 24x7ser...@24x7server.net wrote: but the issue is that we need a tool that will read the body of thedoc/excel attachment and detect if any macros are present and mark it as spam -- clam does not detect macros many a time since there are too many

Re: [qmailtoaster] qtp-install-sanesecurity needs update for new SaneSecurity script version

: Thanks for the info, Angus. I'm going to create an rpm for this. On 5/29/2015 8:30 AM, Angus McIntyre wrote: It seems that there’ve been some changes in the SaneSecurity package, which provides additional ‘virus’ signatures for ClamAV. Recently, the cron job that pulls down new definitions

[qmailtoaster] qtp-install-sanesecurity needs update for new SaneSecurity script version

It seems that there’ve been some changes in the SaneSecurity package, which provides additional ‘virus’ signatures for ClamAV. Recently, the cron job that pulls down new definitions has started erroring out on my server with reports such as: Clamscan reports Sanesecurity honeynet.hdb database

Re: [qmailtoaster] spf

On 2015-04-29 10:03, Dave M wrote: What test to confirm the SPF records ? There are some good tools at: http://www.kitterman.com/spf/validate.html Incidentally, don't expect too much from SPF. There are plenty of services (Yahoo!, I'm looking at you) which will happily try to deliver

Re: [qmailtoaster] what does this command do?

On 2015-04-16 15:43, fsanti...@deviltracks.net wrote: perl -pi -e 's/global.key._domainkey/dkim1/' /var/qmail/control/dkim/public.txt can someone explain this command to me exactly? Thanks. It edits the file '/var/qmail/control/dkim/public.txt' and replaces the string

Re: [qmailtoaster] Fwd: ezmlm warning

I received one of those a few days ago. I did some digging and figured out what was happening. 1. Someone posted to the qmailtoaster list from a host that is currently listed in an RBL. 2. Spamdyke on my server checked their IP against the RBL and rejected the message(s). 3. The

Re: [qmailtoaster] Fwd: ezmlm warning

On 2015-04-12 20:06, Eric Broch wrote: Are you the administrator of the qmailtoaster MX? No, I'm not. I assume that's Eric shubes. I'm just a qmailtoaster user, not part of the 'inner circle' (if such a thing exists) in any way. Angus

Re: [qmailtoaster] New format for spam enlargement emails

Tony White wrote: nothing seems to stop this Subject passing through all the filters in QMT. P_E N-I_S --E-N..L_A-R-G-E_M-E N-T.._ P_I-L L_S The regex: P(\.\.|_| |-)E(\.\.|_| |-)N(\.\.|_| |-)I(\.\.|_| |-)S applied to the Subject should get pretty much all of them. Looking at my

[qmailtoaster] Special-case spam filtering based on envelope sender

I’m seeing an uptick in a particular type of spam that I would very much like to filter. Fortunately, the spam has a quite distinctive fingerprint: the envelope sender of each message matches the regex: ^[A-Za-z0-9_-]+-realuser=realdomain\.realtld\@[a-z0-9-]+\.[a-z]{2,4}$ (where

  1   2   >