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

and trying again. Best, Peter On Fri, Feb 24, 2023 at 4:24 AM あいざわひろし wrote: > Hi Peter, > > What kind of malformed header cause it? > > I wonder whether I can drop such mail in > /var/qmail/alias/.qmail-srs-default . > -- > AIZAWA Hiroshi > > 2023年2月23日(木) 20:32 Pe

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

etter to make the spf record for srs domain. > > -- > AIZAWA Hiroshi > > 2023年1月3日(火) 18:23 Peter Peltonen : > > > > Googling "srs qmailtoaster" gave me this link: > > > > > http://wiki.qmailtoaster.net/index.php/Configuring_SRS_on_Toaster_1.03

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

/srs_domain does not seem to do anything: the first domain listed there is always used. If someone else tries this out, please correct me if I'm wrong! Best, Peter On Fri, Jan 13, 2023 at 3:11 PM Peter Peltonen wrote: > Hi Andreas, > > Unfortunately it needs to be done for every domain that

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

Am 04.01.23 um 18:18 schrieb Peter Peltonen: > > Okay I tested this setup and it seems to work, mail gets through and I get > spf=pass for it in Gmail. > > The only difference to the procedure I posted earlier were: > > - needed to add srs.xyz.com to morercpthosts and not to rcpthos

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

thosts - the toaster will generally add additional domains to > morercpthosts but it should work fine either way. > > Jeff > > On 1/4/2023 12:18 PM, Peter Peltonen wrote: > > Okay I tested this setup and it seems to work, mail gets through and I get > spf=pass for it in

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

and qmailctl restart, not sure if needed Best, Peter On Tue, Jan 3, 2023 at 11:22 AM Peter Peltonen wrote: > Googling "srs qmailtoaster" gave me this link: > > > http://wiki.qmailtoaster.net/index.php/Configuring_SRS_on_Toaster_1.03-1.3.13%2B > > which does not wor

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

- send email to xyz.com: should pass ok What do you think Angus? Best, Peter On Mon, Jan 2, 2023 at 7:52 PM Angus McIntyre wrote: > > > Peter Peltonen wrote on 1/2/23 11:57 AM: > > Some of my toaster users have their email forwarded to Gmail ... Some > > go

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

Some of my toaster users have their email forwarded to Gmail. Earlier this has worked fine, but now there have a been a couple of following cases: 1) user from external domain abc.com with hard SPF fail policy sends an email to xyz.com that is hosted on my toaster 2) my toaster tries forward

Re: [qmailtoaster] Is it safe to block port 465/smtps and how to prevent brute force guessing

68.55.3.234 211.196.236.250 124.165.66.186 183.99.76.78 67.204.24.218 On Wed, Nov 2, 2022 at 10:13 PM Peter Peltonen wrote: > Thanks and yes, submission has been hacked also of course, but for some > reason, I see the brute force attempts directed only against smtps (at > least during

Re: [qmailtoaster] Is it safe to block port 465/smtps and how to prevent brute force guessing

rvise/smtps/down > > # qmailctl start > > # qmailctl stat > > But, if they've hacked smtps then they've also hacked submission; right? > > > On 11/1/2022 1:10 PM, Peter Peltonen wrote: > > Hi, > > I had an email account password guessed through auth attempts v

[qmailtoaster] Is it safe to block port 465/smtps and how to prevent brute force guessing

Hi, I had an email account password guessed through auth attempts via smtps. I did not realize this as I had forgotten I had it enabled at all. I was looking at the submission log and scratching my head not understanding how messages got to the remote queue without anything in the submission

Re: [qmailtoaster] TLS connection failed: ciphersuite wrong

n qmail-remote to load ciphers suits from the control directory > > has been replaced so the default ciphers are loaded instead of the one > > in the control directory. I've made changes to qmail-remote for the > > latest OpenSSL to support TLS 1.3 and am using the proper function to

Re: [qmailtoaster] TLS connection failed: ciphersuite wrong

> servers but use the higher protocol version for the rest of the world? > > Best, > Peter > > > On Mon, Feb 28, 2022 at 1:44 AM Eric Broch wrote: > > > > I'd like to implement this programmatically so that we can set > > parameters in a /var/qmail/control/sslconf file

Re: [qmailtoaster] TLS connection failed: ciphersuite wrong

, Feb 28, 2022 at 1:44 AM Eric Broch wrote: > > I'd like to implement this programmatically so that we can set > parameters in a /var/qmail/control/sslconf file > > On 2/27/2022 2:25 PM, Peter Peltonen wrote: > > Hi Eric, > > > > Okay my crypto-policy is now DEFAULT

Re: [qmailtoaster] TLS connection failed: ciphersuite wrong

back-ends/opensslcnf.config particularly > setting > > CipherString = @SECLEVEL=2 > > change to > > CipherString = DEFAULT@SECLEVEL=1 > > Watch logs > > Eric > > On 2/23/2022 8:53 AM, Peter Peltonen wrote: > > You mean my server with qmail-1.03-3.3.1.qt.md.el8.x

Re: [qmailtoaster] TLS connection failed: ciphersuite wrong

: > > Does your legacy server qmail-1.03-2.2.1 send to all? > > On 2/23/2022 8:03 AM, Peter Peltonen wrote: > > Here is another error I have now seen qmail/send log about 10 times in > > the recent hour: > > > > TLS_connect_failed:_error:141A318A:SSL_routines:

Re: [qmailtoaster] TLS connection failed: ciphersuite wrong

that the other party supports? Best, Peter On Wed, Feb 23, 2022 at 4:29 PM Eric Broch wrote: > > If I remember correctly it had something to do with Dovecot > On Feb 23, 2022, at 2:25 AM, Peter Peltonen wrote: >> >> Hello, >> >> Okay I now tested:: >> >

Re: [qmailtoaster] TLS connection failed: ciphersuite wrong

at 11:25 AM Peter Peltonen wrote: > > Hello, > > Okay I now tested:: > > With LEGACY (which I had earlier) I get the > SSL_routines:set_client_ciphesuite:wrong_cipher_returned error in qmail/send > log: > > But with DEFAULT I get Remote_host_said:_250_2.0.0_OK_acce

Re: [qmailtoaster] TLS connection failed: ciphersuite wrong

've change it to 'update-crypto-policies --set DEFAULT' or > >> 'update-crypto-policies --set FUTURE' and are still having issue ask > >> hornet security if we can see the actual smtp transaction. > >> > >> In my earlier email I was saying that there was not much

Re: [qmailtoaster] TLS connection failed: ciphersuite wrong

> between the old code and the new code for remote delivery and it was not > immediately obvious why we would be having a problem. > > Eric > > > On 2/21/2022 7:17 AM, Peter Peltonen wrote: > > Hi, > > > > Is there something I can test? I didn't quite understand from E

Re: [qmailtoaster] TLS connection failed: ciphersuite wrong

a MAIL proxy and therefore may be the reason > >>>> for Your issue ?? > >>>> > >>>> or maybe it's just a coincidence ? > >>>> > >>>> Regards, > >>>> Finn > >>>> > >>>> > >&g

Re: [qmailtoaster] TLS connection failed: ciphersuite wrong

What I have installed is qmail-1.03-3.3.1.qt.md.el8.x86_64 Any reason to update? Best, Peter On Sun, Feb 13, 2022 at 5:15 PM Eric Broch wrote: > > What version of qmail ? > > On 2/12/2022 12:56 PM, Peter Peltonen wrote: > > Finally got an answer from them (see list below). I

Re: [qmailtoaster] TLS connection failed: ciphersuite wrong

HA256 • ECDHE-RSA-AES128-GCM-SHA256 • ECDHE-RSA-AES128-SHA256 • DHE-RSA-AES128-GCM-SHA256 • DHE-RSA-AES128-SHA256 " On Mon, Feb 7, 2022 at 4:08 PM Eric Broch wrote: > > Is there a way to contact them and find out what obscure B.S. they want? > > On 2/7/2022 12:26 AM, Peter Peltonen

[qmailtoaster] TLS connection failed: ciphersuite wrong

When trying to deliver email to a domain that is using spam protection from antispameurope.com I get the following error: deferral: TLS_connect_failed:_error:1421C105:SSL_routines:set_client_ciphersuite:wrong_cipher_returnedZConnected_to_83.246.65.85_but_connection_died._(#4.4.2)/ So am I

Re: [qmailtoaster] Squirrelmail charset problem

hp issue it > seems but a SM issue. SM has been discontinued for CentOS 8 it seems. > > ftp://ftp.qmailtoaster.org/pub/repo/qmt/CentOS/8/testing/mysql/x86_64/squirrelmail-1.4.23-1.qt.el8.20190710.noarch.rpm > > Eric > > On 2/1/2021 2:37 PM, Peter Peltonen wrote: >

Re: [qmailtoaster] Squirrelmail charset problem

suggested characters: > > On 2/1/2021 6:31 AM, Peter Peltonen wrote: > > Nobody else has this issue with Squirrelmail? You can easily check by > copypasting the following text to both as Subject and Body of the > message, sending the msg to yourself and then trying to view it in &g

Re: [qmailtoaster] Squirrelmail charset problem

up in Squirrelmail Best, Peter On Mon, Jan 25, 2021 at 10:09 PM Peter Peltonen wrote: > > I got those errors when reloading the INBOX message view with messages > having scandinavian characters (ä ö) in their subjects. > > The characters are not visible either. > > Same thing

Re: [qmailtoaster] Squirrelmail charset problem

On Mon, Jan 25, 2021 at 4:22 PM Eric Broch wrote: > > I'm not seeing this error. I have two sd linux 8 hosts, one fresh > install and one migrated from centos 8. Is there a certain page with > squirrelmail? > > Eric > > On 1/25/2021 5:59 AM, Peter Peltonen wrote: > > Af

[qmailtoaster] Squirrelmail charset problem

After migrating to SDL8 + latest QMT with squirrelmail-1.4.22-3.qt.el8.x86_64 I noticed that Squirrelmail cannot show utf8 characters like a with dots (ä) There are errors like this in the php log: PHP Warning: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback

Re: [qmailtoaster] Re: Cannot access Qmailadmin from Squirrelmail from new SDL8 toaster

'; > > 2) #$qmlogin_cgi_url='/cgi-bin/qmailadmin'; > > > > Should this be changed in the default configuration perhaps? > > > > Best, > > Peter > > > > On Thu, Jan 14, 2021 at 11:54 PM Peter Peltonen > > wrote: > >> I can access Qm

[qmailtoaster] Re: Cannot access Qmailadmin from Squirrelmail from new SDL8 toaster

configuration perhaps? Best, Peter On Thu, Jan 14, 2021 at 11:54 PM Peter Peltonen wrote: > > I can access Qmailadmin via http://mytoaster/qmailadmin > > But when I login to Squirrelmail and go to Options > Account > Administration and then enter my password I get > > Not F

[qmailtoaster] Cannot access Qmailadmin from Squirrelmail from new SDL8 toaster

I can access Qmailadmin via http://mytoaster/qmailadmin But when I login to Squirrelmail and go to Options > Account Administration and then enter my password I get Not Found The requested URL was not found on this server. And in the Apache error log: AH01264: script not found or unable to

Re: [qmailtoaster] Re: SDL8 test install hiccups

data from old separate tables to the new multi-domain table? Best, Peter On Thu, Dec 31, 2020 at 10:59 PM Peter Peltonen wrote: > > These commands were posted to the CentOS mailing list earlier and they > worked for me: > > curl -O > "https://springdale.math.ias.edu/data/pu

Re: [qmailtoaster] Re: SDL8 test install hiccups

> Thanks, Peter. > > Can you post the migration notes the list? > > I'll make it a script. > > Eric > > On 12/31/2020 3:52 AM, Peter Peltonen wrote: > > HI, > > > > SDL 8 has the same EOL as RHEL 8: May, 2029. > > > > SDL existed before CentOS,

Re: [qmailtoaster] Re: SDL8 test install hiccups

2/30/2020 3:17 PM, r...@mattei.org wrote: > > So the question here is CentOS 8 eol is 2021 not sure it’s even worth that > route. Anyhow that could be a totally diff topic but CentOS 7 looks to have a > longer support life now. > > Il giorno 30 dic 2020, alle ore 12:08, Peter Pel

[qmailtoaster] Re: SDL8 test install hiccups

, Dec 30, 2020 at 5:07 PM Peter Peltonen wrote: > > Hi, > > I tried installing latest QMT using Eric's qt_install_cos8.sh script. > > I have a CentOS 8 VM that I had converted to Springdale Linux 8. > > > I ran into a few issues: > > 1) MariaDB password setup fa

[qmailtoaster] SDL8 test install hiccups

Hi, I tried installing latest QMT using Eric's qt_install_cos8.sh script. I have a CentOS 8 VM that I had converted to Springdale Linux 8. I ran into a few issues: 1) MariaDB password setup failed somehow. Maybe because I had MariaDB already installed on this server? I could not access the

Re: [qmailtoaster] TLS v1.2 on Centos 6, Thunderbird 78

Hi, This problem is also present on older Dovecot on centos5 I still have installed: dovecot-2.0.17-2.qtp -> the older dovecot does not support the possibility to disable sslv3 Eric in your repo's cos5 downloads I saw a more recent dovecot that should support this:

[qmailtoaster] How to modify autorespond to not include reply in the vacation msgs?

I have autorespond-toaster-2.0.5-1.4.0 installed on my server. Is there a way to modify it server-wide so that it would not include the original email in the reply? I know it sets the .qmail file where a flag can be used to disable it, but how do I change the default behaviour to set that flag?

Re: [qmailtoaster] Encryption problems with Apple devices

you use that option (extensions) apple/microsoft products can give > you an option to trust your certificate. > > Greetings! > > > El 22/08/2020 a las 04:28 a. m., Peter Peltonen escribió: > > I have an old COS5 qmailtoaster > > > > Since yesterday App

[qmailtoaster] Encryption problems with Apple devices

I have an old COS5 qmailtoaster Since yesterday Apple devices using its Mail program have been receiving messages about certificate being not valid. Its a wildcard certificate that is being used elsewhere as well so it should be valid (it has not been expired). All other devices / clients seem

Re: [qmailtoaster] Getting multiple copies of emails

In the past I remember this kind thing happening with the old Courier IMAP. Upgrading to Dovecot solved the issue. Buit you probably are running Dovecot already? Best, Peter On Thu, May 30, 2019 at 3:14 AM Jeff Koch wrote: > > > Hi List: > > All of a sudden this morning everyone using one of

Re: [qmailtoaster] [solved] ClamAv Soft Reject errors

lamavcnt50.html > > This tested fine for me, as always, user at your own risk. > > Eric > > On 3/25/2019 3:28 AM, Peter Peltonen wrote: > > Eric, > > is it possible for you to build these for COS5 32bit (i386) also? > > Best, > Peter > > On Mon, Mar 25, 2019

Re: [qmailtoaster] [solved] ClamAv Soft Reject errors

Eric, is it possible for you to build these for COS5 32bit (i386) also? Best, Peter On Mon, Mar 25, 2019 at 8:30 AM Eric Broch wrote: > > > Here's the updated ClamAV with Curl Devel >= 8.32 rpm version > > http://www.qmailtoaster.com/newopensslclamavcnt50.html > > > Thanks for taking the lead

Re: [qmailtoaster] ClamAv Soft Reject errors

I got hit with this too... Would it be possible for you Eric to make i386 version available as well? And do I need to get newer pcre from somewhere? I have pcre-6.6-9.el5 installed... Best, Peter On Thu, Mar 21, 2019 at 9:53 PM Eric Broch wrote: > > Well, I could be wrong but while installing

Re: [qmailtoaster] TLS issue how to fix it

Replying to myself:yes at least for me everything worked ok after updating tlsserverciphers with command/usr/bin/openssl101e ciphers > tlsserverciphersCheers,Peter On Wed, Mar 6, 2019 at 3:58 PM Peter Peltonen wrote: > > Hi, > > After upgrading COS5 openssl I still encounter these

Re: [qmailtoaster] TLS issue how to fix it

Hi, After upgrading COS5 openssl I still encounter these errors: TLS connect failed: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure; connected to Am I missing something, should I update also tlsserverciphers after the openssl upgrade? Best, Peter On Tue, Dec

[qmailtoaster] Re: messages forwarded by qmail not encrypted

Stupid me: I had two servers and the forwarding account I was testing against had TLS turned off for all outgoing SMTP... So everything working as expected! Sorry for the noise, Peter On Sun, Feb 24, 2019 at 11:38 PM Peter Peltonen wrote: > > Hi, > > I upgraded my TLS setup on my

[qmailtoaster] messages forwarded by qmail not encrypted

Hi, I upgraded my TLS setup on my old toaster as instructed by Eric here: https://www.qmailtoaster.org/newopensslcnt50.html Everything else fine except: 1) if I send a message to a gmail account directly, the message is encrypted 2) if I setup a forward to this gmail account in my toaster say

Re: [qmailtoaster] TLS issue how to fix it

Easiest for COS5 is to turn off TLS entirely for SMTP: 1. create dir /var/qmail/control/tlshosts 2. create file /var/qmail/control/tlshosts/exhaustivelist If someone knows if this can cause any incompatibilities between any receiving servers, please share your experiences? Best, Peter On Thu,

Re: [qmailtoaster] Slightly Off-Topic: CentOS 7 MariaDB Packages

Hi, what client are you referring to? The only client I am aware of is the CLI mysql command /usr/bin/mysql and that is included in the mariadb package: # rpm -qf /usr/bin/mysql mariadb-5.5.60-1.el7_5.x86_64 Best, Peter On Tue, Nov 13, 2018 at 5:13 AM Roxanne Sandesara wrote: > > I have a QMT

Re: [qmailtoaster] bayes setup

Very generic question about teaching spamassassin: If one runs sa-learn against a maildir folder for learning more spam, should that folder: a) contain messages that spamassasin has failed to classify spam or b) contain messages that spamassasin has failed to classify spam AND messages that

Re: [qmailtoaster] rainloop

Great to see that Eric has found Rainloop as well :) One thing I didn't manage to get working was reCAPTCHA witht he pluging provided Have you tried that / succeeded in the installation? Even I have the plugin active I do not see anything related to it in the index.php source code... Best,

Re: [qmailtoaster] Rainloop removed squirrelmail

Hi, I've been now playing with Rainloop for a few days and really like it. It is simple to setup, it is fast and responsive and it has support for accounts on different IMAP servers. The only thing lacking is the documentation: it would be great to createa a plugin for setting vacation message /

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

S), then just use PLAIN auth and ignore the password encryption schemes > all together. The advantage of this is that PLAIN will never require > reconfiguration because it has become "broken". > > Again, I hope with is helpful (and accurate). > > -Andy >

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

his scenario, a PLAIN auth would be very dangerous. > > Hope this helps. > > -Andy > > > On 8/13/2018 11:43 PM, Peter Peltonen wrote: >> Thanks for the suggestions! >> >> So if I have only plain and login auth mechanisms enabled, what does >> t

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

devices / clients for same account? Best, Peter On Tue, Aug 14, 2018 at 5:52 AM, Eric Broch wrote: > I'd remove DIGEST-MD5 from 'auth_mechanisms'. > > > > On 8/13/2018 3:01 PM, Peter Peltonen wrote: >> >> I have a user with Outlook 2016 having this error appea

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

I have a user with Outlook 2016 having this error appearing in the Dovecot logs and not being able to login when it occurs The strange thing is that if I restart dovecot then the Outlook can login and no error: method=DIGEST-MD5, rip=xxx, lip=yyy, mpid=23280, TLS What I have for auth mechanisms

[qmailtoaster] problem with DMARC and forwarded messages

Has anyone encountered the following problem before: msg from us...@non-qmail-host-with-dmarc-in-use.com is sent to us...@qmailtoaster-domain.com and then this message is forwarded from the toaster to us...@gmail.com so userA is using DMARC for his domain when forwarding the message my toaster

Re: [qmailtoaster] Asking the password frequently

Not sure if this relates to any of your problems: I had a few days ago problem with a Outlook 2016 stopping receiving email suddenly. I chased this down to Outlook claming the server did not support the correct authentication method, which was strange as nothing had changed on the server side

Re: [qmailtoaster] Clamav service stopped

Stumbled on this on the CentOS mailing list: it seems 32bit CentOS6 has a zlib that doesn't play along with the new clamav: https://bugzilla.redhat.com/show_bug.cgi?id=1600458 I am wondering if this is an issue with qmailtoaster's clamav as well? Peter On Thu, Jul 12, 2018 at 9:40 AM,

Re: [qmailtoaster] Upgrading openssl in an old Qmailtoaster install

ltoaster.org/newopensslcnt50.html > > Eric > > > > On 6/29/2018 4:51 AM, Peter Peltonen wrote: >> >> Great, thanks for sharing! >> >> One question: >> >> Eric had produced an RPM for qmail 1.03-1.3.23.i386 with the CNAME >> lookups removed. >&

Re: [qmailtoaster] Upgrading openssl in an old Qmailtoaster install

Great, thanks for sharing! One question: Eric had produced an RPM for qmail 1.03-1.3.23.i386 with the CNAME lookups removed. Yours is 1.03-1.3.22 and with CNAME lookups enabled I assume. How would one migrate the changes you did to Eric's version, as I would like to have both: newer TLS

Re: [qmailtoaster] Upgrading openssl in an old Qmailtoaster install

I would be interested in this solution as well. How did you upgrade openssl? Did you follow this tutorial https://miteshshah.github.io/linux/centos/how-to-enable-openssl-1-0-2-a-tlsv1-1-and-tlsv1-2-on-centos-5-and-rhel5/ or something else? Best, Peter On Wed, Jun 27, 2018 at 8:44 AM, Brian

Re: [qmailtoaster] SOLVED - Re: [qmailtoaster] QMT - Problem with MessageID on Vacation Message Responses

Eric - any plans to create an rpm for the new autorespond 2.06 version? I've also opened a new issue with it at GitHub: messages containing scandinavian letters are quoted wrong in the replies generated by the autoresponder. Best, Peter On Thu, Jan 18, 2018 at 6:14 AM, Jeff Koch wrote: > There

Re: [qmailtoaster] Re: CNAME_lookup_failed_temporarily._(#4.4.3)/

EM; > - break; > - } > - } > - if (r == 2) return loop; > -} > - } > - return DNS_HARD; /* alias loop */ > + return 0; > } > > #define FMT_IAA 40 > > > > > > On 4/24/2018 12:48 AM, Peter Peltonen wrote: > > No i

[qmailtoaster] CNAME_lookup_failed_temporarily._(#4.4.3)/

I am getting this error when sending to the tyks.fi domain: 2018-04-18 18:15:18.787618500 starting delivery 32313: msg 2232943 to remote ***@tyks.fi 2018-04-18 18:16:01.777845500 delivery 32313: deferral: CNAME_lookup_failed_temporarily._(#4.4.3)/ I've been searching for this error and found the

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

Hi, I was hit by this error on a server running qmail-toaster-1.03-1.3.22 This patch is not included by default in the toaster qmail package? Strange thing is that the error came from a host that has proper MX records (MX pointing to a A record, not CNAME), so I am wondering what exactly is

[qmailtoaster] where are forwards created in qmailadmin stored?

Hi, Aliases are stored in MySQL and can be managed with the valias command from cmd line. But what about forwards created for an existing account via qmailadmin? I thought that would create a .qmail file but just tested it and I found I was wrong. So where is the forward data stored? What I am

Re: [qmailtoaster] ERROR: accept() failed

First thing that comes to my mind is to check qmail directory ownerships and permissions? On Fri, Jan 26, 2018 at 12:24 PM, Michele Federici wrote: > Hi, > > I have a qmail server that today returns in the smtp log "mail server > temporarily rejected message (# 4.3.0)". > >

Re: [qmailtoaster] connection issues again.

Never worked with fail2ban before. Care to share your config for qmailtoaster? On Fri, Dec 29, 2017 at 8:56 PM, Eric Broch wrote: > Hi Tony, > > I see this more than I'd like. Sometimes I hear my server cranking away > and upon investigation one day (tail -f

Re: [qmailtoaster] logging subjects of sent / received email

ds of the mysql/maria vpopmail alias db. >> >> Eric >> >> >> On 11/13/2017 6:08 AM, Peter Peltonen wrote: >>> Hi, >>> >>> I would need to gather a log of dates and subjects of sent + reiceived >>> emails for one domain. >>>

[qmailtoaster] logging subjects of sent / received email

Hi, I would need to gather a log of dates and subjects of sent + reiceived emails for one domain. Can that be done with our toaster? Googling I found this advice for stock Qmail: " Just rebuild qmail with QUEUE_EXTRA set[1], install DJB's mess822 package[2], and put the following line in

Re: [qmailtoaster] {Disarmed} Re: [qmailtoaster] I am seeing this in my send..

, Remo Mattei <r...@mattei.org> wrote: > Centos 7 > > TY > > On Jul 19, 2017, at 12:25 PM, Eric Broch <ebr...@whitehorsetc.com> wrote: > > Hi Peter, > > What OS were you using? > > > On 7/19/2017 12:49 PM, Peter Peltonen wrote: > > How are you fi

Re: Re: [qmailtoaster] I am seeing this in my send..

How are you finding z-push resource wise? When I tried it couple of years ago I found it eating memory like a monster... Regards, Peter On Wed, Jul 19, 2017 at 9:05 PM, Eric Broch wrote: > Z-push: > > http://www.qmailtoaster.org/msas.html > > > On 7/19/2017 11:53 AM,

Re: [qmailtoaster] setting account forward from command line

have a .qmail file in place > (as I do) this will overwrite it. > > # echo "@destination.com" > > /home/vpopmail/domains/origin.com/user/.qmail > # chmod 0600 /home/vpopmail/domains/origin.com/user/.qmail > # chown vpopmail:vchkpw /home/vpopmail/domains/origin.com

[qmailtoaster] setting account forward from command line

A common task I encounter when managing toaster accounts is setting up / modifying or removing forwards for existing email accounts. Can this be done from command line? I find it very cumbersome to have to do it via qmailadmin. And I mean here real email accounts with inboxes, not aliases that

Re: [qmailtoaster] QMT Instructions (bare bones)

Thats a good starting point, thanks! Best, Peter On Mon, Dec 14, 2015 at 8:20 PM, Eric wrote: > https://www.whitehorsetc.com/files/qmail/qmail.php > > The CentOS 5 link resolves to > http://wiki.qmailtoaster.com/index.php/Configuration. I don't think anyone > is

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

from one place and one would not need to search the archives. Best, Peter On Sat, Dec 12, 2015 at 5:09 PM, Eric <ebr...@whitehorsetc.com> wrote: > That's a great idea. Does anyone have access to the wiki? If not I could > create a page on my site. > > > On 12/12/2015 6:13 AM,

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

Hi, Thanks for Eric for all his work. How about a temporary website that puts all these bits of information together? Best, Peter On Sat, Dec 12, 2015 at 12:58 AM, Angus McIntyre wrote: > Thank you, Eric. > > Ansible is pretty nice: > > http://www.ansible.com/get-started > >

Re: [qmailtoaster] Integrated perdition pop3/imap4 proxy

Hi, On Tue, Jan 20, 2015 at 5:09 PM, Nikolay Mitev mite...@gmail.com wrote: Integrated perdition pop3/imap4 proxy and all received emails started to duplicate ... Don't know about proxies, but message duplication has been caused by courier-imap, which can be fixed by switching to dovecot

Re: [qmailtoaster] Concerns for Updates, Viability, Future of Qmailtoaster

Hi, My 2 cents on this below: On Fri, Jan 16, 2015 at 5:54 AM, Edwin C ecasim...@hotmail.com wrote: How about you guys start charging for an annual fee or something? Just to assure that qmailtoaster gets updated all the time: dovecot, spamassassin, clamav... the rest of the stuff. Then

Re: [qmailtoaster] Forcing authentication (submission) for all users

Dan, that sounds like a good way to setup sending messages. You don't have any idea about the two other issues I asked about, blacklisting local domains and local mail delivery (see my msg below)? Best, Peter On 12/15/2014 3:33 PM, Peter Peltonen wrote: Hi, I would like to force all users

Re: [qmailtoaster] how to block connections

Hi, On Mon, Dec 15, 2014 at 5:08 AM, Eric Broch ebr...@whitehorsetc.com wrote: I think it's a connect and disconnect. I get them a lot. I'm not sure what they are. If I telnet to my own server on port 25 from a remote location and quit the telnet connection on port 25 right away it has the

[qmailtoaster] how to block connections

Hi, In my smtp log I see lots of this kind of connection entries: @4000548e1bdf373b6974 tcpserver: pid 20363 from 103.225.128.9 @4000548e1bdf373b6d5c tcpserver: ok 20363 myserver:myip :103.225.128.9::57521 These are coming from different IPs from 103.225.128.0/255.255.255.0 network I

Re: [qmailtoaster] Re: Need help: How to setup qmailtoaster

Hi Jim, On Fri, Nov 7, 2014 at 10:04 PM, Jim Shupert jshup...@pps-inc.com wrote: Friends, I realize that it is suggested to install cent os with a minimal install but is it OK to install as 'standard desktop' ;; with the selfish reason to have available the stuff the standard desktop

Re: [qmailtoaster] Re: dovecot upgrade

Hi, On Sat, Oct 18, 2014 at 3:03 AM, Eric Shubert e...@shubes.net wrote: If you don't use the spambox option or otherwise use maildrop, you might be able to simply remove maildrop-toaster. There might be some dependency with qmail-admin though, I'm not sure. I do use maildrop, so removing it

Re: [qmailtoaster] Re: Disable SSLv3, POODLE: SSLv3 vulnerability

Hi, On Thu, Oct 16, 2014 at 1:51 AM, Eric Shubert e...@shubes.net wrote: In order to disable SSLv3, you need to change your cyphers list in /etc/dovecot/toaster.conf file for dovecot, and /var/qmail/control/tlsserverciphers for qmail-smtpd. If you turn off SSLv3, that includes TLS, so you'd

[qmailtoaster] dovecot upgrade

As one needs at least dovecot version 2.1 to be able to disable SSLv3, I would need to upgrade my old dovecot-2.0.17-2.qtp packages to newer ones. I thought I just grab the packages from the latest bunch of .qt pacakges, but upgrading to those didn't work out: # rpm -Fvh

[qmailtoaster] Character encoding issue with Squirrelmail + HTML messages

When a user receives an HTML multipart message (for example from outlook.com), I have noticed the following: * the non-HTML version of the message is displayed by default in Squirrelmail, and in this version umlauts are displayed incorrectly (as question marks) * if one opens the HTML attachment

Re: [qmailtoaster] Security - TLS/SSL ciphers

Hi, On Tue, Mar 25, 2014 at 2:27 AM, Eric Shubert e...@shubes.net 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

Re: [qmailtoaster] Re: Virtualizing a QMT server!

Hi, On Sun, Mar 2, 2014 at 3:50 AM, Tony White t...@ycs.com.au wrote: Hi Eric, Thanks for the pointers but it still does not answer my question? Has anyone converted a running server to a VM?. I've done this with my servers, converting to Xen VMs was not that hard and you can find

Re: [qmailtoaster] Virtualizing a QMT server!

Hi, On Sat, Mar 1, 2014 at 7:07 PM, Unai Rodriguez u...@sysbible.org wrote: On Saturday, 01 March, 2014 09:49 PM, Tony White wrote: Hi folks, Has anyone tried to virtualize a QMT server yet? Has it worked? If so can you tell me how you did it so I can do it for my server please? I've

Re: [qmailtoaster] Any writeups out there on blocking email based on pattern matching?

Hi, On Mon, Nov 18, 2013 at 12:08 AM, Kelly Cobean kcob...@vipercrazy.comwrote: So I'm wondering if anyone knows of any good writeups or tutorials on how to do pattern based mail dropping or other suggestions on how to cut down on the garbage. I don't want SA to drop the messages because

Re: [qmailtoaster] IMAP Connection Limit

Hi Dan, On Wed, Nov 13, 2013 at 7:43 PM, Dan McAllister q...@it4soho.com wrote: Greeting Family/Team: Question from a client that I haven't been able to answer: - Is there a limit to the number of simultaneous IMAP connections on a QMT solution? - If so, where is it controlled? I think

Re: [qmailtoaster] dropping Maildrop?

Hi, On Tue, Nov 12, 2013 at 4:13 AM, Eric Shubert e...@shubes.net wrote: Is anyone really using maildrop filters? It seems to me that some time ago there were a couple people who were. I am! They are very useful as one can integrate easily bash scripts to them. I know the 'spambox'

Re: [qmailtoaster] Re: how to disable local delivery for one virtual domain

Hi, On Wed, Nov 6, 2013 at 1:14 AM, Eric Shubert e...@shubes.net wrote: On 11/05/2013 01:48 PM, Peter Peltonen wrote: Hi, I have a virtual domain on a toaster which mails go nowadays to Office365 (- MX is pointint there). I would still need to offer IMAP service for this domain

Re: [qmailtoaster] Re: how to disable local delivery for one virtual domain

Hi, Thanks for your clarification Dan. One question: On Wed, Nov 6, 2013 at 6:29 PM, Dan McAllister q...@it4soho.com wrote: I'm johnny-come-lately on this, and Peter nearly nailed it: 1) If you remove DOMAIN-X.com from *rcpthosts*, you no longer accept mail for it at all -- so it probably

Re: [qmailtoaster] Anyway to Block all login auth attempts outside of te US?

Hi, On Tue, Nov 5, 2013 at 7:19 AM, LHTek dennywjo...@yahoo.com wrote: Hello, I've noticed via the logs that the vast majority of failed login attempts originate from IP's that are outside of the USA. Anyway to configure QMail to simply block any auth request that comes from outside the US?

[qmailtoaster] how to disable local delivery for one virtual domain

Hi, I have a virtual domain on a toaster which mails go nowadays to Office365 (- MX is pointint there). I would still need to offer IMAP service for this domain, but if an email is sent through this toaster to that virtual domain, it should not be delivered locally to the toaster inbox, but it

  1   2   3   4   >