Well I have to say it’s working really well the 5.11 and only doing qmail with the web for qmailadmin .. So not sure to move things over yet..
However I have my personal one on qmailtoaster cents 7 super good! But the auth has changed so moving people because of tither security on the imap .. will require a little bit of training for them.. or I need to see how to adopt the dovecot 1.x auth into the new one .. but again.. that’s not the plan! > On Dec 18, 2017, at 12:08 PM, Sean Murphy <[email protected]> wrote: > > I know, it's nerve-wracking, isn't it? > > > On 12/18/2017 3:04 PM, Remo Mattei wrote: >> I do have that too not sure to move them over yet! >> >> Il giorno 18 dic 2017, alle ore 11:43, Sean Murphy >> <[email protected]> ha scritto: >> >> Eric, >> >> I just watched qmail reject a new address from the date domain. >> >> The syntax is indeed .@*\.date$ in badmailfrom. >> >> I'm still running an older version of the toaster on a CentOS 5.11 machine. >> I have a CentOS 7 box up and ready for a migration, but I'm loathe to move >> over from a machine that's working well even though it's past its date. I >> suppose the time draws nigh, anyway. >> >> And, for what it's worth, the latest rash of spam seems to be from IPs in >> Italy. >> >> Thanks! >> >> -Sean >> >>> On 12/18/2017 2:25 PM, Eric Broch wrote: >>> I put in a spam gateway, specifically, a Sonicwall device because I could >>> never control spam using stock qmailtoaster stuff until Dspam (to much >>> fiddling), but to your question: >>> >>> It'd be preferable to put an entry in /etc/spamdyke/blacklist_senders file >>> '@domain.tld' so email would never reach the smtp daemon. >>> >>> Here's the badmailfrom wiki anyway: >>> http://wiki.qmailtoaster.com/index.php/Badmailfrom >>> >>> >>>> On 12/18/2017 11:27 AM, Sean Murphy wrote: >>>> Greetings all, >>>> >>>> We are seeing a boatload of spammy mail from new top level domains, <dot> >>>> date in particular. Spamassassin is catching most of them and flagging >>>> them as spam, but I'd like to block the domain entirely. Is this possible >>>> in badmailfrom? Will it support a wildcard such as .@*\.date$, or is the >>>> syntax different? I realize there may be legitimate businesses emailing >>>> from that domain at some point in the future, but that future is certainly >>>> not now. >>>> >>>> Also, if there is a better way of doing this, I am open to suggestions. >>>> >>>> Best, >>>> >>>> Sean P. Murphy >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
signature.asc
Description: Message signed with OpenPGP
