Still an issue in Trusty, but fixed in the current release.
** Also affects: python-bleach (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: python-bleach (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: python-bleach (Ubuntu)
Status: Confirmed =>
I've just uploaded an update to Debian that updates README.Debian (which
I neglected to do when adding the service file) that explains how to
handle things in lieu of using /etc/defaults, which is apparently not a
very systemd thing to do.
** Changed in: opendmarc (Ubuntu)
Status: New =>
Unfortunately there isn't enough information here to make the bug
actionable. We need to know how it got in an inconsistent state.
Please check /var/log/apt/term.log (or possibly older term.log.* files)
for postfix installation or upgrade errors and add that information to
the bug.
** Changed
On Monday, January 30, 2017 09:33:36 PM you wrote:
> Which package was updated to fix this problem in Zesty? I could try to
> upgrade it only (I'm not ready to upgrade the whole distro).
postfix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
It would be nice if someone who is having this problem could test
3.1.4-2 or later on Zesty to see if the problem is fixed (I think it
is).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519331
Debian LTS uploaded essentially the same patch (we coordinated and reviewed
what each other had done). I'm not sure what to tell you about testing other
than that we have the change in production on a high volume system and haven't
seen any issues.
I'm no longer involved in Ubuntu
debian/changelog will need the revision number adjusted to whatever you
prefer and the bug number added.
** Also affects: pdns-recursor (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: pdns-recursor (Ubuntu)
Status: New => Invalid
** Changed in: pdns-recursor
*** This bug is a security vulnerability ***
Public security bug reported:
Note: We have this package running in production without any apparent
issues.
* SECURITY UPDATE:
* References
* CVE-2014-8601: PowerDNS Recursor before 3.6.2 does not limit delegation
chaining, which allows
It would have been trivial to look at test-postfix.py and see it still
starts with "#!/usr/bin/python". No it's not fixed. Please don't
randomly change bug status.
** Changed in: postfix (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: postfix (Ubuntu)
Status: Incomplete =>
Now that the upload I had pending is done, I did look into this a bit
further.
By adding the After=network-online.target override, when I look at the
output of systemd-analyze critical-chain with and without an equivalent
Wants= postfix is starting after network-online.target.
I didn't look
I've verified this works on the latest Debian upload and documented the
Debian (and Ubuntu) differences here:
https://git.launchpad.net/postfix/tree/debian/README.Debian?h=stable/v3.1=3d459e01fb9bc7dde304d4c505850e7552cc9491
(that's shipped in the package once you get the right version)
**
On Friday, January 06, 2017 05:30:12 PM you wrote:
> No, there is no trailing whitespace on any of the lines related to lmtp
> in either of my configuration files.
The regex is improved in 3.1.4-2, so please check again once you've upgraded
to that version.
Scott K
--
You received this bug
** Changed in: postfix (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654453
Title:
LMTP delivery to Dovecot stops working in 3.1.4-1
To manage
On Friday, January 06, 2017 01:04:21 AM you wrote:
What does the line for dovecot-lmtp in master.cf look like?
Scott K
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654453
Title:
LMTP delivery
On Wednesday, January 04, 2017 07:28:27 AM you wrote:
> Thanks. OOI, does it really hurt to have the After=systemd-
> resolved.service even for cases where it's not strictly needed?
Probably not. We've got a huge stack of changes queued, of which this is a
small part. I'll look at this for the
On Tuesday, January 03, 2017 08:43:15 PM you wrote:
> @Scott:
> https://git.launchpad.net/postfix/commit/?h=stable/v3.1=1a190cf17cc02
> looks rather complicated and also creates an unmanaged config file. Why
> not just always add those After= to the .service? If resolved is not
> enabled, then
On Tuesday, January 03, 2017 12:34:12 AM you wrote:
> Any idea when the fix will appear in updates for yakkety?
We plan on an upload to Debian in the next day or two. It'll follow into
Ubuntu shortly there after. A Yakkety SRU is work for someone involved in
Ubuntu to do, so no.
--
You
Looks like a upower bug:
dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 36944
package 'libupower-glib3:amd64':
'Recommends' field, reference to 'upower':
'>' is obsolete, use '>=' or '>>' instead
dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 36944
Now that upstream postfix supports splitting the various map types into
separate packages, fixing this bug is feasible. It'll be in the next
upload to Debian.
** Changed in: postfix (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a
** Changed in: postfix (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649453
Title:
systemd starts postfix before resolver
To manage notifications
I've pushed the fix to git for the Debian postfix package. This will be
in the next Debian upload that will get sync'ed into the Ubuntu
development release. Someone who is involved in Ubuntu will need to
work on a stable update after that happens if you want the fix in an
earlier release.
**
** Changed in: postfix (Ubuntu)
Importance: Undecided => High
** Changed in: postfix (Ubuntu)
Assignee: (unassigned) => Scott Kitterman (kitterman)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
On Tuesday, December 20, 2016 12:21:51 AM you wrote:
> This is probably also an issue on Debian, would you be willing to file a
> bug there? Against postfix specifically.
There's no need. I'm already looking at it.
Scott K
--
You received this bug notification because you are a member of
On Monday, December 19, 2016 08:58:24 AM you wrote:
> > This is about how we integrate postfix and networking in Debian (and
>
> thus Ubuntu). It's not an upstream issue. Removing the needs-upstream-
> report tag.
>
> By "upstream", I meant Debian. I'm not aware of a separate bug tag for
> that.
On Monday, December 12, 2016 07:58:42 AM you wrote:
> No, I wanted devel, I am such a diehard. The patch is already queued.
Thanks,
Scott K
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553928
Thanks. Actually you want postfix-users. Postfix-devel is for the core
postfix developers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553928
Title:
postfix-pgsql SSL connection to postgres
The mailing list is the only way.
What version of pgsql introduced PQconnectdb?
Neither of the Debian postfix maintainers use the pgsql maps, so it's
difficult for us to discuss changes with upstream. There is no Ubuntu
maintainer, per se.
--
You received this bug notification because you are
Someone who's still involved in Ubuntu development really ought to slap
a debian/changelog on this and upload it as an SRU.
** Changed in: pdns-recursor (Ubuntu)
Status: New => Triaged
** Changed in: pdns-recursor (Ubuntu)
Importance: Undecided => High
--
You received this bug
We've installed this and have it running in production with no issues.
I believe it's ready to go.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Tuesday, November 29, 2016 06:12:30 PM you wrote:
> Hi Scott,
>
> This looks good to me, although I did notice three changes that I'd
> expect to be documented in debian/changelog:
>
> debian/patches/CVE-2015-5144.patch is updated in a way that looks
> reasonable.
>
>
** Changed in: python-django (Ubuntu)
Status: New => In Progress
** Changed in: python-django (Ubuntu)
Importance: Undecided => Medium
** Also affects: python-django (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: python-django (Ubuntu Trusty)
Importance:
This is about how we integrate postfix and networking in Debian (and
thus Ubuntu). It's not an upstream issue. Removing the needs-upstream-
report tag.
** Tags removed: needs-upstream-report
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug is actually fixed in 3.1.3-4, so there's nothing to fix in the
package. Try:
sudo apt-get -f install
The should either finish the install successfully or force postfix to be
removed entirely after which a fresh install of 3.1.3-4 should succeed.
** Changed in: postfix (Ubuntu)
Public bug reported:
[Impact]
* Between Django 1.6.1 and 1.6.11 upstream did considerable non-
security bug fixing that it would be good to be able to take advantage
of. Since 1.6.11 is the terminal upstream release in the 1.6 branch,
this is one time request.
* Many projects are not ready
This is fixed in all supported releases.
** Changed in: python-geoip (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/378793
Title:
SystemError when
Note: ipaddr is no longer developed separately upstream. It was the
basis for the ipaddress module included in python3.3 and later. It
would be useful to see if this issue is present there as well and if it
is, forwarding it python upstream.
--
You received this bug notification because you
On Thursday, November 17, 2016 09:06:46 PM Flames_in_Paradise wrote:
...
> Debian is in transition-freeze for "Stretch" since Nov.5ŧh [2].
...
One correction:
This applies to library transitions. Partition Manager doesn't provide a
shared library, so this is not an issue. As I'm mentioned to
In the postfix service file (/lib/systemd/system/postfix.service), if
you change:
After=network.target
to:
Requires=network-online.target
After=network-online.target
does that solve your problem?
Note: this is not a general solution as it breaks setups that only
interface with localhost.
--
This is not the kind of change we would make as a distribution patch.
You should join the upstream postfix-users mailing list (subscription
instructions at http://www.postfix.org/lists.html ) and discuss your
idea and patch there.
** Changed in: postfix (Ubuntu)
Status: New => Opinion
--
This is fixed in Debian and Ubuntu Zakkety. Someone involved in Ubuntu
development will need to do an SRU to fix the earlier releases. You
need these two commits:
https://git.launchpad.net/postfix/commit/?h=stable/v3.1=6a19708c5e0dfd188df8898028a9977b811230f5
Not actually a dnspython bug:
Setting up python-support (1.0.15) ...
File "/usr/sbin/update-python-modules", line 52
print x
^
SyntaxError: invalid syntax
** Package changed: dnspython (Ubuntu) => python-support (Ubuntu)
--
You received this bug notification because you are a
This is not a package bug, but a local configuration issue. From the
provided dpkg log:
newaliases: warning: valid_hostname: numeric hostname: 04
newaliases: fatal: file /etc/postfix/main.cf: parameter mydomain: bad parameter
value: 04
dpkg: error processing package postfix (--configure):
FYI, 3.1.3-1 in Debian should fix this.
** Changed in: postfix (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595096
Title:
cannot create multi
Fix committed is the appropriate status. The fix has been uploaded to
Debian and will automatically sync into the next development release
once auto sync starts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Would you please make sure the Ubuntu Forums post is updated as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628258
Title:
unsupported dictionary type: pgsql
They are very close. In the column location of the so file, they are
different:
/usr/lib/postfix/dict_pgsql.so
/usr/lib/postfix/postfix-pgsql.so.1.0.1
The reason why your fix worked for you is you made a symlink that
provided the file in the location indicated by your dynamicmaps.cf. The
more
OK. That explains your problem. It should look like this now:
# Postfix dynamic maps configuration file.
#
#type location of .so fileopen function (mkmap func)
# =
tcp
What is in your /etc/postfix/dynamicmaps.cf file?
** Changed in: postfix (Ubuntu)
Importance: Undecided => High
** Changed in: postfix (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: postfix (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1627117
Title:
After systemd integration enabled, Postfix will no longer send
** Changed in: postfix (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595096
Title:
cannot create multi postfix instance by postmulti command
To
** Also affects: kcoreaddons (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: kcoreaddons (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[18:18:58] infinity: Kubuntu would like to get a security fix in
before release:
https://anonscm.debian.org/git/pkg-kde/frameworks/kcoreaddons.git/commit/?id=ab7258dd8a87668ba63c585a69f41f291254aa43
[18:19:26] ScottK: Security fixes welcome.
[18:19:39] K. Thanks.
--
You received this
This is a direct backport of the upstream commit and it applies cleanly.
I built the package in a clean trusty chroot and installed it on an up
to date Trusty system.
Kmail appears to be working correctly. I do not have a reproducer for
this, so I can't validate that the fix works (since it's
*** This bug is a security vulnerability ***
Public security bug reported:
Through a malicious URL that contained a quote character it
was possible to inject HTML code in KMail's plain text viewer.
Due to the parser used on the URL it was not possible to include
the equal sign (=) or a space
Since this is a pure python package with no binary content,
"Segmentation fault (core dumped)" means it's not a py3dns issue.
** Changed in: py3dns (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This was caused by the clamav daemon failing to start, so it's not
strictly clamsmtp's issue. Reassigning.
You should be able to manually start clamav and then finish the
installation with "sudo apt-get -f install".
** Package changed: clamsmtp (Ubuntu) => clamav (Ubuntu)
** Changed in: clamav
On Friday, September 09, 2016 06:21:34 AM you wrote:
> To be correct we would not pick up the fix automatically but on next
> merge as - while getting less - we still have a delta.
No, currently there is no delta. Also, please don't file a bug in Debian as I
believe this was fixed in postfix
** No longer affects: libyaml (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1591868
Title:
fwupd consuming 100% CPU
To manage notifications about this bug go to:
Google translates the error at the end of the Dpkg terminal log as:
An error occurred while processing the archive
/var/cache/apt/archives/postfix_3.1.0-3_i386.deb (--unpack): dpkg:
Subprocess new pre-installation script is a signal (broken pipe) terminated
After making sure the disk is not
Ack. Approved by ubuntu-backporters.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604209
Title:
apache2 in trusty-backports is vulnerable to CVE-2016-5387
To manage notifications about this bug
See the terminal log:
Running newaliases
newaliases: warning: valid_hostname: numeric hostname: 04
newaliases: fatal: file /etc/postfix/main.cf: parameter mydomain: bad parameter
value: 04
The hostname is invalid, so the error is correct. This is a local
configuration issue and not a packaging
I uploaded an updated backport. I agree that this should be SRU'ed for
the release pocket for the reasons you give, but I'm not really involved
in Ubuntu development any more, so hopefully someone else will pick that
up.
--
You received this bug notification because you are a member of Ubuntu
** Also affects: pypolicyd-spf (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: pypolicyd-spf (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: pypolicyd-spf (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: pypolicyd-spf
Normally in Ubuntu we mark the bug fix released if it's fixed in the
development version, but I'll open a task for 14.04 so this isn't lost.
** Changed in: opendmarc (Ubuntu)
Status: New => Fix Released
** Also affects: opendmarc (Ubuntu Trusty)
Importance: Undecided
Status: New
Public bug reported:
Instead of debian/patches/fallback_procotol_codes.patch, add netbase to
build depends for tests. It's priority minimal, so it'll be present on
a real system. In any case it misses an instance of
socket.getprotobyname, so even if it were the right solution, it's
incomplete.
** Changed in: amarok (Ubuntu)
Assignee: Michael Marley (mamarley) => Scott Kitterman (kitterman)
** Changed in: amarok (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Sunday, April 03, 2016 08:08:20 PM you wrote:
> 3.1, which I'll be uploading to xenial sometime around the 6th or so
> (after it ages in sid a little), has EAI compiled in, and migrates the
> chroot=- entries in master.cf to chroot=y. We don't explicitly enable
> smtputf8_enable yet (too big
I believe most of this is fixed once we upload postfix 3.1 to Debian. Not sure
when it will get to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1561975
Title:
default
I believe most of this is fixed once we upload postfix 3.1 to Debian. Not sure
when it will get to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561975
Title:
default configuration
** Changed in: unity-gtk-module (Ubuntu)
Assignee: Scott Kitterman (kitterman) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556277
Title:
When using unity, the diplom
Reviewing for sponsoring.
** Changed in: unity-gtk-module (Ubuntu)
Importance: Undecided => Medium
** Changed in: unity-gtk-module (Ubuntu)
Status: New => In Progress
** Changed in: unity-gtk-module (Ubuntu)
Assignee: (unassigned) => Scott Kitterman (kitterman)
--
You
On Friday, March 11, 2016 06:24:52 PM you wrote:
> Thanks Msd and Scott for helping with this.
>
> I presume this is fixed in Xenial, so have marked the bug as Fix
> Released but created a task to track this for 14.04.
That's correct. Trusty is the only release affected.
Scott K
--
You
On Friday, March 11, 2016 06:24:52 PM you wrote:
> Thanks Msd and Scott for helping with this.
>
> I presume this is fixed in Xenial, so have marked the bug as Fix
> Released but created a task to track this for 14.04.
That's correct. Trusty is the only release affected.
Scott K
--
You
I would recommend that you write to the postfix-users mailing list about this
as I suspect upstream knowledge will be needed to sort it. When you subscribe
you will get a welcome message that, among other things, gives you specifics
about what information to provide. Read it carefully and
I would recommend that you write to the postfix-users mailing list about this
as I suspect upstream knowledge will be needed to sort it. When you subscribe
you will get a welcome message that, among other things, gives you specifics
about what information to provide. Read it carefully and
I'm not sure what to tell you then as based on the original information in the
bug, postfix thinks it is supposed to relay that domain.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
I'm not sure what to tell you then as based on the original information in the
bug, postfix thinks it is supposed to relay that domain.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549388
Title:
On Thursday, February 25, 2016 08:55:40 AM you wrote:
> Hi,
>
> Here is the output of "postconf -n | grep relay" :
>
> relayhost =
>
> Thank you for your help !
Do you have any relay map files in /etc/postfix/? If you don't know, please
provide a list of the files present in that directory.
On Thursday, February 25, 2016 08:55:40 AM you wrote:
> Hi,
>
> Here is the output of "postconf -n | grep relay" :
>
> relayhost =
>
> Thank you for your help !
Do you have any relay map files in /etc/postfix/? If you don't know, please
provide a list of the files present in that directory.
** Changed in: postfix (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549388
Title:
In some rare cases Postfix connect to a wrong MX server
To manage
** Changed in: postfix (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1549388
Title:
In some rare cases Postfix connect to a wrong MX
What's the output of (run on the server that has postfix installed):
postconf -n | grep relay
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1549388
Title:
In some rare cases
What's the output of (run on the server that has postfix installed):
postconf -n | grep relay
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549388
Title:
In some rare cases Postfix connect to a
On Tuesday, February 23, 2016 02:58:40 AM you wrote:
> Public bug reported:
>
> 3.0.4-1ubuntu1 uses python 2.7 instead of 3.0 for the test suite. This
> should be corrected: migrate the test suite to python 3.0.
>
> ** Affects: postfix (Ubuntu)
> Importance: Undecided
> Status:
On Tuesday, February 23, 2016 02:58:40 AM you wrote:
> Public bug reported:
>
> 3.0.4-1ubuntu1 uses python 2.7 instead of 3.0 for the test suite. This
> should be corrected: migrate the test suite to python 3.0.
>
> ** Affects: postfix (Ubuntu)
> Importance: Undecided
> Status:
He also made a direct upload to Ubuntu.
** Changed in: postfix (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to postfix in Ubuntu.
https://bugs.launchpad.net/bugs/1531801
Title:
He also made a direct upload to Ubuntu.
** Changed in: postfix (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531801
Title:
Please update to
On Tuesday, January 26, 2016 06:11:48 PM you wrote:
> On Jan 26, 2016, at 05:49 PM, Scott Moser wrote:
> > mdadm Recommends -> postfix Recommends -> python
>
> Can we bump the latter down to a Suggests?
I don't think so, but the scripts are all pretty trivial. I'd just port it
and be done.
On Tuesday, January 26, 2016 06:11:48 PM you wrote:
> On Jan 26, 2016, at 05:49 PM, Scott Moser wrote:
> > mdadm Recommends -> postfix Recommends -> python
>
> Can we bump the latter down to a Suggests?
I don't think so, but the scripts are all pretty trivial. I'd just port it
and be done.
Changing /usr/bin/python3 to point to /usr/bin/python3.5 on a 15.10
system is guaranteed to break things. Don't do that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1518023
Title:
pip3 installs
Fix released in version 0.5.5 today.
** Changed in: dkimpy
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350141
Title:
dkim.sign crashs on python3
To
On Sunday, October 25, 2015 03:12:44 AM you wrote:
> Serge - your changes from comment #22 will break juju with lxc. juju
> will need to be modified to call systemctl add-wants multi-user.target
> lxc.service
If that's the case, this approach for a fix probably isn't appropriate for an
SRU.
--
On Sunday, October 25, 2015 03:12:44 AM you wrote:
> Serge - your changes from comment #22 will break juju with lxc. juju
> will need to be modified to call systemctl add-wants multi-user.target
> lxc.service
If that's the case, this approach for a fix probably isn't appropriate for an
SRU.
--
Note that the clamtk version is from a PPA: clamtk
5.19-1ppa1~inameiname1. Bugs in PPA packages should be addressed to the
PPA owner and not to the bug tracker which is for bugs in packages in
the Ubuntu archive.
** Changed in: clamtk (Ubuntu)
Status: New => Invalid
--
You received this
Hello Jonathan, or anyone else affected,
Accepted into vivid-proposed. The package will build now and be
available in a few hours in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use
Dear whoever subscribed the Debian Python Modules Team to this bug:
Please don't do such a thing again. If there is a bug that's also
present in Debian, please file a bug in the Debian BTS and then link it
to the Ubuntu bug.
--
You received this bug notification because you are a member of
Altering the envelope-from would solve this problem, but would
circumvent SPF as you suggest. What you might do is use your mail from
to send the mail and then use SRS (Sender Rewriting Service) to redirect
bounce messages to other domains, but I don't know of a simple solution
for setting that
Altering the envelope-from would solve this problem, but would
circumvent SPF as you suggest. What you might do is use your mail from
to send the mail and then use SRS (Sender Rewriting Service) to redirect
bounce messages to other domains, but I don't know of a simple solution
for setting that
The verification of the Stable Release Update for resiprocate has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for oslo.messaging has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
101 - 200 of 13616 matches
Mail list logo
