Hi List,
I'm having problems receiving mails from a list (assuming LISTSERV).
Messages getting rejected with "553 Wrong mailbox syntax". I think
the error is caused by several asterisks in the MAIL FROM argument.
As I read in RFC 821, asterisks are allowed in , but
even with quotes in the local
On 04.07.2016 11:25, Martin Bley wrote:
> Any hints, where to screw would be appreciated.
You'll find that this literal translation of a German expression does
not mean what apparently think it does in English... ;-)
As for helping with your problem at hand: samples of the incoming
e-mails and "
Hi,
We have an internet facing MX server whereby all users authenticate their
outgoing connection to submit emails via port 587. This MX server routes
incoming mail for our domain to an internal postfix smtp server which then
delivers mail to local imap servers.
The internal postfix smtp server u
[Please ignore my last email as this was sent by mistake before it was
finished]
Hi,
We have an internet facing MX server whereby all users authenticate their
outgoing connection to submit emails via port 587. This MX server routes
incoming mail for our domain to an internal postfix smtp server w
Bill, sorry if I'm being inconvenient, but my knowledge of Postfix is very
basic.
I understand but I do not know how to do. Could you explain better how I do
it?
Thank you
Marcelo
P.S. Yes, I offer a submission (port 587) service.
--
View this message in context:
http://postfix.1071664.n5.
Martin Bley:
> Hi List,
>
> I'm having problems receiving mails from a list (assuming LISTSERV).
> Messages getting rejected with "553 Wrong mailbox syntax". I think
I have searched every Postfix version that was ever released,
and there is no Postfix version that says "Wrong mailbox syntax".
Pl
Hi Wietse,
wie...@porcupine.org:
I have searched every Postfix version that was ever released,
and there is no Postfix version that says "Wrong mailbox syntax".
Please show the actual input and response.
sorry, you are right. I noticed, that the SMTP traffic is filtered
by a security gateway.
Quoting wie...@porcupine.org:
j...@conductive.de:
Quoting wie...@porcupine.org:
> Wietse Venema:
>> Joel Linn:
>> > Why is it chosen to "not support stored procedures" instead of
adding two
>> > lines of code?
>>
>> The original mysql client may well have been written at a time that
>> st
j...@conductive.de:
> So yes, looping results and generating an error for more than one
> result is sufficient to prevent hiccups in following queries.
>
> That bugfix however would be very close to my suggested change.
> Is there someone maintaining the mysql portion of postfix,
> I mean except y
I am running mysql here to manage my postfix aliases, and keep the tables in db
files as normal
virtual_alias_maps = mysql:/usr/local/etc/postfix/mysql-virtual-alias-maps.cf
virtual_gid_maps = static:5000
virtual_mailbox_base = /var/mail/vhosts
virtual_mailbox_domains =
mysql:/usr/local/etc/post
On 7/4/2016 5:55 AM, Jack Beanstallk wrote:
> [Please ignore my last email as this was sent by mistake before it
> was finished]
>
> Hi,
>
> We have an internet facing MX server whereby all users authenticate
> their outgoing connection to submit emails via port 587. This MX
> server routes incom
On 07/04/16 11:05, postmas...@quantum-radio.net wrote:
> I am running mysql here to manage my postfix aliases, and keep the
> tables in db files as normal
This doesn't directly solve your specific problem, but ... have you
considered using GNU Mailman instead of Majordomo? Majordomo is
terribly o
Thanks Phil
I hadn't considered it, but I will have a look at it. I'm on OSX too, which can
make a difference.
I'm so close to having Major-domo work, but maybe because I'm not using the old
standard /etc/aliases it never will. I can't see how I can get this to work
otherwise.
But thanks, I'll
On 2016-07-04 19:10, Phil Stracchino wrote:
On 07/04/16 11:05, postmas...@quantum-radio.net wrote:
I am running mysql here to manage my postfix aliases, and keep the
tables in db files as normal
This doesn't directly solve your specific problem, but ... have you
considered using GNU Mailman in
On 07/04/2016 03:30 PM, j...@conductive.de wrote:
>
> Quoting wie...@porcupine.org:
>
>> j...@conductive.de:
>>>
>>> Quoting wie...@porcupine.org:
>>>
>>> > Wietse Venema:
>>> >> Joel Linn:
>>> >> > Why is it chosen to "not support stored procedures" instead of
>>> adding two
>>> >> > lines of code
Quoting John Fawcett :
I can propose a code submission to add stored procedure support (based
on the proof of concept code from 2008), but the biggest part will be
doing the testing and non regression testing not the actual coding.
I believe the best approach to adding stored procedure support
On 3 Jul 2016, at 0:36, li...@lazygranch.com wrote:
This is probably more of a freebsd question, but it seems to me that
Postfix should be hogging (bound) to the mail ports, so if something
is sending email, it has to be using Postfix.
That's not how TCP/IP or Postfix works. Postfix binds lis
On 07/04/16 14:47, Benny Pedersen wrote:
> On 2016-07-04 19:10, Phil Stracchino wrote:
>> On 07/04/16 11:05, postmas...@quantum-radio.net wrote:
>>> I am running mysql here to manage my postfix aliases, and keep the
>>> tables in db files as normal
>>
>> This doesn't directly solve your specific pr
On 4 Jul 2016, at 7:10, mmgomess wrote:
Bill, sorry if I'm being inconvenient, but my knowledge of Postfix is
very
basic.
I understand but I do not know how to do. Could you explain better how
I do
it?
Thank you
Marcelo
P.S. Yes, I offer a submission (port 587) service.
This makes it si
On 2016-07-04 23:47, Phil Stracchino wrote:
mailman breaks dkim, does the outdated one do this aswell ?
Unfortunately a *LOT* of things break DKIM and DMARC at this point in
time. However, the upcoming ARC standard for authentication relaying
is
expected to improve that state of affairs.
"reject_unverified_sender" not used.
The VPS is 13 months old and I never ran rkhunter on it. Very lame in my part.
However, no rootkit found. It did find some symbolic links that went nowhere
regarding perl, which I deleted once I verified the problem was common. I also
ran rkhunter on all li
21 matches
Mail list logo
