[Bug 6848] HTML URI spoofing detection
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6848 Kevin A. McGrail changed: What|Removed |Added Resolution|--- |FIXED CC||kmcgr...@apache.org Status|NEW |RESOLVED --- Comment #9 from Kevin A. McGrail --- Let's give it another week ;-) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 6848] HTML URI spoofing detection
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6848 Giovanni Bechis changed: What|Removed |Added CC||giova...@paclan.it --- Comment #8 from Giovanni Bechis --- committed 5 years ago, I think it is time to close the bz. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 6664] check_freemail_header() misses many domains
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=6664 --- Comment #9 from Giovanni Bechis --- Created attachment 5490 --> https://bz.apache.org/SpamAssassin/attachment.cgi?id=5490&action=edit fix for multiple emails in headers As the original post said, if there are multiple emails in a Reply-To header as on test1 example it wont get catched. Adding an option to be able to do more tests is an additional enhancement and a second step. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7518] spamc bounces e-mail with more than 16 receipients
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7518 --- Comment #5 from Dirk --- (In reply to Benny Pedersen from comment #4) > http://postfix.1071664.n5.nabble.com/Split-multiple-recipient-mail-td48458. > html > > its multirecipient limit > > _destination_recipient = 1 > > mta stage is no limit, but content filter transport should hae this in > main.cf > > sorry for write after its declared invalid :=) Thanks, that helps as a workaround for this behaviour. Setting the limit to 15 works fine now. Dirk -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7517] Universal Acceptance Outreach: j...@decorum.link New gTLD email addresses are spammed
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7517 --- Comment #7 from Kevin A. McGrail --- Stop using bugzilla, please. This is not a development or a bug issue. Post on us...@spamassassin.apache.org. -- You are receiving this mail because: You are the assignee for the bug.
Re: Universal Acceptance Outreach: j...@decorum.link New gTLD email addresses are spammed [ ref:_00D61 [ ref:_00D616tJk._50061FvoUR:ref ]
The attachment is unparseable the way it was attached. However, from the text I can see, this is a configuration and domain issue having little to do with development. You'll want to discuss this on us...@spamassassin.apache.org, not dev@. My $0.02: - It sounds like the sender has gotten himself on blacklists which needs to be investigated 1 by 1. - It also sounds like the recipients have a poorly configured anti-spam implementations. I don't personally see why ICANN is involved in this but kudos to you for giving them free support. I'd recommend both the sender or recipient are at the level where they likely need to hire a consultant to advise them on email deliverability. Regards, KAM On 12/6/2017 7:23 AM, ICANN Global Support Center wrote: Dear all, I appreciate your rapid follow-up messages. I have forwarded the instructions and feedback you have provided to the reporter. I am including his response below for your review. Attached you can also find the screenshots the reporter mentioned in his response. Reporter's response: --- Because their system is marking my domain address as spam, the rules internal further block the mail in each person's system. I have spoken with the respective company's IT people which is how I became aware of Spam Assassin. It appears from our own investigation that Spam Assassin might be using some old possibly bad black list servers to determine what should be marked as Spam. These servers are not recognized by tools like MXtoolbox or DNSStuff for listed black lists. Both of these organizations I am dealing with have tried to configure their Spam Assassin software to stop the mislabeling. However, in doing so for the domain frankweyer.com it caused the other domain to be blocked. The previous attachment I provided was a direct result of what the Spam Assassin gave back according to the IT department at these locations. --- I hope to hear your recommendations and support at this point. Please let us know if you need additional information. Best regards, Seda Akbulut Lead Global Support Analyst ICANN Global Support Team
[Bug 7517] Universal Acceptance Outreach: j...@decorum.link New gTLD email addresses are spammed
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7517 --- Comment #6 from seda.akbu...@icann.org --- Dear Kevin and John, I appreciate your rapid follow-up messages. I have forwarded the instructions and feedback you have provided to the reporter. I am including his response below for your review. Attached you can also find the screenshots the reporter mentioned in his response. Reporter's response: --- Because their system is marking my domain address as spam, the rules internal further block the mail in each person's system. I have spoken with the respective company's IT people which is how I became aware of Spam Assassin. It appears from our own investigation that Spam Assassin might be using some old possibly bad black list servers to determine what should be marked as Spam. These servers are not recognized by tools like MXtoolbox or DNSStuff for listed black lists. Both of these organizations I am dealing with have tried to configure their Spam Assassin software to stop the mislabeling. However, in doing so for the domain frankweyer.com it caused the other domain to be blocked. The previous attachment I provided was a direct result of what the Spam Assassin gave back according to the IT department at these locations. --- I hope to hear your recommendations and support at this point. Please let us know if you need additional information. Best regards, Seda Akbulut Lead Global Support Analyst ICANN Global Support Team -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7518] spamc bounces e-mail with more than 16 receipients
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7518 Benny Pedersen changed: What|Removed |Added CC||m...@junc.eu --- Comment #4 from Benny Pedersen --- http://postfix.1071664.n5.nabble.com/Split-multiple-recipient-mail-td48458.html its multirecipient limit _destination_recipient = 1 mta stage is no limit, but content filter transport should hae this in main.cf sorry for write after its declared invalid :=) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7518] spamc bounces e-mail with more than 16 receipients
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7518 Kevin A. McGrail changed: What|Removed |Added Status|REOPENED|RESOLVED CC||kmcgr...@apache.org Resolution|--- |INVALID --- Comment #3 from Kevin A. McGrail --- (In reply to Dirk from comment #2) > As you can see in the log snipplet there is an error coming from spamc which > causes postfix to bounce the email. > > The error states a configuration error in spamc.conf, which is not true as > you can see also in my message. > > So i think i am not trying to use this tracker as a support tool! > > SPAMC produces this error when checking emails with more than 16 receipients > (double-checked with test-emails). > > So do you still think the is not a bug in spamc? Configuration issue NOT a bug. This is not a support form. Subscribe to us...@spamassassin.apache.org and discuss there. Do not reopen bugs. KAM -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7518] spamc bounces e-mail with more than 16 receipients
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7518 Dirk changed: What|Removed |Added CC||dirk.traen...@nwowhv.de Status|RESOLVED|REOPENED Resolution|INVALID |--- --- Comment #2 from Dirk --- As you can see in the log snipplet there is an error coming from spamc which causes postfix to bounce the email. The error states a configuration error in spamc.conf, which is not true as you can see also in my message. So i think i am not trying to use this tracker as a support tool! SPAMC produces this error when checking emails with more than 16 receipients (double-checked with test-emails). So do you still think the is not a bug in spamc? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7518] spamc bounces e-mail with more than 16 receipients
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7518 AXB changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #1 from AXB --- SpamAssassin does not bounce mail. I can only tag and or log. Please, do not abuse the bug tracker as a support tool. Use SA user mailing list for such questions. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 7518] New: spamc bounces e-mail with more than 16 receipients
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7518
Bug ID: 7518
Summary: spamc bounces e-mail with more than 16 receipients
Product: Spamassassin
Version: 3.4.0
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: spamc/spamd
Assignee: dev@spamassassin.apache.org
Reporter: dirk.traen...@nwowhv.de
Target Milestone: Undefined
Hi,
on monday one of our users reported a bounced outgoing email. After analysing
the maillog we found 17 bounces of the same postfix email-queue-id.
This is the error-text:
Dec 4 17:24:32 nwomx postfix/pipe[40200]: 5973C906554: to=,
relay=spamchk, delay=0.18, delays=0.12/0.01/0/0.05, dsn=5.3.5, status=bounced
(local configuration error. Command output: Exceeded max number of arguments
(24) in /etc/mail/spamassassin/spamc.conf
spamc.conf:
-s 268435456
After some tests we can reproduce this behavoiur when sending an email to more
than 16 receipients.
Any ideas?
Regards
Dirk
Environment:
OS: CentOS Linux release 7.4.1708 (Core)
Spamassassin: 3.4.0-2.el7
Postfix-Integration:
spamchk unix - n n - - pipe
flags=Rq user=spam argv=/usr/bin/spamc -e /usr/sbin/sendmail -oi -f ${sender}
${recipient}
--
You are receiving this mail because:
You are the assignee for the bug.
